I think I have nailed down some important information about the bug. In
order to reproduce, you need to hibernate, then close the lid of your
laptop right away. (You don't have to slam it, but close it prior to x
windows unloading.)
I assume the problem occurs because the screen is normally turn
*** This bug is a duplicate of bug 98641 ***
https://bugs.launchpad.net/bugs/98641
** This bug has been marked a duplicate of bug 98641
NVidia driver missing libwfb
--
Nvidia kernel module not receiving interrupts from graphics device
https://bugs.launchpad.net/bugs/103118
You received t
I have the exact same problem.
** Attachment added: "lspci -vv output"
http://librarian.launchpad.net/7147684/lspci.txt
--
Restricted Drivers, always needs computer restart for linmodem
https://bugs.launchpad.net/bugs/102859
You received this bug notification because you are a member of Ubunt
** Attachment added: "Partial output of /var/log/messages"
http://librarian.launchpad.net/7147676/messages-partial.txt
--
Screen blank after hibernate
https://bugs.launchpad.net/bugs/103119
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
** Attachment added: "lspci -vv output"
http://librarian.launchpad.net/7147672/lspci.txt
--
Screen blank after hibernate
https://bugs.launchpad.net/bugs/103119
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
Partial output of /var/log/messages
--
Screen blank after hibernate
https://bugs.launchpad.net/bugs/103119
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Public bug reported:
Binary package hint: gnome-power-manager
When I resume from hibernation on my Toshiba Tecra M3, the screen
appears entirely black and blank. Closing the lid and reopening it
appears to fix the problem, but not everyone will think to do this.
** Affects: gnome-power-manager
** Attachment added: "lspci -vv output"
http://librarian.launchpad.net/7147662/lspci.txt
--
Nvidia kernel module not receiving interrupts from graphics device
https://bugs.launchpad.net/bugs/103118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
** Attachment added: "xorg.conf"
http://librarian.launchpad.net/7147661/xorg.conf
--
Nvidia kernel module not receiving interrupts from graphics device
https://bugs.launchpad.net/bugs/103118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: "Xorg.0.log"
http://librarian.launchpad.net/7147657/Xorg.0.log
--
Nvidia kernel module not receiving interrupts from graphics device
https://bugs.launchpad.net/bugs/103118
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
Public bug reported:
Binary package hint: nvidia-glx
When I attempt to start x with the nvidia driver, x fails to start with
the error message:
(EE) NVIDIA(0): The NVIDIA kernel module does not appear to be receiving
(EE) NVIDIA(0): interrupts generated by the NVIDIA graphics device
(EE) NVI
I'm running restricted-manager 0.18 and it seems that my Nvidia Go 6600
isn't showing up either.
The results of lspci -n | grep 0300 is:
01:00.0 0300: 10de:0146 (rev a2)
Matt
--
Please ship proper modaliases for nvidia, fglrx & co
https://bugs.launchpad.net/bugs/93209
You received this bug not
I also have this problem, although I've found that I can manually start
dbus using "sudo /etc/init.d/dbus start" that dbus is properly
initialized.
It gives all the normal messages when starting:
* Starting system message bus dbus
I don't know much about package management, but it seems like it might
be a few more packages than just libgl1-mesa-dri involved.
I attempted to just remove libgl1-dri earlier and perform an upgrade,
but it continued to fail unless I removed more. There are a total of 7
packages I removed:
libgl
term.log was empty, and could not be uploaded.
--
Could not calculate the upgrade
https://launchpad.net/bugs/62225
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "main.log"
http://librarian.launchpad.net/4422159/main.log
--
Could not calculate the upgrade
https://launchpad.net/bugs/62225
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "apt.log"
http://librarian.launchpad.net/4422158/apt.log
--
Could not calculate the upgrade
https://launchpad.net/bugs/62225
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: update-manager
Was attempting to upgrade from dapper to edgy using "update-manager -c
-d". At the step marked "Fetching and Installing the upgrades", I
received the error:
"Could not calculate the upgrade"
It asked me to include the files in /var/log/d
18 matches
Mail list logo
