[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2012-04-16 Thread Joseph Salisbury
@Atheist1993 Can you apply the latest updates and see if the latest kernel also fixes this bug for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Suspend (to RAM) Cando touc

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2012-04-14 Thread mweyen
seems to be fixed for me in precise with the updates of now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Suspend (to RAM) Cando touchscreen stops working To manage notification

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2012-04-13 Thread Brad Figg
Thank you for taking the time to file a bug report on this issue. However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is s

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2012-04-13 Thread Fabio Marconi
** Tags added: natty oneiric precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Suspend (to RAM) Cando touchscreen stops working To manage notifications about this bug go to:

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2012-04-13 Thread mweyen
i have the same problem as described with the latest precise beta version (and before with oneiric). Acer 1825PTZ here too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Suspend (

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-30 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Suspend (to RAM) Cando touchscreen stops working To manage notific

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-24 Thread Fabio Marconi
** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Suspend (to RAM)

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-24 Thread fgossart
I try now the kernel 3.2 RC2 My wireless is not active now But suspend touchscreen bug is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Suspend (to RAM) Cando touchscre

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-24 Thread fgossart
having a 1825ptz, I have the same bug when suspend and BIOS is V1.3127 I tried with some kernels 3.0XX and 3.1XX ubuntu is 11.10 64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-18 Thread Fabio Marconi
>From Kern.log attached in #7 Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [0.00] WARNING: at /build/buildd/linux-3.0.0/drivers/pci/dmar.c:634 warn_invalid_dmar+0x8f/0xa0() Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [0.00] Hardware name: Aspire 1825PTZ Nov 13 18:59:57 malti-Aspi

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-15 Thread sapiensapiens
Nice catch! But...I reinstalled the BIOS but the issue persists. Exact same output. The BIOS version I have is the latest one (V1.3127) so updating doesn't apply here. The issue doesn't affect Windows 7. Thanks again, -- You received this bug notification because you are a member of Ubuntu Bug

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-13 Thread Fabio Marconi
So please try to fix this reinstalling or updating your bios. Thanks Fabio ** Changed in: ubuntu Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: A

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-13 Thread Fabio Marconi
Ok, looking at kern.log we can see just at the start this error: WARNING: at /build/buildd/linux-3.0.0/drivers/pci/dmar.c:634 warn_invalid_dmar+0x8f/0xa0() Hardware name: Aspire 1825PTZ Nov 13 18:59:57 malti-Aspire-1825PTZ kernel: [0.00] Your BIOS is broken; DMAR reported at address 0!

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-13 Thread sapiensapiens
Hey Fabio, Thanks for the prompt reply. I attached the following files for a vanilla kernel on a fresh Oneiric install: /var/log/kern.log /var/log/dmesg /var/log/dmesg.0 There's no /var/log/kern.log.1 on my system. I hope this helps, ** Attachment added: "log_files.tar.gz" https://bugs.lau

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-12 Thread Fabio Marconi
Hello sapienssapiens >From the attached logs i can see that you are running an upstream kernel >(3.0.0-rc7) To triage your bug we need to work with a standard kernel, so if you are in natty please upgrade to oneiric, elsewhere if you are in Oneiric boot from the standard kernel and attach the re

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-12 Thread sapiensapiens
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+bug/783587/+attachment/2594017/+files/dmesg ** Changed in: ubuntu Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-12 Thread sapiensapiens
** Attachment added: "kern.log.1" https://bugs.launchpad.net/ubuntu/+bug/783587/+attachment/2594016/+files/kern.log.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Suspend (t

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-11-12 Thread sapiensapiens
** Also affects: fedora Importance: Undecided Status: New ** Changed in: ubuntu Status: Expired => Incomplete ** Attachment added: "Log files as requested by Fabio." https://bugs.launchpad.net/ubuntu/+bug/783587/+attachment/2594015/+files/kern.log -- You received this bug n

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-07-17 Thread Launchpad Bug Tracker
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783587 Title: After Sus

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-05-18 Thread Fabio Marconi
Hello Atheist1993 Can you please reproduce the bug and attach here, using below button 'Add attachment or patch' the files: /var/log/kern.log /var/log/kern.log.1 /var/log/dmesg Thanks Fabio ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you

[Bug 783587] Re: After Suspend (to RAM) Cando touchscreen stops working

2011-05-16 Thread Atheist1993
** Description changed: On my ACER1825PTZ (netvertible) a capacitive touch-screen (listed as Cando) is used. - It works quite well, but after suspending (and unsuspending of course) it didn't restart. + It works quite well, but after suspending (and unsuspending of course) it didn't restart (