I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.
Installation Method
Git Clone
Open WebUI Version
v0.6.41
Ollama Version (if applicable)
N/A
Operating System
Linux
Browser (if applicable)
Edge
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
When hovering on a user name in the admin section, I would expect that the profile card corresponds to the it.
It works well with the default display of the users view (sorted by user creation date):
Actual Behavior
But there is a mismatch when, for example, sorting users by last activity:
It's like the profile card in the 3rd position (which corresponds to my profile in the default view) stays at the same location.
Steps to Reproduce
Just change the sorting order of the users and check the match with the profile card.
Logs & Screenshots
See above.
Additional Information
Anybody else being able to reproduce?
Originally created by @pierrelouisbescond on GitHub (Dec 19, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20046
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
- [x] I am using the latest version of Open WebUI.
### Installation Method
Git Clone
### Open WebUI Version
v0.6.41
### Ollama Version (if applicable)
N/A
### Operating System
Linux
### Browser (if applicable)
Edge
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
When hovering on a user name in the admin section, I would expect that the profile card corresponds to the it.
It works well with the default display of the users view (sorted by user creation date):
<img width="1060" height="191" alt="Image" src="https://github.com/user-attachments/assets/bb6d8da3-fd40-4df5-af79-9a8789d086c5" />
### Actual Behavior
But there is a mismatch when, for example, sorting users by last activity:
<img width="1060" height="191" alt="Image" src="https://github.com/user-attachments/assets/a2610a27-e0a1-4cc7-a438-f3aad7025776" />
It's like the profile card in the 3rd position (which corresponds to my profile in the default view) stays at the same location.
### Steps to Reproduce
Just change the sorting order of the users and check the match with the profile card.
### Logs & Screenshots
See above.
### Additional Information
Anybody else being able to reproduce?
GiteaMirror
added the bug label 2026-05-05 21:30:46 -05:00
If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
If you found a solution in any of these issues, please share it here to help others
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
<!-- gh-comment-id:3674900765 -->
@owui-terminator[bot] commented on GitHub (Dec 19, 2025):
🔍 **Similar Issues Found**
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
1. [#19877](https://github.com/open-webui/open-webui/issues/19877) **issue:**
*by dotmobo • Dec 11, 2025 • `bug`*
2. [#19861](https://github.com/open-webui/open-webui/issues/19861) **issue:**
*by QuitHub • Dec 10, 2025 • `bug`*
3. [#19864](https://github.com/open-webui/open-webui/issues/19864) **issue:**
*by Haervwe • Dec 10, 2025 • `bug`*
4. [#20019](https://github.com/open-webui/open-webui/issues/20019) **issue:**
*by j63440490 • Dec 17, 2025 • `bug`*
5. [#19777](https://github.com/open-webui/open-webui/issues/19777) **issue:**
*by Yaute7 • Dec 05, 2025 • `bug`*
<details>
<summary>Show 5 more related issues</summary>
6. [#19563](https://github.com/open-webui/open-webui/issues/19563) **issue:**
*by naruto7g • Nov 28, 2025 • `bug`*
7. [#19211](https://github.com/open-webui/open-webui/issues/19211) **issue:**
*by Byrnes9 • Nov 16, 2025 • `bug`*
8. [#14440](https://github.com/open-webui/open-webui/issues/14440) **issue:**
*by ehsan8203 • May 28, 2025 • `bug`*
9. [#14650](https://github.com/open-webui/open-webui/issues/14650) **issue:**
*by lilosti • Jun 04, 2025 • `bug`*
10. [#16959](https://github.com/open-webui/open-webui/issues/16959) **issue:**
*by Te-eMster • Aug 27, 2025 • `bug`*
</details>
---
💡 **Tips:**
- If this is a duplicate, please consider closing this issue and adding any additional details to the existing one
- If you found a solution in any of these issues, please share it here to help others
*This comment was generated automatically by a bot.* Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@pr-validator-bot commented on GitHub (Dec 19, 2025):
⚠️ Invalid Issue Title
Hey @pierrelouisbescond, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
<!-- gh-comment-id:3674901129 -->
@pr-validator-bot commented on GitHub (Dec 19, 2025):
# ⚠️ Invalid Issue Title
Hey @pierrelouisbescond, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @pierrelouisbescond on GitHub (Dec 19, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/20046
Check Existing Issues
Installation Method
Git Clone
Open WebUI Version
v0.6.41
Ollama Version (if applicable)
N/A
Operating System
Linux
Browser (if applicable)
Edge
Confirmation
README.md.Expected Behavior
When hovering on a user name in the admin section, I would expect that the profile card corresponds to the it.
It works well with the default display of the users view (sorted by user creation date):
Actual Behavior
But there is a mismatch when, for example, sorting users by last activity:
It's like the profile card in the 3rd position (which corresponds to my profile in the default view) stays at the same location.
Steps to Reproduce
Just change the sorting order of the users and check the match with the profile card.
Logs & Screenshots
See above.
Additional Information
Anybody else being able to reproduce?
@owui-terminator[bot] commented on GitHub (Dec 19, 2025):
🔍 Similar Issues Found
I found some existing issues that might be related to this one. Please check if any of these are duplicates or contain helpful solutions:
#19877 issue:
by dotmobo • Dec 11, 2025 •
bug#19861 issue:
by QuitHub • Dec 10, 2025 •
bug#19864 issue:
by Haervwe • Dec 10, 2025 •
bug#20019 issue:
by j63440490 • Dec 17, 2025 •
bug#19777 issue:
by Yaute7 • Dec 05, 2025 •
bugShow 5 more related issues
#19563 issue:
by naruto7g • Nov 28, 2025 •
bug#19211 issue:
by Byrnes9 • Nov 16, 2025 •
bug#14440 issue:
by ehsan8203 • May 28, 2025 •
bug#14650 issue:
by lilosti • Jun 04, 2025 •
bug#16959 issue:
by Te-eMster • Aug 27, 2025 •
bug💡 Tips:
This comment was generated automatically by a bot. Please react with a 👍 if this comment was helpful, or a 👎 if it was not.
@pr-validator-bot commented on GitHub (Dec 19, 2025):
⚠️ Invalid Issue Title
Hey @pierrelouisbescond, please provide a descriptive title for your issue. Titles that are empty, very short (under 10 characters), or generic (like "issue:") make it difficult for volunteer contributors to understand and triage issues.
Please update the title to reflect the content of your issue.
@Classic298 commented on GitHub (Dec 19, 2025):
This is fixed in dev already, thanks