** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.
There have been thousands of bug
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack
of information which is needed in order to accurately reproduce and
confirm the problem. We encourage you to retest your bug against the
latest
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack
of information which is needed in order to accurately reproduce and
confirm the problem. We encourage you to retest your bug against the
latest
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for over a year. Your bug is still set to NEW which means that it
is open and confirmed. It would be nice to have the bug confirmed on a
newer version than the
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack
of information which is needed in order to accurately reproduce and
confirm the problem. We encourage you to retest your bug against the
latest
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack
of information which is needed in order to accurately reproduce and
confirm the problem. We encourage you to retest your bug against the
latest
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
Please read the entire message before proceeding.
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is
Dear Bug Submitter,
Please read the entire message before proceeding.
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is
Dear Bug Submitter,
Please read the entire message before proceeding.
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is
Dear Bug Submitter,
Please read the entire message before proceeding.
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack
of information which is needed in order to accurately reproduce and
confirm the problem. We encourage you to retest your bug against the
latest
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INVALID due to inactivity and a lack
of information which is needed in order to accurately reproduce and
confirm the problem. We encourage you to retest your bug against the
latest
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least 6
months. Please provide the requested information as soon as possible and
mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if
the bug is still in NEEDINFO status with no change in 30 days the
201 - 264 of 264 matches
Mail list logo
