[Kernel-packages] [Bug 1676918] Re: blackscreen when trying to resume from suspend

2017-03-28 Thread Daniel Holz
** Package changed: ubuntu => linux (Ubuntu)

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-power-manager (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1676918

Title:
  blackscreen when trying to resume from suspend

Status in gnome-power-manager package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676918] Re: blackscreen when trying to resume from suspend

2017-03-28 Thread Daniel Holz
apport information

** Tags added: apport-collected wayland-session zesty

** Description changed:

  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.
  
  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland.
+ --- 
+ ApportVersion: 2.20.4-0ubuntu2
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 17.04
+ InstallationDate: Installed on 2017-03-24 (4 days ago)
+ InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
+ Package: systemd 232-19
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ Tags:  zesty wayland-session
+ Uname: Linux 4.8.17-040817-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1676918/+attachment/4849417/+files/Dependencies.txt

-- 
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/1676918

Title:
  blackscreen when trying to resume from suspend

Status in gnome-power-manager package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676918] JournalErrors.txt

2017-03-28 Thread Daniel Holz
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1676918/+attachment/4849418/+files/JournalErrors.txt

-- 
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/1676918

Title:
  blackscreen when trying to resume from suspend

Status in gnome-power-manager package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676912] Re: Suspend - Freezing of tasks failed

2017-03-28 Thread Daniel Holz
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1676912

Title:
  Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676918] Re: blackscreen when trying to resume from suspend

2017-03-28 Thread Daniel Holz
** Description changed:

  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.
  
  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland.
- --- 
+ 
+ I'm currently testing Kernel 4.8 from the mainline ppa because of this
+ other suspend resume bug, that appeared only with 17.04:
+ 
+ https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912
+ 
+ ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

-- 
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/1676918

Title:
  blackscreen when trying to resume from suspend

Status in gnome-power-manager package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676912] Re: Suspend - Freezing of tasks failed

2017-03-29 Thread Daniel Holz
This problem also appears whenn using Kernel 4.11 from the mainline ppa.

-- 
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/1676912

Title:
  Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676912] Re: Suspend - Freezing of tasks failed

2017-03-29 Thread Daniel Holz
I had some similar suspend/resume issues when trying mainline Kernels in 16.04. 
Every Kernel since 4.9 would cause terribly slow system after resuming. 
I will test Kernel 4.8 in next days to see if this problem is present there too.

-- 
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/1676912

Title:
  Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676918] Re: blackscreen when trying to resume from suspend

2017-03-29 Thread Daniel Holz
Trying Kernel 4.11 since yesterday. So far no blackscreens but I think I
should test it for a longer duration. Unfortunately Kernel 4.11 is no
real solution for me because of another suspend/resume bug that as far
as I can tell at the moment might exist since Kernel 4.9.

-- 
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/1676918

Title:
  blackscreen when trying to resume from suspend

Status in gnome-power-manager package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676918] Re: blackscreen when trying to resume from suspend

2017-03-30 Thread Daniel Holz
Got a blackscreen with Kernel 4.11. Unfortunately kern.log and syslog
don't have any entries about it.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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/1676918

Title:
  blackscreen when trying to resume from suspend

Status in gnome-power-manager package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676918] Re: Kernel 4.10+ regression: blackscreen when trying to resume from suspend

2017-04-02 Thread Daniel Holz
** Summary changed:

- blackscreen when trying to resume from suspend
+ Kernel 4.10+ regression: blackscreen when trying to resume from suspend

** Description changed:

  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.
  
  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland.
  
  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:
  
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912
+ 
+ Update: So far I did not encounter any issues with suspend/resume with
+ Kernel 4.8 and 4.9. This seems to be a regression in 4.10.
  
  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

-- 
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/1676918

Title:
  Kernel 4.10+ regression: blackscreen when trying to resume from
  suspend

Status in gnome-power-manager package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  Update: So far I did not encounter any issues with suspend/resume with
  Kernel 4.8 and 4.9. This seems to be a regression in 4.10.

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1676912] Re: Suspend - Freezing of tasks failed

2017-04-02 Thread Daniel Holz
** Description changed:

  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears and
  allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.
  
  In syslog I found the line:
  
  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"
  
  According to syslog
  
  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor
  
  are responsible.
  I tried disabling some of them, but it did not solve the problem.
  
+ Update: I tested different Kernel versions in the last days. So far
+ there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
+ problem is present in 4.10 and 4.11.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

** Summary changed:

- Suspend - Freezing of tasks failed
+ Kernel 4.10+ regression: Suspend - Freezing of tasks failed

-- 
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/1676912

Title:
  Kernel 4.10+ regression: Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom,

[Kernel-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

2017-04-04 Thread Daniel Holz
** Summary changed:

- Kernel 4.10+ regression: Suspend - Freezing of tasks failed
+ Kernel 4.9+ regression: Suspend - Freezing of tasks failed

** Description changed:

  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears and
  allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.
  
  In syslog I found the line:
  
  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"
  
  According to syslog
  
  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor
  
  are responsible.
  I tried disabling some of them, but it did not solve the problem.
  
  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.
  
+ Update 2: I just encountered this issue with Kernel 4.9.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

-- 
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/1676912

Title:
  Kernel 4.9+ regression: Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.

  Update 2: I just encountered this issue with Kernel 4.9.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
  

[Kernel-packages] [Bug 1123943] Re: Chrontel CH7036 chip not supported

2014-06-13 Thread Daniel Holz
I already thought about offering a package of the driver on my blog, but
sadly even with some online tutorials I wasn't able to create a working
package.

-- 
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/1123943

Title:
  Chrontel CH7036 chip not supported

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I'm running a WeTab with ubuntu and the ch7036 chip is not supported.
  There is a driver for the chromebook (called chrontel), but that driver is 
more or less a hacked daemon that sends some data to the chip and gives me the 
following error message:

  Found device ID 0x56
  Found revision ID 0x81
  Mode 1366x786 (44)
  1366y786, dot clock 6930  -Hsync -Vsync
  H: start 1414, end 1446, skew 0, total 1456
  V: start 771, end 777, total 793
  State: 0
  Firmware size = 3295 bytes.
  State: 2
  State: 3
  Timeout waiting for MCU to return EDID
  CH7036 MCU ver 1.41, Device 56 rev 1 capability 0x1
  EDID timed out: Ignore HPD because EDID failed just after firmware load
  Get EDOD Failed (initial block) using 640x480@60
  Could not find a useful resolution. Maybe hardware problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Feb 13 10:46:06 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Device [1b0a:00c7]
 Subsystem: Device [1b0a:00c7]
  InstallationDate: Installed on 2013-02-08 (4 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MachineType: PEGATRON WeTab
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic 
root=UUID=7cedb257-8646-45d8-a06b-c1a32d485cec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Lucid-GE-133
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: WeTab
  dmi.board.vendor: PEGATRON
  dmi.board.version: 30011578
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: PEGATRON
  dmi.chassis.version: TT116A01
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrLucid-GE-133:bd11/19/2010:svnPEGATRON:pnWeTab:pvrTT116A01:rvnPEGATRON:rnWeTab:rvr30011578:cvnPEGATRON:ct1:cvrTT116A01:
  dmi.product.name: WeTab
  dmi.product.version: TT116A01
  dmi.sys.vendor: PEGATRON
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Wed Feb 13 10:45:09 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1123943] Re: Chrontel CH7036 chip not supported

2014-02-01 Thread Daniel Holz
I'm the creator of this blog. I'm using a WeTab which uses the same
hardware as the bModo 12 so it should normally work. Did you try it when
the hdmi was originally off?

-- 
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/1123943

Title:
  Chrontel CH7036 chip not supported

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I'm running a WeTab with ubuntu and the ch7036 chip is not supported.
  There is a driver for the chromebook (called chrontel), but that driver is 
more or less a hacked daemon that sends some data to the chip and gives me the 
following error message:

  Found device ID 0x56
  Found revision ID 0x81
  Mode 1366x786 (44)
  1366y786, dot clock 6930  -Hsync -Vsync
  H: start 1414, end 1446, skew 0, total 1456
  V: start 771, end 777, total 793
  State: 0
  Firmware size = 3295 bytes.
  State: 2
  State: 3
  Timeout waiting for MCU to return EDID
  CH7036 MCU ver 1.41, Device 56 rev 1 capability 0x1
  EDID timed out: Ignore HPD because EDID failed just after firmware load
  Get EDOD Failed (initial block) using 640x480@60
  Could not find a useful resolution. Maybe hardware problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Feb 13 10:46:06 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Device [1b0a:00c7]
 Subsystem: Device [1b0a:00c7]
  InstallationDate: Installed on 2013-02-08 (4 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MachineType: PEGATRON WeTab
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic 
root=UUID=7cedb257-8646-45d8-a06b-c1a32d485cec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Lucid-GE-133
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: WeTab
  dmi.board.vendor: PEGATRON
  dmi.board.version: 30011578
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: PEGATRON
  dmi.chassis.version: TT116A01
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrLucid-GE-133:bd11/19/2010:svnPEGATRON:pnWeTab:pvrTT116A01:rvnPEGATRON:rnWeTab:rvr30011578:cvnPEGATRON:ct1:cvrTT116A01:
  dmi.product.name: WeTab
  dmi.product.version: TT116A01
  dmi.sys.vendor: PEGATRON
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Wed Feb 13 10:45:09 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1123943] Re: Chrontel CH7036 chip not supported

2014-02-02 Thread Daniel Holz
Yeah there are many tablets like this. They are alll based on the
Pegatron Lucid and sold under the name ExoPC, WeTab, Ciara Vibe, JS-Tab,
W8Pad etc. Most come with Windows 7 but the WeTab came with its own
Meego-based OS which had drivers for everything in the tablet.

Did you try some configuration options in /etc/chrontel-wetab.conf?

You could try the -E-parameter for forcing some test edid numbers. 
Maybe with that the driver ignores the missing signal.
If that doesn't work you can force one of the following resolutions 

0 - HDMI 640x480
 1 - HDMI 720x480
 2 - HDMI 1280x720
 3 - HDMI 1920x1080
 4 - HDMI 1920x1080
 5 - HDMI 720x576
 6 - HDMI 1280x720
 7 - HDMI 1920x1080
 8 - HDMI 1920x1080
 9 - DVI 640x480
10 - DVI 720x480
11 - DVI 720x576
12 - DVI 800x600
13 - DVI 1024x768
14 - DVI 1280x720
15 - DVI 1280x1024
16 - DVI 1440x900
17 - DVI 1680x1050
18 - DVI 1920x1080
19 - DVI 1600x1200
20 - DVI 1600x1200
21 - DVI 1600x1200
22 - DVI 1920x1200 

with -M.

Even though the linux driver is a piece of crap it offers much higher
resolutions. :D

-- 
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/1123943

Title:
  Chrontel CH7036 chip not supported

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  I'm running a WeTab with ubuntu and the ch7036 chip is not supported.
  There is a driver for the chromebook (called chrontel), but that driver is 
more or less a hacked daemon that sends some data to the chip and gives me the 
following error message:

  Found device ID 0x56
  Found revision ID 0x81
  Mode 1366x786 (44)
  1366y786, dot clock 6930  -Hsync -Vsync
  H: start 1414, end 1446, skew 0, total 1456
  V: start 771, end 777, total 793
  State: 0
  Firmware size = 3295 bytes.
  State: 2
  State: 3
  Timeout waiting for MCU to return EDID
  CH7036 MCU ver 1.41, Device 56 rev 1 capability 0x1
  EDID timed out: Ignore HPD because EDID failed just after firmware load
  Get EDOD Failed (initial block) using 640x480@60
  Could not find a useful resolution. Maybe hardware problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Wed Feb 13 10:46:06 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Device [1b0a:00c7]
 Subsystem: Device [1b0a:00c7]
  InstallationDate: Installed on 2013-02-08 (4 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MachineType: PEGATRON WeTab
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic 
root=UUID=7cedb257-8646-45d8-a06b-c1a32d485cec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Lucid-GE-133
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: WeTab
  dmi.board.vendor: PEGATRON
  dmi.board.version: 30011578
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: PEGATRON
  dmi.chassis.version: TT116A01
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrLucid-GE-133:bd11/19/2010:svnPEGATRON:pnWeTab:pvrTT116A01:rvnPEGATRON:rnWeTab:rvr30011578:cvnPEGATRON:ct1:cvrTT116A01:
  dmi.product.name: WeTab
  dmi.product.version: TT116A01
  dmi.sys.vendor: PEGATRON
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Wed Feb 13 10:45:09 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

To manage notifications about this bug go to:
htt

[Kernel-packages] [Bug 1326885] Re: desktop start rotated

2015-02-25 Thread Daniel Holz
I wrote this guide because I had the same problem with my WeTab:

http://lackofalucidmind-en.blogspot.de/2014/06/wrong-screen-orientation-
at-greeter-and.html

-- 
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/1326885

Title:
  desktop start rotated

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after
  login the screen rotates to rightwards (no matter what direction the
  screen is actually at). I had to run this everytime:

  $ xrandr -o normal

  Note this is not gravity sensor at work. If gravity sensor is at work,
  and turned screen leftwards or rightwards, 'xrandr -o normal' will not
  have any effect.

  Expected behaviour: the desktop rotation should be decided by gravity sensor, 
or, without its input, defaults to normal. If it is intended that even without 
gravity sensor input the desktop should rotate anyway (because it consider 
itself running on a tablet) then it should do so since login screen, not to 
change orientation right after login.
  ---
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-04-28 (38 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.15.0-031500rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp