[MacPorts] #27068: pidgin runs in background, can't see it in an X window

[MacPorts]

#27068: pidgin runs in background, can't see it in an X window
-------------------------------+--------------------------------------------
 Reporter:  tixetsal@…         |       Owner:  nefar@…            
     Type:  submission         |      Status:  new                
 Priority:  Low                |   Milestone:                     
Component:  ports              |     Version:  1.9.1              
 Keywords:  pidgin X11 window  |        Port:  pidgin             
-------------------------------+--------------------------------------------
Changes (by ryandesign@…):

  * owner:  macports-tickets@… => nefar@…
  * milestone:  MacPorts Future =>


Old description:

> I am running Snow Leopard, and I can't find a prebuilt binary of pidgin,
> so I settled on this "package manager."  I am new to MacPorts, so it is
> possible that I am missing something simple.
>
> I installed MacPorts from a binary.  I installed pidgin.  Pidgin failed
> b/c of an issue building db46.  I installed the Java Developers Package,
> and I was able to install pidgin.
>
> I setup pidgin with all of my IM accounts, and it was working acceptably.
> The last time that I used it, I clicked on the little red X icon (in OS
> X) to close the X window.  This doesn't stop pidgin from running in the
> background, so I killed the process.
>
> The next time that I started pidgin, I got the usual (i saw this when the
> X window was visible) gripe:
>
> Dynamic session lookup supported but failed: launchd did not provide a
> socket path, verify that org.freedesktop.dbus-session.plist is loaded!
>
> It fires up the X11 (OS X) app, but it never creates a pidgin X window.
> If I
>
> pro:~ shaun$ ps aux | grep -i 'pidgin'
> shaun      443   0.0  0.0  2470384    364 s000  S+    7:25PM   0:00.00
> pidgin
> shaun      442   0.0  0.0  2470384    376 s000  S+    7:25PM   0:00.00
> pidgin
> shaun      438   0.0  0.5  2472160  22484 s000  S+    7:25PM   0:00.34
> pidgin
> shaun      444   0.0  0.0  2470868    400 s000  S+    7:25PM   0:00.00
> pidgin
>
> I can see that there are 4 processes running related to pidgin, but there
> is no way to view the X window.
>
> If I spawn pidgin as root, I can again see the X window which walks you
> through account configuration, so I think that the solution is probably
> pretty simple and basic.
>
> Can anyone please advise?  I am not really a "mac guy," and I don't know
> much at all about MacPorts.
>
> TIA

New description:

 I am running Snow Leopard, and I can't find a prebuilt binary of pidgin,
 so I settled on this "package manager."  I am new to MacPorts, so it is
 possible that I am missing something simple.

 I installed MacPorts from a binary.  I installed pidgin.  Pidgin failed
 b/c of an issue building db46.  I installed the Java Developers Package,
 and I was able to install pidgin.

 I setup pidgin with all of my IM accounts, and it was working acceptably.
 The last time that I used it, I clicked on the little red X icon (in OS X)
 to close the X window.  This doesn't stop pidgin from running in the
 background, so I killed the process.

 The next time that I started pidgin, I got the usual (i saw this when the
 X window was visible) gripe:

 {{{
 Dynamic session lookup supported but failed: launchd did not provide a
 socket path, verify that org.freedesktop.dbus-session.plist is loaded!
 }}}

 It fires up the X11 (OS X) app, but it never creates a pidgin X window.
 If I

 {{{
 pro:~ shaun$ ps aux | grep -i 'pidgin'
 shaun      443   0.0  0.0  2470384    364 s000  S+    7:25PM   0:00.00
 pidgin
 shaun      442   0.0  0.0  2470384    376 s000  S+    7:25PM   0:00.00
 pidgin
 shaun      438   0.0  0.5  2472160  22484 s000  S+    7:25PM   0:00.34
 pidgin
 shaun      444   0.0  0.0  2470868    400 s000  S+    7:25PM   0:00.00
 pidgin
 }}}

 I can see that there are 4 processes running related to pidgin, but there
 is no way to view the X window.

 If I spawn pidgin as root, I can again see the X window which walks you
 through account configuration, so I think that the solution is probably
 pretty simple and basic.

 Can anyone please advise?  I am not really a "mac guy," and I don't know
 much at all about MacPorts.

 TIA

--

-- 
Ticket URL: <https://trac.macports.org/ticket/27068#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS