Page MenuHomePhabricator

Users trying to analyze pages are being told they are blocked when they are not
Closed, ResolvedPublic

Description

If you are experiencing this bug, it usually clears up by itself after one or two days.

If you are encountering this problem, please open the page source, of the tool, which can usually be done by right clicking on the page and selecting "Inspect", and copy the commented out, everything between <!-- and -->, material from it. It can be found at the top of the source viewer. Please paste the contents in a new response to this bug.

There is an ongoing InternetArchiveBot bug which causes users to encounter this error:

blocked: You have been blocked from editing.

This is a distinct message from the one InternetArchiveBot serves to users who are actually blocked. For one, users would not be able to use the bot to begin with if they were blocked.

Our investigation currently points to this being an issue with upstream MediaWiki. Meanwhile, we have had difficulty reproducing this bug on our own end. We are continuing to investigate this bug.

Steps to reproduce:

  1. Use the Management Interface to (try to) archive a single page. Confirm you are not blocked on the wiki you are trying to edit.
  1. While editing, receive the error "blocked: You have been blocked from editing."

Original report:

Hello, today I tried to archive a page using this tool. When I click analyze, it says that I can't archive the page because I'm blocked. But I'm not blocked on the wiki, and this page (https://iabot.toolforge.org/index.php?page=user&id=52135372&wiki=enwiki) doesn't say I'm blocked either. Any idea how to fix this? Thanks...

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Was there any progress made as to the source of this issue? And did anyone find any methods of correcting it besides just waiting and praying?

My storages resources are a bit scarce right now, so I’m hesitant to do so, however as I mentioned I can have the full response passed back to the user ad-verbatim so they can report it themselves. It’s quicker and easier.

That would be appreciated. Could you confirm here when this change is made, so we can wait for additional reports? I would probably also link this task, to make sure reporters know where this is discussed.

Ping? It's next to impossible to debug this from a MW standpoint without having the error message on hand :/.

Harej raised the priority of this task from Low to Medium.Aug 20 2021, 8:28 PM
Harej merged a task: T289378: Blocked?.
Harej added a subscriber: Ved_havet.
AntiCompositeNumber changed the task status from Open to Stalled.Aug 21 2021, 12:08 AM

This has just happened to me this morning. I am not blocked, and https://iabot.toolforge.org/index.php?page=user&id=5852725&wiki=enwiki knows that i am not blocked, but when I submit a page the bot says I am blocked.

It's still doing it. The error message is "Analysis error: blocked: You have been blocked from editing."
I am not blocked

The fake "you are blocked" thing has just cleared for me: the bot did https://en.wikipedia.org/w/index.php?diff=prev&oldid=1045784815

Please remove me from these notifications

Cyberpower678 raised the priority of this task from Medium to High.Dec 10 2021, 4:39 PM
Cyberpower678 updated the task description. (Show Details)

Now it says, "Fatal Error: You are upgrading from v2.0.8.3 to v2.0.8.4. This update requires a clean install, or an update script. Please run update.php in the source root directory."

Now it says, "Fatal Error: You are upgrading from v2.0.8.3 to v2.0.8.4. This update requires a clean install, or an update script. Please run update.php in the source root directory."

Thank you; we have fixed this.

Unfortunately, also experiencing this error. I attempted to run the bot on several pages several hours ago, with Justin Briner being the one I tried multiple times.

If I do not have "Add archives to all non-dead references (Optional)" checked, it runs - but as I'm trying to use the bot for this option, the bot is unusable for me. The interface logs (04:31, 2022-01-27) can confirm that I was able to run it on this page with this option not checked. Hopefully MediaWiki, or whichever upstream entity which is causing this problem can get this resolved... wish I could provide more info, but alas - this tool is a huge benefit to Wikipedia and editors, and I was excited to start using it but that enthusiasm has faded as barely a day after, it's already not working due to this bug.

This is what is presenting at the top at the page source:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
<meta name="description" content="">
<meta name="author" content="">
<link rel="icon" href="https://upload.wikimedia.org/wikipedia/commons/6/6c/IABot_logo.svg">

<title>Analyze a page - IABot Management Interface</title>

<!-- Bootstrap core CSS -->
<link href="static/darkly/css/bootstrap.min.css?v=1.0" rel="stylesheet">
<!-- IE10 viewport hack for Surface/desktop Windows 8 bug -->
<link href="static/ie10-viewport-bug-workaround.css?v=1.0" rel="stylesheet">

<!-- Custom styles for this template -->
<!--<link href="static/theme.css" rel="stylesheet">-->

<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
<!--[if lt IE 9]>
<script src="static/html5shiv.min.js?v=1.0"></script>
<script src="static/respond.min.js?v=1.0"></script>
<![endif]-->

<!-- XHProf interface mods -->
<link href='static/xhprof/css/xhprof.css?v=1.0' rel='stylesheet' type='text/css'/>
<link href='static/xhprof/jquery/jquery.autocomplete.css?v=1.0' rel='stylesheet' type='text/css'/>
<link href='static/xhprof/jquery/jquery.tooltip.css?v=1.0' rel='stylesheet' type='text/css'/>

<!-- Custom bootstrap mods for IABot -->
<link href="static/bootstrap-mods.css?v=1.0" rel="stylesheet">
<script>

The source comments you provided does not actually have any run data in it. Did you copy before or after running the tool?

I figured, but wanted to at least try to follow the instructions at the top of the page ;/ - I clicked "page source" after running the tool, it opens a new tab and presents a "Resubmit the form?" that browsers usually display. Could be because I'm running Edge, or I'm just doing it wrong-

@Cyberpower678 Can we just display the information visibly, as part of the tool-provided error message? That will be much easier to deal with.

Well, it resolved itself in less than two days which is nice. Sorry I can't help push this issue to be resolved ; (

Found the info - it's under "inspect" not view page source as the instructions say. I've received no block notifications from the site, or from here - but the user "ToBeFree" is a real Wikipedia user... so either I'm blocked and wasn't notified anywhere, or something's gone horribly wrong...

I'm guessing that we are supposed to create a bot account to use this tool, and didn't realize we needed to - and that's what is creating this "Bug"? Tl;dr - this "bug" isn't actually a bug, just ignorant editors (including me, rip) who didn't read the bot policy?

Here's what's generating:

<!--
Logging on as Canadianerk...Success!!

The paywall table exists

The global external links table exists

The enwiki external links table exists

The archive cache table exists

The external links scan log exists

The availability table exists

A log table exists

The edit error log table exists

The watchdog table exists

A stat table exists

Analyzing Wendy Powell (6166924)...
Fetching previous bot revisions...
Fetching all references...
Phase 1: Checking what's available and what needs archiving...
Phase 2: Submitting requests for archives...
Phase 3: Applying necessary changes to page...
Rescued: 9; Tagged dead: 0; Archived: 0; Memory Used: 10 MB; Max System Memory Used: 10 MB
EDIT ERROR: blocked: You have been blocked from editing.
Array
(

[error] => Array
    (
        [code] => blocked
        [info] => You have been blocked from editing.
        [blockinfo] => Array
            (
                [blockid] => 12946111
                [blockedby] => ToBeFree
                [blockedbyid] => 16759563
                [blockreason] => [[WP:Disruptive editing|Disruptive editing]]
                [blockedtimestamp] => 2022-01-30T23:03:37Z
                [blockexpiry] => 2022-02-06T23:03:37Z
                [blocknocreate] => 
                [blockedtimestampformatted] => 23:03, January 30, 2022
                [blockexpiryformatted] => 23:03, February 6, 2022
                [blockexpiryrelative] => in 6 days
            )

        [*] => See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/&gt; for notice of API deprecations and breaking changes.
    )

[servedby] => mw1376

)
Response: {"error":{"code":"blocked","info":"You have been blocked from editing.","blockinfo":{"blockid":12946111,"blockedby":"ToBeFree","blockedbyid":16759563,"blockreason":"[[WP:Disruptive editing|Disruptive editing]]","blockedtimestamp":"2022-01-30T23:03:37Z","blockexpiry":"2022-02-06T23:03:37Z","blocknocreate":"","blockedtimestampformatted":"23:03, January 30, 2022","blockexpiryformatted":"23:03, February 6, 2022","blockexpiryrelative":"in 6 days"},"*":"See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/&gt; for notice of API deprecations and breaking changes."},"servedby":"mw1376"}

-->

[blockedby] => ToBeFree
[blockedbyid] => 16759563
[blockreason] => [[WP:Disruptive editing|Disruptive editing]]
[blockedtimestamp] => 2022-01-30T23:03:37Z
[blockexpiry] => 2022-02-06T23:03:37Z

Tried archiving a page as well and I had this pop up in the comments too. The given block seems to correlate with this block by ToBeFree. As to why the block of a completely different user is affecting every single user attempting to use the IABot interface, I have no clue.

Sounds like it's autoblock-related, same as T68639/T74501: Need a way for trusted OAuth apps to make edits from blocked IPs. https://en.wikipedia.org/wiki/MediaWiki:Block-autoblock-exemptionlist does have WMF IP ranges on it though, and Cloud VPS shouldn't be handing out IPv6 addresses yet I don't think (T37947). So I'm not entirely sure what's going on there. Per https://openstack-browser.toolforge.org/server/cyberbot-exec-iabot-02.cyberbot.eqiad1.wikimedia.cloud the current floating IP should be 185.15.56.29.

I'm guessing that we are supposed to create a bot account to use this tool, and didn't realize we needed to - and that's what is creating this "Bug"? Tl;dr - this "bug" isn't actually a bug, just ignorant editors (including me, rip) who didn't read the bot policy?

no, it's a bug. It's not related to the account you are using (unless you have . Someone else used the tool, or another tool with the same IP address, then got blocked. The Cloud Services IP then gets autoblocked, breaking the tool. In this case, it appears to be this edit.

Sounds like it's autoblock-related, same as T68639/T74501: Need a way for trusted OAuth apps to make edits from blocked IPs. https://en.wikipedia.org/wiki/MediaWiki:Block-autoblock-exemptionlist does have WMF IP ranges on it though, and Cloud VPS shouldn't be handing out IPv6 addresses yet I don't think (T37947). So I'm not entirely sure what's going on there. Per https://openstack-browser.toolforge.org/server/cyberbot-exec-iabot-02.cyberbot.eqiad1.wikimedia.cloud the current floating IP should be 185.15.56.29.

No, we're currently only using 172.16.0.0/21 and 185.15.56.0/25 for any WMCS user traffic. MW is also parsing the exemption list correctly:

taavi@mwmaint1002 ~ $ mwscript shell.php enwiki
Psy Shell v0.10.12 (PHP 7.2.34-18+0~20210223.60+debian10~1.gbpb21322+wmf5 — cli) by Justin Hileman
>>> \MediaWiki\Block\DatabaseBlock::isExemptedFromAutoblocks("185.15.56.29")
=> true

Sounds like it's autoblock-related, same as T68639/T74501: Need a way for trusted OAuth apps to make edits from blocked IPs. https://en.wikipedia.org/wiki/MediaWiki:Block-autoblock-exemptionlist does have WMF IP ranges on it though, and Cloud VPS shouldn't be handing out IPv6 addresses yet I don't think (T37947). So I'm not entirely sure what's going on there. Per https://openstack-browser.toolforge.org/server/cyberbot-exec-iabot-02.cyberbot.eqiad1.wikimedia.cloud the current floating IP should be 185.15.56.29.

I'm guessing that we are supposed to create a bot account to use this tool, and didn't realize we needed to - and that's what is creating this "Bug"? Tl;dr - this "bug" isn't actually a bug, just ignorant editors (including me, rip) who didn't read the bot policy?

no, it's a bug. It's not related to the account you are using (unless you have . Someone else used the tool, or another tool with the same IP address, then got blocked. The Cloud Services IP then gets autoblocked, breaking the tool. In this case, it appears to be this edit.

Those floating IPs are for the bot's main processes. Using the tool on OAuth produces Toolforge IPs.

Those floating IPs are for the bot's main processes. Using the tool on OAuth produces Toolforge IPs.

Toolforge grid exec nodes and kubernetes workers are too using IP addresses that should be exempt from autoblocks. Wouldn't the block message be different ("Your IP address has been blocked because it was recently used by username" or something like that) too?

Just successfully used the bot on Wendy Powell, so it's clear something changed somewhere which freed me from this other users' block. - I'll stay subscribed in hopes of hearing good news about fixing this at some point - and ofc, if there's anything I can provide as a user, I'd be happy to help-

Thank you AntiCompositeNumber for clarifying re: bot account, genuinely panicked when that possibility hit my mind...
Until then, all the best to everyone involved w this bot/issue-

I checked block ID 12946111 at enwiki and there is no autoblock associated with the block ATM (there might've been one yesterday though). That said, the (blocked) user indeed did use IABot on 2022-01-30 (so the day before IABot mistakenly tells "You are blocked" to someone else).

There was https://en.wikipedia.org/w/index.php?title=MediaWiki:Block-autoblock-exemptionlist&diff=1066969344&oldid=1066536004 made recently, but that's not enough to explain what's happening. The list of exempted IPs is cached for a day, so the cache very likely was updated when the block with ID 12946111 was made (2022-01-30).

I copied enwiki's exemption list to cswiki, edited via IABot on my test account, blocked it, and no autoblock appeared in the DB. My other test account was happily allowed to use IABot.

Well, I got a different message - specifically "you have been blocked from editing this page" - don't want to badger y'all, but figured I might as well pass this on as at the very least, it gave me a different message on the page... same impact ofc - but :shrug:, I'll just have to get used to random blocks, or apply for a second account to run the bot under bot policy and hope it makes a difference.

<!--
Logging on as Canadianerk...Success!!

The paywall table exists

The global external links table exists

The enwiki external links table exists

The archive cache table exists

The external links scan log exists

The availability table exists

A log table exists

The edit error log table exists

The watchdog table exists

A stat table exists

Analyzing Brandon Potter (13120221)...
Fetching previous bot revisions...
Fetching all references...
Delaying one or more links!
https://www.catholicweekly.com.au/review-the-chosen-season-2-episode-7/ is ALIVE!
https://blog.funimation.com/2013/05/20/full-english-cast-for-appleseed-xiii/ is ALIVE!
https://www.funimation.com/v/appare-ranman/i-am-gil is ALIVE!
https://www.behindthevoiceactors.com/Brandon-Potter/ is ALIVE!
https://blog.funimation.com/2017/02/16/home-video-acquisition-cast-announcement-gosick/ is ALIVE!
https://blog.funimation.com/2017/07/13/summer-2017-simuldubs-funimationnow/ is ALIVE!
Phase 1: Checking what's available and what needs archiving...
Phase 2: Submitting requests for archives...
Phase 3: Applying necessary changes to page...
Rescued: 19; Tagged dead: 0; Archived: 1; Memory Used: 12 MB; Max System Memory Used: 12 MB
EDIT ERROR: blocked: You have been blocked from editing this page.
Array
(

[error] => Array
    (
        [code] => blocked
        [info] => You have been blocked from editing this page.
        [blockinfo] => Array
            (
                [blockid] => 12946111
                [blockedby] => Rosguill
                [blockedbyid] => 32763026
                [blockreason] => Convert to partial block on all namespaces other than Wikipedia to allow for participation in an RfD.
                [blockedtimestamp] => 2022-01-30T23:03:37Z
                [blockexpiry] => 2022-02-06T23:03:37Z
                [blockpartial] => 
                [blocknocreate] => 
                [blockedtimestampformatted] => 23:03, January 30, 2022
                [blockexpiryformatted] => 23:03, February 6, 2022
                [blockexpiryrelative] => in 4 days
            )

        [*] => See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/&gt; for notice of API deprecations and breaking changes.
    )

[servedby] => mw1339

)
Response: {"error":{"code":"blocked","info":"You have been blocked from editing this page.","blockinfo":{"blockid":12946111,"blockedby":"Rosguill","blockedbyid":32763026,"blockreason":"Convert to partial block on all namespaces other than Wikipedia to allow for participation in an RfD.","blockedtimestamp":"2022-01-30T23:03:37Z","blockexpiry":"2022-02-06T23:03:37Z","blockpartial":"","blocknocreate":"","blockedtimestampformatted":"23:03, January 30, 2022","blockexpiryformatted":"23:03, February 6, 2022","blockexpiryrelative":"in 4 days"},"*":"See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/&gt; for notice of API deprecations and breaking changes."},"servedby":"mw1339"}

-->

Block 12946111 https://en.wikipedia.org/wiki/Special:BlockList?wp_target=%2312946111&blockType=&limit=50&wpFormIdentifier=blocklist is for User:Lallint .. confirming they have used the IABot tool before, last active 22:45 30 January 2022

Cookie blocks show as the original block, not an autoblock, and don't have the autoblock exemption list applied. But the cookie should only have been applied if a request was made as the blocked user while they were blocked, right? And IABot would have to be sharing cookies between users. Might be worth looking in the cookie jar for any enwikiBlockID cookies.

Cookie blocks show as the original block, not an autoblock, and don't have the autoblock exemption list applied. But the cookie should only have been applied if a request was made as the blocked user while they were blocked, right? And IABot would have to be sharing cookies between users. Might be worth looking in the cookie jar for any enwikiBlockID cookies.

Cookie sharing is a big no-no.

Hi, if I use a bot for simple article analysis, the bot works. If they use it to analyze and add archived copies, the bot writes that I am blocked (blocked: You have been blocked from editing this page.)
I am in the Ru Wiki. I take articles for analysis in the same place. I need to provide some more data.

Harej changed the task status from Open to Stalled.Mar 13 2022, 11:41 PM
Harej moved this task from Backlog: Other to Blocked on the InternetArchiveBot board.

Bug reproduction successful. (Note that these steps may not successfully reproduce the bug in the future.)

  1. Set wiki to "English Wikipedia"
  1. Run bot on Wikipedia article "Erma Bossi"
  1. Check box to add archives to all links
  1. Encounter "blocked: You have been blocked from editing."

Resulting debug log:

<!--
Logging on as Harej...Success!!

The paywall table exists

The global external links table exists

The enwiki external links table exists

The archive cache table exists

The external links scan log exists

The availability table exists

A log table exists

The edit error log table exists

The watchdog table exists

A stat table exists

Analyzing Erma Bossi (64786836)...
Fetching previous bot revisions...
Fetching all references...
Phase 1: Checking what's available and what needs archiving...
Phase 2: Submitting requests for archives...
Phase 3: Applying necessary changes to page...
Rescued: 6; Tagged dead: 0; Archived: 0; Memory Used: 10 MB; Max System Memory Used: 10 MB
EDIT ERROR: blocked: You have been blocked from editing.
Array
(
    [error] => Array
        (
            [code] => blocked
            [info] => You have been blocked from editing.
            [blockinfo] => Array
                (
                    [blockid] => 13471853
                    [blockedby] => Ponyo
                    [blockedbyid] => 3965251
                    [blockreason] => [[WP:Disruptive editing|Disruptive editing]]
                    [blockedtimestamp] => 2022-03-07T22:22:33Z
                    [blockexpiry] => infinite
                    [blocknocreate] => 
                    [blockedtimestampformatted] => 22:22, 7 March 2022
                )

            [*] => See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/&gt; for notice of API deprecations and breaking changes.
        )

    [servedby] => mw1390
)
Response: {"error":{"code":"blocked","info":"You have been blocked from editing.","blockinfo":{"blockid":13471853,"blockedby":"Ponyo","blockedbyid":3965251,"blockreason":"[[WP:Disruptive editing|Disruptive editing]]","blockedtimestamp":"2022-03-07T22:22:33Z","blockexpiry":"infinite","blocknocreate":"","blockedtimestampformatted":"22:22, 7 March 2022"},"*":"See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/&gt; for notice of API deprecations and breaking changes."},"servedby":"mw1390"}

-->

@Harej is repeatedly hitting this now. I am able to get around this, presumably because I am an enwiki sysop.

I received the same error running the tool on a different Wikipedia article, so the specific article being run doesn't seem to affect reproduction of the bug.

_target of block was user Lallint.

I just got

<!--
Logging on as Markjgraham hmb...Success!!

The paywall table exists

The global external links table exists

The enwiki external links table exists

The archive cache table exists

The external links scan log exists

The availability table exists

A log table exists

The edit error log table exists

The watchdog table exists

A stat table exists

Analyzing Chandler, Arizona (106644)...
Fetching previous bot revisions...
Fetching all references...
Phase 1: Checking what's available and what needs archiving...
Phase 2: Submitting requests for archives...
Phase 3: Applying necessary changes to page...
Rescued: 13; Tagged dead: 0; Archived: 0; Memory Used: 14 MB; Max System Memory Used: 16 MB
EDIT ERROR: blocked: You have been blocked from editing.
Array
(

[error] => Array
    (
        [code] => blocked
        [info] => You have been blocked from editing.
        [blockinfo] => Array
            (
                [blockid] => 13471853
                [blockedby] => Ponyo
                [blockedbyid] => 3965251
                [blockreason] => [[WP:Disruptive editing|Disruptive editing]]
                [blockedtimestamp] => 2022-03-07T22:22:33Z
                [blockexpiry] => infinite
                [blocknocreate] => 
                [blockedtimestampformatted] => 22:22, 7 March 2022
            )

        [*] => See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/&gt; for notice of API deprecations and breaking changes.
    )

[servedby] => mw1394

)
Response: {"error":{"code":"blocked","info":"You have been blocked from editing.","blockinfo":{"blockid":13471853,"blockedby":"Ponyo","blockedbyid":3965251,"blockreason":"[[WP:Disruptive editing|Disruptive editing]]","blockedtimestamp":"2022-03-07T22:22:33Z","blockexpiry":"infinite","blocknocreate":"","blockedtimestampformatted":"22:22, 7 March 2022"},"*":"See https://en.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at &lt;https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/&gt; for notice of API deprecations and breaking changes."},"servedby":"mw1394"}

-->

I suspect the blocked user Lallint may have signed in to the tool to try and use it, and the OAuth requests used to log them in triggered an auto block of some sort.

Harej changed the task status from Stalled to Open.Mar 29 2022, 12:14 AM

After a long debug session at IRC, the rootcause of this issue was determined as cookie-based autoblocks. At one point, the tool receives a Set-Cookie for enwikiBlockID=XXX. Because IABot apparently uses a single cookie jar for MW cookies shared with all tool users, it then started to send the enwikiBlockID cookie to the server together with all user requests, which in turn means everyone was considered blocked.

I have re-opened this tsk because I have just had the false "You have been blocked from editing" message

This comment was removed by Kailash29792.

Now it seems IABot cannot add archives to pages where there are archive.today links. It just gets stuck during submitting.

JJMC89 subscribed.

Do not reopen tasks for unrelated issues.

@Kailash29792 Please follow the steps at https://meta.wikimedia.org/wiki/InternetArchiveBot/Problem to file a new bug report. As JJMC89 said above, you should not re-open tasks once they are closed to report an unrelated issue.

  NODES
Done 1
eth 5
News 1
orte 1
see 12
Users 9