Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,842
    • Issues 1,842
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 86
    • Merge requests 86
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

An update will be applied May 24th, between 12PM and 1PM EDT (UTC -400). The site may be slow during that time.

  • ParaView
  • ParaViewParaView
  • Issues
  • #7189

Closed
Open
Created Jun 12, 2008 by Kitware Robot@kwrobotOwner

Client/server connect ID flag is not random in Linux

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


The client/server connect ID flag is not random in Linux once again. As a speculation, it is probably being passed from run to run, as are the other parameters. This was probably broken due to resolving bug number 5487. This flag MUST be random.

To replicate, open ParaView, File/ Connect. Select a server. Notice the popup/ connect ID flag entry. It will be the same every time.

This is a show stopper for the 3.4 release.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking