Public bug reported:
Binary package hint: devicekit-disks
If I do:
$ devkit-disks --ata-smart-refresh /dev/sda
Refreshing ATA SMART data failed: Device does not support ATA SMART
However:
$ sudo hdparm -I /dev/sda|grep -i smart
*SMART feature set
*
With -intel version 2:2.7.99.901+git20090702.74227141-0ubuntu1 and
kernel 2.6.30-rc2, I've not seen any freezes or other issues, even
running compiz KMS.
--
[GM45] Intel/X: Session freezes on login with compiz and KMS
https://bugs.launchpad.net/bugs/391220
You received this bug notification
With -intel version 2:2.7.99.901+git20090702.74227141-0ubuntu1 and
kernel 2.6.30-rc2, I've not seen any freezes or other issues, even
running compiz KMS.
--
[GM45] [karmic] X lockup on idle compiz/gnome desktop on X200
https://bugs.launchpad.net/bugs/394952
You received this bug notification
Luke Maurer wrote:
I've been able to reproduce it 100% reliably (rm a single file = crashy
crashy) just in the Jaunty
LiveCD environment. AFAIK, the most exotic filesystem hackery it uses is that
union filesystem,
though I was crashing on deleting something on a separate, non-unionized
Thanks, but I don't think further confirmations are needed at this
point. The bug is already well-confirmed, and the fix is known. It's
just a matter of getting a kernel with the fix uploaded to the archive.
--
[karmic] linux-image 2.6.31-1.13 crashes on boot
Interesting -- I am running a self-built kernel (basically ubuntu karmic
kernel + latest Linus git as of yesterday) and suspend/resume is solid
for me; I haven't seen any X hangs related to suspend since updating to
2.6.31-rc1 (and I suspend from an X session running compiz). I am using
a Lenovo
I see from the karmic-changes list that linux 2.6.31-1.14 has been
uploaded with the fix for this bug; however the ubuntu-karmic.git tree
on kernel.ubuntu.com does not seem to include the change in question.
Is it typical not to update the git tree with everything in the kernel
package actually
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I am running up-to-date karmic on a Lenovo X200 with GM45 graphics,
using a self-built kernel (basically 2.6.31-1.13 with upstream kernel
pulled in to fix boot crasher and other bugs; this kernel has fixed lots
of i915 issues, eg
** Attachment added: intel-gpu-dump and dri debugfs info
http://launchpadlibrarian.net/28642162/dri_debug-2009-07-02--16.47.tgz
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/28642163/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
OK, will try xserver-xorg-video-
intel_2.7.99.901+git20090702.74227141-0ubuntu1 (one heck of a version
number there :)
It may take a while to find out if the hangs are fixed, since they don't
happen that often and are not very reproducible.
--
[GM45] [karmic] X lockup on idle compiz/gnome
What went wrong here? It seems linux-meta 2.6.31.1.11 was uploaded on
June 29, 3 days after I reported that kernel 2.6.31-1.13 would not boot
on a large class of machines, and giving the exact upstream changelog
required to fix the bug. I understand that using versions of Ubuntu
that are in the
The Ubuntu kernel build system is hard enough that I have no idea how to
get source packages I could upload to a ppa -- just building packages
locally is pretty much the limit of my understanding of building Ubuntu
kernels. However if you get the latest daily upstream kernel build
(which is
Public bug reported:
Binary package hint: devicekit-power
After the update in karmic of devicekit-power from 008-1 to
008-1ubuntu1, the devkit-power daemon does not seem to get started. The
symptoms are that gnome-power-manager no longer knows I have a battery
(it just shows the plug icon no
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28452349/Dependencies.txt
--
[karmic] devicekit-power broken by 008-1 to 008-1ubuntu1 update
https://bugs.launchpad.net/bugs/392798
You received this bug notification because you are a member of Ubuntu
Bugs, which is
By the way, I'm also attaching another patch that fixes a memory leak in
the pm-powersave patch (also sent upstream) that fixes a memory leak in
the pm-powersave patch; the leak is likely very slow so it wouldn't hurt
for a long time, but anyway here it is...
** Attachment added:
I debugged most of the problem here; it is indeed coming from the pm-
powersave patch, and there are a couple of related problems. First, the
patch adds a call to g_spawn_command_line_async() to run pm-powersave,
and when the devkit-power daemon is started by the dbus system bus, that
call is
Public bug reported:
Binary package hint: xserver-xorg-video-intel
On my Lenovo X200 laptop, with an internal display that is natively
1280x800, the X desktop comes up with a screen size of 1360x800 --
xdpyinfo shows:
screen #0:
dimensions:1360x800 pixels (277x163 millimeters)
Note
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/28436628/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/28436629/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28436630/Dependencies.txt
**
Public bug reported:
On my Lenovo ThinkPad X200, the recently built 2.6.31-1.13 kernel
crashes during boot with a NULL dereference in acpi_get_pci_dev(). This
is a bug in 2.6.31-rc1 that has already been fixed in the upstream
commit 412af978 (ACPI: video: prevent NULL deref in
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/28442029/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/28442031/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28442033/Dependencies.txt
**
I updated my system to 2.6.31-rc1 (note: not the 2.6.31-1.13 just
uploaded to karmic, since that crashes on boot on X200, see bug #392709
-- I pulled the upstream tree up to commit 4075ea8c and built it myself,
and that works). It seems this is related to the message:
[ 14.864118] i2c-adapter
I just pulled the upstream tree up to commit 4075ea8c into the karmit
kernel tree and rebuilt it, and that boots fine on my X200.
--
[karmic] linux-image 2.6.31-1.13 crashes on boot
https://bugs.launchpad.net/bugs/392709
You received this bug notification because you are a member of Ubuntu
Bugs,
I updated my system to 2.6.31-rc1 (note: not the 2.6.31-1.13 just
uploaded to karmic, since that crashes on boot on X200, see bug #392709
-- I pulled the upstream tree up to commit 4075ea8c and built it myself)
and I was able to suspend/resume from within an X session and not have
it freeze on my
I updated my system to 2.6.31-rc1 (note: not the 2.6.31-1.13 just
uploaded to karmic, since that crashes on boot on X200, see bug #392709
-- I pulled the upstream tree up to commit 4075ea8c and built it myself)
and I was able to suspend/resume from within an X session and not have
it freeze on my
The 2.6.31-rc1+(git fix for boot crash) kernel seems to fix a *lot* of
problems seen with 2.6.30 on my ThinkPad X200 laptop: the intel X driver
gets the right screen size to avoid things cut off on the right,
suspend/resume works with KMS, and compiz works with KMS. So getting a
fixed
Hmm, sounds unfortunate that closed/non-free or out-of-tree things block
2.6.31 from reaching testers when (as I mentioned in my previous
comment) so many things are fixed for Intel graphics in the new kernel.
Oh well, I can continue to use my own builds...
--
[karmic] linux-image 2.6.31-1.13
*** This bug is a duplicate of bug 389911 ***
https://bugs.launchpad.net/bugs/389911
Yes, does look like it.
** This bug has been marked a duplicate of bug 389911
kms: screen doesnt turn on resume from suspend
--
Lenovo X200 fails to resume from suspend
I just noticed a string of lines like:
sleep: invalid number '0.1'
in the console before the message about not finding the root device. So
I guess something changed the version of sleep in the initramfs from
klibc to busybox, since:
/usr/lib/klibc/bin/sleep 0.1
works fine, but
Public bug reported:
Since updating to the (64-bit) 2.6.30-10 kernel with KMS on Intel
graphics, my laptop no longer resumes from suspend-to-RAM properly -- it
seems to come most of the way back but then hangs with a black screen.
The attached dmesg is from a fresh boot after enabling pm-trace,
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/28265450/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/28265454/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28265457/Dependencies.txt
**
Public bug reported:
With the latest 2.6.30-10-generic kernel on my Lenovo X200 laptop
(running a 64-bit OS), the boot drops into the initramfs shell saying it
can't find the root device; however just hitting ctrl-D and continuing
works fine and the system boots up as normal. It seems that the
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/28253570/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/28253571/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28253572/Dependencies.txt
**
Public bug reported:
Binary package hint: xserver-xorg-video-intel
After the recent update on my Lenovo X200 laptop (with GM45 graphics) to
kernel 2.6.30-10, which enables KMS by default, when I log into my gnome
session, things freeze before any panel or other apps open; the pointer
does still
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/28254212/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/28254213/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28254214/Dependencies.txt
**
I see that 0.10.5-0.1ubuntu1 is now in the archive, which has the fix
for this bug. So this bug can probably be marked as resolved now.
--
ggl-gtk crashed with SIGSEGV in ggadget::dbus::DBusProxy::CallMethod()
https://bugs.launchpad.net/bugs/319874
You received this bug notification because you
This crash is occurring because ggl-gtk is not able to connect to the
DBus system bus and it ends up blindly trying to invoke a method on the
uninitialized NULL pointer for its system bus object. In
Machine::Machine(), the code calls DBusProxy::NewSystemProxy(), which
fails internally (and
It seems that the newer upstream release 0.10.5 has code to check the
return value of NewSystemProxy() and continue without crashing. This
version is already packaged in the Debian repository, and I tried
building it on my Jaunty system. On startup, it prints
No permissions to access D-Bus.
I missed a key part of this paragraph before. You say that the whole point
is that
unprivileged userspace applications can use RDMA directly?
Yes, non-suid executables run by normal users should be able to use RDMA
directly in a safe fashion.
If that's the case, should these devices not
I have nearly the same issue here. I just did a fresh install from the
current livecd (which booted fine), but when booting from the hard disk,
I get the same BUG: INT 14: CR2 ff... type message. The message
appears nearly instantly after the kernel has started, so something very
early in
Adding a PolicyKit authorization to use RDMA devices is not practically
any harder than adding a group; in fact, maintenance-wise it's
substantially easier.
I have to admit I have no idea how to do that. But anyway, what's the
point? No one is wants to change their app to talk to
D-Bus/PolicyKit seems very much overengineered and too complex for this
issue, and it doesn't fit the model of RDMA very well anyway, since the
whole point of RDMA is that unprivileged userspace applications use RDMA
hardware directly without the overhead of a system call into the kernel,
let
Yes, let's have the discussion please. I understand that this isn't a
high priority for you, but taking a little time early in the release
cycle seems to be the only way to get this resolved for Jaunty. I don't
see any way to make progress unless you give a hint as to what you feel
is a better
Past history is irrelevant.
I think backwards compatibility and simplicity count for something. The
only point about libibverbs is that the group rdma permissions are
already applied to /dev/infiniband/uverbsX, and the class of
users/applications that use those nodes are the same as the ones
Is now an appropriate time to address this for Jaunty?
--
Ubuntu is missing /dev/infiniband/rdma_cm group ownership udev rule
https://bugs.launchpad.net/bugs/256216
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Seems like time is running out to address this in 8.10?
This isn't really a security issue -- the rdma_cm device node is
designed to be safe for unprivileged users to access, and Debian has
been shipping udev rules that give group rdma access for quite a while
with no reported security issues.
How do we make progress on this? As it stands only root (or suid apps)
can use librdmacm with Intrepid. (Intrepid is the first release to
include librdmacm)
--
Ubuntu is missing /dev/infiniband/rdma_cm group ownership udev rule
https://bugs.launchpad.net/bugs/256216
You received this bug
Fair questions, although it probably would have been better to look at
this before the other group rdma changes went into libibverbs as part
of hardy (see bug #225788). And I wish we could have had this
discussion two months ago, rather than two weeks before the Intrepid
release.
Anyway, I'll
FWIW, as suggested by Wayne Towe, editing my /etc/ppp/options so that it
has
lcp-echo-failure 0
instead of
lcp-echo-failure 4
makes my CDMA connection stable as well.
--
CDMA (cellular modem) connection drops often with network-manager
https://bugs.launchpad.net/bugs/268667
You
FWIW, dns-nameservers comes from the resolvconf package.
--
[intrepid] new 0.7 branch ignores /etc/network/interfaces
https://bugs.launchpad.net/bugs/256054
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'll file it on bugzilla.gnome.org.
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
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
OK, filed as gnome bug 555701
(http://bugzilla.gnome.org/show_bug.cgi?id=555701)
** Bug watch added: GNOME Bug Tracker #555701
http://bugzilla.gnome.org/show_bug.cgi?id=555701
** Also affects: gnome-desktop via
http://bugzilla.gnome.org/show_bug.cgi?id=555701
Importance: Unknown
So I've analyzed the gnome-screensaver/gnome_bg_create_pixmap() problem
a little further. I believe this is (arguably) a bug in libgnome-
desktop: gnome_bg_create_pixmap() creates an X client with CloseDownMode
set to RetainPermanent, and uses this client to create a new pixmap,
which it then
Yes, I've been doing some debugging too, and in my setup gnome-
screensaver is the culprit as well. Specifically it calls
gnome_bg_create_pixmap() (from libgnome-desktop) with root == TRUE,
which ends up creating a new connection to the X server, calling
XSetCloseDownMode() to change to
I see this to on an Intrepid system (running gnome, not kde). After a
while, no more X clients can be started, and I get the error 'Maximum
number of clients reachedxlsclients: unable to open display :0.0'
However if I close some client, then I am able to start another client.
And apparently X
I have a system connected to a wired network that requires a static IP
and 802.1x authentication, and I have an /etc/network/interfaces stanza
like
auto eth1
iface eth1 inet static
address 10.33.42.9
netmask 255.255.255.0
gateway 10.33.42.1
wpa-driver wired
wpa-ap-scan 0
Is there any possibility of this getting reviewed and sponsored for
Intrepid?
--
Ubuntu is missing /dev/infiniband/rdma_cm group ownership udev rule
https://bugs.launchpad.net/bugs/256216
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not sure what you mean to verify that your connection is still as
stable with chat but I will restate the problem as follows:
I booted up my up-to-date intrepid system, and connected by selecting
Auto CDMA network connection from the network manager applet menu.
The connection worked but it
Public bug reported:
I am using network-manager 0.7~~svn20080908t183521+eni0-0ubuntu2 on an
Intrepid system. I have a Verizon/Kyocera CDMA modem, and I the new NM
0.7 adds support for this modem. This works pretty well -- NM is able
to connect to the network fine, and everything works. The
that -latest tarball link doesn't look
like a new upstream release.
-- Roland Dreier [EMAIL PROTECTED] Fri, 08 Aug 2008 14:25:17 -0700
** Affects: libcxgb3 (Ubuntu)
Importance: Undecided
Status: New
--
Please sync libcxgb3 1.2.2-1 (universe) from Debian unstable (main).
https
Public bug reported:
The Debian version of udev ships with the rule
KERNEL==rdma_cm, GROUP=rdma
in /etc/udev/rules.d/020_permissions.rules. This means that loading the
rdma_ucm module results in a device file like
crw-rw 1 root rdma 10, 60 2008-08-08 14:39
/dev/infiniband/rdma_cm
Here is a debdiff that bumps the version to -ubuntu1 and adds a
librdmacm1.udev file with the required udev rule. It would be great if
this could be integrated into the Ubuntu package
** Attachment added: librdmacm-udev.patch
http://launchpadlibrarian.net/16665354/librdmacm-udev.patch
--
Just built an upstream git kernel (same tree that worked in my Fedora 9
VM with kvm 70/2.6.26-rc9 host) in my Intrepid VM on Hardy kvm/kernel,
and had the same problems without no-kvmclock. I wonder if the current
Intrepid gcc is miscompiling some part of the kvmclock code?
--
intrepid kernel
Yes, with Soren's patch to disable the kvm clock in Hardy's kvm 62, the
intrepid kernel seems to boot OK even without no-kvmclock. However
some intrepid updates seem to have broken X with the new kernel: now my
intrepid VM hangs when starting gdm with 2.6.26 (using the Hardy 2.6.24
kernel allows
I just tried booting various recent Intrepid amd64 CD images under kvm
70+dfg-1 (the latest Debian package) on a host running a very recent
self-built 2.6.26-rc9 kernel, and I also had the same problem that the
guest locked up early in boot unless I passed in the no-kvmclock
kernel option.
So
I wonder if this problem comes from the fact that the intrepid kernel
doesn't seem to have upstream commit ca373932 (x86: KVM guest: Add
memory clobber to hypercalls), which went in just after 2.6.26-rc9.
The patch description says:
Hypercalls can modify arbitrary regions of memory. Make
Just as a test, I built the latest upstream kernel (post-2.6.26-rc9 git,
including the commit I mentioned above) in a Fedora 9 image I happen to
have, and it booted fine on the same kvm 70/2.6.26-rc9 host system that
the Intrepid CD image failed on. And I verified:
$ cat
So I just built a kernel from the ubuntu-intrepid git tree (as of commit
e5cb6d2d) with just upstream commit ca373932 (the hypercall fix) patched
in by hand, and tried that kernel in my intrepid VM running on hardy kvm
62/2.6.24. Unfortunately that kernel fails in the same way without no-
For the record -- my time problems booting with the new kernel seem to
be coming from the paravirtual clocksource (KVM_CLOCK) introduced in
2.6.26. Booting with no-kvmclock on the kernel command line makes
things work OK. The next question to answer is whether this is an issue
with the Intrepid
Out of curiousity, is the bug really in Hardy's 2.6.24 kernel, or in the
version of kvm 62 shipped with Hardy? As I understand things, the host
side of paravirt clock support is entirely in the userspace kvm code.
--
intrepid kernel 2.6.26-2-generic (amd64) won't boot as kvm guest
Actually for me the Intrepid 2.6.26-3.9 kernel does boot inside a Hardy
kvm VM (with a Hardy 2.6.24-19/kvm 1:62+dfsg-0ubuntu7 host), while
2.6.26-2 still hangs.
However there is now another problem, which is that the guest is pretty
much unusable due to time running much too fast: I see several
Public bug reported:
Binary package hint: linux-source-2.6.26
I have a Hardy kvm virtual machine (amd64) created in virt-manager. I
just updated to Intrepid Alpha1 (using update-manager), and the
2.6.26-2-generic kernel that gets installed won't boot... on some boots
it hangs at the waiting for
Thanks for the 'large-memory' option tip. It makes sense that there
would be problems without that, since without the option it seems lilo
tries to load everything under 15 MB, and with an 8+ MB initramfs and a
nearly 2 MB kernel, it seems plausible that something could go wrong.
I agree that
Public bug reported:
libibverbs has Ubuntu-specific changes to add udev rules that are
shipped with udev in Debian but are split out into libibverbs in Ubuntu.
** Affects: libibverbs (Ubuntu)
Importance: Undecided
Assignee: Roland Dreier (roland.dreier)
Status: In Progress
I am working on the merge.
** Changed in: libibverbs (Ubuntu)
Assignee: (unassigned) = Roland Dreier (roland.dreier)
Status: New = In Progress
--
Please merge libibverbs 1.1.2-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/225788
You received this bug
I am attaching a debdiff from Debian's libibverbs 1.1.2-1 to get a
1.1.2-1ubuntu1 suitable for Intrepid. I'm not including a
1.1.1-1ubuntu1 - 1.1.2-1ubuntu1 diff because the upstream changes are
huge (due to new versions of autotools creating different generated
files) -- however I can provide it
Diff for merge attached, ready for sponsorship
** Changed in: libibverbs (Ubuntu)
Status: In Progress = Confirmed
--
Please merge libibverbs 1.1.2-1 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/225788
You received this bug notification because you are a member
Public bug reported:
Binary package hint: lilo
I just updated an x86-64 system from gutsy to hardy, and the boot of
2.6.24-16-generic hung after the line
checking if image is initramfs...it isn't (bad gzip magic numbers);
looks like an initrd
I was able to boot successfully with the old
It's no problem to update the maintainer field...but let me make sure I
know what to update it to. I am the Debian package maintainer and I am
also trying to update my package with Ubuntu-specific changes. Should I
still set the maintainer to Ubuntu MOTU Developers ubuntu-
[EMAIL PROTECTED]?
--
Anyway, here's the patch updated by running update-maintainer...
** Attachment added: libibverbs-udev-maint.patch
http://launchpadlibrarian.net/13828120/libibverbs-udev-maint.patch
--
Ubuntu is missing /dev/infiniband/uverbs* group ownership udev rule
https://bugs.launchpad.net/bugs/218500
Public bug reported:
The Debian version of udev ships with the rule
KERNEL==uverbs*, GROUP=rdma
in /etc/udev/rules.d/020_permissions.rules. This means that on systems
with RDMA devices available, loading the ib_uverbs modules results in
device files like
Here is a debdiff that bumps the version to -ubuntu1 and adds a
libibverbs1.udev file with the required udev rules. It would be great
if this could be integrated into the Ubuntu package for Hardy+1 (I
assume it's too late for Hardy).
** Attachment added: libibverbs source patch to add
Sorry... here's an updated patch with my correct email in the
debian/changelog.
** Attachment added: updated libibverbs patch
http://launchpadlibrarian.net/13533138/libibverbs-udev.patch
--
Ubuntu is missing /dev/infiniband/uverbs* group ownership udev rule
Public bug reported:
Binary package hint: linux-source-2.6.24
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu hardy (development branch)
I installed a new Chelsio T302 ethernet NIC in a system running hardy's
2.6.24-12. The network interface did not
** Attachment added: patch to fix parity set up in cxgb3 on new rev Chelsio T3
NICs
http://launchpadlibrarian.net/12637169/cxgb3-parity.txt
--
New revision Chelsio NICs don't work with cxgb3 driver from 2.6.24
https://bugs.launchpad.net/bugs/201893
You received this bug notification because
Public bug reported:
Binary package hint: linux-image
On a Thinkpad X60s with fairly recent BIOS/firmware and Hardy's 2.6.24
kernel, I get a lot of kernel messages like the following flooding my
log:
thinkpad_acpi: unknown LID-related HKEY event: 0x5010
in my kernel log. This comes from
Yes, good point... the issm, uverbs and ucm rules are all missing
closing quotes () for the KERNEL== part of the rules.
--
udev: typo in rdma_ucm rules
https://bugs.launchpad.net/bugs/192552
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still happening here on my Thinkpad X60s, with an up-to-date hardy
system.
--
Caps lock LED changes state even when caps lock is mapped to ctrl
https://bugs.launchpad.net/bugs/173350
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Public bug reported:
Unfortunately the rules that I included in the report for bug #124990 that
added handling
of the rdma_ucm module's misc device had a typo. Although the module name is
rdma_ucm, the device that is created has
KERNEL==rdma_cm
as its name, so the udev rules need to use
This seems to be a known issue with kernel 2.6.24-rc's and hal; see for example
http://lkml.org/lkml/2007/12/8/24 and
https://bugzilla.novell.com/show_bug.cgi?id=342808
Since kernel 2.6.24 has recently gone into Hardy, it's not surprising
this is now showing up.
Anyway, here's the hal-device
I started seeing this with Hardy on my Thinkpad X60s -- I have caps lock
and ctrl switch, and the key labeled CapsLk still toggles the caps
lock LED, even though it actually behaves like the control key. (And
the key labeled Ctrl does not affect the caps lock LED, even though it
does work like
On my system (thinkpad X60s), with
ii gnome-power-mana 2.19.6-0ubuntu2 frontend for gnome-powermanager
this is definitely still happening. In fact as I type this into the
comment box, the brightness meter has stayed stuck on my screen the
whole time.
Also something seems to be setting the
No, as I said I am using a thinkpad X60s.
I killed my running gnome-power-manager and ran
gnome-power-manager --no-daemon --verbose
After letting my computer sit idle for a couple minutes (with the screen
open), I came back to g-p-m spewing messages and the brightness meter
stuck on the
By the way, I do agree that my g-p-m log looks similar to Jarmo Ilonen's
log at the end of bug #122666, so that may be a duplicate.
--
[gutsy tribe 3] screen brightness meter randomly displays on macbook
https://bugs.launchpad.net/bugs/129109
You received this bug notification because you are a
FWIW, I gave iwl3945 a try on my Thinkpad X60s with 3945 wireless. It
works OK for a while on my wireless network (using WEP), but I see lots
of
iwl3945: REPLY_ADD_STA failed
in my kernel log, and then after a few hours the network dies and I see
iwl3945: ipw going down
Freeing
The reference counting problem may be the same as
http://www.bughost.org/bugzilla/show_bug.cgi?id=1341
--
Please update to iwlwifi 1.0 and latest ucode
https://bugs.launchpad.net/bugs/129112
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
With the latest linux-ubuntu-modules package (which updates to
e1000-ich9 version 7.6.5-NAPI), this problem seems to be gone.
--
e1000-ich9 doesn't work without turning off tx checksum offload
https://bugs.launchpad.net/bugs/125659
You received this bug notification because you are a member of
I see the same problem with a default boot of Gutsy on my X60s, which
has kernel 2.6.22, and loads the video module but not the thinkpad-acpi
module. However, if I do modprobe -r video (to get rid of the ACPI
video driver) and modprobe thinkpad-acpi (to load the thinkpad-acpi
module), then
no problem, here's the dmidecode output
** Attachment added: dmidecode.out
http://launchpadlibrarian.net/8519049/dmidecode.out
--
Gutsy tribe 2 amd64 hangs on Intel DG33BU motherboard without pci=nommconf boot
option
https://bugs.launchpad.net/bugs/124294
You received this bug notification
Is any progress being made on this? Is more information needed to fix
it? Is a workaround available?
It's kind of disheartening to see a confirmed bug with importance High
be open for 5 months without even being assigned to anyone.
--
Root fs on LVM on mdadm fails to boot
Thanks. I just did a big update that picked up mdadm 2.6.2-1ubuntu1 and
I can confirm that my system with LVM on RAID1 boots without dropping
into the initramfs.
--
Root fs on LVM on mdadm fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a
301 - 400 of 444 matches
Mail list logo
