← Back to team overview

documentation-packages team mailing list archive

[Bug 1426224] Re: its been a month and a week and you still have not fixed my ubuntu


Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!

** Information type changed from Private Security to Public

** Changed in: ubuntu-docs (Ubuntu)
       Status: New => Invalid

You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.

  its been a month and a week and you still have not fixed my ubuntu

Status in ubuntu-docs package in Ubuntu:

Bug description:
  i have filed more than 10 bug reports and non of them have been
  answered yet.i looked in the list of bugs report and you have got rid
  of any of my reports .they have not been answered because if they had
  i would have my missing files,pictures,videos,music,and programs and
  it still would not keep erasing everything i put on the computer one
  day and gone the next .ubuntu would not be in the default mode and it
  would have erased that guest session. all of this was suppose to be
  fixed the last week into the first week of the month thats what the
  tech said and it was not

To manage notifications about this bug go to:

Follow ups