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 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
Sorry, that was a mistake. Setting as confirmed as Kernel Team needs to
action this as Won't Fix or otherwise.
[Note: fixed in 2.6.17]
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete = Confirmed
--
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
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete = Invalid
--
Random system lockup on video playback
https://bugs.launchpad.net/bugs/66892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Passing to kernel team. They may (or may not) want to do something about
this in future releases.
** Changed in: linux-source-2.6.17 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete = Confirmed
--
Inserting USB device causes system to hang
Passing to the kernel team.
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete = Confirmed
--
Inserting USB device causes system to hang
https://bugs.launchpad.net/bugs/68140
You received this bug
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
I experienced this problem in Feisty found that a small change to /etc/hosts
file fixed the problem. (sorry I can no longer remember the details).
I have upgraded to every release since without re-occurrence of this issue. I
presently use Hardy.
** Changed in: gnome-system-tools (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 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.20 (Ubuntu)
Status: Incomplete = Invalid
--
/proc/acpi does not exists
https://bugs.launchpad.net/bugs/106400
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 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
*** This bug is a duplicate of bug 149076 ***
https://bugs.launchpad.net/bugs/149076
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 149076, so it is being marked as such. Please look
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
gherardo,
Thanks for letting us know. Good to hear you found the problem.
Marking INVALID against linux kernel: problem due to hardware failure
on reporters equipment.
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = (unassigned)
Status: Confirmed =
The TSSTcorpCD/DVDW TS-L632D has a firmware bug.
Solutions discussed here:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/75295/comments/97
The following are indicators of this problem:
[ 1430.749371] ata1: port is slow to respond, please be patient (Status 0xd0)
see wjpwu
mirak,
Thanks for the update.
Do you mean that this is fixed for hardy release?
--
Doesn't recognise USB Serial device
https://bugs.launchpad.net/bugs/39101
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
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
In view of Michael comments (regarding apturl) the original reporter still
considers stated synaptic enhancement idea as an important feature proposal for
synaptic.
Therefore, confirming for further (perhaps final) consideration by Michael
other synaptic maintainers.
** Changed in: synaptic
*** This bug is a duplicate of bug 215728 ***
https://bugs.launchpad.net/bugs/215728
Marking as duplicate of Bug #215728 (Fix recently released).
** Changed in: xulrunner-1.9 (Ubuntu)
Status: Incomplete = Fix Released
** This bug has been marked a duplicate of bug 215728
[MASTER]
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
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
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
1 - 100 of 750 matches
Mail list logo
