[p4] anybody use p4v on this list?

Sat Apr 26 01:05:14 PDT 2008

MY problem - was that I was running 2007.2 server, and 2007.3 clients.

Once I updated the server to 2007.3, problems went away.  I am now in  
login ticket goodness!

A thanks to all who've helped or offered suggestions - and I'll give  
now my configuration:

p4d PPC Darwin 2007.3 (an old iMac "lamp")
p4v 2007.3 Linux (x86 32 bit)
p4v 2007.3 WinXP (x86 32 bit)
p4v 2007.3 Mac OS 10.5 (x86 intel)

All of the above behave properly now.

It seems a very frequent occurrence for a typical software house -  
where a slightly out of date server, and newer clients are downloaded  
(as new machines are requisitioned or new hires are brought on).  I  
wonder if I had searched perforce knowledgebase before coming to this  
list, would I have found this to be a common issue that is addressed  
there?  Well, I just did such a search and found no such information.   
I suppose to email their tech support with my issue and resolution is  
helpful.

-jon

On Apr 26, 2008, at 1:52 AM, Zoltan Grose wrote:

> I've never seen the UI prompt for a password more than once every 12
> hours (the ticket expiration timer).
>
> I'm using Rev. Perforce Visual Client/MACOSX104X86/2007.3/149519 at
> the moment.
>
> My only variable in .bash_profile is P4PORT (set to 1666) since p4
> doesn't seem to try the default by default. =)
>
> -zoltan
>
> On Apr 25, 2008, at 11:23 PM, Jon Gamble wrote:
>
>> I get repeated credentials dialogs, regardless of server security
>> level, using p4v on all three platforms (linux, mac, win).  p4  
>> command
>> line client works great, always has.  Funny that p4v is just a p4
>> wrapper right?  I haven't tried p4win, it's such a pile last time I
>> looked, I don't even want to download it for debugging's sake.
>>
>> Well, I have tried remove .p4tickets directory and doing a fresh  
>> login
>> -a, I've removed P4XXXX environment variables (especially P4PASSWD)
>> exported by .bashrc (don't know why this would help anyways those
>> environment variables shouldn't affect processes launched outside the
>> terminal (by say gdm) on *NIXes eh, or those launched by the window
>> manager on mac eh?)
>>
>> For those who have p4v working, I am talking specifically about p4v
>> 2007.3 release.  You have this working?  I have my doubts!  :)
>>
>> I suppose I will call perforce Monday morning to see if they've heard
>> of this issue.  Maybe they have a build to fix it in the works.  I
>> will let all of you know what I hear.
>>
>> -jon
>>
>> On Apr 23, 2008, at 2:04 PM, Eric.Walker at smsc.com wrote:
>>
>>>
>>> We are only on tickets also. I still see the disconnection in the
>>> p4v gui from time to time.  I have a user who only uses the gui to
>>> login to perforce. He gets the same issue.
>>>
>>> Eric B. Walker
>>>
>>>
>>>
>>>
>>> Matthew Janulewicz <MJanulewicz at greendotcorp.com>
>>> 04/23/08 12:00 PM
>>>
>>> To
>>> "'Jamison, Shawn'" <sjamison at ciena.com>, Brad Holt <brad.holt at autodesk.com
>>>> , "Jeff A. Bowles" <jab at pobox.com>, Jon Gamble
>>> <jonbgamble at gmail.com>, Eric Walker/SMSC at SMSC
>>> cc
>>> "perforce-user at perforce.com" <perforce-user at perforce.com>
>>> Subject
>>> RE: [p4] anybody use p4v on this list?
>>>
>>>
>>>
>>>
>>>
>>> It's my understanding that you should use tickets OR P4PASSWD, but
>>> not both. Nobody here has P4PASSWD set, we're all tickets, all the
>>> time and have no problems with P4V. Having two different (possible)
>>> authentication methods seems like it's asking for trouble.
>>>
>>>
>>> -Matt
>>>
>>>
>>> -----Original Message-----
>>> From: perforce-user-bounces at perforce.com [mailto:perforce-user-bounces at perforce.com
>>> ] On Behalf Of Jamison, Shawn
>>> Sent: Wednesday, April 23, 2008 10:58 AM
>>> To: Brad Holt; Jeff A. Bowles; Jon Gamble; Eric.Walker at smsc.com
>>> Cc: perforce-user at perforce.com
>>> Subject: Re: [p4] anybody use p4v on this list?
>>>
>>> The issues was had was a conflict between the P4PASSWD environment
>>> variable and the .p4ticket file and the way P4V interacted with our
>>> environment and those variables.
>>>
>>> There is a lot that can be going on to cause this.  If the P4PASSWD
>>> is
>>> not set correctly or you are setting your p4passwd in
>>> your .bash_profile
>>> and you have an old p4tickets file.
>>>
>>> To much to list every possible solution.
>>>
>>> Try the following:
>>>
>>> Try cleaning out your user environment and get rid of ALL the P4*
>>> entries.
>>>
>>> Delete your .p4tickets file
>>>
>>> Try using p4 login -a then start the p4v client with p4v & and see  
>>> if
>>> that helps.
>>>
>>> Good luck!
>>> -Shawn Jamison>
>>> Ciena Corp.
>>> Perforce Admin
>>>
>>> -----Original Message-----
>>> From: Brad Holt [mailto:brad.holt at autodesk.com]
>>> Sent: Wednesday, April 23, 2008 12:48 PM
>>> To: Jeff A. Bowles; Jon Gamble; Jamison, Shawn; Eric.Walker at smsc.com
>>> Cc: perforce-user at perforce.com
>>> Subject: RE: [p4] anybody use p4v on this list?
>>>
>>> Let us know what you find.
>>>
>>> -----Original Message-----
>>> From: perforce-user-bounces at perforce.com
>>> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff A.
>>> Bowles
>>> Sent: Wednesday, April 23, 2008 9:41 AM
>>> To: Jon Gamble; Jamison, Shawn; Eric.Walker at smsc.com
>>> Cc: perforce-user at perforce.com
>>> Subject: Re: [p4] anybody use p4v on this list?
>>>
>>> I think that I would ask Tech Support this question.  Something's
>>> going
>>> on, and this forum is good for the question "is anyone else seeing
>>> this
>>> behavior?" but lousy for "can someone fix this for me" because,  
>>> well,
>>> it's a Perforce binary that we cannot directly change.
>>> Get to support. There are very good questions in this thread  
>>> ("delete
>>> that tickets file / directory and try again") and Support will lead
>>> you
>>> to some other questions. Make sure that you're able to answer
>>> questions
>>> about your local DNS server and network topology; it's possible
>>> you'll
>>> have something like that to debug.
>>>
>>> Call them. It'll be more fruitful.
>>>
>>> -Jeff Bowles
>>>
>>>
>>> On Tue, Apr 22, 2008 at 9:52 PM, Jon Gamble <jonbgamble at gmail.com>
>>> wrote:
>>>
>>>> Successfully?  Does it work?
>>>>
>>>> I'm trying to find out if the behavior that me and a collaborator  
>>>> in
>>>> California are seeing is unique to our situation, because if it is
>>>> not, then p4v does not work.  Surely this can't be the case.
>>> Perforce
>>>
>>>> has always been quality software in my estimation.
>>>>
>>>> The problem is that p4v client continually demands authentication
>>> over
>>>
>>>> and over for every tiny action, regardless of the server's
>>>> authentication counter/model (password, ticket, etc).  Why does  
>>>> this
>>>> only happen to us?
>>>>
>>>> -jon
>>>> _______________________________________________
>>>> perforce-user mailing list  -  perforce-user at perforce.com
>>>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>>>
>>>
>>>
>>>
>>> --
>>> ---
>>> Jeff Bowles - jeff.a.bowles at gmail.com
>>> _______________________________________________
>>> perforce-user mailing list  -  perforce-user at perforce.com
>>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>>
>>> _______________________________________________
>>> perforce-user mailing list  -  perforce-user at perforce.com
>>> http://maillist.perforce.com/mailman/listinfo/perforce-user
>>>
>>
>> _______________________________________________
>> perforce-user mailing list  -  perforce-user at perforce.com
>> http://maillist.perforce.com/mailman/listinfo/perforce-user
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user