From 5064ba3f1dd290ca37c1435eeb349274a6bea585 Mon Sep 17 00:00:00 2001 From: Adam Honse Date: Wed, 24 Jun 2026 15:02:20 -0500 Subject: [PATCH] Update warning messages and remove references to help.openrgb.org. --- ResourceManager.cpp | 30 +++++++++++++----------------- 1 file changed, 13 insertions(+), 17 deletions(-) diff --git a/ResourceManager.cpp b/ResourceManager.cpp index b5641fa0d..3ab7a2e2a 100644 --- a/ResourceManager.cpp +++ b/ResourceManager.cpp @@ -35,36 +35,32 @@ #endif /*---------------------------------------------------------*\ -| Translation Strings | +| Warning Dialog Strings | \*---------------------------------------------------------*/ const char* I2C_ERR_WIN = QT_TRANSLATE_NOOP("ResourceManager", - "

Some internal devices may not be detected:

" - "

One or more I2C or SMBus interfaces failed to initialize.

" - "

RGB DRAM modules, some motherboards' onboard RGB lighting, and RGB Graphics Cards, will not be available in OpenRGB without I2C or SMBus.

" - "

How to fix this:

" + "

Warning:

" + "

One or more I2C/SMBus interfaces failed to initialize.

" + "

Depending on which interfaces failed to initialize, some RGB DRAM modules, some motherboards' onboard RGB lighting, and RGB graphics cards may not be available in OpenRGB.

" "

On Windows, this is usually caused by a failure to load the PawnIO driver.

" - "

You must first install PawnIO, then you must OpenRGB as administrator in order to access these devices.

" - "

See help.openrgb.org for additional troubleshooting steps if you keep seeing this message.

" - "

If you are not using internal RGB on a desktop this message is not important to you.

"); + "

For OpenRGB to access these devices, you must install PawnIO from https://pawnio.eu and run OpenRGB as administrator or as a system service.

" + "

If you are not using any of the devices listed above, you can safely ignore this message.

"); const char* I2C_ERR_LINUX = QT_TRANSLATE_NOOP("ResourceManager", - "

Some internal devices may not be detected:

" - "

One or more I2C or SMBus interfaces failed to initialize.

" - "

RGB DRAM modules, some motherboards' onboard RGB lighting, and RGB Graphics Cards, will not be available in OpenRGB without I2C or SMBus.

" - "

How to fix this:

" + "

Warning:

" + "

One or more I2C/SMBus interfaces failed to initialize.

" + "

Depending on which interfaces failed to initialize, some RGB DRAM modules, some motherboards' onboard RGB lighting, and RGB graphics cards may not be available in OpenRGB.

" "

On Linux, this is usually because the i2c-dev module is not loaded.

" - "

You must load the i2c-dev module along with the correct i2c driver for your motherboard. " + "

For OpenRGB to access these devices, you must load the i2c-dev module along with the correct I2C driver module for your motherboard. " "This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.

" - "

See help.openrgb.org for additional troubleshooting steps if you keep seeing this message.

" - "

If you are not using internal RGB on a desktop this message is not important to you.

"); + "

If you are not using any of the devices listed above, you can safely ignore this message.

"); const char* UDEV_MISSING = QT_TRANSLATE_NOOP("ResourceManager", - "

WARNING:

" + "

Warning:

" "

The OpenRGB udev rules are not installed.

" "

Most devices will not be available unless running OpenRGB as root.

" "

If using AppImage, Flatpak, or self-compiled versions of OpenRGB you must install the udev rules manually

" "

See https://openrgb.org/udev to install the udev rules manually

"); const char* UDEV_MUTLI = QT_TRANSLATE_NOOP("ResourceManager", - "

WARNING:

" + "

Warning:

" "

Multiple OpenRGB udev rules are installed.

" "

The udev rules file 60-openrgb.rules is installed in both /etc/udev/rules.d and /usr/lib/udev/rules.d.

" "

Multiple udev rules files can conflict, it is recommended to remove one of them.

");