Re: Installation instructions for Debian/Ubuntu is wrong

2025-06-25 Thread Akshay Joshi
Apologies, ignore my previous email. Please provide the corrections for the page https://www.pgadmin.org/download/pgadmin-4-apt/ in plain text format here, and we will update the page accordingly. On Thu, Jun 26, 2025 at 11:49 AM Akshay Joshi wrote: > Hi Mario, > > You can raise a PR to https://

Re: Cant View/Edit Data

2025-06-25 Thread Aditya Toshniwal
Hi Tevor, It looks same as - https://github.com/pgadmin-org/pgadmin4/issues/8830 On Thu, Jun 26, 2025 at 11:53 AM Akshay Joshi wrote: > Hi Trevor, > > Could you please provide a screen recording, the version of pgAdmin 4 > you're using, and indicate whether it's running in Desktop or Server mod

Re: Installation instructions for Debian/Ubuntu is wrong

2025-06-25 Thread Akshay Joshi
Hi Mario, You can raise a PR to https://github.com/pgadmin-org/pgadmin4 On Wed, Jun 25, 2025 at 9:53 PM Mario Splivalo wrote: > Hi, all. > > Newer versions of Ubuntu/Debian strongly recommend using .soruces > (deb822) over .list files for configuring package repositories. > > Also, the document

Re: Cant View/Edit Data

2025-06-25 Thread Akshay Joshi
Hi Trevor, Could you please provide a screen recording, the version of pgAdmin 4 you're using, and indicate whether it's running in Desktop or Server mode? On Wed, Jun 25, 2025 at 8:48 PM Trevor Smith wrote: > [image: image.png] > -- > Hello, > > I am encountering an

Installation instructions for Debian/Ubuntu is wrong

2025-06-25 Thread Mario Splivalo
Hi, all. Newer versions of Ubuntu/Debian strongly recommend using .soruces (deb822) over .list files for configuring package repositories. Also, the documentation puts the pgadmin repository key file inside /usr/share/keyrings/ directory, which should not happen (the proper place for such fi

Cant View/Edit Data

2025-06-25 Thread Trevor Smith
[image: image.png] -- Hello, I am encountering an issue where I cannot view or edit data. Nothing opens when i click All Rows, and there are no error messages. I have tried this across multiple databases and tables, but the problem persists. Without any error messages o