Hmm. I keep seeing related bugs added to this one and marked invalid,
when no one has addressed my question:
Should Notify-OSD follow the standard behavior (i.e suppress
notifications when a full-screen application is active)?
This has nothing to do with the driver issue. As I said before, but
I've been having the same problem and after looking at the source, I
think the problem is that the mimetype database was updated to report
icons as image/vnd.microsoft.icon instead of image/x-ico. I
attached a patch in the upstream bugzilla:
http://bugzilla.gnome.org/show_bug.cgi?id=578575
This
While the flashing/flickering may be due to the drivers issue, this
doesn't address that fact that the standard notification-daemon doesn't
send a notification at all when a full-screen application is active,
while Notify-OSD does. Should Notify-OSD follow the standard behavior
(i.e suppress
Apparently, you can add 'processor.max_cstate=2' to the kernel line in
you grub config and this will work in setting the max_cstate and thus
prevent the annoying whine.
--
Unable to set max_cstate on hardy kernel
https://bugs.launchpad.net/bugs/206864
You received this bug notification because
I attached a patch that will remove the warning and keep the
functionality. I just did what the warning said and replaced sha with
hashlib.
** Attachment added: Use hashlib instead of sha
http://launchpadlibrarian.net/24172237/gdata.patch
--
Deprecation warning with python2.6
This problem persists in Intrepid and in Jaunty. In fact, in Jaunty you
can't even use the /etc/modprobe.d/options method anymore. Is this
going to be addressed or are we left with to deal with whining CPUs?
There should be some way that the user can set the max_cstate, whether
that is at
To expand on what others wrote, there appears to be something wrong with
the synaptics driver. If I remove xserver-xorg-input-synaptics from the
client, restart X, and then connect, everything works fine except I
can't use the touchpad on the client. If I leave the synaptics driver
in, restart
Attached is my dmesg following the debugging procedure. My machine does
not complete resume. It gets to the virtual console and the cursor just
blinks. I have to hold the power button down to shut it down and then
restart it.
** Attachment added: dmesg.txt
@Andy -- I wasn't addressed in your questions but my bug was marked a
duplicate of this one, so I figured I'd add my input. As noted in bug
322914, my laptop did not make it as far as sleeping, so it may not be a
duplicate of this one.
--
Notebook crashes after suspend with new Kernel
So I went back to kernel-2.6.27-11.27 to see if I can gather anymore
information, and here is what I found:
- If I do a pm-suspend on virtual console 1 before I log into GNOME,
suspend and resume will work just fine.
- If I log into GNOME and let NetworkManager connect to a network I can
NOT
*** This bug is a duplicate of bug 322886 ***
https://bugs.launchpad.net/bugs/322886
cat /proc/version_signature
Ubuntu 2.6.27-11.27-generic
On Mon, Feb 2, 2009 at 8:11 AM, Leann Ogasawara
leann.ogasaw...@canonical.com wrote:
Hi Peter,
For the 2.6.27-11 kernel can you also tell us the
Public bug reported:
Binary package hint: linux-image-2.6.27-11-generic
I upgraded from 2.6.27-9 to 2.6.27-11 and now when I go to suspend my
laptop (Dell Latitude D420) everything looks like it works (ie. X shuts
down) until it gets to the virtual console where it just hangs and
doesn't
** Attachment added: lspci -vvv
http://launchpadlibrarian.net/21783607/lspci
--
Suspend causes hang on 2.6.27-11
https://bugs.launchpad.net/bugs/322914
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
13 matches
Mail list logo
