Re: [Bug 550046] mouse does not resume after waking from suspend to ram triggered by closing lid
I've updated to Natty on the one laptop to which I currently have access and haven't seen this issue. I have also installed as a VM in Virtualbox and have not seen the problem again. -- Ali On Wed, Jun 22, 2011 at 20:20, Pedro Villavicencio pe...@ubuntu.com wrote: Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance and sorry for the late response. ** Changed in: gnome-power-manager (Ubuntu) Importance: Undecided = Low ** Changed in: gnome-power-manager (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/550046 Title: mouse does not resume after waking from suspend to ram triggered by closing lid Status in “gnome-power-manager” package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-power-manager Dell Latitude D630 Package details: gnome-power-manager: Installed: 2.29.91-0ubuntu9 Candidate: 2.29.91-0ubuntu9 Version table: *** 2.29.91-0ubuntu9 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Release info: Description: Ubuntu lucid (development branch) Release: 10.04 When waking from suspend to RAM triggered by closing the lid of the machine, the mouse pointer takes 4+ minutes to return while the keyboard is responsive immediately. I had to start filing this bug- report by using Alt+F2 and opening gnome-terminal to run ubuntu-bug, which brought up the firefox window. I am running off the amd64 live desktop image burned to a 8GB USB stick. I expect the mouse to be responsive shortly after boot, around the same time as the keyboard. ProblemType: Bug Architecture: amd64 Date: Sun Mar 28 04:37:10 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/gnome-power-manager GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No LiveMediaBuild: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100327) MachineType: Dell Inc. Latitude D630 Package: gnome-power-manager 2.29.91-0ubuntu9 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 SourcePackage: gnome-power-manager Uname: Linux 2.6.32-17-generic x86_64 XsessionErrors: (polkit-gnome-authentication-agent-1:11622): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-terminal:12486): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL entry-lock_count 0' failed dmi.bios.date: 11/24/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.asset.tag: 161910 dmi.board.name: 0WM416 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 161910 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0WM416:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/550046/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550046 Title: mouse does not resume after waking from suspend to ram triggered by closing lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/550046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545398] Re: lucid's motd text not updated
I get the following output on Ubuntu 10.04 i386 installed using the alternate installed disk. I have removed the hostname information on the line that has lastlogin info. Linux lotia-et-mm 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux Ubuntu 10.04 (lucid) Welcome to Ubuntu! * Documentation: https://help.ubuntu.com/ Checking for a new ubuntu release No new release found Welcome to Ubuntu! * Documentation: https://help.ubuntu.com/ 141 packages can be updated. 0 updates are security updates. Checking for a new ubuntu release No new release found *** System restart required *** Last login: specific lastlogin information removed -- lucid's motd text not updated https://bugs.launchpad.net/bugs/545398 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551936] [NEW] value of Configuration doesn't change on initial switch to Keep synchronized with Internet servers
Public bug reported: Binary package hint: gnome-system-tools When initially changing the value of the Configuration dropdown in the Time and Date Settings window to Keep synchronized with Internet servers on a newly set up machine, a dialog pops up informing the user that NTP is required but it isn't installed. It gives the user the option to install it. After selecting that option and installing NTP support, the user is brought back to the Time and Date Settings window, but the value of Configuration drop down is still Manual. Checking the process list shows that ntpd is in fact running. The value of the Configuration drop down should be changed to Keep synchronized with Internet Servers to indicate to the user that the change made has taken effect. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-system-tools 2.29.92-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-18-generic i686 Architecture: i386 Date: Tue Mar 30 14:11:05 2010 ExecutablePath: /usr/bin/time-admin InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-system-tools XsessionErrors: (polkit-gnome-authentication-agent-1:1380): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-terminal:1743): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL entry-lock_count 0' failed ** Affects: gnome-system-tools (Ubuntu) Importance: Low Status: New ** Tags: apport-bug i386 lucid -- value of Configuration doesn't change on initial switch to Keep synchronized with Internet servers https://bugs.launchpad.net/bugs/551936 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 551936] Re: value of Configuration doesn't change on initial switch to Keep synchronized with Internet servers
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42524897/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/42524898/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/42524899/ProcStatus.txt -- value of Configuration doesn't change on initial switch to Keep synchronized with Internet servers https://bugs.launchpad.net/bugs/551936 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550059] [NEW] error in test description text for usb audio device test
Public bug reported: Binary package hint: checkbox There is an error in the textual test description above that asks the user to right click on the speaker icon when the user is required to left click on the speaker icon in order to open up the sound preferences. ProblemType: Bug Architecture: amd64 Date: Sun Mar 28 01:56:49 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100327) Package: checkbox 0.9 PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 SourcePackage: checkbox Uname: Linux 2.6.32-17-generic x86_64 ** Affects: checkbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- error in test description text for usb audio device test https://bugs.launchpad.net/bugs/550059 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550059] Re: error in test description text for usb audio device test
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42244731/Dependencies.txt -- error in test description text for usb audio device test https://bugs.launchpad.net/bugs/550059 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550083] [NEW] jockey-gtk initially reports confusing driver choices
Public bug reported: When first running jockey-gtk, it initially gives the user two choices of proprietary drives for the Broadcom wireless networking hardware on this machine. I installed the Broadcom STA drivers and after running jockey again, it no longer displays Broadcom 43 as an option. Unlike the NVIDIA choices (of which there are also 2), there is no (recommended) or other helpful text describing the options. Making the right choice requires that the user do some research. IMHO, the installation of drivers is already fraught with fear amongst the majority of users. jockey makes it incredibly simple to install proprietary drivers, but I feel that providing fewer, better choices would be a major win for people attempting to get their hardware to work, I also understand that since these drivers are proprietary, it may be hard to obtain useful descriptive information, or to get details on the differences and to adjust the provided choices accordingly. If at all possible, fewer choices in this space would be better. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: jockey-gtk 0.5.8-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-17-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Sun Mar 28 03:17:04 2010 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude D630 PackageArchitecture: all PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-17-generic root=/dev/mapper/storage-root ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jockey dmi.bios.date: 11/24/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.asset.tag: 161910 dmi.board.name: 0WM416 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 161910 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0WM416:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- jockey-gtk initially reports confusing driver choices https://bugs.launchpad.net/bugs/550083 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550083] Re: jockey-gtk initially reports confusing driver choices
** Attachment added: .var.log.jockey.log.txt http://launchpadlibrarian.net/42250718/.var.log.jockey.log.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/42250719/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/42250720/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42250721/Dependencies.txt ** Attachment added: Devices.txt http://launchpadlibrarian.net/42250722/Devices.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/42250723/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/42250724/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/42250725/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/42250726/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/42250727/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/42250728/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/42250729/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/42250730/XorgConf.txt -- jockey-gtk initially reports confusing driver choices https://bugs.launchpad.net/bugs/550083 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550281] [NEW] confusing interaction between NotifyOSD and network-manager
Public bug reported: Binary package hint: network-manager I am not sure if this is a problem with network manager or NotifyOSD or both. When the notification comes up to inform the user that wireless networks are available, it asks them to click on the icon to proceed further. The OSD isn't clickable and it is unclear what the user should do next in order to connect to one of the detected wireless networks. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: network-manager 0.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-17-generic x86_64 NonfreeKernelModules: wl nvidia Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Sun Mar 28 10:40:06 2010 InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' IpRoute: 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.60 metric 2 169.254.0.0/16 dev eth1 scope link metric 1000 default via 192.168.1.1 dev eth1 proto static Keyfiles: Error: [Errno 2] No such file or directory ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash RfKill: SourcePackage: network-manager ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- confusing interaction between NotifyOSD and network-manager https://bugs.launchpad.net/bugs/550281 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550281] Re: confusing interaction between NotifyOSD and network-manager
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42281028/Dependencies.txt ** Attachment added: Gconf.txt http://launchpadlibrarian.net/42281029/Gconf.txt ** Attachment added: IfupdownConfig.txt http://launchpadlibrarian.net/42281030/IfupdownConfig.txt ** Attachment added: IpAddr.txt http://launchpadlibrarian.net/42281031/IpAddr.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/42281032/IwConfig.txt ** Attachment added: NetDevice.eth0.txt http://launchpadlibrarian.net/42281033/NetDevice.eth0.txt ** Attachment added: NetDevice.eth1.txt http://launchpadlibrarian.net/42281034/NetDevice.eth1.txt ** Attachment added: NetDevice.lo.txt http://launchpadlibrarian.net/42281035/NetDevice.lo.txt ** Attachment added: PciNetwork.txt http://launchpadlibrarian.net/42281036/PciNetwork.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/42281037/WifiSyslog.txt ** Attachment added: nm-system-settings.conf.txt http://launchpadlibrarian.net/42281038/nm-system-settings.conf.txt -- confusing interaction between NotifyOSD and network-manager https://bugs.launchpad.net/bugs/550281 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550473] [NEW] confusing instructions Time and Date Settings panel
Public bug reported: Binary package hint: gnome-system-tools The Time and Date Settings panel has text on the bottom that says Click to make changes. The time to click is not highlighted or differentiated in any way. Clicking on the text does nothing and the click target padlock icon is so small that it is not immediately obvious that the user needs to click that icon. Highlighting the icon, making the text a click target, or changing to the text to say Click lock to make changes (English example of course), may help clear up matters for the novice user. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-system-tools 2.29.92-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-17-generic x86_64 NonfreeKernelModules: wl nvidia Architecture: amd64 Date: Sun Mar 28 16:15:05 2010 ExecutablePath: /usr/bin/time-admin InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-system-tools ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- confusing instructions Time and Date Settings panel https://bugs.launchpad.net/bugs/550473 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550473] Re: confusing instructions Time and Date Settings panel
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42310036/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/42310037/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/42310038/ProcStatus.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/42310039/XsessionErrors.txt -- confusing instructions Time and Date Settings panel https://bugs.launchpad.net/bugs/550473 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550041] [NEW] incorrect/confusing wireless network disconnect OSD notification on wake from suspend to RAM
Public bug reported: Binary package hint: network-manager Package: network-manager Package version details: Installed: 0.8-0ubuntu2 Candidate: 0.8-0ubuntu2 Version table: *** 0.8-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Distro version details: Description:Ubuntu lucid (development branch) Release:10.04 This bug is very similar to #432369 but I was unsure from the bug description if the two are exactly alike. I am connected via a wired connection and when I resume from sleep, I get an OSD notification of disconnection from a wireless network to which as far as I know I was never connected, particularly not at the time when the system was suspended to RAM. This notification is confusing and is then followed by a notification of an establishment of a network connection over the wired interface. I expect a single notification of reconnection to the previously active network connection, or unless required, no notification at all. Instead the system should simply return to the state it was in prior to being suspended. IMHO, there is little need to inform the user. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: network-manager 0.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-17.26-generic-pae 2.6.32.10+drm33.1 Uname: Linux 2.6.32-17-generic-pae i686 NonfreeKernelModules: nvidia wl Architecture: i386 CRDA: Error: [Errno 2] No such file or directory CheckboxSubmission: dff18a7c98a7f904c82da66259654b61 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sun Mar 28 00:15:22 2010 ExecutablePath: /usr/sbin/NetworkManager Gconf: IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha i386 (20100326) IpRoute: 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.58 metric 1 169.254.0.0/16 dev eth1 scope link metric 1000 default via 192.168.1.1 dev eth1 proto static Keyfiles: Error: [Errno 2] No such file or directory ProcEnviron: PATH=(custom, no user) SourcePackage: network-manager ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- incorrect/confusing wireless network disconnect OSD notification on wake from suspend to RAM https://bugs.launchpad.net/bugs/550041 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550041] Re: incorrect/confusing wireless network disconnect OSD notification on wake from suspend to RAM
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42239978/Dependencies.txt ** Attachment added: IpAddr.txt http://launchpadlibrarian.net/42239979/IpAddr.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/42239980/IwConfig.txt ** Attachment added: NetDevice.eth1.txt http://launchpadlibrarian.net/42239981/NetDevice.eth1.txt ** Attachment added: NetDevice.eth2.txt http://launchpadlibrarian.net/42239982/NetDevice.eth2.txt ** Attachment added: NetDevice.lo.txt http://launchpadlibrarian.net/42239983/NetDevice.lo.txt ** Attachment added: PciNetwork.txt http://launchpadlibrarian.net/42239984/PciNetwork.txt ** Attachment added: ProcAttrCurrent.gz http://launchpadlibrarian.net/42239985/ProcAttrCurrent.gz ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/42239986/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/42239987/ProcStatus.txt ** Attachment added: RfKill.txt http://launchpadlibrarian.net/42239988/RfKill.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/42239989/WifiSyslog.txt ** Attachment added: nm-system-settings.conf.txt http://launchpadlibrarian.net/42239990/nm-system-settings.conf.txt -- incorrect/confusing wireless network disconnect OSD notification on wake from suspend to RAM https://bugs.launchpad.net/bugs/550041 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550046] [NEW] mouse does not resume after waking from suspend to ram triggered by closing lid
Public bug reported: Binary package hint: gnome-power-manager Dell Latitude D630 Package details: gnome-power-manager: Installed: 2.29.91-0ubuntu9 Candidate: 2.29.91-0ubuntu9 Version table: *** 2.29.91-0ubuntu9 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Release info: Description:Ubuntu lucid (development branch) Release:10.04 When waking from suspend to RAM triggered by closing the lid of the machine, the mouse pointer takes 4+ minutes to return while the keyboard is responsive immediately. I had to start filing this bug-report by using Alt+F2 and opening gnome-terminal to run ubuntu-bug, which brought up the firefox window. I am running off the amd64 live desktop image burned to a 8GB USB stick. I expect the mouse to be responsive shortly after boot, around the same time as the keyboard. ProblemType: Bug Architecture: amd64 Date: Sun Mar 28 04:37:10 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/gnome-power-manager GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No LiveMediaBuild: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100327) MachineType: Dell Inc. Latitude D630 Package: gnome-power-manager 2.29.91-0ubuntu9 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 SourcePackage: gnome-power-manager Uname: Linux 2.6.32-17-generic x86_64 XsessionErrors: (polkit-gnome-authentication-agent-1:11622): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (gnome-terminal:12486): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL entry-lock_count 0' failed dmi.bios.date: 11/24/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.asset.tag: 161910 dmi.board.name: 0WM416 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: 161910 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0WM416:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- mouse does not resume after waking from suspend to ram triggered by closing lid https://bugs.launchpad.net/bugs/550046 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550046] Re: mouse does not resume after waking from suspend to ram triggered by closing lid
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/42240889/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/42240890/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/42240891/Dependencies.txt ** Attachment added: DevkitPower.txt http://launchpadlibrarian.net/42240892/DevkitPower.txt ** Attachment added: GConfNonDefault.txt http://launchpadlibrarian.net/42240893/GConfNonDefault.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/42240894/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/42240895/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/42240896/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/42240897/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/42240898/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/42240899/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/42240900/ProcStatus.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/42240901/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/42240902/UdevLog.txt ** Attachment added: gnome-power-bugreport.txt http://launchpadlibrarian.net/42240903/gnome-power-bugreport.txt -- mouse does not resume after waking from suspend to ram triggered by closing lid https://bugs.launchpad.net/bugs/550046 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550046] Re: mouse does not resume after waking from suspend to ram triggered by closing lid
Some further testing shows that every alternate wake from suspend to RAM while running off the amd64 live image results in a blank screen at wake. Switching to the first or second virtual console works, and then going to virtual console 7 (in which the x session is running) brings back the display. The order of events is: 1. Suspend by closing lid. 2. Open lid, note problem with mouse pointer disappearing as reported above. 3. Suspend by closing lid. 4. Open lid and get a black screen. 5. Attempt to switch to different virtual console, successful. 6. Switch back to virtual console 7. Get restored X session. 7. Suspend by closing lid. 8. Open lid and have system restore to X session very fast. 9. Suspend by closing lid. 10. Open lid and get a black screen. 11. Switch to virtual console 1 or 2. Then back to 7 and return to X session. So it appears that waking from suspend to RAM in even-numbered sessions has problems with restoring the X session and requires that you switch to a different virtual console and switch back to console 7. I have also noticed that the problem with the mouse (reported above) only happened after the first wake from suspend to RAM. -- mouse does not resume after waking from suspend to ram triggered by closing lid https://bugs.launchpad.net/bugs/550046 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
