Since the mic is showing up in the "Hardware" tab of the pulseaudio
controls, I'm also thinking this is a pulseaudio issue, and not a kernel
issue.
** Package changed: linux (Ubuntu) => pulseaudio (Ubuntu)
--
USB-Audio devices do not show up as input devices
https://bugs.launchpad.net/bugs/53685
@Robert B:
Please retest on the latest kernel. The graphics drivers in 2.6.32-16
are updated and include a lid switch fix for intel graphics too. If you
still see issues, please move the bug state to New. If you don't, please
move the bug state to Invalid.
Thanks
** Changed in: linux (Ubuntu)
@Robert B:
Also, if you still have the issue, please run 'apport-collect 519735' to
attach information on your hardware and software to this bug.
--
Booting with laptop lid closed causes black screen
https://bugs.launchpad.net/bugs/519735
You received this bug notification because you are a memb
e bug to handle the documentation.
** Changed in: linux (Ubuntu)
Importance: Medium => Wishlist
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
Please enable CONFIG_IWL3945_DEBUG
Are you able to boot into the official Ubuntu 2.6.32-16 kernel?
--
BUG: scheduling while atomic: irq/18-b43/674/0x0101
https://bugs.launchpad.net/bugs/55
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
@Dominique:
I really need a dmesg log showing the output when the device is plugged
in twice, so we can see what is output on the second plugging.
As for statically compiling the modules in, we'll need to figure out why
that fixes things. We won't be able to statically compile them into
Lucid at
all
the information as before and attach the dmesg from this kernel.
Thanks
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
[karmic] CPU load not being reported accurately
@Dominique:
Thanks for the log. I've done a diff of the two sections where you
plugged in the device to see what the difference is, please see the
attachment. I replaced memory locations with '' so the diff would
be clean. Unfortunately, I didn't find anything useful in the diff.
** Attachment ad
One other useful test would be to try the mainline kernel. We have built
kernels at http://kernel.ubuntu.com/~kernel-ppa/mainline/. Please
install the latest current kernel and test whether it functions
correctly. If it does, then we can narrow down what's wrong. If it does
not (which I'm guessing
@Kai Jauch:
The 2.6.32-16 kernel has the 2.6.33 drm (graphics drivers) stack in it.
This was done for many varied reasons, one of which is better support
for intel graphics. If you are having issues now, I suggest opening a
new bug just to keep things separate and not get too tangled up with the
f
linux (Ubuntu)
Assignee: Chase Douglas (chasedouglas) => (unassigned)
--
Misidentified HP pavilion bios fails kernel suspend
https://bugs.launchpad.net/bugs/529477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Just to be clear, the 2.6.32-16 kernel does contain the patch that fixed
the 2.6.32-15 kernel, but it does not appear to be the complete fix
anymore.
** Description changed:
The backlight of the laptop display doesn't come back on after closing
and opening the lid on a Dell Latitude E6400.
@Kai:
Please test the latest 2.6.34 mainline kernel at
http://kernel.ubuntu.com/~kernel-ppa/mainline/ to see if there's better
behavior there. If not, I suggest opening a bug at bugzilla.kernel.org
so upstream is aware of the issue. Please note the bug here if you do
open one.
Thanks
--
Screen
@Nicolò Chieffo:
Your comment about the latest intel drivers jogged my memory. There's
also the drm-intel-next kernels at the mainline ppa page that would be
useful to try it. It contains changes that haven't hit Linus' tree yet.
--
Screen backlight doesn't come on again after opening the lid
ht
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
--
echo indigo iox soundcard not recognized
https://bugs.launchpad.net/bugs/398468
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
@ThomasNovin:
There was an original bug that was fixed in pm-utils. I should have
asked people at that point to open a new bug if they still have non-
working suspend/resume on nvidia.
It's probably a good time to do that now. If you or someone else open a
new bug to track further issues with res
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/43307520/BootDmesg.txt
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/43307521/CoreDump.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/43307522/CurrentDmesg.txt
** Attachment
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Won't Fix
--
Broadcom driver no wireless
https://bugs.launchpad.net/bugs/365561
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
Public bug reported:
I think when this occurs one or both of my displays (internal LVDS and
external mini display port -> DVI) will turn off, though X thinks they
are still present.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-19-generic 2.6.32-19.28
Regression:
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/43310277/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/43310278/AplayDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/43310279/ArecordDevices.t
@Thomas:
I assume you are referring to -stable kernels from kernel.org?
Thanks
--
[K8M800] Xorg freeze / Kernel 2.6.32-10-generic freeze
https://bugs.launchpad.net/bugs/508699
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
@Martin:
This sounds like it could be partly gnome-settings-daemon misbehaving.
g-s-d performs the xrandr configuration for the gnome desktop. I've been
working on bug 484186 where g-s-d will fail to change the configuration
settings of a CRTC output. You may be seeing the same bug from the DVI
si
My initial instructions were a little wrong. Please see the instructions
at https://wiki.ubuntu.com/KernelTeam/DebuggingSchedulingWhileAtomic
Thanks
--
BUG: scheduling while atomic: swapper/0/0x1001
https://bugs.launchpad.net/bugs/555496
You received this bug notification because you are a m
My initial instructions were a little wrong. Please see the instructions
at https://wiki.ubuntu.com/KernelTeam/DebuggingSchedulingWhileAtomic
Thanks
--
BUG: scheduling while atomic: swapper/0/0x1001
https://bugs.launchpad.net/bugs/554724
You received this bug notification because you are a m
@pripps:
I haven't uploaded a new firmware package for Karmic. The package I've
asked for testing is for Lucid. As it seems everything has gone well, I
will look into backporting the changes into Karmic once they get into
Lucid.
--
dvb-usb-af9015 should be updated to the latest version to resolv
@Scott:
Great! The trace gives me good information. Unfortunately, I forgot one
important step: enabling the proper trace format. To make sure I don't
repeat the same mistake again, I wrote up the process on a wiki page.
Can you follow it and attach a new trace with the correct latency-
format?
h
My initial instructions were a little wrong. Please see the instructions
at https://wiki.ubuntu.com/KernelTeam/DebuggingSchedulingWhileAtomic
Thanks
--
BUG: scheduling while atomic: swapper/0/0x1001
https://bugs.launchpad.net/bugs/555261
You received this bug notification because you are a m
FYI, my initial instructions were a little wrong. Please see the
instructions at
https://wiki.ubuntu.com/KernelTeam/DebuggingSchedulingWhileAtomic
Thanks
--
BUG: scheduling while atomic: swapper/0/0x1001
https://bugs.launchpad.net/bugs/554266
You received this bug notification because you ar
is forward!
** Changed in: linux-firmware (Ubuntu)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
--
snd-asihpi firmware c
I was assuming that the driver for this firmware was in kernel or at
least a part of an Ubuntu package somewhere. I haven't been able to find
anything other than a link to the beta drivers tarball at [1] (the
current drivers link is broken). Is this available in an Ubuntu package
somewhere?
I'm fa
I think what's going on is the bug has already hit, which turns off the
tracing. We need to turn it back on. Before executing the steps I
mentioned, please do the following:
$ sudo sh -c "echo 1 > /sys/kernel/debug/tracing/tracing_enabled"
$ sudo sh -c "echo 1 > /sys/kernel/debug/tracing/tracing_o
@Martin:
That's too bad. g-s-d calculates its own configurations, and the fn-F7
handler sometimes gets called without the key actually being pressed
(i.e. when my laptop lid is opened and it resumes). I was hoping this
might be related to your issues. Oh well...
--
[2.6.32-19 regression] Does no
@Daniel:
Can you try the pci=nomsi option as well?
Thanks
--
[X700] KMS, amd64: Kernel panic while trying to launch system > preferences >
appearance
https://bugs.launchpad.net/bugs/544741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
@David:
Yes, I agree that the GPL statement should be removed. Eliot, any issues
with that?
--
snd-asihpi firmware could be included in linux-firmware
https://bugs.launchpad.net/bugs/557037
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ttoine:
I'm not sure where you got that impression. Can you be more specific?
The alsa-firmware package is not part of Ubuntu even, so there should be
no hard coded interaction between the two.
--
snd-asihpi firmware could be included in linux-firmware
https://bugs.launchpad.net/bugs/557037
You
@Thomas:
I'm going to upload test kernels for you to try out. Each one will help
us narrow down which change cause your problems. This process will
require about 7 or 8 kernel tests. When you have tried each one out,
please reply in this bug with whether it worked or not. The kernels can
be found
@lightrush:
Unfortunately, this time I don't think you hit the bug. The end of the
trace even shows me that the process was bzip2 :). When you hit the bug,
the end of the trace will be in the schedule_bug function. Would you
mind trying again?
I'll add the enablement lines to the wiki page now th
After conferring with others on the kernel team, it's best if we only
include firmware in linux-firmware for drivers that are provided by some
Ubuntu package. Since there does not appear to be a package providing
this driver in any of the Lucid archives, I feel we shouldn't include
the firmware in
Martin Pitt in comment #72 linked to the commit with instructions on how
to fix this issue. Polling is not disabled by default because it stops
media detection and does not cause issues for most people. Please follow
his instructions to disable polling using udev.
Note that udev has replaced hal i
@Paolo:
I am not sure why the synaptics X driver isn't picking this up. Please
open a new bug against the xserver-xorg-input-synaptics package. You can
do this through launchpad or by running 'ubuntu-bug xserver-xorg-input-
synaptics'.
Thanks
--
ALPS device (E7: 73 02 64) needs new model entry
@Thomas:
Thanks. I've just uploaded v2. Please test it out. I only need the
results of booting from power on since that's what we are really trying
to fix here.
--
[K8M800] Xorg freeze / Kernel 2.6.32-10-generic freeze
https://bugs.launchpad.net/bugs/508699
You received this bug notification bec
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Chase Douglas
(chasedouglas)
--
TouchPad buttons don't work on HP Mini 210 (1030NR)
https://bugs.launchpad.net/bugs/516329
Y
@Cloudany:
Yes, the beta 2 freeze was in place one week ago. No changes were
allowed until the release of beta 2 unless they were serious (like the
installer dying half-way through). Now that it has been released, the
freeze is lifted and we can add in more bug fixes that are less serious.
The las
I've created a test kernel with the patch Ákos Maróy posted. Please test
it out and report back on how it works. We'll need to know very soon
(within a day or two) for it to get into the 10.04 release image.
Otherwise it will need to be deferred to a release update.
http://people.canonical.com/~cn
@Thomas:
FYI, you don't need to do any more kernel testing outside of the kernels
I provide. My kernels will help us narrow down to the individual commit
that causes your issue.
--
[K8M800] Xorg freeze / Kernel 2.6.32-10-generic freeze
https://bugs.launchpad.net/bugs/508699
You received this bug
The kernel patch allows basic clicking functionality. For the true
"clickpad" functionality you describe, the X synaptics driver needs to
be involved according to the upstream linux-input mailing list.
My suggestion is that we invalidate the X synaptics bug here and that a
new bug be opened agains
@Erni35:
Your new issue is likely unrelated to this bug. Please open a new bug so
we can track it more easily. The best way is to run 'ubuntu-bug linux'.
Thanks
--
[Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI
https://bugs.launchpad.net/bugs/509273
You received this bug notif
@Daniel:
Please attach the output of lspci so I can confirm that a quirk to
disable pci msi interrupts will be in the next Lucid kernel.
Thanks
--
[X700] KMS, amd64: Kernel panic while trying to launch system > preferences >
appearance
https://bugs.launchpad.net/bugs/544741
You received this b
@Daniel:
I'm sorry, I forgot that lspci -v doesn't give the information we need.
Can you post the output of 'lspci -n instead?
What I'm looking for is specific vendor and model pci ids. We have a
quirk for specific motherboards to disable pci msi interrupts, but there
are more upstream. If you ha
That's perfect! I need to analyze this further, but at a glance it
appears to be related to the keyboard driver somehow.
Thanks!
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chase Douglas (c
@Anders:
We don't have any mechanism in place for backports of the dvb drivers.
Due to the nature of the issue, it unfortunately would not be high on
our priority list of things to do in the kernel team either.
I suggest you do one of the following, depending on your interest and
skill level:
1.
to fix his issues, I'll be sending the
patch to the kernel-team mailing list for inclusion into Lucid.
** Changed in: linux (Ubuntu Lucid)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Lucid)
Assignee: Canonical Kernel Team (canonical-kernel-team) => Ch
@Thomas:
Please test v3.
Thanks
--
[K8M800] Xorg freeze / Kernel 2.6.32-10-generic freeze
https://bugs.launchpad.net/bugs/508699
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
@lightrush:
I've uploaded a test kernel with a patch that should hopefully fix this
issue. Please download and install the packages at
http://people.canonical.com/~cndougla/555261/. Then test it out,
especially through flipping the rf switch lots of times to ensure the
bug doesn't appear. Please r
Stable Release Update Justification:
Impact of bug: On low load systems with specific work load
characteristics the load average may not be representative of the real
load. Given a specific test case it is possible to load a system with
NR_CPUS number of tasks and yet have a load avg of 0.00, thou
** Attachment added: "testcase"
http://launchpadlibrarian.net/43572858/testcase
--
[karmic] CPU load not being reported accurately
https://bugs.launchpad.net/bugs/513848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Patch added:
"0001-sched-update-load-count-only-once-per-cpu-in-10-tick.patch"
http://launchpadlibrarian.net/43572916/0001-sched-update-load-count-only-once-per-cpu-in-10-tick.patch
** Changed in: linux (Ubuntu Karmic)
Milestone: None => karmic-updates
--
[karmic] CPU load not being
I accidentally nominated this for jaunty by mistake. Please ignore.
--
[karmic] CPU load not being reported accurately
https://bugs.launchpad.net/bugs/513848
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
@lightrush:
Thanks for being so thorough! I will send the patch on to the kernel-
team mailing list so it can be reviewed and hopefully inserted into the
10.04 image before release.
A new kernel went out today (2.6.32-20), and when you install it should
upgrade your kernel to the released one. So
With Lucid, the kernel is now telling the BIOS that it supports win7
ACPI features. Part of the Win7 feature set is display configuration
changing through win+p instead of the unique key code used by previous
versions of windows. The real problem here is that gnome-settings-
daemon, the process tha
@Sennaista and @Erni35:
Both of you have separate bugs from this one. Please open new bugs for
these issues.
Thanks
--
[Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI
https://bugs.launchpad.net/bugs/509273
You received this bug notification because you are a member of Ubuntu
Bu
Now that I see the driver is available in l-b-m-alsa shipped in the main
section, I think this firmware is suitable for linux-firmware. I will
work to get it into 10.04, but I don't think it will get in before the
release.
** Changed in: linux-firmware (Ubuntu)
Status: Won't Fix => Triaged
Now that I see the driver is available in l-b-m-alsa shipped in the main
section, I think this firmware is suitable for linux-firmware. I will
work to get it into 10.04, but I don't think it will get in before the
release.
--
snd-asihpi firmware could be included in linux-firmware
https://bugs.la
Now that I see the driver is available in l-b-m-alsa shipped in the main
section, I think this firmware is suitable for linux-firmware. I will
work to get it into 10.04, but I don't think it will get in before the
release.
--
snd-asihpi firmware could be included in linux-firmware
https://bugs.la
@Slimfat and @Marius:
Have you tested the kernel I provided? The patch is not in any Ubuntu
released kernels because it hasn't seen sufficient testing and success
reports.
Thanks
--
WARNING: at /build/buildd/linux-2.6.32/net/wireless/core.c:614
wdev_cleanup_work+0xa7/0xd0 [cfg80211]()
https://
@dl.zerocool:
The -16 kernel is a bit old now. Perhaps the dependency has been fixed
in a newer kernel. I will build a new kernel with the patch. I'll reply
when it's available.
Thanks
--
WARNING: at /build/buildd/linux-2.6.32/net/wireless/core.c:614
wdev_cleanup_work+0xa7/0xd0 [cfg80211]()
ht
x27;s called twice like this.
** Changed in: linux (Ubuntu)
Assignee: Andy Whitcroft (apw) => Chase Douglas (chasedouglas)
--
Cannot switch Monitor configuration CRTC 58
https://bugs.launchpad.net/bugs/484186
You received this bug notification because you are a member of Ubuntu
Bugs,
Gnome-settings-daemon is receiving two input events in a very short
amount of time from the kernel. The input events are basically fn-F7, or
"change my display output configuration". Unfortunately, these events
are coming in reverse order, so the timestamps go backwards. The input
timestamps are fe
I've uploaded a new kernel based on the 2.6.32-19 kernel. Please install
it and test.
Thanks
--
WARNING: at /build/buildd/linux-2.6.32/net/wireless/core.c:614
wdev_cleanup_work+0xa7/0xd0 [cfg80211]()
https://bugs.launchpad.net/bugs/528688
You received this bug notification because you are a mem
** Branch linked: lp:~chasedouglas/ubuntu/lucid/gnome-settings-daemon
/CRTC-fix
--
Cannot switch Monitor configuration CRTC 58
https://bugs.launchpad.net/bugs/484186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: gnome-settings-daemon (Ubuntu)
Milestone: None => ubuntu-10.04
--
Cannot switch Monitor configuration CRTC 58
https://bugs.launchpad.net/bugs/484186
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
@Arturas K:
Unfortunately, the oops message in your picture was cut off. Is the full
oops message in /var/log/messages? If so, can you attach it as well?
Thanks
--
[X700] KMS, amd64: Kernel panic while trying to launch system > preferences >
appearance
https://bugs.launchpad.net/bugs/544741
Yo
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
[K8M800] Xorg freeze / Kernel 2.6.32-10-generic freeze
https://bugs.launchpad.net/bugs/508699
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
@Anders:
I wrote the wrong command to install the updated linux-firmware-nonfree
package. The third command should be:
$ sudo apt-get install linux-firmware-nonfree
That will install the package if it wasn't already installed, and it
will upgrade it if it was. Please try this and retest.
Thanks
In the 2.6.32-19 kernel a patch went it to disable lid switch usage for
all gpus of both i915 generation 2 and 3 [1]. Please test this kernel
out to see if it fixes your issue.
Thanks
[1] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
lucid.git;a=commitdiff;h=02cf17d29ec2b659b7e058318721a1ad980d9b
@Nicholas Christian Langkjær Ipsen:
Please don't assign anyone else to bugs. Assignments mean that a
specific person is actively working on a fix, and it's not fair to them
to assign a bug without their knowledge. The best approach is to ensure
that the person is subscribed to a bug. They will be
@Anders:
Yep, I made a mistake in that version. I've updated it and tested it out
again. The new package has been pushed to my ppa as version 1.8~ppa2.
Please do the following and then retest:
$ sudo apt-get update
$ sudo apt-get install linux-firmware-nonfree
Thanks
--
dvb-usb-af9015 should b
@Lollerke:
Where did you get 0001-PCI-quirks-disable-msi-on-AMD-rs4xx-internal-gfx-
br.patch?
--
[Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI
https://bugs.launchpad.net/bugs/509273
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Tom Louwrier:
Since you seem to be having a different issue compared to others in this
bug, I suggest opening a new bug for it. It's easier to track issues
when we work on only one issue per bug report.
Thanks
--
[Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI
https://bugs.lau
@Arturas K:
Can you try booting with the cmdline option pci=nomsi? There are reports
that this can solve instability in certain motherboards.
Thanks
--
[X700] KMS, amd64: Kernel panic while trying to launch system > preferences >
appearance
https://bugs.launchpad.net/bugs/544741
You received t
Due to the positive reports in comments #15, #16, and #17 I have sent
the patch to the kernel-team mailing list for inclusion in 10.04 LTS. It
is not likely to make it in for the release image, but it should make it
into the first update release.
--
WARNING: at /build/buildd/linux-2.6.32/net/wire
I'd prefer to leave this bug unduplicated, since I've been following
this bug and will be working on it shortly.
Thanks
** This bug is no longer a duplicate of bug 527890
ALPS touchpad in HP Mini 311 not configurable/recognized as a touchpad
--
Alps touchpad is recognized but neither gsynapt
J, McDonald:
Just so you know, marking bugs as duplicates is generally a good thing
and helps keep bugs manageable. Definitely keep doing what you're doing.
It's just that in this case, I have a history with this bug, so I want
to work through things here. If this is marked as a duplicate, it gets
That's fantastic! I'm sorry I hadn't sent out a new image to test yet. I
was at a conference this past week. I hope things are all fixed for you.
I'll mark the bug as Fixed. If you find that it isn't, you can change it
back to Triaged.
Thanks
** Changed in: linux (Ubuntu)
Status: Incomplet
@Anders:
Unfortunately, the Lucid driver does not support your tuner card. It
does look like there is a patch to the driver that would enable
functionality, but at this point we can't include this patch into Lucid
due to the possibility of introducing regressions for others. You should
be able to
@toad:
Can you explain what you did to make your card work for you? Did you
install my updated linux-firmware-nonfree package or did you manually
install some firmware?
Thanks
--
dvb-usb-af9015 should be updated to the latest version to resolve some issues
https://bugs.launchpad.net/bugs/458444
@Thomas:
Can you be a little more specific about this handler you are talking
about? Are you speculating as to what is going on, or do you have some
more details?
What we really need is to find out what changes caused this behavior.
Can you help me perform a git bisect as I requested in comment #
@toad:
Can you move out your firmware and install my linux-firmware-nonfree
package? We need to be sure the firmware in my package is working right
before we publish it, if possible.
Thanks
--
dvb-usb-af9015 should be updated to the latest version to resolve some issues
https://bugs.launchpad.n
@toad:
If you want to revert the package you can do the following:
$ sudo apt-get install ppa-purge
$ sudo ppa-purge ppa:chasedouglas/linux-firmware-nonfree
If you really wanted to, you could get rid of ppa-purge after you are
done with it:
$ sudo apt-get remove ppa-purge
but that's not really
I've uploaded a test kernel to
http://people.canonical.com/~cndougla/509273. It includes the patch
Lollerke attached, which disables pci msi interrupts for specific
systems. Anyone who had their issues fixed with the pci=nomsi boot
option should try this kernel to see if it works without the boot
o
** Changed in: linux (Ubuntu Lucid)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
--
[Lucid] Radeon Xpress 200M needs PCI quirk to fix or disable MSI
https://bugs.launchpad.net/bugs/509273
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Guilherme:
I've uploaded a test kernel to http://people.canonical.com/545039/.
Please install it and test it out. When the bug occurs, hopefully we
will see some output in dmesg that will help us diagnose the mutex
issue. It isn't guaranteed that any useful data will be output though,
so this is
** Changed in: ubuntu
Status: New => Invalid
--
[needs-packaging] rinputd in universe
https://bugs.launchpad.net/bugs/518268
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
I've uploaded a fixed version of gnome-settings-daemon to my ppa at
ppa:chasedouglas/gnome-settings-daemon. Please test it out by doing the
following:
$ sudo add-apt-repository ppa:chasedouglas/gnome-settings-daemon
$ sudo apt-get update
$ sudo apt-get install gnome-settings-daemon
Ensure this in
@Scott:
The oops text normally contains data we need to debug the issue.
However, for these bugs the data is useless. To get the data we need,
please do the following:
$ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer"
Trigger the bug, then capture the trace output:
$ cat /
@Matt:
The oops text normally contains data we need to debug the issue.
However, for these bugs the data is useless. To get the data we need,
please do the following:
$ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer"
Trigger the bug, then capture the trace output:
$ cat /s
This looks to be a bug with your wireless card driver. Unfortunately,
the driver for your card is proprietary and closed source. We don't have
a way to debug and support this driver. Thus, I am closing this bug as
Won't Fix.
** Changed in: linux (Ubuntu)
Status: New => Won't Fix
--
BUG: E
@lightrush:
The oops text normally contains data we need to debug the issue.
However, for these bugs the data is useless. To get the data we need,
please do the following:
$ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer"
Trigger the bug, then capture the trace output:
$ c
@David:
The oops text normally contains data we need to debug the issue.
However, for these bugs the data is useless. To get the data we need,
please do the following:
$ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer"
Trigger the bug, then capture the trace output:
$ cat /
@Anthony:
The oops text normally contains data we need to debug the issue.
However, for these bugs the data is useless. To get the data we need,
please do the following:
$ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer"
Trigger the bug, then capture the trace output:
$ cat
301 - 400 of 2064 matches
Mail list logo
