I am also still getting some occasional corruption (on KDE) with the
331.38-0ubuntu5 drivers when resuming. I don't get freezes anymore, but
what I do see is windows that were open before suspending becoming
glitched (see attached screenshot) but those do not occur every time
after resuming unlike
This is fixed for me with nvidia-graphics-drivers-331 version 331.38-0ubuntu5
(see also
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1210077
which the original issue seems to be a duplicate of)
--
You received this bug notification because you are a member of
I have this bug as well with a geforce GT 640M. To answer that question,
it happens to me on both KDE (with compositing) and LXDE (no
compositing) so compositing does not appear to matter.
Also, for me, kernel 3.9 works fine; the issue only appears on newer
ones than that.
Another report of what
I've been having this problem as well, still not working with 331.20.
Kernel 3.9 works fine, but newer ones don't seem to.
Using an Acer v3-517g laptop with the nvidia 640M graphics for the
record. And to me it really sounds like Flittermice's problem is not the
same one as the reporter's (and
Hi,
From what I gather, to give you that information I need to be able to
reproduce the crash. But as I said in the original report, I have no idea
whatsoever how to reproduce it (it has only occurred once) so I don't think I
can help you with that.
--
You received this bug notification
Please disregard my former comment, I was looking at the wrong bug and
wasn't supposed to comment on this one :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712987
Title:
empathy crashed with
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723287
Title:
empathy crashed with SIGSEGV in g_type_check_instance_cast()
--
ubuntu-bugs mailing list
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/719166
Title:
compiz crashed with SIGSEGV in g_slice_alloc()
--
ubuntu-bugs mailing list
That package indeed seems to work now. Dmesg says that intel_ips doesn't
support my CPU, but X works fine, so..
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received
I tested the kernel of yours, and I still have the same oops with it.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a
Indeed, I have X working flawlessly with intel_ips blacklisted.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of
You're welcome. And thanks to you too for the help!
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs,
I guess blacklisting the module isn't enough, then?
(I've never compiled a kernel before, I'll do so later on if needed though)
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
Well, the kernel 2.6.35-22 booted with no noticeable issues with
intel_ips blacklisted.
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
https://bugs.launchpad.net/bugs/648631
You received this bug notification
** Attachment added: dmesg.2.6.35-22_working
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1675297/+files/dmesg.2.6.35-22_working
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
** Attachment added: lspci.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1673523/+files/lspci.txt
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
** Attachment added: uname-2.6.35-22
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1673524/+files/uname-2.6.35-22
--
Kernel Oops - unable to handle kernel NULL pointer dereference; IP:
[a007e3c6] ips_detect_cpu+0x76/0x1d0 [intel_ips]
Also, looking at the edited report, perhaps you didn't read one of my
comments closely enough. I don't know whether the kernel 2.6.35-16 works
because I never had it installed for some reason. I'd test it, but I did
some looking around and I can't seem to find any packages for it. I
found the
I tested the mainline kernels you asked me to, all of them worked with
no noticeable issues whatsoever. I also used the 2.6.35-3 kernel because
I do not have the -16 one and so I wasn't sure whether that one should
work fine or not. Either way, here are my dmesg and Xorg logs. Sorry for
taking so
** Attachment added: Xorg.0.log-2.6.35-3
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671621/+files/Xorg.0.log-2.6.35-3
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification
** Attachment added: Xorg.0.log-2.6.35-2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671622/+files/Xorg.0.log-2.6.35-2
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification
** Attachment added: Xorg.0.log-2.6.35-1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671623/+files/Xorg.0.log-2.6.35-1
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification
** Attachment added: dmesg-2.6.36-rc6
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671624/+files/dmesg-2.6.36-rc6
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because
** Attachment added: dmesg-2.6.35-3
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671625/+files/dmesg-2.6.35-3
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
** Attachment added: dmesg-2.6.35-2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671630/+files/dmesg-2.6.35-2
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
Is there a method for submitting more than one attachment at once,
anyway? I couldn't figure one out, at least..
** Attachment added: dmesg-2.6.35-1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671632/+files/dmesg-2.6.35-1
--
Intel graphics drivers not working on
I have already tested it, and it doesn't work either.
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: dmesg.2.6.35-22
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671972/+files/dmesg.2.6.35-22
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
You received this bug notification because you
Leaving for today by the way, I'll submit more information if needed
tomorrow.
** Attachment added: Xorg.0.log-2.6.35-22
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/648631/+attachment/1671973/+files/Xorg.0.log-2.6.35-22
--
Intel graphics drivers not working on new kernels on
Which kernel do you want me to attach the output of? All of the ones I've
tested?
Two other observations which I probably should've mentioned before, I'm not
sure if they're related or not:
I also have this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642421
It doesn't actually
No, I wasn't trying to click it. I did understand how to use a link with
that browser, it just didn't seem to think the Continue button was a
link at all. (Other links worked fine.) I think it may be related to the
Continue button being different from Firefox too (I can't see where does
it lead
on Firefox, even.
--
Intel graphics drivers not working on new kernels on Maverick?
https://bugs.launchpad.net/bugs/648631
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 ran into an unrelated problem yesterday trying to run apport-collect to get
the information you requested.
Upon running it, it opened up a text-only web browser and took me to the
launchpad login page. The problem was, the Continue button didn't work at all
using the browser, it didn't even
Ah, maybe I wasn't clear enough. The -15 ḱernel didn't introduce the
bug, as that kernel works perfectly. It's only the newer ones than that
not working. Either way, I will run these tests and report back later.
--
Intel graphics drivers not working on new kernels on Maverick?
To my untrained eye, the dmesg log in my report shows that *something*
is crashing at bootup (starting at line 765) which isn't happening on
the kernels that are working just fine. I'd bet that's related.
--
Intel graphics drivers not working on new kernels on Maverick?
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Basically, on Maverick, X fails to start properly for me on newer
kernels. Kernels up to 2.6.35-15 work just fine, but the later ones
don't. While booting, I get into a terminal login. If I run startx from
there, it complains
36 matches
Mail list logo
