Maintenance signature request for PaperCut Hive v2.1.0
Incident Properties
Question
Hi,
Please find attached version 2.1.0 of the PaperCut Hive application for a maintenance signature.
The changes are described as follows:
- Added support for pull print
Kind regards
REQUEST MAINTENANCE SIGNATURE RICOHSOP 1.3.0.634
Incident Properties
Question
Hi RiDP,
Please help to create a maintenance signature for the attached version (1.3.0.634)
This version includes fixing the bug below:
Intermittent "Please Wait" screen when logging into Ricoh Devices
Regards
Printix: Certification installation reboot failure
Incident Properties
Question
This is in direct connection to a certification request (https://ricoh-ridp.com/ridp/support-system/incident/5676 assigned to Mark Stiller), The installation of our product seems to be failing on a step that reboots the machine (the 3500 in question in that ticket).
Attached to this ticket are rxop debug logs and the TAR logs from the machine in question.
A. A quick example of a failed reboot request:
In "deploy logs 12 29.zip\rxinst\10.77.2.159\log\", line 11916 -> 11946 is a failed reboot attempt (I removed some content for brevity to include inline in this update the log of course has the full content):
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:34] DEBUG - Reboot SOP Device -- entered.
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:43] INFO - ---- DmServletResponse ----
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:43] INFO - url: https://10.77.2.159:443/DH/devicemanagement
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:43] DEBUG - ip: 10.77.2.159
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:43] DEBUG - name: /DH/devicemanagement
.....
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:43] INFO - status: 200
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:43] INFO - rawData: <?xml version="1.0" encoding="UTF-8" ?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><tns:terminateSessionResponse xmlns:tns="http://www.ricoh.co.jp/xmlns/soap/rdh/devicemanagement"><returnValue></returnValue></tns:terminateSessionResponse></s:Body></s:Envelope>
...
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:43] INFO - rawData: <?xml version="1.0" encoding="UTF-8" ?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><tns:rebootDeviceResponse xmlns:tns="http://www.ricoh.co.jp/xmlns/soap/rdh/devicemanagement"><returnValue>REJECTED</returnValue></tns:rebootDeviceResponse></s:Body></s:Envelope>
...
[rxinst-10.77.2.159-772110021][2025-12-29 14:54:43] ERROR - reboot -- STATE_REBOOT_ERROR Failed to reboot device.2. I couldn't tell if there was anything useful in the rxsp log.
3. Another reboot attempt in the rxinst log failed for the same reason.
B. I have tried to correlate info 2025-12-29 14:54:43 in the decoded tar logs, but I'm having trouble determining an exact correspondence. But the time in the rxinst log is a definitive place to start.
In our rxop installer, the reboot call occurs after our printix packages are installed (as has generally been the case, there haven't been any changes in the sequence of events for awhile.
C. Here are some handpicked lines from the rxinst log that show our app being installed, and uninstalled, successfully:
Line 6475: [rxinst-10.77.2.159-1934145297][2025-12-29 14:11:06] INFO - uninstall -- STATE_UNINSTALL_CONFIRM SUCCESSFUL 1667825665
Line 11328: [rxinst-10.77.2.159-158726944][2025-12-29 14:54:10] INFO - install -- STATE_INSTALL_CONFIRM SUCCESSFUL 1667825665
Line 18430: [rxinst-10.77.2.159-711197454][2025-12-29 15:13:19] INFO - uninstall -- STATE_UNINSTALL_CONFIRM SUCCESSFUL 1667825665
Line 23283: [rxinst-10.77.2.159-2097623497][2025-12-29 15:31:22] INFO - install -- STATE_INSTALL_CONFIRM SUCCESSFUL 1667825665
The reboot generally occurs after the program installation, and there is a 30 second pause period after setting the sp modes.
D. So the main ask is the cause of the reboot failures. Any advice you can give would be appreciated.
REQUEST MAINTENANCE SIGNATURE RICOHSOP 1.3.0.631
Incident Properties
Question
Hi RiDP,
Please help to create a maintenance signature for the attached version (1.3.0.631)
This version includes fixing the bug below:
Scan orientation to 90 degrees on smaller devices
Regards
REQUEST MAINTENANCE SIGNATURE RICOHSOP 2025.2.0.920
Incident Properties
Question
Hi RiDP,
Please help to create a maintenance signature for the attached version (2025.2.0.920)
This version includes fixing the bugs below:
Device Becomes Unresponsive When Users Don’t Log Out
Erase Centre/Border Settings Cannot Be Disabled Globally - Incorrect scan defaults
Regards
Adding certificates to trust store
Incident Properties
Question
Hi,
We are encountering an SSL/TLS handshaking failure when the embedded webview attempts to connect to our service because the service's Root Certificate Authority (CA) is not present in the device's default system trust store.
We need to understand the supported method for establishing trust for this specific connection.
- Trust Store Access:
- Is there a documented procedure or administrative tool available to permanently add a custom Root CA certificate to the device's system-wide default trust store?
- If modification is not possible, is the trust store populated exclusively by CAs included in the device firmware, or is it pulled from an external list?
- Webview/Browser Trust Configuration:
- If system-wide modification is prohibited, is there a mechanism (e.g., a specific API, a configuration file, or an application-level setting) that allows an embedded application or webview to temporarily trust a specific certificate chain?
- For example, is there an equivalent to the Android Network Security Configuration or a Ricoh-specific API method to pass an explicit set of trusted anchors to the webview instance?
Any documentation, tool names, or technical guidance you can provide on modifying or extending the trust store for the embedded webview would be greatly appreciated.
Thank you for your time and assistance.
Significant delay when performing card swipe login from sleep on IM C2510 devices
Incident Properties
Question
Hello team,
A customer is running into the following issue on their IM C2510 devices: when the device panel is asleep and the user does a card swipe, it takes almost 15 seconds for the card swipe request to be received by the server. It is unlikely that it is a network issue on the customer's end, as it works fine when the device is not in a sleep state.
I have attached the device logs and settings. The issue happens between 10:50:18 and 10:50:33.
Based on the logs, we can see that the device recognises the card attached event at 10:50:19.256.
12-12 10:50:19.256 4832 4832 I BRWS : BrowRcvr:onReceive[jp.co.ricoh.isdk.sdkservice.card.IC_CARD_ATTACHED]However, the logs suggest that the page actually takes 13 seconds to start.
12-12 10:50:32.051 4594 4594 D WebViewClient: onPageStarted()I don't see much else in the device logs that could indicate why there is a delay, aside from these kinds of messages:
12-12 10:50:20.842 3821 3821 I LegacyAppManagerService: ACTION_HOME_DISPLAY CATS NOT READY!! rlt:11We have not been able to reproduce this issue internally on our IM C2010 and IM C3010 with firmware 2.06.
Could you please have a look at the issue described, in addition to the logs collected from the device (in the attached tar file), and hopefully have some insight to this problem that is impacting our customer? Could it be a firmware issue on or a device misconfiguration?
Thanks
Maintenance Signature request for RfIdeasReaderPlugin
Incident Properties
Question
Hi Team,
I am requesting a maintenance signature on our latest released plugin. Please find attached version 1.4.0 of our RF IDEAS Reader Plugin (zipped DALP & APK), along with the release notes for this build.
This version includes:
- One File Configuration support in Ricoh Plugin.
- Replace pc Prox with reader model name.
- Unit Test Cases addition.
We have internally tested the plugin updates on G2, G2.5, and G3 devices across multiple reader models.
Renew signature of Package
Incident Properties
Question
Our application certification is coming up on 2 years and is going to expire. Since we do not have any new new changes other than the ones that have already been resubmitted for bug fixes. Is the process for Compatibility testing the same in that it needs to be an unsigned package? Or since this is using the same build can it be the signed package?
REQUEST MAINTENANCE SIGNATURE RICOHSOP 1.3.0.632
Incident Properties
Question
Hi RiDP,
Please help to create a maintenance signature for the attached version (1.3.0.632)
This version includes fixing the bug below:
-[Ricoh UC - AS Scan] The job returned appears as a .BIN instead of correct extension file.
Regards