kernel-packages team mailing list archive

[Kinsey Zarske <kinseyann.zarske@xxxxxxxxxxxxxx>]

It was my brother's computer, and he no longer has it. Without the
computer, I'm afraid I can't help.
Sorry,
Kinsey
On Aug 24, 2013 8:21 PM, "Christopher M. Penalver" <
christopher.m.penalver@xxxxxxxxx> wrote:

> Kinsey Zarske, this bug was reported a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an
> issue? If so, could you please test for this with the latest development
> release of Ubuntu? ISO images are available from
> http://cdimage.ubuntu.com/daily-live/current/ .
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications->Accessories->Terminal), as it will automatically gather
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-with-bug-number>
>
> Also, could you please test the latest upstream kernel available following
> https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
> upstream developers to examine the issue. Please do not test the daily
> folder, but the one all the way at the bottom. Once you've tested the
> upstream kernel, please comment on which kernel version specifically you
> tested. If this bug is fixed in the mainline kernel, please add the
> following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested. For
> example:
> kernel-fixed-upstream-v3.11-rc5
>
> This can be done by clicking on the yellow circle with a black pencil icon
> next to the word Tags located at the bottom of the bug description. As
> well, please remove the tag:
> needs-upstream-testing
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> As well, please remove the tag:
> needs-upstream-testing
>
> Once testing of the upstream kernel is complete, please mark this bug's
> Status as Confirmed. Please let us know your results. Thank you for your
> understanding.
>
> ** Tags added: needs-full-computer-model needs-upstream-testing
>
> ** Changed in: linux (Ubuntu)
>        Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1005058
>
> Title:
>   screen issue after using lockscreen then suspend immediately
>
> Status in “linux” package in Ubuntu:
>   Incomplete
>
> Bug description:
>   On a fresh install of 12.04:
>   -Hardware is an Acer Aspire with a 1.6 GHz Intel Atom processor.
>   -When you select suspend, and then close the lid, all is well.
>   -When you select lock screen, and then close the lid, it seems fine.
> However, when you try to resume, the screen flicks on and off, only
> remaining on for a second or two, making the system unusable. The only way
> I found to stop it was to turn it off by holding down the power button, and
> then turning it back on.
>   -This is the only computer I have this version installed on, so I don't
> know if this is hardware specific or not. I searched google and the usual
> forums, but I came up empty.
>   -The computer seemed unaware it had an issue, so I doubt the log files
> were preserved when I had to power it off to restore usability.
>   ---
>   AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
>   ApportVersion: 1.95-0ubuntu1
>   Architecture: i386
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC0:  michael    1629 F.... pulseaudio
>   CurrentDmesg: [  139.436694] init: plymouth-stop pre-start process
> (2117) terminated with status 1
>   DistroRelease: Ubuntu 12.04
>   HibernationDevice: RESUME=UUID=f913c22a-324a-4d2a-9920-7c531ac51b04
>   InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386
> (20120328)
>   MachineType: Acer Aspire one
>   Package: linux (not installed)
>   ProcEnviron:
>    TERM=xterm
>    LANG=en_US.UTF-8
>    SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae
> root=UUID=06b18e2c-8596-4633-90ed-3f5da919e7ba ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
>   Tags:  precise
>   Uname: Linux 3.2.0-20-generic-pae i686
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   dmi.bios.date: 04/13/2009
>   dmi.bios.vendor: Acer
>   dmi.bios.version: V1.03
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: Aspire one
>   dmi.board.vendor: Acer
>   dmi.board.version: V1.03
>   dmi.chassis.type: 1
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V1.03
>   dmi.modalias:
> dmi:bvnAcer:bvrV1.03:bd04/13/2009:svnAcer:pnAspireone:pvrV1.03:rvnAcer:rnAspireone:rvrV1.03:cvnAcer:ct1:cvrV1.03:
>   dmi.product.name: Aspire one
>   dmi.product.version: V1.03
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005058/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1005058

Title:
  screen issue after using lockscreen then suspend immediately

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  On a fresh install of 12.04:
  -Hardware is an Acer Aspire with a 1.6 GHz Intel Atom processor.
  -When you select suspend, and then close the lid, all is well.
  -When you select lock screen, and then close the lid, it seems fine. However, when you try to resume, the screen flicks on and off, only remaining on for a second or two, making the system unusable. The only way I found to stop it was to turn it off by holding down the power button, and then turning it back on.
  -This is the only computer I have this version installed on, so I don't know if this is hardware specific or not. I searched google and the usual forums, but I came up empty.
  -The computer seemed unaware it had an issue, so I doubt the log files were preserved when I had to power it off to restore usability.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.95-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  michael    1629 F.... pulseaudio
  CurrentDmesg: [  139.436694] init: plymouth-stop pre-start process (2117) terminated with status 1
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=f913c22a-324a-4d2a-9920-7c531ac51b04
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  MachineType: Acer Aspire one
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=06b18e2c-8596-4633-90ed-3f5da919e7ba ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
  Tags:  precise
  Uname: Linux 3.2.0-20-generic-pae i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/13/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.03
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire one
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: dmi:bvnAcer:bvrV1.03:bd04/13/2009:svnAcer:pnAspireone:pvrV1.03:rvnAcer:rnAspireone:rvrV1.03:cvnAcer:ct1:cvrV1.03:
  dmi.product.name: Aspire one
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005058/+subscriptions