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
ubun
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
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
** 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 han
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 notifica
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
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 t
*** 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 at
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 t
I can confirm this on U7.10.
I also have some extra information.
Sebastien: For me Nautilus doesn't crash just uses 100% CPU (I think the
crash reports above are different bugs). No record of crash or any
details entered in any log for me.
This is how it occurs for me:
1/ startup PC.
2/ login
3
Sebastien: Sorry there is something logged to nautilus-debug-log.txt
This file fills rapidly when nautilus is 100% CPU hungry.
See attached.
** Attachment added: "nautilus-debug-log.txt"
http://launchpadlibrarian.net/10111028/nautilus-debug-log.txt
--
[Gutsy] high processor activity after lo
Solution:
I have just discovered that my Keyring Manager was muddled.
This is what worked for me:
1/ restart PC & get wireless going.
2/ Goto Keyring Manager.
3/ You should see perhaps 4 entries (under the view drop-down menu choose
keyrings).
Entries will probably be "SSID name", Login", "
I can confirm this bug on two separate Feisty installations & with the
Live CD. Problem is just as described by jdo above.
It appears from the Nabble link above that unfortunately adventurous
libgphoto code got caught in feisty distribution.
Much looking forward to ubuntu upgrade for libgphoto2.
A third party source which I have used in Edgy and now Feisty is:
http://les-ejk.cz/ubuntu/
All the associated packages are up to date (Gdal, proj4 etc)
Jachym Cepicky ( http://les-ejk.cz/ ) seems to have a fair bit to do
with QGIS & Grass GIS development and I have found his packages very
reliabl
I have Ubuntu 7.04 (with the standard U7.04 Thunderbird) + latest updates.
I don't have this problem on either my desktop or laptop.
However, one of my users does have this problem. They have exactly the same
Ubuntu 7.04 installation as I do. They have slightly different hardware but
still i386.
Fixed for me. Thanks.
--
kernel Oops in unionfs with l-u-m version 2.6.22-12.32 using Edubuntu amd64
daily 200709025
https://bugs.launchpad.net/bugs/144945
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
** Attachment added: "syslog_success"
http://launchpadlibrarian.net/10106967/syslog_success
--
nm-applet (network manager) - don't remember settings
https://bugs.launchpad.net/bugs/155304
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I can confirm this also for 7.10.
This occurs for both "roaming mode" & manual setup (dhcp).
See attached syslog extracts: one for fail & one for success.
It appears that the Network Manager requests a key and is given a key
but the key appears to be incorrect.
Also, [Logout] and then [Log back
Here is another duplicate. ATI radeon 200m again.
Bug #138084
--
[Gutsy] ATI (Radeon) with pci id 1002:5a62 and Linux 2.6.22 - X will not start
https://bugs.launchpad.net/bugs/144297
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Ubuntu 7.10beta still has the same problem.
Seems to be a problem with some ATI radeon graphics.
I think this bug is a duplicate of Bug #144297
--
No screen in Asus Laptop with Feisty
https://bugs.launchpad.net/bugs/144013
You received this bug notification because you are a member of Ubuntu
Bugs
I suspect this is a duplicate of Bug #144297
Could e-r-i-k-98 report hardware specs (especially graphics card type) and
check Bug #144297
to see if it is the same problem. If e-r-i-k-98 has an ATI radeon graphics card
then it's likely to be the same bug.
--
gutsy: X server is crashing
https://
Checkout Bug #144297
Maybe the same bug. It offers a fix you could try.
--
(Gutsy beta) X server broken upon startup
https://bugs.launchpad.net/bugs/147031
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
For interest & instruction:
For ATI Radeon 200m but type RS482 [Radeon Xpress 200M] [1002:5975],
See Bug #144760
Symptoms similar but notably different - ie. gets to a login screen.
--
[RC410] Xpress 200m with pci id 1002:5a62 and Linux 2.6.22 - X will not start
https://bugs.launchpad.net/bugs/1
This is probably Bug #144760
--
Gtusy hangs after boot on HP laptop
https://bugs.launchpad.net/bugs/138184
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
See Bug #144760
--
Install - Tribe 5 CD's won't get to install GUI or Text based, x64 or i386
https://bugs.launchpad.net/bugs/136709
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
This is Bug #144760
--
[gutsy tribe-5] cannot install
https://bugs.launchpad.net/bugs/135188
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
Ubuntu doesn't detect and install my wireless orinoco_usb chipset
https://bug
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
scheduling while atomic warnings after hibernate/resume
https://bugs.launchpad.net/bugs/45861
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
currently included arcmsr module causes file corruption on amd64
https://bugs.launchpad.net/bugs/45679
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
senao nl-2511cd pcmcia - wrong driver loading
https://bugs.launchpad.net/bugs/67060
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
CPU not detected on a Compaq Proliant 3000 dual P II 400 Mhz
https://bugs.launchpad.net/bugs/64133
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
CPIA webcam support has sysfs problem
https://bugs.launchpad.net/bugs/84470
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
cryptsetup / LUKS won't work
https://bugs.launchpad.net/bugs/58102
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
Kernel race condition if nfs mounts present on real or virtual nodes [kernel
BUG at lib/radix-tree.c]
https://bugs.launchpad.net/bugs/58170
You received this bug notification bec
** Changed in: linux-source-2.6.15 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
no aic94xx support in dapper kernel
https://bugs.launchpad.net/bugs/38421
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
--
PowerBook G4 12" - Suspend to disk doesn't work
https://bugs.launchpad.net/bugs/47994
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Matthew,
Can you attach the following files:
uname -a > uname-a.log
cat /proc/version_signature > version.log
sudo lspci -vvnn > lspci-vvnn.log
Also, please attach a complete dmesg log which includes the error point (ie.
the point at which your PC display sleeps & then lock-up occurs).
Thanks.
*
Jack,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Unfortunately we can't fix it, because your description does not yet
have enough information.
Please include the following additional information, if you have not already
done so (pay attention to lspci's
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Can you supply more detailed information on the problem
you have reported (for example when does the problem occur: during boot
or does some other event trigger this?).
Please include the following additional infor
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Can you supply more detailed information on the problem
you have reported (for example when does the problem occur: during boot
or does some other event trigger this? Does it always occur or just
occasionally or jus
Wangrui,
Is there a bug number associated with this fix? Or have you just found that the
problem disappears with the Hardy kernel?
Thanks.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Incomplete
--
Ubuntu 7.10 AMD64 freeze if the buffer exceed 4GB
https://bugs.launchpad.net
Jasjeet,
This is a known issue with your laptop. See here (under section headed Sleep):
https://wiki.ubuntu.com/LaptopTestingTeam/Lenovo3000N100_0768
The issue is being dealt with in Bug #59867 (This bug covers several laptops)
Thanks.
Note: This bug is due to be marked as a duplicate of Bug #5986
Thank you for taking the time to report this bug and helping to make
Ubuntu better. More information is required.
Please follow the section on "fan issues" at
https://wiki.ubuntu.com/DebuggingACPI and report findings to this bug
report.
Also, please include the information as separate attachments
*** This bug is a duplicate of bug 59867 ***
https://bugs.launchpad.net/bugs/59867
** This bug has been marked a duplicate of bug 59867
Synaptics touchpad ceases functioning after suspend and resume.
--
The touchpad freezes everytime I restore system from standby
https://bugs.launchpad.ne
Fodder,
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Please include the following additional information, if you have not already
done so (pay attention to lspci's additional options):
1. Please include the output of the command "uname -a" in your next resp
mehurt,
Thanks for the information. I have noticed that dmesg gives two suggestions as
follows:
[0.00] ACPI: If "acpi_apic_instance=2" works better, notify [EMAIL
PROTECTED]
[ 17.702988] ACPI: Please test with "acpi_osi=!Linux"
If you are able can you try booting with these kernel boot
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete => Confirmed
--
[Gutsy] Kernel oops resulting in fan not spinning and laptop overheating
https://bugs.launchpad.net/bugs/217932
You received this bug notifi
Note to Kernel Team:
While this issue is likely to be an ACPI support issue, it appears to be
causing a Kernel oops.
Passing to Kernel Team for further assessment.
--
[Gutsy] Kernel oops resulting in fan not spinning and laptop overheating
https://bugs.launchpad.net/bugs/217932
You received this
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete => Invalid
--
Dapper flight 5: Installation hangs at formating harddisk progress
https://bugs.launchpad.net/bugs/35389
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
-
Jonathan & Tejasvi,
Does this issue occur always or just occasionally or just once only?.
Waiting on Tejasvi for Gutsy info.
Thanks.
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-source-2.6.24 => li
Lau,
OK we've checked some likely causes with no success. I think we need to move
this issue along to the Kernel Team.
However, we need to re-establish the baseline data for this bug report since
the problem was originally reported under Feisty and you now appear to be using
Hardy. The Kernel T
Thanks for the report.
Can you provide the following from your booting kernel [2.6.15]:
1. Please include the output of the command "uname -a" in your next response.
2. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the
resulting file "lspci-vvnn.log" to this bug report.
3.
*** This bug is a duplicate of bug 214810 ***
https://bugs.launchpad.net/bugs/214810
Marking as duplicate as this has been confirmed under bug 214810 and passed to
kernel team as kernel 2.6.24 bug.
If you think this assignment as a duplicate is in error then please re-mark as
NEW.
Thanks.
*
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
--
segfault at startup
https://bugs.launchpad.net/bugs/220779
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Maciej,
Older PC's require this kernel boot option. Early in ACPI development many PCs
didn't support ACPI and many that did implemented their own individual ACPI
frameworks. Consequently, if the kernel discovers an older PC (I can't recall
the cut-off date now) it disables ACPI by default. Guts
If anyone is still wishing to progress this bug report they need to take note
of Brian Murray's instructions above.
Only two people have responded to Brian's instructions and it seems that they
had different issues to that originally reported in this commentary.
** Changed in: linux-source-2.6
Harold,
If you are receiving this (or similar) error message but it appears to be
causing no ill effects then this is the bug report you are looking for:
Bug #159241
The several comments I read on the forum you linked to above indicate this is
an error message with no ill effects.
It appears fro
Dell Latitude D610 has contained a range of hardware components over the
life of the product. Graphics: ATI M300 & Intel i915GM. Wireless: Intel
Corporation PRO/Wireless 2200BG & Broadcom Corporation BCM4318. More
substantial technical information is required. Some people report this
laptop with Su
This bug commentary requires the input of substantial technical information.
See my previous comment regarding help on this matter.
Without this, the bug report cannot progress!
** Changed in: k3b (Ubuntu)
Assignee: Gareth Fitzworthington (mapping-gp) => (unassigned)
--
K3B is freez
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
Can't hibernate - Dell Latitude D610
https://bugs.launchpad.net/bugs/45804
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailin
** Also affects: acpi-support (Ubuntu)
Importance: Undecided
Status: New
** Changed in: acpi-support (Ubuntu)
Status: New => Incomplete
--
Can't hibernate - Dell Latitude D610
https://bugs.launchpad.net/bugs/45804
You received this bug notification because you are a member of Ub
Closing bug as acpi is disabled by default on older PCs (pre year 2000). ACPI
must be forced with kernel option if acpi functionality exists. Please re-mark
as NEW if you think referral to INVALID is errant.
Thanks.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete => Invali
*** This bug is a duplicate of bug 159241 ***
https://bugs.launchpad.net/bugs/159241
Marking this as a duplicate of Bug #159241 as no other comments have
been offered. If anyone thinks this referral is errant then please re-
mark this bug to NEW. Thanks.
** This bug has been marked a duplicat
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Sourcepack
Erik,
thanks for the reply.
The issue you are experiencing is clearly quite different to the bug reported
here by "clearzen".
Different CPU, chipsets and graphics.
Your issue seems to be a specific problem between the interfacing of the Ultron
UH-420 and probably your C840 chipset & BIOS. Difficu
*** This bug is a duplicate of bug 153195 ***
https://bugs.launchpad.net/bugs/153195
Marking as duplicate of Bug #153195
If anyone thinks this referral is errant then please re-mark as NEW.
Thanks.
** This bug has been marked a duplicate of bug 153195
ksoftirqd/0 always using about 30% cp
** Also affects: linux-source-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-source-2.6.24 => linux
Status: New => Incomplete
--
senao nl-2511cd pcmcia - wrong driver loading
https://bugs.launchpad.net/bugs/67060
You rece
Can anyone report on the status of this issue against later Ubuntu releases?
Confirming. Kernel Team to decide where to take this issue.
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Incomplete => Confirmed
--
cryptsetup / LUKS won't work
https://bugs.launchpad.net/bugs/58102
You re
Johannes,
Thankyou for your suggestion.
Have you examined this issue against later release LiveCDs? Are things still
the same?
Thanks.
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: New => Incomplete
** Summary changed:
- not a bug but usefull suggestion
+ LiveCD user feedback- tim
1 - 100 of 750 matches
Mail list logo
