Hi Jarmo,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.472 seconds. I'm setting this
to
Hi DaDo,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.790 seconds. I'm setting this
to
Hi syldeb35,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 64.120 seconds. I'm setting this
Hi Valder,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 31.452 seconds. I'm setting this
to
Hi luarwo,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.184 seconds. I'm setting this
to
Hi Hans-Christian,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.092 seconds. I'm setting
Hi dan,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 30.680 seconds. I'm setting this
to
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi Tony,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded.
Hi Trevor,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 14.440 seconds. I'm setting this
to
Hi Michael,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.600 seconds. I'm setting this
to
Hi Tony,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.860 seconds. I'm setting this
to
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi tajreed,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded.
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi wodam,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded.
Hi Matthew,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 63.508 seconds. I'm setting this
to
Hi Janderson,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.460 seconds. I'm setting this
Hi mooglinux,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 12.010 seconds. I'm setting this
Hi groetz,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.930 seconds. I'm setting this
to
Hi dan,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 31.350 seconds. I'm setting this
to
Hi santa,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 14.330 seconds. I'm setting this
to
Hi Valder,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 31.452 seconds. I'm setting this
to
Hi Kevin,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.450 seconds. I'm setting this
to
Hi tajreed,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.640 seconds. I'm setting this
to
Hi Richard,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 13.000 seconds. I'm setting this
to
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi it.henrik,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded.
Hi Dean,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 12.460 seconds. I'm setting this
to
Hi Juan,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 60.970 seconds. I'm setting this
to
Hi Johnwatkinson,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.728 seconds. I'm setting
Hi Spartan117,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.660 seconds. I'm setting this
Hi Hurin,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.650 seconds. I'm setting this
to
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi Chris,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded.
Hi Flittermice,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.988 seconds. I'm setting
Hi Ian,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.730 seconds. I'm setting this
to
Hi Vítor,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 15.744 seconds. I'm setting this
to
Hi Brandon,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.640 seconds. I'm setting this
to
Hi David,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 12.020 seconds. I'm setting this
to
Hi Roch,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.600 seconds. I'm setting this
to
Hi Roch,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.600 seconds. I'm setting this
to
*** This bug is a duplicate of bug 464552 ***
https://bugs.launchpad.net/bugs/464552
Hi Steve,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based
Hi Lukasz,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 10.050 seconds. I'm setting this
to
Hi Jan,
The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.380 seconds. I'm setting this
to
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/751689
Title:
Thinkpad x201* overheats due to slow fans when on 'auto'
--
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/634487
Title:
t1.micro instance hangs when installing java
--
ubuntu-bugs
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/539467
Title:
SATA link power management causes disk errors and corruption
--
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595896
Title:
Thinkpad SL510 Mute button not working
--
ubuntu-bugs mailing
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
** Changed in: linux (Ubuntu Natty)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/588715
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/549447
Title:
eGalax touchscreen configured as tablet
--
ubuntu-bugs mailing
Fix Releasing as this seems to have been fixed.
~JFO
** Changed in: linux (Ubuntu Natty)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/733805
Title:
[powerpc]
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/626622
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/751634
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/747707
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744163
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739277
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734051
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/733223
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/757242
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/754781
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** This bug has been marked a duplicate of bug 746717
WARNING: at
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/752012
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764340
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760494
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760173
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/765557
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764977
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** Summary changed:
- 9] [ cut here ]
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Tags removed: regression-proposed
** This bug has been marked a duplicate of bug 746717
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
natty has no proposed candidates ergo, this cannot be a regression-
proposed bug. Removing the tag.
~JFo
** Summary changed:
- 8051] [ cut here ]
+ WARNING: at
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
** This bug has been marked a duplicate of bug 746717
WARNING: at /build/buildd/linux-2.6.38/net/sched/sch_generic.c:256
dev_watchdog 0x213/0x220()
* You can subscribe to bug 746717 by following this
*** This bug is a duplicate of bug 746717 ***
https://bugs.launchpad.net/bugs/746717
** This bug has been marked a duplicate of bug 746717
WARNING: at /build/buildd/linux-2.6.38/net/sched/sch_generic.c:256
dev_watchdog 0x213/0x220()
* You can subscribe to bug 746717 by following this
** Tags added: kernel-key
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Natty)
Importance: Low
Status: Fix Released
** Tags removed: needs-upstream-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
milestoned for Natty updates.
~JFo
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/754712
Title:
[Lenovo L420] System unable
marking Won't Fix for Natty, but the Oneiric task will remain. We will
evaluate for a fix for SRU if a viable patch is found.
~JFo
** Changed in: linux (Ubuntu Natty)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
smoser,
Is this still an issue for you in Natty? Also, does the pm-utils
workaround work for you?
Folks,
This bug has become unmanageable and has grown way past its initial
report. As such, if you feel you are affected by this or a very similar issue,
please file new unique bugs
** Changed in: linux (Ubuntu Natty)
Milestone: None = natty-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/751471
Title:
[Lenovo T410] Microphone mute key does not fuction
--
Benjamin Meeusen,
I'm interested in your current testing of this issue. Have the recent
Natty updates resolved the issue for you?
Thanks!
~JFo
** Changed in: linux (Ubuntu Natty)
Status: Triaged = Incomplete
** Tags added: kernel-key
--
You received this bug notification
Set Natty task Won't Fix. We will review potential fixes and SRU where
applicable.
Thanks!
~JFo
** Changed in: linux (Ubuntu Natty)
Status: In Progress = Won't Fix
** Description changed:
- Recently upgraded from 10.04LTS to 10.10 Beta on a Samsung N150 NetBook.
- Since update, my
Keng-Yü Lin,
Does it look like this will land in time for natty-updates? I'd like to
milestone this appropriately for the release team.
Thanks!
~JFo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Scott,
Have you had the chance ti test this against the latest?
Thanks!
~JFo
** Changed in: linux (Ubuntu Natty)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Matt,
Thanks for the screenshot of the apport error. I'll look into that.
On the issue reported in this bug, did you see the error more than once
or is is a recurring issue? In the past we have encountered this issue,
but in the majority of cases it is benign. The usual case is that a
patch
ubuntic,
If you test this with a mainline kernel, as outlined here:
https://wiki.ubuntu.com/KernelTeam/MainlineBuilds, do you still see this issue?
We'd like to use this to narrow what could be a regression. Please report back
here and set the bug to confirmed state.
Thanks!
~JFo
**
Micah,
From our IRC conversation and the quick chat with TGardner, I am curious
where this version of aufs is coming from. Any idea if it was a required
install for something else?
I'm going to inquire with our resident aufs expert when he is available,
but in the meantime, would you mind
Jo,
If you test against a mainline kernel as outlined here:
https://wiki.ubuntu.com/Kernel/MainlineBuilds do you see the same behavior?
Also, please run 'apport-collect linux 763992 for us to get environment
information. Once you complete these tasks, please set the bug status to
Matt,
Is this from the same install as your earlier bug or is this a different
attempt? Is this a consistently recurring oops? Once you respond with the
requested information, please set the bug status back to confirmed.
Thanks!
~JFo
** Changed in: linux (Ubuntu)
Status: New =
deepud,
Is this an issue in the current development branch (natty)? Also, if you
test against the mainline kernel as outlined here:
https://wiki.ubuntu.com/Kernel/MainlineBuilds is the behavior still present?
And last, do you happen to recall when you first started seeing this issue or
is
reassigning to skype as the GPF doesn't really give the kernel team much
to go on. Best that this get investigated by the skype team. Let me know
if you think this is in error.
Thanks!
~JFo
** Package changed: linux (Ubuntu) = skype (Ubuntu)
--
You received this bug notification because you
Juan,
Do you see this same behavior when you test the mainline kernel as outlined
here: https://wiki.ubuntu.com/Kernel/MainlineBuilds? Once you complete the test
and provide the requested feedback, please set this bug's status to Confirmed.
Thanks!
~JFo
** Changed in: linux (Ubuntu)
701 - 800 of 22237 matches
Mail list logo
