Web/Marketplace Bugs

Marketplace and SL websites
  • Search existing bugs before submitting
  • Use support.secondlife.com for customer support issues
  • Keep posts on-topic
Over abundance of 'account security' emails
I've tried filing this as a 'support case', but Freckle Linden (who?) closed my ticket and told me to bring this issue here. Thank you for submitting your case. After investigation, it appears as though this issue may be a bug or error which would be best handled through our bug report system known as JIRA ( http://jira.secondlife.com ). While our Support team is always happy to help, there are certain technical issues which can only be addressed via a development or engineering investigation. Something strange is happening with the 'account security' emails. I have several alt accounts, and I am seeing a large number of emails saying I've logged in to a new machine. Far more often than I am used to, and far more than seems reasonable. This increase in frequency seems to have started around October 17, 2025. I will focus on just two accounts for the purpose of this report, and I will so you can see the issue clearly. Oct 17 - Of the accounts I logged in on October 17, I received 6 emails (one per user) stating that <account A> or <account B> accessed Second Life from a new machine. <my IP> Oct 19 - Important: <account A> accessed Second Life from a new machine. <my IP> Oct 20 - Important: <account B> accessed Second Life from a new machine. <my IP> Oct 22 - Important: <account B> accessed Second Life from a new machine. <my IP> Nov 4 - Important: <account A> accessed Second Life from a new machine. <my IP> Nov 6 - Important: <account A> accessed Second Life from a new machine. <my IP> Nov 20 - Important: <account A> accessed Second Life from a new machine. <my IP> Nov 23 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 1 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 1 - Important: <account B> accessed Second Life from a new machine. <my IP> Dec 5 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 9 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 16 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 17 - Important: <account B> accessed Second Life from a new machine. <my IP> Dec 20 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 20 - Important: <account B> accessed Second Life from a new machine. <my IP> Dec 26 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 28 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 28 - Important: <account B> accessed Second Life from a new machine. <my IP> Dec 29 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 29 - Important: <account B> accessed Second Life from a new machine. <my IP> Now here's the thing. Aside from a couple of attempts to use the mobile viewer, I have been consistently using my desktop computer. This computer hasn't changed. My IP Address (both on our home LAN, and the household IP) hasn't changed! My MAC hasn't changed. My OS hasn't changed. I haven't done any major computer rebuilds or OS reinstalls that would result in notable hardware or software changes. I also haven't logged these accounts in with any other computers. I feel it's important to note that I didn't attempt to log <account B> into SL every single day. <account A> is my 'daily driver' account. These emails are coming in FAR too frequently to be explained by those brief mobile app attempts. The app has not been launched in days, and the device it is installed on, has been powered off and rebooted in the time since. To confuse things more, someone else, in the same household (on the same external IP!) has been logging in from a different computer, and has received NONE of these alert messages.. it's JUST ME and my accounts! I've enabled Multi-factor authentication on both accounts, I've checked my transaction history, both https://accounts.secondlife.com/transaction_history and https://secondlife.com/my/lindex/history.php and I have seen no transactions that would indicate someone is using my accounts without my permission. I only see these notification emails after I log in to my own accounts.. I've never seen them appear any other time.. and no one to my knowledge has access to my email. I do not believe that this is an unauthorized account access issue. These messages are important.. it's important for me to know if my account is logged in without my consent. I value these messages. But at this point, the system is crying wolf.. and it's getting to the point where I've considered making an email filter to automatically delete them before I see them.. because they are only creating false scares and annoying me. Something's wrong with the system here.. whether it's on your end or mine, I can't tell. What I do know is that these emails aren't useful in their current form.. and they should be! They need to be!
7
Major outages and failures to Process Credits (Multiple Banks/Customers)
Outage issue: Effective early October 2025, there have been consistent and constant failures to uphold process credit cash outs to customers across multiple banks (inclusive of the US). Customers are using the Next Day Bank Deposit option. Paying the fee for said service. No payment is then made to the customer. Where a payment is made, it is late and does not adhere to the Next Day Bank Deposit statement and fee paid. Eventually the USD is silently, without notification to the customer, returned to their USD Balance after being missing in action for days. This is a risk and inappropriate management of fiat currency under customer accounts. Furthermore, the transaction is then "wiped" from the process credit history under the pending queue. Removing access to customers of a full and proper audit trail of their USD funds during those periods. This effectively obscures the issue "as if it never happened". Support: (a) Tickets remain unanswered. (b) Customers remain with out the ability to tag tickets into prioritized RL financial or tax queues (despite requests at meetings with LL on this exact topic). (c) Live Chat is barely contactable. Corporate Governance: This is an extraordinary lack of governance with inappropriate communication and compliance risk to customers. There are also regulatory components to consider within this. USD funds held on the platform do not receive FDIC insurance. Scope of Impact: (a) These are not first time payments, they are payments where the bank accounts have been previously successfully cashed out to. (b) This is not one customer, folk are sharing their experiences and it indicates a systemic failure impacting multiple elements. This does not appear to be Plaid (contacted their compliance team and they have confirmed not their issue), ACH (no outages during this time has also been confirmed). Customers: (a) These are customers who have completed all AML-KYC paperwork and tax forms. (b) These are customers in the US and International so not restricted to one area. (c) These are customers who have used the platform for years and who have a history of cashing out so are a known entity. Remediation sought: (a) A formal communication and plan should be shared with customers to resolve, including the measures to resolve delayed payments and failure to pay the USD owed to customers. (b) Go-forward timely communication to customers (email) to be implemented where, and if you, fail to make a payment of USD. (c) Heightened monitoring of payment risks and your integration with Tilia to ensure payments in USD are made on time going forward to ensure payment obligations are met appropriately. Where a payment is not made on time, a consideration of reduction of the fee charged for said service. (d) Ensure a clear understanding of regulatory and payment requirements are utilized to ensure compliant under current US regulation and law go-forward.
5
·
tracked
SL Wiki: Please fix SVG support (old issue reported on Jira)
Hi there! SVG uploads have been broken on the SL Wiki since September 2022 . This was reported on the Jira [the link is to the archived Jira]. To reproduce, all that is needed is to search for SVGs on the file library. Almost all (and all from September 2022 onwards) will appear to be broken. Here is a (slightly more recent) test from October 2023: https://wiki.secondlife.com/wiki/File:Second_Life_Logo.svg And the error given is: Error creating thumbnail: convert-im6.q16: delegate failed `'rsvg-convert' -o '%o' '%i'' @ error/delegate.c/InvokeDelegate/1928. convert-im6.q16: unable to open file `/tmp/magick-4352gcUpm5k4VXzw': No such file or directory @ error/constitute.c/ReadImage/600. convert-im6.q16: no images defined `PNG:/tmp/transform_553c1ae0c6da.png' @ error/convert.c/ConvertImageCommand/3258. This is an error message from ImageMagick 6, used to resize thumbnails, and a prerequisite for uploading images. With all other (supported) image types (including WebP!) everything works without errors, because all of those are natively supported by ImageMagick (i.e., they're built-in modules). Several other graphic file formats — the most obvious and pertinent of those being SVG, but others, such as PDF, might have similar issues — aren't natively handled by ImageMagick; rather, depending on the underlying operating system, they are handled by what ImageMagick calls delegates . A delegate is simply an external tool which converts first the 'foreign' file to a format that ImageMagick can handle natively; this will then be further processed by ImageMagick (and all its, well, magic , applied as normal). In other words: for SVGs, the first step in the complex ImageMagick pipeline is to convert the file to something ImageMagick can process. Usually, that means rasterising the vector file to an adequate size. On macOS, for instance, for some reason, my MacBook Pro uses Inkscape ; on Ubuntu and Debian Linux, rsvg-convert is more common. The full delegate lis can be retrieved from a file called delegates.xml which, under Debian and Ubuntu, is found under /etc/ImageMagick-X/ (where X is the ImageMagick version — 6 in the case of the SL Wiki). This should also list the kind of command arguments passed to rsvg-convert . What seems to be happening is that rsvg-convert is being correctly called, but it's unable to write a temporary file (the intermediary conversion file to a raster format) on /tmp — possibly because the process running the MediaWiki PHP does not have read/write access to /tmp — and therefore is unable to pass the results back to ImageMagick. Please note that the MediaWiki installation may be using the ImageMagick module for PHP, as opposed to launching an external process; this means that common file formats are handled directly inside PHP itself. External delegates, however, need to be spawned; and it's very likely that the PHP support on that server does not have direct access to /tmp , and, therefore, anything spawned by it will inherit its permissions (or lack thereof). Also note that the upload itself didn't fail: the SVG has been correctly stored — the link is obtained by clicking on the Time/Date column of the File: Second_Life_Logo.svg page. It's only the thumbnail that is broken; but without a valid thumbnail, nothing works on the SL Wiki. This should be a very easy fix! After all, before September 2022, there was no problem in uploading SVGs. But now all are broken .
6
·
tracked
Marketplace ANS bug – PaymentFee incorrect for multi-item carts with profit sharing
Hello, I’m reporting an issue with Marketplace ANS (Automatic Notification System) messages on the Second Life Marketplace. When a customer purchases multiple products in a single cart, and more than one of those products uses profit sharing with another creator, the PaymentFee value in the ANS request is incorrect for some items. Only one item shows the correct PaymentFee in its ANS payload. For the other items in the same cart, the ANS payload shows an incomplete PaymentFee that includes only the standard Marketplace fee (10%), as if no profit sharing were applied. However, profit sharing is actually applied correctly: The sales report email shows the full set of fees (Marketplace fee + profit sharing percentage) for each item. The transaction history also shows the correct complete fees for each item. So the issue appears to be limited to the ANS data for multi-item carts, not the actual accounting. Example: An item sells for L$1000 with 50% profit sharing. In a normal (single-item) purchase, the ANS payload reports the correct PaymentFee: Marketplace fee: 10% of 1000 = L$100 Profit-sharing portion: 50% of the net after Marketplace fee (1000 × 0.9 = L$900) → 900 × 0.5 = L$450 Total PaymentFee = 100 + 450 = L$550 However, when the same item is purchased as part of a multi-item cart, the ANS payload reports PaymentFee = L$100 (only the 10% Marketplace fee), incorrectly omitting the L$450 profit-sharing amount. Am I missing something? Or is this really a bug? If it's a bug, I hope you can fix it.
0
·
Marketplace
Load More