@Alberto
Hi again. To update the thread and bug report, i've upgraded to lastest
nvidia-current (190.53-0ubuntu5) and here are the results:
dkms status:
nvidia-current, 190.53, 2.6.32-10-generic, x86_64: installed
* I have -9 and -10 kernel. Should upgrade process install module on both
@Alberto
Thanks. I removed the file, forced reinstall of 2.6.32-10-generic kernel
as to force dkms module to reinstall. After that I saw no changes and my
system was still booting in low res mode, getiing an error (xorg log) on
loading nvidia kernel module. I just installed lastest update of
Sure. I also copy some lines from apt log. Now I'm running out of time
but if you want I can uninstall/install package again.
dkms status:
nvidia-current, 190.53, 2.6.32-9-generic, x86_64: installed
uname -r:
2.6.32-9-generic
grep nvidia /etc/modprobe.d/*:
Alberto, should nvidia-current be installed on all kernels during
installation/upgrade process? I've currently installed it and during
synaptic installation process it said that module was installed on .9
and .10 kernel. The kernel used during install process was 2.6.32-9, but
if I boot using
Just to say that bug #503727 may be marked as private and we can not
access it.
--
computer-janitor-gtk crashed with KeyError in create_column()
https://bugs.launchpad.net/bugs/503656
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
apport information
** Tags added: apport-collected
** Description changed:
It seems there's a bug affecting all Asustek mb that prevents to
suspend/resume successfully. Following the
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume let's
gather some more information:
apport information
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/37761116/AplayDevices.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member
apport information
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/37761117/ArecordDevices.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a
apport information
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37761118/BootDmesg.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member of
apport information
** Attachment added: Card0.Amixer.values.txt
http://launchpadlibrarian.net/37761119/Card0.Amixer.values.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you
apport information
** Attachment added: Card0.Codecs.codec.0.txt
http://launchpadlibrarian.net/37761120/Card0.Codecs.codec.0.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37761121/CurrentDmesg.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/37761122/Lspci.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: PciMultimedia.txt
http://launchpadlibrarian.net/37761124/PciMultimedia.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/37761127/ProcCpuinfo.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member of
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/37761132/ProcInterrupts.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/37761133/ProcModules.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member of
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/37761135/UdevDb.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/37761136/UdevLog.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: WifiSyslog.txt
http://launchpadlibrarian.net/37761137/WifiSyslog.txt
--
[ASUSTeK Computer INC. C51-MCP51] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/419353
You received this bug notification because you are a member of
Pepe, thanks for your suggestion.
Suspend/Resume with current kernel has the same results. I paste the
dmesg results using 2 different kernels. Any suggestion/test would be
appreciated.
Linux esbiete-desktop 2.6.32-9-generic #13-Ubuntu SMP Thu Dec 17
17:01:59 UTC 2009 x86_64 GNU/Linux
[
*** This bug is a duplicate of bug 494166 ***
https://bugs.launchpad.net/bugs/494166
Please refer to LP 494166.
** This bug has been marked a duplicate of bug 494166
[lucid] nvidia-glx can't work with new xorg 7.5
--
package nvidia-glx-185 (not installed) failed to install/upgrade:
After manually installing nVidia drivers, upgrading to a new kernel will
break your system back to svga resolution, I assume threre's something
wrong with nvidia kernel mod autoinstallation (sorry, I don't have more
knowledge about this).
--
package nvidia-glx-185 (not installed) failed to
You can workarround this bug by manually installing the nVidia drivers
following the instructions on
http://ubuntuforums.org/showthread.php?t=990978, this bug seems just a
dependency problem.
I've just installed the latests 64bits drivers (195.22) on lucyd and
after restart all is fine. Let's see
I've assigned bug to xserver-xorg package as there is a problem with its
dependencies causing nvidia-graphics-drivers-* to uninstall.
** Package changed: nvidia-graphics-drivers-180 (Ubuntu) = xserver-
xorg-driver-nv (Ubuntu)
** Changed in: xserver-xorg-driver-nv (Ubuntu)
Status: New =
Public bug reported:
It seems there's a bug affecting all Asustek mb that prevents to
suspend/resume successfully. Following the
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume let's
gather some more information:
Did the machine break while going to sleep or waking up? - Sleep
Is
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/30862204/dmesg.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/30862205/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/30862206/AplayDevices.txt
** Attachment
cmdline: BOOT_IMAGE=/boot/vmlinuz-2.6.31-6-generic
root=UUID=322d85e3-e51c-45a4-b723-81eb5b2a5475 ro quiet splash
conf.d/resume: RESUME=UUID=9a66ed5d-e330-49b4-94d7-72284247d547
Trying to suspend from VT1 after restart with no_console_suspend kernel
switch has the same results.
Deeping on
I have the same issue, but to difficult things a bit, the popup error
notification windows does not show the conf filename, it shows the
following:
--
The file '\UO' could not be read or does not contain recognized VPN
connection information
Error: does not look like a Cisco Compatible
First, sorry for the double -
May be my report differs from the initial problem mentioned and needs a
separate entry, but it seems there's something wrong with the file
parsing.
** Bug watch added: GNOME Bug Tracker #590054
http://bugzilla.gnome.org/show_bug.cgi?id=590054
** Also affects:
Thank you Martin.
I've upgraded from 2.20.10-ubuntu5 and the process has renamed custom,
deleted some obsolete conffiles and installed the new ones. Gdm action
reload failed but installation finished correctly without closing any
active screen. When trying to reboot the system asked me for
Public bug reported:
Binary package hint: gdm
Yesterday I did upgrade from gdm 2.20.10-0ubuntu5 to gdm 2.26.1-0ubuntu2
on my HP2133 netbook.
Ubuntu 9.10
Kernel: 2.6.31-1-generic
GNOME: 2.27.3
After rebooting erratic behavior is observed:
1) login is asked in correct resolution (1024x600). I'm
** Description changed:
Binary package hint: gdm
Yesterday I did upgrade from gdm 2.20.10-0ubuntu5 to gdm 2.26.1-0ubuntu2
on my HP2133 netbook.
Ubuntu 9.10
Kernel: 2.6.31-1-generic
GNOME: 2.27.3
After rebooting erratic behavior is observed:
1) login is asked in correct
** Attachment added: 0-greeter.log
http://launchpadlibrarian.net/28682666/0-greeter.log
--
upgrading to gdm 2.6.1-0ubuntu2: double login, wrong screen resolution and
unable to console
https://bugs.launchpad.net/bugs/395460
You received this bug notification because you are a member of
** Attachment added: 0-slave.log
http://launchpadlibrarian.net/28682672/0-slave.log
--
upgrading to gdm 2.6.1-0ubuntu2: double login, wrong screen resolution and
unable to console
https://bugs.launchpad.net/bugs/395460
You received this bug notification because you are a member of Ubuntu
** Attachment added: 0.log
http://launchpadlibrarian.net/28682674/0.log
--
upgrading to gdm 2.6.1-0ubuntu2: double login, wrong screen resolution and
unable to console
https://bugs.launchpad.net/bugs/395460
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sebastien, I do agree about the resolution, but I think you may have
missed rest of the bug report about double login and erratic behavior
after login. That happened after upgrading gdm, and that's why I've
classified it under gdm and not xorg
--
upgrading to gdm 2.6.1-0ubuntu2: double login,
I've reported to bugzilla.gnome.org
(http://bugzilla.gnome.org/show_bug.cgi?id=587732)
** Bug watch added: GNOME Bug Tracker #587732
http://bugzilla.gnome.org/show_bug.cgi?id=587732
--
'These windows do not support save current setup' metacity warning when
logging in with gdm 2.26
Reverting the system to gdm 2.20.10-0ubuntu5 solves the problem, so may
be there's some problem with xorg on the last release, but definitively
there is something wrong on 2.26.1 that breaks, at least, my
installation.
I think this bug has to be assigned to gdm team.
Please ask for any test you
This bug also affected me more or less in the same way.
On a clean installation I started Evolution for first time and it
crashed like mentioned by Khorne. Tried some more times with the same
result.
After running Evolution on valdrind it started normally. I setup my
account against exchange and
Martin, I had the same problem, but it's now solved in the lastest
devicekit-power package update (008-1ubuntu2).
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Fix Released
--
cannot suspend, GpmControlError.Code0: Cannot suspend as not allowed from
policy Failed
** Package changed: gnome-power-manager (Ubuntu) = devicekit-power
(Ubuntu)
--
cannot suspend, GpmControlError.Code0: Cannot suspend as not allowed from
policy Failed
https://bugs.launchpad.net/bugs/393021
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: b43-fwcutter (Ubuntu)
Status: New = Fix Released
--
karmic: login screen freezes after installing b43-fwcutter
https://bugs.launchpad.net/bugs/390177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
System was unstable and kept on crashing from time to time. Disabling
wireless from BIOS delayed the freezes to a greater random interval of 5
to 20 minutes aprox.
Upgrading all system to latest available karmic kernel apparently has
solved the problem, no more freezes since I started up with
Public bug reported:
Binary package hint: b43-fwcutter
After some reinstallations and going step-by-step I've detected that
after installing b43-fwcutter-012-1 and rebooting, startup login screen
freezes after few seconds, usually not having time to enter the
username.
It's a fresh install and
** Attachment added: lspci.txt
http://launchpadlibrarian.net/28165931/lspci.txt
** Branch linked: lp:ubuntu/karmic/b43-fwcutter
--
karmic: login screen freezes after installing b43-fwcutter
https://bugs.launchpad.net/bugs/390177
You received this bug notification because you are a member of
** Attachment added: dmesg.log
http://launchpadlibrarian.net/28165958/dmesg.log
--
karmic: login screen freezes after installing b43-fwcutter
https://bugs.launchpad.net/bugs/390177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: dpkg.log
http://launchpadlibrarian.net/28165961/dpkg.log
--
karmic: login screen freezes after installing b43-fwcutter
https://bugs.launchpad.net/bugs/390177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: apt-cache_b43fwcutter.txt
http://launchpadlibrarian.net/28165975/apt-cache_b43fwcutter.txt
--
karmic: login screen freezes after installing b43-fwcutter
https://bugs.launchpad.net/bugs/390177
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
Binary package hint: b43-fwcutter
After some reinstallations and going step-by-step I've detected that
after installing b43-fwcutter-012-1 and rebooting, startup login screen
freezes after few seconds, usually not having time to enter the
username.
It's a
Manually installing b43-fwcutter-011 and firmware broadcom-wl-4.150.10.5
freezes the system more randomly, some time I'm able to get into
desktop.
It seems a gnome/openchrome related to b43-fwcutter interaction.
When disabling WLAN from BIOS the system startup and runs normally (at
least for the
51 matches
Mail list logo
