secondlife / secondlife/viewer

Messages sent using a third-party viewer disappear in the SecondLife viewer.

Open
#3,433 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug linux team:viewer
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Description

I often switch between third-party and Linden viewers for testing or operational issues, but sometimes messages sent with a third-party viewer don't appear in the Linden viewer, or messages sent with a Linden viewer don't appear in the third-party viewer.
This often happens when switching between Windows and Linux.
I found that the cause is that the files recording the chat history are created separately.

For example, let's say there is a user called "Example.Account".

In that case, the following files may be created:

  1. Example.Account
  2. Example.account
  3. example.Account
  4. example.account
  5. Example Account
  6. Example account
  7. example Account
  8. example account

These files are treated as completely different files on Linux, so in the worst case scenario, eight different files may be created.

Is it possible to make the message appear even if any of these files exist?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are identified in the issue. Start by locating the viewer's chat-history file naming and lookup logic, then reproduce the problem across Windows and Linux with the listed name variants. Done means messages are found consistently when an equivalent history file already exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.