We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Confirming.
Based upon Andrew's comments: it appears that vim doesn't report the limitation
to the user then proceeds as though the large file doesn't exist.
** Changed in: vim (Ubuntu)
Status: Incomplete = Confirmed
--
can't open files larger than 2gb
Still a problem in Hardy Heron on Compaq Presario laptop
One has to touch the power key to make the system resume from standby.
The comparison with Windows is not relevant to a user.
what matters is the original message as in the bug report:
either the keyboard should wake the system, or the
Compaq Presario 1500 laptop 1GB Ram - Hardy Heron fully updated
Resuming (power key) from standby (deliberate) or from screensaver/powersaver
timeout, the keyboard is dead.
I think this is a hard fail - I do not remember a successful resume.
Trying the above change user/options/standby trick
Public bug reported:
Binary package hint: foomatic-db
Heron LTS release(available updates to 8 May 2008 all loaded)
Installed HP3600 Color Laser over network
using the System / Administration / Printers dialogue (Appsocket/HP Jetdirect).
as hp:/net/HP_Color_Laserjet_3600?ip=102.168.1.114
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: php5 (Ubuntu)
Status: Incomplete = Invalid
--
PHP5 FREETDS
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: sysklogd (Ubuntu)
Status: Incomplete = Invalid
--
[apport] syslogd
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: tkvnc (Ubuntu)
Status: Incomplete = Invalid
--
tkvnc for edgy is missing
Closing. To reopen the report you can click on the current status, under
the Status column, and change the Status back to New. Thanks again!
** Changed in: yarssr (Ubuntu)
Status: Incomplete = Invalid
--
Yarssr becomes unusable after you change check-up time to zero
Closing. To reopen the report you can click on the current status, under
the Status column, and change the Status back to New. Thanks again!
** Changed in: cyrus-imapd-2.2 (Ubuntu)
Status: Incomplete = Invalid
--
cvt_cyrusdb fail to convert deliver.db created by cyrus21-common
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete = Invalid
--
GPM console
Setting as invalid: No response to the argument If the user cannot verify that
ulimit -a shows no limit in file size, this bug should be closed as invalid.
To reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
**
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: samba (Ubuntu)
Status: Incomplete = Invalid
--
Bug in Samba after
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: adept (Ubuntu)
Status: Incomplete = Invalid
--
desktop crashes during an
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: qtparted (Ubuntu)
Status: Incomplete = Invalid
--
gtparted does not find
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: gpar2 (Ubuntu)
Status: Incomplete = Invalid
--
gpar2 doesn't start on
We are closing this report (no affirmative response to request for
information regarding present state of issue). To reopen the report you
can click on the current status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: pppoeconf (Ubuntu)
Status:
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = Invalid
--
installer crashed
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete = Invalid
--
2.6.22-rt
We are closing this report (no response to request for information). To
reopen the report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = Invalid
--
LiveCD fails on Aspire
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report (no affirmative responses to questioning
regarding present status of issue). Please reopen it if you think this
issue requires on-going attention, and don't hesitate to submit bug
reports in the future. To reopen the bug report you can click on the
current status,
We are closing this bug report (no response to questioning). Please
reopen it if you can give us the missing information, and don't hesitate
to submit bug reports in the future. To reopen the bug report you can
click on the current status, under the Status column, and change the
Status back to
We are closing this bug report (no affirmative responses to questioning
regarding present state of the issue). Please reopen it if you think
this issue requires on-going attention, and don't hesitate to submit bug
reports in the future. To reopen the bug report you can click on the
current status,
Closing.
Marking as invalid as cause (and cure) was not sufficiently well defined to
record as a 'fix'.
To reopen the bug report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: ubuntu
Status: Incomplete =
We are closing this bug report (no longer an issue). To reopen the bug
report you can click on the current status, under the Status column, and
change the Status back to New. Thanks again!
** Changed in: firefox (Ubuntu)
Status: Incomplete = Invalid
--
I attempted to delete my trash
We are closing this bug report (appears to no longer be an issue). To
reopen the bug report you can click on the current status, under the
Status column, and change the Status back to New. Thanks again!
** Changed in: update-manager (Ubuntu)
Status: Incomplete = Invalid
--
tzdata and
*** This bug is a duplicate of bug 126863 ***
https://bugs.launchpad.net/bugs/126863
** This bug has been marked a duplicate of bug 126863
Panic: CPU too old (after installing Gutsy i386 server)
--
Ubuntu Server enable PAE without checking for support
We are closing this bug report (appears to no longer be an issue). To
reopen the bug report you can click on the current status, under the
Status column, and change the Status back to New. Thanks again!
** Changed in: update-manager (Ubuntu)
Status: Incomplete = Invalid
--
unable to
Marking as invalid as issues appear to have been sufficiently addressed
by David and 3 months is enough time to allow for responses. To reopen
the report you can click on the current status, under the Status column,
and change the Status back to New. Thanks again!
** Changed in: ubuntu
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete = Confirmed
--
No sound on fresh install of 7.10
https://bugs.launchpad.net/bugs/185811
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 215728 ***
https://bugs.launchpad.net/bugs/215728
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #215728, so it is being marked as such. Please look
We are closing this bug report. Please reopen it if you feel this is
enhancement idea is important to carry forward. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to New. Thanks again!
** Changed in: gnome-app-install (Ubuntu)
We are closing this bug report (no response to questioning). Please
reopen it if you can give us the missing information, and don't hesitate
to submit bug reports in the future. To reopen the bug report you can
click on the current status, under the Status column, and change the
Status back to
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Closing.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete = Invalid
--
Inspiron 8600 no longer resumes from RAM after daily Dapper update
https://bugs.launchpad.net/bugs/42490
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report (no response to previous request for
expressions of interest in this report). To reopen the bug report you
can click on the current status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
We are closing this bug report (no response to previous request for
expressions of interest in this report). To reopen the bug report you
can click on the current status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Closing: marking as fix released in later releases based upon user comment.
To reopen the bug report you can click on the current status, under the Status
column, and change the Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete = Fix Released
We are closing this bug report (no response to previous request for
expressions of interest in this report). To reopen the bug report you
can click on the current status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report (no response to previous request for
expressions of interest in this report). To reopen the bug report you
can click on the current status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report (no response to previous request for
expressions of interest in this report). To reopen the bug report you
can click on the current status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Closing.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Incomplete = Invalid
--
areca enabled
https://bugs.launchpad.net/bugs/88717
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for
expressions of interest in this report). To reopen the report you
can click on the current status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.17 (Ubuntu)
Status:
Sorry - didn't read closely enough previously. My apologies.
Tom Tobin: Your issue should be reported in a new bug or existing bug which is
specific to MacBook hardware.
Thanks.
--
fan staying on constantly
https://bugs.launchpad.net/bugs/134555
You received this bug notification because you
Masnevets,
Have you been able to test this issue against Hardy release yet?
I gather from your initial bug report that this is a regression from Feisty. Is
this correct?
Thanks.
--
fan staying on constantly
https://bugs.launchpad.net/bugs/134555
You received this bug notification because you
Blue: thanks for the reply.
Closing report.
Ben's earlier judgement with regard to this as a security issue still stands.
Thanks for the report.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete = Invalid
--
Badness after wpa_supplicant is launched
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
We are closing this report (no response to previous request for expressions of
interest in this report). To reopen the report you can click on the current
status, under the Status column, and change the
Status back to New. Thanks again!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status:
501 - 600 of 1264 matches
Mail list logo