The apparmor stack has been updated in version 2.6.32-16. Please test
using the new kernel. If you are unable to reproduce the issue, mark the
bug as invalid. Otherwise, please set the bug to "Confirmed" again.
Thanks
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in:
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
--
BUG: Bad page map in process aptd pte:88003c521330 pmd:5404b067
https://bugs.launchpad.net/bugs/529210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The graphics drivers, where this bug occurred, have been updated
starting with the 2.6.32-16 kernel. Please retest this or a newer
kernel. If you can reproduce this issue, please set the bug to
confirmed. If you cannot reproduce this issue, please move the bug to
invalid.
Thanks
** Changed in: li
The graphics drivers, where this bug occurred, have been updated in
version 2.6.32-16. Please test using the new kernel. If you are unable
to reproduce the issue, mark the bug as invalid. Otherwise, please set
the bug to "Confirmed" again.
Thanks
** Changed in: linux (Ubuntu)
Status: New =
The graphics drivers, where this bug occurred, have been updated in
version 2.6.32-16. Please test using the new kernel. If you are unable
to reproduce the issue, mark the bug as invalid. Otherwise, please set
the bug to "Confirmed" again.
Thanks
** Changed in: linux (Ubuntu)
Importance: Undec
The graphics drivers, where this bug occurred, have been updated in
version 2.6.32-16. Please test using the new kernel. If you are unable
to reproduce the issue, mark the bug as invalid. Otherwise, please set
the bug to "Confirmed" again.
Thanks
** Changed in: linux (Ubuntu)
Status: New =
The graphics drivers, where this bug occurred, have been updated in
version 2.6.32-16. Please test using the new kernel. If you are unable
to reproduce the issue, mark the bug as invalid. Otherwise, please set
the bug to "Confirmed" again.
Thanks
** Changed in: linux (Ubuntu)
Status: New =
The graphics drivers, where this bug occurred, have been updated in
version 2.6.32-16. Please test using the new kernel. If you are unable
to reproduce the issue, mark the bug as invalid. Otherwise, please set
the bug to "Confirmed" again.
Thanks
** Changed in: linux (Ubuntu)
Status: New =
Colin,
I can't tell from lspci (and I'm not sure from procCpuinfo cause I can't
find what the model and family numbers are) whether this is an arrandale
system, but it looks like the TSC issue you've been working on. Does
this look like the same bug to you?
--
[1266874882.415546] BUG: soft locku
The graphics drivers, where this bug occurred, have been updated in
version 2.6.32-16. Please test using the new kernel. If you are unable
to reproduce the issue, mark the bug as invalid. Otherwise, please set
the bug to "Confirmed" again.
Thanks
--
BUG: unable to handle kernel paging request at
Nevermind, I see this is a bug found in the -16 kernel already.
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
BUG: unable to handle kernel paging request at 21b0001c
https://bugs.launchpad.net/bugs/534765
You receive
@Martin-Éric Racine:
Can you explain in more detail what you mean by "KMS no longer works"?
What symptoms are you seeing?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
KMS broken since 2.6.32-16-generic
https:
@ruud:
This bug is caused by the graphics driver. How reproducible is this bug?
I suggest openning a bug upstream at bugs.freedesktop.org. When you do
so, please report back with the bug url here so we can link the two
bugs.
Thanks
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
@Truxpin:
If you still have Windows around, you may want to try booting into it to
see if you can enable wifi in windows. Maybe the windows driver can
unblock the hard block somehow? You should also double check your bios,
as there may be a switch in there for wireless.
--
ifconfig returns SIOCS
@Everyone:
First, everything in this bug looks to be hardware related due to all
the rfkill issues. The issues are not related to Lucid or Karmic or any
other Linux, unfortunately. Because of this, I am moving the bug state
to Invalid so that it is removed from the bugs we are tracking as
regressi
ware-nonfree (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
** Changed in: linux-firmware-nonfree (Ubuntu)
Status: Triaged => In Progress
--
cx24116 firmware doesn't load - firmware corrupt
https://bugs.launchpad.net/bugs/363682
You received this bug notificat
@Thomas:
Have you tried removing plymouth yet? Because of the instability of
plymouth, we really need to know if that's the cause of this issue or if
there's some other cause.
Thanks
--
[K8M800] Xorg freeze / Kernel 2.6.32-10-generic freeze
https://bugs.launchpad.net/bugs/508699
You received th
@dave945:
Something odd is going on here. In the first dmesg where things began to
work, the -2 firmware wasn't found and the following was output:
Feb 27 22:45:43 tabord-laptop kernel: [ 12.817604] iwlagn :03:00.0:
firmware: requesting lbm-iwlwifi-5000-2.ucode
Feb 27 22:45:43 tabord-laptop
@TDB:
I'll only make this comment once. The issues outlined in this bug seem
to be hardware issues. We have diagnosed them down to hard blocks in the
hardware that are keeping wifi from being enabled. There is nothing that
can be done from within linux of any form to turn off a hard block. If
the
I'm perplexed. Maybe firmware.sh isn't getting called? I just noticed
that there's a recent update to udev that fixes a potential issue with
hotplug support. Can you ensure you are running the latest udev package?
It should be version 147~-6.1.
--
e100: eth0: e100_request_firmware: Failed to load
@austin_is:
I'm still stumped, but the one difference I see in my system and yours
(I don't have e100, so I can't compare exactly) is that I don't have any
firmware in /lib/firmware. My firmware files exist only under the
/lib/firmware/`uname -r`/ directory. I don't think that removing the
firmwar
After you tried reloading the firmware, more messages should have shown
up in your /var/log/syslog. Can you paste them here? Maybe some
different output resulted?
--
e100: eth0: e100_request_firmware: Failed to load firmware "e100/d101m_ucode.bin
https://bugs.launchpad.net/bugs/530348
You receive
@Nicolás Lichtmaier:
The scaling_max_freq parameter is settable:
$ sudo sh -c "echo [frequency] >
/sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_max_freq"
My guess is that some software is intentionally limiting your cpu
frequency because you hit an internal processor temperature that is too
high.
@austin_is:
Please run 'udevadm monitor --property' and capture the output as you
run 'rmmod e100 && modprobe e100 && ifconfig eth0 up'. Paste the output
of udevadm here. This should show us an event being passed up from the
kernel to initiate a firmware load.
--
e100: eth0: e100_request_firmwar
Have you used ubuntu on this machine before without this issue? It helps
us to know if this is a bug that was present in previous releases.
--
hp tx2 restarts on shut down
https://bugs.launchpad.net/bugs/530317
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
This is the failing part from VarLogDistupgradeApttermlog.gz:
Instellen van linux-image-2.6.32-14-generic (2.6.32-14.20) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.32-14-generic
Running postinst hook script /usr/sbin/update-grub.
head: kan `/boot/grub/video.lst’ niet ope
Google translate tells me that everything started failing because
update-grub couldn't find /boot/grub/video.lst.
--
package linux-image-2.6.32-14-generic 2.6.32-14.20 failed to install/upgrade:
https://bugs.launchpad.net/bugs/528931
You received this bug notification because you are a member of
Are you able to reproduce this issue?
--
BUG: Bad page map in process aptd pte:88003c521330 pmd:5404b067
https://bugs.launchpad.net/bugs/529210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Package changed: linux (Ubuntu) => grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Medium
--
package linux-image-2.6.32-14-generic 2.6.32-14.20 failed to install/upgrade:
https://bugs.launchpad.net/bugs/528931
You received this bug notification because you are a memb
What that shows us is that udev is receiving the proper events for
firmware uploading from the kernel. Now, lets find out what udev is
doing with them. Execute the following:
1. sudo udevadm control --log-priority debug
2. tail -f /var/log/syslog > udev.log
3. (in another terminal) rmmod e100 && m
I got mixed up in this bug report. Part of the problem is that there are
many rfkill issues on different hardware. I was working with Truxpin for
a while, and his issue is different than the original issue reported in
this bug. So we need to clean things up a bit to ensure we have
everything handle
@dave945:
I'm not real sure what the best way forward is now. You can try various
combinations of firmware and drivers to see if any work, and if you find
anything be sure to let us know. The latest compat-wireless tree may
include some fixes that affect you. Some newer drivers can be found in
the
@Thomas:
Can you try a kernel from the "red" ppa:
https://launchpad.net/~apw/+archive/red. It has backported graphics
drivers from 2.6.33 that may make a difference for you. We're currently
evaluating whether to ship the current kernel or this kernel.
Thanks
--
[K8M800] Xorg freeze / Kernel 2.6
I'll still try to help you with your issue, but I'm marking this as
invalid as it's a custom udev rule that's causing issues. The purpose of
marking it as invalid is to keep our bug report counts against Ubuntu as
accurate as possible.
** Changed in: linux-firmware (Ubuntu)
Status: Incomple
Try this for your rule instead:
ENV{ID_SERIAL_SHORT}=="9QM42EXK", ACTION=="add",
RUN="/usr/local/bin/backup %k%n drive1"
>From the udev man page:
The following key names can be used to match against device
properties. Some of the keys also match against properties of the parent
devices in
Public bug reported:
Binary package hint: grub2
I booted from the latest Lucid Netbook iso today. Everything seemed
good, so I went to install using ubiquity. The installation went
smoothly until the grub installation at the end. It hung with the
caption "Looking for other operating systems..." f
I'll take a look at this issue (though probably tomorrow as its near the
end of the day for me). This likely fell through the cracks as we are
working on regression bugs for Lucid.
--
dell 1557 special key
https://bugs.launchpad.net/bugs/465250
You received this bug notification because you are a
Doh! Should have looked closer. It's been committed to the kernel
sources for Karmic, but after the -20 kernel was pushed to -proposed. It
will be in the -21 kernel. I'm not sure what the timeline is for that
kernel. Stefan Bader would know more about that.
--
dell 1557 special key
https://bugs.l
@mythterious:
The random lockups with nForce Ethernet are unrelated to this message.
This message appears when you try to use the legacy hardware monitoring
driver for your motherboard with a newer kernel. The newer kernel is
guarding against instability by preventing two drivers from trying to
ta
This new system is confirmed defective (stuck F12 key). I have no clue
whether this could cause the issue I saw, but I'm invalidating the bug
anyways because it will be too difficult to determine the root cause
with the defective keyboard.
** Changed in: grub2 (Ubuntu)
Status: New => Invali
Per's test on the latest kernel gives us some good information. On top
of that, we have made a decision to base Lucid on the 2.6.32 kernel, but
with the drm stack backported from 2.6.33. The first official kernel
with the .33 drm stack has yet to be released, but there is a test
kernel available in
Per's test on the latest kernel gives us some good information. On top
of that, we have made a decision to base Lucid on the 2.6.32 kernel, but
with the drm stack backported from 2.6.33. The first official kernel
with the .33 drm stack has yet to be released, but there is a test
kernel available in
We have a new patch slated for Lucid that will time how long each device
takes to resume (for example, nvidia binary graphics can take 5 s to
resume, while other devices may take milliseconds). Unfortunately, the
patch is not yet available in any lucid kernel (it will be in the next
lucid kernel th
*** This bug is a duplicate of bug 528688 ***
https://bugs.launchpad.net/bugs/528688
** This bug has been marked a duplicate of bug 528688
WARNING: at /build/buildd/linux-2.6.32/net/wireless/core.c:614
wdev_cleanup_work+0xa7/0xd0 [cfg80211]()
--
WARNING: at /build/buildd/linux-2.6.32/net
*** This bug is a duplicate of bug 528688 ***
https://bugs.launchpad.net/bugs/528688
** This bug has been marked a duplicate of bug 528688
WARNING: at /build/buildd/linux-2.6.32/net/wireless/core.c:614
wdev_cleanup_work+0xa7/0xd0 [cfg80211]()
--
WARNING: at /build/buildd/linux-2.6.32/net
*** This bug is a duplicate of bug 488720 ***
https://bugs.launchpad.net/bugs/488720
** This bug has been marked a duplicate of bug 488720
Suspend/resume with nvidia driver fails
--
Need to VT-switch after resume from suspend to get display to work
https://bugs.launchpad.net/bugs/532177
Y
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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
We've seen this issue a few times from a few people now. I think I may
have a fix
(http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c0ce77b8323c1a0d4eeef97caf16c0ea971222a9),
but I'm not positive. I can build a test kernel with the fix, but we
need a way to properly test
inux (Ubuntu Lucid)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
--
Suspend/resume with nvidia driver fails
https://bugs.launchpad.net/bugs/488720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
--
i need drivers for my notebook sony vaio vpceb1j1e/wi
https://bugs.launchpad.net/bugs/532021
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Basically your laptop is a very new system that is based on Intel's
"Arrandale" architecture. There is not support for it out of the box on
Karmic. There will be support in Lucid. I will try to get more
information on if/when your system will be supported on Karmic.
Thanks
** Package changed: lin
@Jono:
Please try the upstream mainline kernel to see if it's any better.
Packages can be found at: http://kernel.ubuntu.com/~kernel-
ppa/mainline/. Please try the latest 2.6.33 kernel.
If that doesn't help, the next thing to try would likely be asking for
support from the linux wireless communit
@jsweiss:
Thanks for that input. There are often issues with various combinations
of wireless cards and routers. That's something we should always keep in
mind when we are working on wireless issues. I'm sure others have brands
they like, but I try to use Apple routers personally because they seem
@dave945:
Can you try what jsweiss has tried? First, trying to use WPA2-PSK using
AES, and then trying other routers if possible?
--
Intel iwlagn driver hangs from time to time
https://bugs.launchpad.net/bugs/518196
You received this bug notification because you are a member of Ubuntu
Bugs, whic
er look
at this.
** Changed in: kernel-package (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
** Changed in: kernel-package (Ubuntu)
Status: New => Triaged
** Changed in: kernel-package (Ubuntu)
Importance: Undecided => Medium
--
make-kpkg --initrd debian [o
I've uploaded a kernel to http://people.canonical.com/~cndougla/505474/.
The kernel contains the fix for alps that is included in Lucid. I don't
expect it to work here though, since Lucid doesn't appear to work.
However, it has some debugging output enabled. Please install and run
the kernel. Captu
It would be helpful if someone could follow the instructions provided by
Tim in comment #13 and attach the appropriate dmesg logs.
Also, there may be fixes in the latest 2.6.34 kernel that is being
developed. If someone could test out the Ubuntu mainline package for
that kernel it may help us find
I've uploaded a new kernel to
http://people.canonical.com/~cndougla/505474/alps2. This kernel adds
support for the alps device that zK has according to his dmesg. There
are a few options that I had to guess at, so I'm hoping they are
correct. For instance, I had to guess that it has both a trackpad
@Mary:
I did get your lshal output (it's attached to this bug now). Since you
don't have an eraserhead/stick, I think you have a different model of
alps touchpad. Please attach a dmesg log by running "dmesg > dmesg.txt"
and attaching it to this bug.
Thanks
--
Alps touchpad not recognized, defau
@zk:
OK, we're getting somewhere then. Can you try out the buttons and stick
(to generate log messages) and then post your dmesg from this new
kernel? It may have some output in it from when you tried to use the
other buttons and stick but they failed.
Thanks
--
Alps touchpad not recognized, de
@lavinog:
Because of the nature of suspend/resume issues, your issue is likely to
be due to a different cause than the original submitter's. Please search
for a suspend/resume issue dealing with the radeon driver, or open a new
one if you can't find one.
Thanks
--
No longer able to resume from
@Mary:
As I suspected, your ALPS device is different than zK's. Please open a
new bug report for your device and include all the apport information
along with it. You can do this by running "ubuntu-bug -p linux". I'd
suggest a title for the bug report like: "ALPS device (E7: 73 02 64)
needs new mo
** Tags added: karmic lucid
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Wishlist
--
ALPS device (E7: 73 02 64) needs new model entry in alps.c
https://bugs.launchpad.net/bugs/545307
You received this bug notification beca
** Tags added: karmic lucid
--
Alps touchpad not recognized, defaults to macintosh mouse button emulation
https://bugs.launchpad.net/bugs/505474
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
@tgabi:
Can you be more specific? If things are working correctly, then great.
Otherwise, I'll need more information.
--
[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 sub
I've done some debugging of this issue. This seems to be a poor
interaction between lid closure and suspend. If you run pm-suspend (or
send the dbus signal the gnome-power-manager uses when it detects a lid
closure), my laptop resumes fine both by using the power button and by
closing and opening t
Setting the nouveau param ignorelid to 1 fixes things for me. I'd be
interested to hear if it fixes things for others. I'm going to try to
figure out what the best solution to this is.
--
No longer able to resume from suspend with the Lucid kernel
https://bugs.launchpad.net/bugs/523072
You receiv
me. I sent
the patch to sta...@kernel.org and to the Ubuntu kernel team mailing
list.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New =&g
.S.: I may know how to get your "stick" working as well, but I'll wait
for feedback on your buttons before I spin a new kernel.
Thanks
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
** Changed in: linux (Ubuntu)
Status: Triaged =>
Public bug reported:
Binary package hint: indicator-me
I upgraded from Karmic to Lucid today. I found that the indicator-me
package was missing. After installing the package and logging back in,
the Me Menu was there.
My upgrade experience was not too smooth because update-manager crashed
at one
Public bug reported:
Binary package hint: rhythmbox-ubuntuone-music-store
I upgraded to Lucid from Karmic today. The rhythmbox-ubuntuone-music-
store package was not installed during the upgrade.
I had some issues with the upgrade: update-manager crashed once, and
qemu-common failed to install.
@zK:
I've uploaded a new test kernel to
http://people.canonical.com/~cndougla/505474/alps3. I'm hoping this will
enable both the stick and the upper two buttons. Please test it out and
report back.
Thanks
--
Alps touchpad not recognized, defaults to macintosh mouse button emulation
https://bugs
I've uploaded a kernel for folks to test. Hopefully it will enable
proper synaptics support for these alps devices, but there are a few
options. If any of them fail to work, we'll have to try a different
option. The kernel can be found at:
http://people.canonical.com/~cndougla/545307/lp545307_1/
T
@zK:
Anything interesting in the dmesg? I wouldn't mind seeing the output of
dmesg | grep -i alps. If the output is too large you can attach it to
the bug.
Thanks
--
Alps touchpad not recognized, defaults to macintosh mouse button emulation
https://bugs.launchpad.net/bugs/505474
You received th
OOPS! I built the wrong type of kernel for you. I'll upload a new
version in a bit.
--
ALPS device (E7: 73 02 64) needs new model entry in alps.c
https://bugs.launchpad.net/bugs/545307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
--
ALPS device (E7: 73 02 64) needs new model entry in alps.c
https://bugs.launchpad.net/bugs/545307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
@zk:
I've built a new kernel with a new option. I'm not sure whether it will
work based on your last comment. The "refusing packet[0]" lines worry
me, because they aren't valid for any protocol that I see. Hopefully
this new option will make things better *crosses fingers*.
http://people.canonica
@Martin Spacek:
Since your issue is different, you need to find a bug that looks like
your issue, or open a new one.
Thanks
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a
As per comment #77, I'm closing out this bug.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launch
I've uploaded a new set of packages for i386. Please test them out.
Thanks
--
ALPS device (E7: 73 02 64) needs new model entry in alps.c
https://bugs.launchpad.net/bugs/545307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
@zK:
Does the dmesg look the same or is the output different?
--
Alps touchpad not recognized, defaults to macintosh mouse button emulation
https://bugs.launchpad.net/bugs/505474
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
--
vga16fb sometimes claims fb0 before kms driver, a causing blank screen on boot
https://bugs.launchpad.net/bugs/518387
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Per:
Sorry, I misread your comment and thought things were working on the
Lucid kernel. I'm moving this back to Triaged then.
** Changed in: linux (Ubuntu)
Status: Invalid => Triaged
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.ne
@vladilinsky:
Please reproduce the issue and then run 'apport-collect 518387'. This
will upload logs of your system to this bug so we can analyze the
problem.
Thanks
--
vga16fb sometimes claims fb0 before kms driver, a causing blank screen on boot
https://bugs.launchpad.net/bugs/518387
You rece
** Changed in: linux (Ubuntu)
Assignee: Chase Douglas (chasedouglas) => (unassigned)
--
vga16fb sometimes claims fb0 before kms driver, a causing blank screen on boot
https://bugs.launchpad.net/bugs/518387
You received this bug notification because you are a member of Ubuntu
Bugs, which
Basically, there's no good solution to this bug for Lucid. There's no
reasonable way to keep vga16fb from loading when a suitable hw
framebuffer is available. There's a hacked solution, but due to the lack
of locking that I can find in register_framebuffer (maybe there's
locking above, but I can't
After browsing the lshw source, it does a lot of detection by opening
and querying the framebuffer. I don't think we can teach lshw about
vga16fb easily, and it would likely be very hackish.
I've made a hackish patch for Lucid that would prevent vga16fb from
registering after another framebuffer a
@Mary:
If I had to guess, I think these are issues with the mouse preferences.
I just confirmed with a colleague that Karmic's mouse preferences are
broken in this regard (I'm running Lucid now, and it works for me here).
That functionality is also above the kernel. There's probably another
launch
@Filex:
Can you confirm Mary's results?
Thanks
--
ALPS device (E7: 73 02 64) needs new model entry in alps.c
https://bugs.launchpad.net/bugs/545307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
@vladilinsky:
Good news!
@zine92:
I'm moving this bug to invalid now. If you can reproduce the issue,
please move it back to New and attach a dmesg or kern.log from a failed
boot.
Thanks
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
vga16fb sometimes claims fb0 before
y have a better idea of what to try. If you do open a bug, please
link it to this bug so it can be tracked.
Sorry I can't be more help.
** Changed in: linux (Ubuntu)
Assignee: Chase Douglas (chasedouglas) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress =&
** Bug watch added: Linux Kernel Bug Tracker #15359
http://bugzilla.kernel.org/show_bug.cgi?id=15359
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=15359
Importance: Unknown
Status: Unknown
--
ALPS device (E7: 73 02 64) needs new model entry in alps.c
https
I've uploaded a new kernel to
http://people.canonical.com/~cndougla/545307/lp545307_2/. This kernel is
the same as before, except that it outputs debugging information from
the alps driver. Please test it out by installing it and then trying to
use the touchpad, buttons, and synaptics features. Aft
There was a bluetooth related fix that solves an issue similar to this
that went into the 2.6.32-17 kernel. Please test the -17 kernel to see
if you can reproduce this bug. If you can, please move the bug back to
the New state. Otherwise, please move the bug to Invalid.
Thanks
** Changed in: linu
** Summary changed:
- [185713.209801] [ cut here ]
+ WARNING: at /build/buildd/linux-2.6.32/lib/kref.c:43 kref_get+0x21/0x30()
--
WARNING: at /build/buildd/linux-2.6.32/lib/kref.c:43 kref_get+0x21/0x30()
https://bugs.launchpad.net/bugs/546280
You received this bug notific
@Mary:
Your dmesg doesn't show any errors, so from what I've read that's the
sign that everything is right at the driver level. I will submit the
patch upstream to the driver maintainer so it can be included in the
kernel.
Run "gpointing-device-settings &" in a terminal to try it out. You may
see
@Mary:
I'm not real sure why things are working quite right yet. I'll keep
thinking about it.
Unfortunately, your lshal2.txt is mostly empty, as if most of the output
was cut off. Can you try attaching again?
Thanks
--
ALPS device (E7: 73 02 64) needs new model entry in alps.c
https://bugs.lau
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
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 member of Ubuntu
Bugs, whi
*** This bug is a duplicate of bug 534549 ***
https://bugs.launchpad.net/bugs/534549
I believe this is fixed in the current Lucid kernel. Please move it back
to 'New' if you can reproduce it on an up to date system.
Thanks
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
@Mary:
Unfortunately, it's still cut off. In case you are trying to hard :),
the easiest way to get the output is to run "lshal > lshal.txt". If
you've got the full file, but it's not attaching right in launchpad, I
would try attaching it using the form here at the bug report instead of
through em
601 - 700 of 2064 matches
Mail list logo
