[Bug 350409] Re: [TOSHIBA Satellite M105] suspend/resume failure
** Attachment added: version.log http://launchpadlibrarian.net/24456758/version.log ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/24456759/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/24456760/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24456761/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/24456762/HalComputerInfo.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/24456763/Lspci.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/24456764/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/24456765/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/24456766/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/24456767/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/24456768/ProcStatus.txt -- [TOSHIBA Satellite M105] suspend/resume failure https://bugs.launchpad.net/bugs/350409 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 350409] [NEW] [TOSHIBA Satellite M105] suspend/resume failure
Public bug reported: Is this really a failure: Yes. The battery is fully charged and the AC adapter is plugged in. Is this repetition of a previous failure: Yes. This laptop has never supended properly in any edition of Ubuntu, nor any other distribution of Linux for that matter. I am only talking about suspend-to-ram. Suspending to disk(Hibernate) does resume properly and consistently. Did the machine break while going to sleep or waking up?: As far as I can tell, it breaks upon waking up. On sleep, the screen dims, shuts off, and both the power LED and power button change from a constant green to a pulsing orange, indicating sleep. Upon waking back up, the fan spins, but the lcd does not turn on. There is no indication that anything is going on. Did it work before?: No. Suspend-to-ram has never worked. Did you end up with flashing caps-lock or similar?: No, the caps lock light does not flash on resume. The LED responds as it does during normal operation: it toggles on and off with a keypress. I will follow up with further information from the output of pm-suspend ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: TOSHIBA Satellite M105 Package: linux-image-2.6.28-11-generic 2.6.28-11.37 ProcAttrCurrent: unconfined ProcCmdLine: root=UUID=eb868545-07f4-4857-90b0-bb1bfa00f547 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-11.37-generic SourcePackage: linux StressLog: v--- Waiting for suspend to complete 29 to go ... Waiting for suspend to complete 28 to go ... Waiting for suspend to complete 27 to go ... Tags: resume suspend Title: [TOSHIBA Satellite M105] suspend/resume failure UserGroups: ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume suspend -- [TOSHIBA Satellite M105] suspend/resume failure https://bugs.launchpad.net/bugs/350409 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 350409] Re: [TOSHIBA Satellite M105] suspend/resume failure
** Description changed: - - Is this really a failure: Yes. The battery is fully charged and the AC adapter is plugged in. + Is this really a failure: Yes. The battery is fully charged and the AC + adapter is plugged in. Is this repetition of a previous failure: Yes. This laptop has never supended properly in any edition of Ubuntu, nor any other distribution of Linux for that matter. I am only talking about suspend-to-ram. Suspending to disk(Hibernate) does resume properly and consistently. Did the machine break while going to sleep or waking up?: As far as I can tell, it breaks upon waking up. On sleep, the screen dims, shuts off, and both the power LED and power button change from a constant green to a pulsing orange, indicating sleep. Upon waking back up, the fan spins, but the lcd does not turn on. There is no indication that anything is going on. Did it work before?: No. Suspend-to-ram has never worked. - Did you end up with flashing caps-lock or similar?: No, the caps lock - light does not flash on resume. The LED responds as it does during - normal operation: it toggles on and off with a keypress. + Did you end up with flashing caps-lock or similar?: Upon resume, no: the + caps lock light does not flash on resume. In fact, the Caps Lock key + doesn't do anything; upon key press, the LED does not toggle. However, + the power led and button are green, indicating the machine is on, as + opposed to sleeping. I will follow up with further information from the output of pm-suspend ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: TOSHIBA Satellite M105 Package: linux-image-2.6.28-11-generic 2.6.28-11.37 ProcAttrCurrent: unconfined ProcCmdLine: root=UUID=eb868545-07f4-4857-90b0-bb1bfa00f547 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-11.37-generic SourcePackage: linux StressLog: v--- Waiting for suspend to complete 29 to go ... Waiting for suspend to complete 28 to go ... Waiting for suspend to complete 27 to go ... Tags: resume suspend Title: [TOSHIBA Satellite M105] suspend/resume failure UserGroups: -- [TOSHIBA Satellite M105] suspend/resume failure https://bugs.launchpad.net/bugs/350409 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 350409] Re: [TOSHIBA Satellite M105] suspend/resume failure
I did the steps described in https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume regarding pm-suspend. There was no difference in output. However, upon switching to the console, I got the series of messages in the attached image. I will follow up with output from following the guidelines in https://wiki.ubuntu.com/DebuggingKernelSuspend ** Attachment added: DSC00117.JPG http://launchpadlibrarian.net/24458674/DSC00117.JPG -- [TOSHIBA Satellite M105] suspend/resume failure https://bugs.launchpad.net/bugs/350409 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 350409] Re: [TOSHIBA Satellite M105] suspend/resume failure
Actually, I won't. Aren't the steps outlined in the latter link the steps that are now performed automatically in Jaunty? -- [TOSHIBA Satellite M105] suspend/resume failure https://bugs.launchpad.net/bugs/350409 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 222756] Re: gnome-terminal, firefox and nautilus freeze
Could you attach the contents of your .xsession-errors? I have the same problem as you. -- gnome-terminal, firefox and nautilus freeze https://bugs.launchpad.net/bugs/222756 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 197452] Re: gnome-sound-recorder does not start with usb mike
This is still a problem in Hardy (8.04). If you disable PulseAudio, and make the default source USB Audio via gstreamer-properties, gnome-sound-recorder reports the same error. -- gnome-sound-recorder does not start with usb mike https://bugs.launchpad.net/bugs/197452 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 223452] [NEW] USB mic produces garbled output in System-Preferences-Sound Using Pulseaudio
Public bug reported: I have a Logitech Quickcam STX. I also have Intel HDA provided by Realtek ALC883 drivers. My webcam includes a USB mic, and it records fine when ALSA manages sound input and output. When I turn on the Pulseaudio server and set the default source to the usb mic via padevchooser, Gnome Sound Recorder also records fine from it. What fails to work properly is the following: Ensure that the usb mic is set as the default source for pulseaudio (I did via padevchooser). Go to System-Preferences-Sound Ensure all inputs and outputs are using Pulseaudio Run Test for sound capture. What happens to me is that 1 second of garbled recording from the mic is played live, then silence. What should happen: When I hit test, I should be able to hear myself speak through the mic. I am using Hardy Heron 8.04 ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - USB mic produces garbled output in System-Prefereces-Sound Using Pulseaudio + USB mic produces garbled output in System-Preferences-Sound Using Pulseaudio -- USB mic produces garbled output in System-Preferences-Sound Using Pulseaudio https://bugs.launchpad.net/bugs/223452 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 223452] Re: USB mic produces garbled output in System-Preferences-Sound Using Pulseaudio
I did some searching, and it seems to be the same as this issue. http://www.pulseaudio.org/ticket/270 I have attached a log with the message that play when the test is engaged. ** Attachment added: debug_log.txt http://launchpadlibrarian.net/13977878/debug_log.txt -- USB mic produces garbled output in System-Preferences-Sound Using Pulseaudio https://bugs.launchpad.net/bugs/223452 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 222883] [NEW] Test sound source in system-sound is distorted
Public bug reported: In Hardy Heron Go to System-Preferences-Sounds Select Autoselect for Sound Output Select the Test Audio Source for Sound Capture. Press test. The audio should beep for a few seconds before distoring horribly, then turning into silence. There is no crash. The test simply ceases to play sound soon after. ** Affects: ubuntu Importance: Undecided Status: New -- Test sound source in system-sound is distorted https://bugs.launchpad.net/bugs/222883 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 87539] Re: Many examples from python-qt4-doc crashes.
I am attempted to implement overpainting as outlined in /usr/share/doc /python-qt4-doc/examples/opengl/overpainting.py. Unfortunately, I can't because the example I am following doesn't work. I am not the only one with this error: http://article.gmane.org/gmane.comp.python.pyqt- pykde/9548/match=overpainting http://episteme.arstechnica.com/eve/forums?a=tpcs=50009562f=96509133m=969006996831r=88007831#88007831 However, when contacting riverbank computing about the failure of the example, I was told works for me. This is the only example I've tried to run. If there are other failing examples, perhaps this is symptomatic of something wrong? -- Many examples from python-qt4-doc crashes. https://bugs.launchpad.net/bugs/87539 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 12124] Re: touchpads occasionally gone wild
his was a problem for me in Dapper and remains an issue in Edgy. I have a Alps Glidepoint touchpad on my Toshiba M100, and it is detected as such. Unfortunately, sometimes the mouse jumps around on screen, quadruple taps on movement. Sometimes, moving the mouse results in whatever application I have focused behaving as if I pressed the F7 key (which is really annoying in Firefox- I get ~10 windows asking if I want to enable Caret Browsing). I opened up /var/log/syslog when using both Dapper (2.6.15) and Edgy (2.6.17) and something approximating the following always shows up when my touchpad goes berserk: Oct 20 00:35:04 localhost kernel: [17180160.432000] psmouse.c: GlidePoint at isa0060/serio4/input0 lost sync at byte 1 Oct 20 00:35:04 localhost kernel: [17180160.436000] psmouse.c: GlidePoint at isa0060/serio4/input0 - driver resynched. Oct 20 00:35:04 localhost kernel: [17180160.436000] psmouse.c: GlidePoint at isa0060/serio4/input0 lost sync at byte 1 Oct 20 00:35:04 localhost kernel: [17180160.448000] psmouse.c: GlidePoint at isa0060/serio4/input0 - driver resynched. In Edgy (2.6.17), a new behavior will sometimes occur: Oct 20 00:35:05 localhost kernel: [17180161.272000] psmouse.c: GlidePoint at isa0060/serio4/input0 lost synchronization, throwing 1 bytes away. Oct 20 00:35:06 localhost kernel: [17180161.776000] psmouse.c: resync failed, issuing reconnect request Oct 20 00:35:06 localhost kernel: [17180162.504000] input: PS/2 Mouse as /class/input/input6 Oct 20 00:35:06 localhost kernel: [17180162.524000] input: AlpsPS/2 ALPS GlidePoint as /class/input/input7 This resyncing results in the Glidepoint being treated only as a PS/2 Mouse (i.e no vertical/horizontal scrolling, no tap-and-drag). Everytime this behavior happens, the two mice are reattached to /class/input/n+1 -- touchpads occasionally gone wild https://launchpad.net/bugs/12124 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60985] There is a new version out
Public bug reported: The version of festalon packaged for ubuntu is 0.2. The latest version of festalon is 0.5.5 and is available at: http://projects.raphnet.net/#festalon Could someone update the ubuntu package? ** Affects: festalon (Ubuntu) Importance: Untriaged Status: Unconfirmed -- There is a new version out https://launchpad.net/bugs/60985 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
