Skip to content

Added memory page - #136

Closed
garakangas wants to merge 1 commit into
linuxmint:masterfrom
garakangas:memory-page
Closed

garakangas wants to merge 1 commit into
linuxmint:masterfrom
garakangas:memory-page

Conversation

@garakangas

Copy link
Copy Markdown

Added a memory page which matches the output given by the inxi -mxxx command. This was requested in #105.

Added a memory page which matches the output given by the inxi -mxxx command. This was requested in linuxmint#105.
@Sturm0

Sturm0 commented Sep 7, 2026 •

Copy link
Copy Markdown

This is exactly what I want.
Is there any reason why this hasn't been merged?
It's particularly useful if someone wants to upgrade their RAM and needs to know what type of RAM they have: DDR3/DDR4/DDR5, DIMM/SO-DIMM, available slots etc.
I have a close acquaintance who's in that situation, and it would be great to have a graphical way to check this, since a novice user might not be comfortable using the terminal to check these things.

@Sturm0

Sturm0 commented Sep 7, 2026 •

Copy link
Copy Markdown
imagen

I cloned the memory-page branch on my Linux Mint 22.3 system, compiled and installed it, but the RAM information appears empty.

Did I do something wrong?

I used these commands:

git clone -b memory-page https://github.com/garakangas/mintreport
cd mintreport/
dpkg-buildpackage --no-sign
cd ..
sudo dpkg -i mintreport*.deb

When I run it from the terminal, I get this:

federico@federico-a320:~/Descargas$ mintreport
/usr/lib/linuxmint/mintreport/app.py:329: DeprecationWarning: Gtk.ImageMenuItem.set_image is deprecated
  item.set_image(image)
Checking 045_xappstatusapplet-missing
Checking 050_install-media-codecs
Checking 060_timeshift-no-setup
Checking 070_new-release
Checking 071_new_major_release
Checking 080_release-eol
Checking 100_usrmerge-not-done
Checking 200_xappstatusapplet-blocked
Checking 500_install-language-packs
Checking 900_drivers
Exception in thread Thread-16 (load):
Traceback (most recent call last):
  File "/usr/lib/python3.12/threading.py", line 1073, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.12/threading.py", line 1010, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/linuxmint/mintreport/memory.py", line 187, in load
    info_memory_devices.append([_('Manufacturer'), device['manufacturer']])
                                                   ~~~~~~^^^^^^^^^^^^^^^^
KeyError: 'manufacturer'

If it helps at all:

federico@federico-a320:~/Descargas$ LANG=C inxi -mxxxc0
Memory:
  System RAM: total: 16 GiB available: 15.54 GiB used: 8.09 GiB (52.1%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB note: check slots: 2 modules: 2 EC: None
    max-module-size: 64 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2133 MT/s volts: 1 note: check
    width (bits): data: 64 total: 64 manufacturer: N/A
    part-no: W641GU42J9266NC serial: N/A
  Device-2: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 2133 MT/s volts: 1 note: check
    width (bits): data: 64 total: 64 manufacturer: TeamGroup part-no: UD4-2133
    serial: 0104251A

@clefebvre

Copy link
Copy Markdown
Member

I think the page is too technical. A little bit like the Sensors page I added earlier this year. It shows too much data and dilutes the valuable info so it's not easy to read and doesn't add much value compared to CLI.

Sensors moved to monitoring graphs in superlight. RAM usage/available belongs there as well.

RAM brand, speed, number of sticks and things which matter to people could be shown. There wouldn't be enough for a whole page, so maybe it belongs to the first page, or maybe we can show more details about the CPU cores also, and put that together somewhere.

@clefebvre clefebvre closed this Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants