[Touch-packages] [Bug 1606122] Re: Cairo drawing coordinates are broken w/nouveau (affects xfwm4)

[Ryan Prichard]

Here's what the test program's output *should* look like, using the
NVIDIA driver.

$ apt-cache policy nvidia-361
nvidia-361:
  Installed: 361.42-0ubuntu2
  Candidate: 361.42-0ubuntu2
  Version table:
 *** 361.42-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu xenial/restricted amd64 Packages
100 /var/lib/dpkg/status


** Attachment added: "correct-nvidia.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1606122/+attachment/4706859/+files/correct-nvidia.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1606122

Title:
  Cairo drawing coordinates are broken w/nouveau (affects xfwm4)

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using xfwm4 with Xubuntu 16.04.  With compositing enabled, and
  when I cycle through windows with Alt-Tab, xfwm4 draws an opaque
  rectangle bordering a candidate window, and it fills that rectangle
  with a semi-transparent blue color.  When I use the nouveau driver,
  the filled rectangle is clipped.  The problem does not reproduce with
  the proprietary nvidia driver.

  It seems as though a drawing command should be issued using a window-
  relative coordinate, but sometimes is instead issued using a screen-
  relative coordinate.

  I extracted relevant bits of xfwm4 into a small test program that
  reproduces the problem.  The test program creates a transparent
  XWindow at (100,100) with size (210,210).  It draws six rectangles
  centered inside the window of varying parameters.  Two of them are
  drawn at the wrong place.

  xfwm4 should be off-the-hook, I think, unless it's doing something
  wrong (e.g. unspecified/undefined behavior).

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy xserver-xorg-video-nouveau
  xserver-xorg-video-nouveau:
Installed: 1:1.0.12-1build2
Candidate: 1:1.0.12-1build2
Version table:
   *** 1:1.0.12-1build2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy xfwm4
  xfwm4:
Installed: 4.12.3-1ubuntu2
Candidate: 4.12.3-1ubuntu2
Version table:
   *** 4.12.3-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  I created a video demonstrating the problem in xfwm4:
  https://www.youtube.com/watch?v=8dZN80tMA6M.  If you look closely, you
  can see that the opaque blue border is positioned correctly, while the
  semi-transparent overlay isn't.

  FWIW, I'm using an NVIDIA GeForce GTX 750 Ti card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul 25 00:50:21 2016
  InstallationDate: Installed on 2016-07-19 (6 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1606122] Re: Cairo drawing coordinates are broken w/nouveau (affects xfwm4)

[Ryan Prichard]

Here's the test program's output with the nouveau driver.

** Attachment added: "broken-nouveau.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1606122/+attachment/4706860/+files/broken-nouveau.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1606122

Title:
  Cairo drawing coordinates are broken w/nouveau (affects xfwm4)

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using xfwm4 with Xubuntu 16.04.  With compositing enabled, and
  when I cycle through windows with Alt-Tab, xfwm4 draws an opaque
  rectangle bordering a candidate window, and it fills that rectangle
  with a semi-transparent blue color.  When I use the nouveau driver,
  the filled rectangle is clipped.  The problem does not reproduce with
  the proprietary nvidia driver.

  It seems as though a drawing command should be issued using a window-
  relative coordinate, but sometimes is instead issued using a screen-
  relative coordinate.

  I extracted relevant bits of xfwm4 into a small test program that
  reproduces the problem.  The test program creates a transparent
  XWindow at (100,100) with size (210,210).  It draws six rectangles
  centered inside the window of varying parameters.  Two of them are
  drawn at the wrong place.

  xfwm4 should be off-the-hook, I think, unless it's doing something
  wrong (e.g. unspecified/undefined behavior).

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy xserver-xorg-video-nouveau
  xserver-xorg-video-nouveau:
Installed: 1:1.0.12-1build2
Candidate: 1:1.0.12-1build2
Version table:
   *** 1:1.0.12-1build2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy xfwm4
  xfwm4:
Installed: 4.12.3-1ubuntu2
Candidate: 4.12.3-1ubuntu2
Version table:
   *** 4.12.3-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  I created a video demonstrating the problem in xfwm4:
  https://www.youtube.com/watch?v=8dZN80tMA6M.  If you look closely, you
  can see that the opaque blue border is positioned correctly, while the
  semi-transparent overlay isn't.

  FWIW, I'm using an NVIDIA GeForce GTX 750 Ti card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul 25 00:50:21 2016
  InstallationDate: Installed on 2016-07-19 (6 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1606122] [NEW] Cairo drawing coordinates are broken w/nouveau (affects xfwm4)

[Ryan Prichard]

Public bug reported:

I'm using xfwm4 with Xubuntu 16.04.  With compositing enabled, and when
I cycle through windows with Alt-Tab, xfwm4 draws an opaque rectangle
bordering a candidate window, and it fills that rectangle with a semi-
transparent blue color.  When I use the nouveau driver, the filled
rectangle is clipped.  The problem does not reproduce with the
proprietary nvidia driver.

It seems as though a drawing command should be issued using a window-
relative coordinate, but sometimes is instead issued using a screen-
relative coordinate.

I extracted relevant bits of xfwm4 into a small test program that
reproduces the problem.  The test program creates a transparent XWindow
at (100,100) with size (210,210).  It draws six rectangles centered
inside the window of varying parameters.  Two of them are drawn at the
wrong place.

xfwm4 should be off-the-hook, I think, unless it's doing something wrong
(e.g. unspecified/undefined behavior).

$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04

$ apt-cache policy xserver-xorg-video-nouveau
xserver-xorg-video-nouveau:
  Installed: 1:1.0.12-1build2
  Candidate: 1:1.0.12-1build2
  Version table:
 *** 1:1.0.12-1build2 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy xfwm4
xfwm4:
  Installed: 4.12.3-1ubuntu2
  Candidate: 4.12.3-1ubuntu2
  Version table:
 *** 4.12.3-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status

I created a video demonstrating the problem in xfwm4:
https://www.youtube.com/watch?v=8dZN80tMA6M.  If you look closely, you
can see that the opaque blue border is positioned correctly, while the
semi-transparent overlay isn't.

FWIW, I'm using an NVIDIA GeForce GTX 750 Ti card.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Jul 25 00:50:21 2016
InstallationDate: Installed on 2016-07-19 (6 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

** Attachment added: "extracted-from-xfwm4.c"
   
https://bugs.launchpad.net/bugs/1606122/+attachment/4706853/+files/extracted-from-xfwm4.c

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1606122

Title:
  Cairo drawing coordinates are broken w/nouveau (affects xfwm4)

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using xfwm4 with Xubuntu 16.04.  With compositing enabled, and
  when I cycle through windows with Alt-Tab, xfwm4 draws an opaque
  rectangle bordering a candidate window, and it fills that rectangle
  with a semi-transparent blue color.  When I use the nouveau driver,
  the filled rectangle is clipped.  The problem does not reproduce with
  the proprietary nvidia driver.

  It seems as though a drawing command should be issued using a window-
  relative coordinate, but sometimes is instead issued using a screen-
  relative coordinate.

  I extracted relevant bits of xfwm4 into a small test program that
  reproduces the problem.  The test program creates a transparent
  XWindow at (100,100) with size (210,210).  It draws six rectangles
  centered inside the window of varying parameters.  Two of them are
  drawn at the wrong place.

  xfwm4 should be off-the-hook, I think, unless it's doing something
  wrong (e.g. unspecified/undefined behavior).

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy xserver-xorg-video-nouveau
  xserver-xorg-video-nouveau:
Installed: 1:1.0.12-1build2
Candidate: 1:1.0.12-1build2
Version table:
   *** 1:1.0.12-1build2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy xfwm4
  xfwm4:
Installed: 4.12.3-1ubuntu2
Candidate: 4.12.3-1ubuntu2
Version table:
   *** 4.12.3-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  I created a video demonstrating the problem in xfwm4:
  https://www.youtube.com/watch?v=8dZN80tMA6M.  If you look closely, you
  can see that the opaque blue border is positioned correctly, while the
  semi-transparent overlay isn't.

  FWIW, I'm using an NVIDIA GeForce GTX 750 Ti card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  Appor

[Touch-packages] [Bug 1605990] Re: package account-plugin-twitter (not installed) failed to install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-options.d/api.twitter.com.conf“, který je tak

[Alberto Mardegan]

*** This bug is a duplicate of bug 1565772 ***
https://bugs.launchpad.net/bugs/1565772

** This bug has been marked a duplicate of bug 1565772
   [SRU] Allow plugins to decide which username to set on new accounts

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1605990

Title:
  package account-plugin-twitter (not installed) failed to
  install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-
  options.d/api.twitter.com.conf“, který je také v balíku kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  I cannot install this package because I have KDE5 installed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-twitter (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 14:06:57 2016
  ErrorMessage: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/api.twitter.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-06-11 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-twitter (not installed) failed to 
install/upgrade: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/api.twitter.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1605990/+subscriptions

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

[Touch-packages] [Bug 1605989] Re: package account-plugin-facebook (not installed) failed to install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-options.d/www.facebook.com.conf“, který je t

[Alberto Mardegan]

*** This bug is a duplicate of bug 1565772 ***
https://bugs.launchpad.net/bugs/1565772

** This bug has been marked a duplicate of bug 1565772
   [SRU] Allow plugins to decide which username to set on new accounts

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1605989

Title:
  package account-plugin-facebook (not installed) failed to
  install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf“, který je také v balíku kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  I cannot install this package because I have KDE5 installed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-facebook (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 14:06:56 2016
  ErrorMessage: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/www.facebook.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-06-11 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/www.facebook.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.signon-ui.webkit-options.d.www.facebook.com.conf: 
2016-03-10T00:26:54

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1605989/+subscriptions

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

[Touch-packages] [Bug 1506358] Re: unity8/libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

[Daniel van Vugt]

Although the offending exception might have been a regression from:


revno: 2870 [merge]
author: Kevin DuBois 
committer: Tarmac
branch nick: development-branch
timestamp: Fri 2015-08-21 14:52:44 +
message:
  client: Do some internal refactoring to separate out mcl::BufferStream's 
logic that ties it to the BufferDepository. If the client gets a buffer at 
creation, it will use the exchange based system. If not, it will keep the 
current behavior of throwing an exception. 
  .
  
  Approved by PS Jenkins bot, Alan Griffiths, Chris Halse Rogers, Alexandros 
Frantzis.


We probably don't have to fix it directly... Because Mir 0.24.0 aims to
avoid this old code path for good, and you shouldn't ever hit it again.

** Changed in: mir
Milestone: 0.25.0 => 0.24.0

** Changed in: mir
   Status: Confirmed => Fix Committed

** Changed in: mir
 Assignee: (unassigned) => Kevin Dubois (kevin-dubois05)

** Changed in: mir (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1506358

Title:
  unity8/libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  ---
  Duplicate bug reports now show Unity8 is another such client suffering from 
this crash. It's occurring on phones and desktops in the wild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions

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

[Touch-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

[Daniel van Vugt]

Another duplicate today.

This bug in libmirclient is now causing Untiy8 to fail start-up
sometimes, and black-screen.

** Tags added: black-screen unity8-desktop

** Summary changed:

- libmirclient gives up and terminates prematurely with "std::exception::what: 
disconnected: no new buffers" via ExchangeSemantics::submit()
+ unity8/libmirclient gives up and terminates prematurely with 
"std::exception::what: disconnected: no new buffers" via 
ExchangeSemantics::submit()

** Description changed:

  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:
  
  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: disconnected: no new buffers
  
  The strange thing is it's only the client that died. The server survived
  and I can connect new clients to it.
  
- Duplicate bug reports now show Unity8 is another such client suffering
- from this crash. It's occurring on phones in the wild.
+ ---
+ Duplicate bug reports now show Unity8 is another such client suffering from 
this crash. It's occurring on phones and desktops in the wild.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1506358

Title:
  unity8/libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
 >
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  ---
  Duplicate bug reports now show Unity8 is another such client suffering from 
this crash. It's occurring on phones and desktops in the wild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions

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

[Touch-packages] [Bug 1606112] [NEW] package account-plugin-identica (not installed) failed to install/upgrade: попытка перезаписать «/etc/signon-ui/webkit-options.d/identi.ca.conf», который уже имеет

[chtcherba]

Public bug reported:

-

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-identica (not installed)
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Jul 25 07:59:19 2016
ErrorMessage: попытка перезаписать 
«/etc/signon-ui/webkit-options.d/identi.ca.conf», который уже имеется в пакете 
kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2016-03-29 (118 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: account-plugins
Title: package account-plugin-identica (not installed) failed to 
install/upgrade: попытка перезаписать 
«/etc/signon-ui/webkit-options.d/identi.ca.conf», который уже имеется в пакете 
kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: Upgraded to xenial on 2016-05-12 (73 days ago)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1606112

Title:
  package account-plugin-identica (not installed) failed to
  install/upgrade: попытка перезаписать «/etc/signon-ui/webkit-
  options.d/identi.ca.conf», который уже имеется в пакете kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-identica (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Jul 25 07:59:19 2016
  ErrorMessage: попытка перезаписать 
«/etc/signon-ui/webkit-options.d/identi.ca.conf», который уже имеется в пакете 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-03-29 (118 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-identica (not installed) failed to 
install/upgrade: попытка перезаписать 
«/etc/signon-ui/webkit-options.d/identi.ca.conf», который уже имеется в пакете 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: Upgraded to xenial on 2016-05-12 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1606112/+subscriptions

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

[Touch-packages] [Bug 1511074] Re: camera is missing auto focus options OFF

[dinamic]

:(( another example https://www.youtube.com/watch?v=7Ag99Akpb38

recording is really really really bad!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1511074

Title:
  camera is missing auto focus options OFF

Status in camera-app:
  Triaged
Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Triaged

Bug description:
  camera is missing auto focus options ON/OFF

  i really need to turn OFF auto focus. i can't record the screen
  without turning OFF the auto focus, but there is no settings...

  Sample video showing the refocusing
  https://www.youtube.com/watch?v=8Zdpp7mZEQs

  Its a bit odd that its going out of focus at all, wonder if there is a
  way to improve the configuration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1511074/+subscriptions

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

[Touch-packages] [Bug 1573470] Re: BQ M10 tablet. Libreoffice Impress presentation mode displays wrong colors

[Daniel van Vugt]

Upgrading to Mesa 12 unfortunately has not solved this bug.

I suspect however the idea will still work, and most likely that
aforementioned enhancement in Mesa 12 is just unfinished and/or
untested.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1573470

Title:
  BQ M10 tablet. Libreoffice Impress presentation mode displays wrong
  colors

Status in Canonical System Image:
  Confirmed
Status in Puritine:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  On the new BQ M10 tablet.

  1- switch to desktop mode (manual, no external peripheral attached)
  2- launch libreoffice
  3- open impress file
  4- colours in images are all messed up on the BQ M10 screen when toggle to 
presentation view.

  Can anyone confirm?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573470/+subscriptions

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

[Touch-packages] [Bug 1575516] Re: Mir is just a black screen and mouse cursor on Nvidia GTX 900

[Daniel van Vugt]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1575516

Title:
  Mir is just a black screen and mouse cursor on Nvidia GTX 900

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  Nvidia (using nouveau not binary drivers): Mir servers freeze on
  start-up for 30 seconds, and then you get just a black screen and
  mouse cursor (which at least moves).

  Using lp:mir r3480 ...

  [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms 
(version 0.22.0)
  nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22
  [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor
  [2016-04-27 15:20:51.937691] mirserver: Initial display configuration:
  [2016-04-27 15:20:51.937703] mirserver:   0.36: unused DVI-I
  [2016-04-27 15:20:51.937713] mirserver:   0.39: DVI-D 24.0" 520x320mm
  [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz
  [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 
59.95Hz
  [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0
  [2016-04-27 15:20:51.937781] mirserver:   0.41: unused HDMI-A
  [2016-04-27 15:20:51.937799] mirserver:   0.43: unused DisplayPort
  [2016-04-27 15:20:51.937972] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [2016-04-27 15:20:51.938015] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.9
  [2016-04-27 15:20:51.938107]  mircommon: Failed to load module: 
bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: 
cannot open shared object file: No such file or directory)
  [2016-04-27 15:20:51.938119] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.9
  [2016-04-27 15:20:51.938142] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.9
  [2016-04-27 15:20:51.938536] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.5
  [2016-04-27 15:20:51.955316] mirserver: Selected input driver: 
mir:evdev-input (version: 0.22.0)
  [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0
  [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project
  [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2)
  [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES 
OpenGL_ES2 OpenGL_ES3
  [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context 
EGL_MESA_configless_context EGL_MESA_image_dma_buf_export
  [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc.
  [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe 
(LLVM 3.8, 256 bits)
  [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0
  [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00

  lspci:
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] 
(rev a1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575516/+subscriptions

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

[Touch-packages] [Bug 1605663] Re: No webcam connection from camera-app in desktop-session

[Daniel van Vugt]

** Changed in: unity8-desktop-session (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1605663

Title:
  No webcam connection from camera-app in desktop-session

Status in camera-app package in Ubuntu:
  New
Status in unity8-desktop-session package in Ubuntu:
  Invalid

Bug description:
  In my laptop, if I launch the camera-app, I get the app running but
  the webcam input is totally black. I would have instead expected to
  see the input from my integrated webcam.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1605663/+subscriptions

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

[Touch-packages] [Bug 1605672] Re: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()

[Daniel van Vugt]

*** This bug is a duplicate of bug 1118903 ***
https://bugs.launchpad.net/bugs/1118903

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1118903, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1118903
   [enhancement] Mir lacks a software rendering backend (and doesn't work in 
virtual machines)

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1605672

Title:
  unity-system-compositor crashed with SIGABRT in
  mir::fatal_error_abort()

Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.6.0+16.10.20160609-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Jul 22 17:13:48 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-05-19 (63 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   mir::fatal_error_abort(char const*, ...) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
   ?? () from 
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.9
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.40
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.40
   ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
  Title: unity-system-compositor crashed with SIGABRT in 
mir::fatal_error_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.69-1
  version.lightdm: lightdm 1.19.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1605672/+subscriptions

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

[Touch-packages] [Bug 1118903] Re: [enhancement] Mir lacks a software rendering backend (and doesn't work in virtual machines)

[Daniel van Vugt]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1118903

Title:
  [enhancement] Mir lacks a software rendering backend (and doesn't work
  in virtual machines)

Status in Canonical System Image:
  New
Status in Mir:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  As always, it's a critical requirement for Ubuntu to be able to render
  the same thing on any machine (metal or virtual), regardless of the
  availability of hardware acceleration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1118903/+subscriptions

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

[Touch-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

[ernsteiswuerfel]

@Fritz:

>From the XorgLog.txt you posted I gather that you are running the "ATI
Rage 128 PRO AGP 4x" in a 15bpp screen mode, so no 24bpp true color,
which causes your blotchy images:

[25.931] (EE) Screen 0 deleted because of no matching config section.
[25.931] (II) UnloadModule: "modesetting"
[25.931] (II) FBDEV(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 15/16

Do you use some config-file in /etc/X11/xorg.conf.d/ or is this the
default behauviour of the ATI Rage 128 PRO in your Power Mac 3,1?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1541082

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

Status in xorg package in Ubuntu:
  New

Bug description:
  The background image and other image files are blotchy.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: powerpc
  BootLog:
   fsck from util-linux 2.27.1
   /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DpkgLog:

  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-01-31 (154 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
  Lsusb:
   Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
   Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
   Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: powerpc
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10
  Renderer: Software
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-24-powerpc-smp ppc
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1605478] Re: supertux2 crashes on native Mir (which is an SDL2 platform), trying to call GLX functions

[Daniel van Vugt]

That's OK, then you can ignore this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glew in Ubuntu.
https://bugs.launchpad.net/bugs/1605478

Title:
  supertux2 crashes on native Mir (which is an SDL2 platform), trying to
  call GLX functions

Status in glew package in Ubuntu:
  Confirmed
Status in supertux package in Ubuntu:
  Confirmed

Bug description:
  supertux2 crashes on native Mir, trying to call GLX functions...

  Thread 1 "supertux2" received signal SIGSEGV, Segmentation fault.
  0x7519a95d in XQueryExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  (gdb) bt
  #0  0x7519a95d in XQueryExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #1  0x7518e4c2 in XInitExtension ()
 from /usr/lib/x86_64-linux-gnu/libX11.so.6
  #2  0x76f8269c in ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  #3  0x76f7e041 in glXQueryVersion ()
 from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  #4  0x76d2eb34 in glxewInit ()
 from /usr/lib/x86_64-linux-gnu/libGLEW.so.1.13
  #5  0x00560eeb in GLRenderer::GLRenderer() ()
  #6  0x0055e153 in GLVideoSystem::GLVideoSystem() ()
  #7  0x004f4b85 in VideoSystem::create(VideoSystem::Enum) ()
  #8  0x004ad662 in Main::launch_game() ()
  #9  0x004af0ad in Main::run(int, char**) ()
  #10 0x004a9f13 in main ()

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

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

[Touch-packages] [Bug 1603070] Re: Ubuntu store doesn't show app preview images (all grey ubuntu logos) -- falsely detected network missing when it's not

[Daniel van Vugt]

Per comment:
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1603453/comments/4

I have separated the two bugs. Because although we believe the root
causes are the same, their titles and the problems the user observes are
vastly different. It's OK to have one fix for two bugs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1603070

Title:
  Ubuntu store doesn't show app preview images (all grey ubuntu logos)
  -- falsely detected network missing when it's not

Status in Canonical System Image:
  New
Status in unity-scope-click package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10 desktop
  [dash] ubuntu store doesn't show app preview images if network-manager is 
absent.

  The store is incorrectly thinking there is no network when there
  really is.

  The first bug is network-manager not running -> bug 1603453
  But this bug is about the store detecting the absence of network connectivity 
incorrectly. It should not be looking to network-manager as that's clearly not 
a reliable detection method.

  please see attached image

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603070/+subscriptions

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

[Touch-packages] [Bug 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

[Daniel van Vugt]

I've already confirmed Cherryview is not affected by this bug. But I'll
update and check again.

** Description changed:

  Qt clients are failing to create an egl context when running on Intel
- Pineview, but not Cherryview systems under Mir.
+ Diamondville and Pineview, but not Cherryview systems under Mir.
  
  eglCreateContext fails with a EGL_BAD_MATCH error code.
  
  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)
  
  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1549455

Title:
  Unity8-dash on Intel Atom graphics crashes and restarts continuously
  [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
  EGL_TRUE"]

Status in Mir:
  Invalid
Status in qtubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Diamondville and Pineview, but not Cherryview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+subscriptions

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

[Touch-packages] [Bug 1603183] Re: Bottom right area of touchpad no longer treated as right click

[Daniel van Vugt]

** Changed in: mir
   Importance: Medium => Low

** Changed in: mir (Ubuntu)
   Importance: Medium => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-ubuntu-touch-
schemas in Ubuntu.
https://bugs.launchpad.net/bugs/1603183

Title:
  Bottom right area of touchpad no longer treated as right click

Status in Canonical System Image:
  New
Status in Mir:
  Triaged
Status in gsettings-ubuntu-touch-schemas package in Ubuntu:
  In Progress
Status in libinput package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Invalid
Status in unity8-desktop-session package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Using the touchpad I was not able to trigger any right click (with a
  single finger in the bottom right area), and I tought it was a problem
  of how unity8 handled the right clicks. Instead I just tried with a
  mouse and right click trigger different actions from left clicks.

  In the end the problem is that my touchpad right click is considered a
  left click by the system. This does not happen with an usb mouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603183/+subscriptions

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

[Touch-packages] [Bug 1606071] Re: [HP ProBook 455 G3] Unable to boot

[Christopher M. Penalver]

Brian, thank you for reporting this and helping make Ubuntu better.

To clarify, are you able to boot with 15.10 if you uninstall fglrx?

** Description changed:

- This bug affects me on Ubuntu 16.04, but not on 15.10 where the fglrx
- drivers are still available. I have the graphics card A10-8700P APU
- "Carrizo" on my HP ProBook 455 G3 laptop. I get a black screen
- immediately unless I set the kernel parameter nomodeset and boot into
- low graphics.
+ When using Ubuntu 16.04 I get a black screen immediately when booting up. I 
tried using kernel parameter amdgpu.runpm=0 Ubuntu boots up into the live 
Ubuntu with the correct resolution but after 5 minutes or so, I got the black 
screen again. This doesn't happen with 15.10 where the fglrx drivers are still 
available. My hardware:
+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 00 [VGA controller])
+   Subsystem: Hewlett-Packard Company Device [103c:80ef]
  
- I found a recommendation at
- https://bugzilla.kernel.org/show_bug.cgi?id=117591 Comment #7, to append
- "amdgpu.runpm=0" to the kernel command line in Grub setparams. I did try
- that with the Ubuntu 16.04 LiveUSB. The result was that it booted into
- the live Ubuntu with the correct resolution but after 5 minutes or so, I
- got the black screen again.
- 
- I wish AMD or Canonical or whoever is responsible for the decision to
- make fglrx unavailable in 16.04 would reconsider and provide for a
- smoother transition by allowing users with graphics cards that are still
- unsupported by amdgpu to "opt-in" to fglrx until AMD works out the all
- the kinks. It's as if they just don't care about end users whatsoever.
- This is the behavior one would expect of Microsoft, not Ubuntu. Man, am
- I frustrated!
+ WORKAROUND: The following kernel parameter allows me to boot into low 
graphics mode:
+ nomodeset
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jul 24 17:45:49 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:80ef]
+  Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:80ef]
  InstallationDate: Installed on 2016-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: HP HP ProBook 455 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed 
root=UUID=3995b7d0-4563-4eb7-b27b-220f98ff0526 ro nomodeset quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N79 Ver. 01.11
  dmi.board.name: 80EF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 92.49
  dmi.chassis.asset.tag: 5CD6216FPW
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN79Ver.01.11:bd04/11/2016:svnHP:pnHPProBook455G3:pvr:rvnHP:rn80EF:rvrKBCVersion92.49:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 455 G3
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Jul 24 21:30:05 2016
  xserver.configfile: default
  xserver.errors:
-  open /dev/dri/card0: No such file or directory
-  AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modu

[Touch-packages] [Bug 1605797] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all

[Bug Watch Updater]

** Changed in: alsa-driver
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1605797

Title:
  [ICH - Intel 82801AA-ICH, playback] No sound at all

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New ubuntu install on 2016-07-22; latest version.
  Running as virtualbox guest on latest OS X.
  Sound card recognized on mac, but not on guest.
  No sound in or out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 22 19:00:19 2016
  InstallationDate: Installed on 2016-07-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  Symptom_Type: No sound at all
  Title: [ICH - Intel 82801AA-ICH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1605797/+subscriptions

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

[Touch-packages] [Bug 1606071] Re: [HP ProBook 455 G3] Unable to boot

[Christopher M. Penalver]

** Summary changed:

- AMDGPU driver does not support graphics card A10-8700P APU "Carrizo"
+ [HP ProBook 455 G3] Unable to boot

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1606071

Title:
  [HP ProBook 455 G3] Unable to boot

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug affects me on Ubuntu 16.04, but not on 15.10 where the fglrx
  drivers are still available. I have the graphics card A10-8700P APU
  "Carrizo" on my HP ProBook 455 G3 laptop. I get a black screen
  immediately unless I set the kernel parameter nomodeset and boot into
  low graphics.

  I found a recommendation at
  https://bugzilla.kernel.org/show_bug.cgi?id=117591 Comment #7, to
  append "amdgpu.runpm=0" to the kernel command line in Grub setparams.
  I did try that with the Ubuntu 16.04 LiveUSB. The result was that it
  booted into the live Ubuntu with the correct resolution but after 5
  minutes or so, I got the black screen again.

  I wish AMD or Canonical or whoever is responsible for the decision to
  make fglrx unavailable in 16.04 would reconsider and provide for a
  smoother transition by allowing users with graphics cards that are
  still unsupported by amdgpu to "opt-in" to fglrx until AMD works out
  the all the kinks. It's as if they just don't care about end users
  whatsoever. This is the behavior one would expect of Microsoft, not
  Ubuntu. Man, am I frustrated!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jul 24 17:45:49 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:80ef]
  InstallationDate: Installed on 2016-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: HP HP ProBook 455 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed 
root=UUID=3995b7d0-4563-4eb7-b27b-220f98ff0526 ro nomodeset quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N79 Ver. 01.11
  dmi.board.name: 80EF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 92.49
  dmi.chassis.asset.tag: 5CD6216FPW
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN79Ver.01.11:bd04/11/2016:svnHP:pnHPProBook455G3:pvr:rvnHP:rn80EF:rvrKBCVersion92.49:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 455 G3
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Jul 24 21:30:05 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: fglrx

To manage notifications about this bug

[Touch-packages] [Bug 1606071] Re: AMDGPU driver does not support graphics card A10-8700P APU "Carrizo"

[Christopher M. Penalver]

** Tags added: latest-bios-1.11

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1606071

Title:
  AMDGPU driver does not support graphics card A10-8700P APU "Carrizo"

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug affects me on Ubuntu 16.04, but not on 15.10 where the fglrx
  drivers are still available. I have the graphics card A10-8700P APU
  "Carrizo" on my HP ProBook 455 G3 laptop. I get a black screen
  immediately unless I set the kernel parameter nomodeset and boot into
  low graphics.

  I found a recommendation at
  https://bugzilla.kernel.org/show_bug.cgi?id=117591 Comment #7, to
  append "amdgpu.runpm=0" to the kernel command line in Grub setparams.
  I did try that with the Ubuntu 16.04 LiveUSB. The result was that it
  booted into the live Ubuntu with the correct resolution but after 5
  minutes or so, I got the black screen again.

  I wish AMD or Canonical or whoever is responsible for the decision to
  make fglrx unavailable in 16.04 would reconsider and provide for a
  smoother transition by allowing users with graphics cards that are
  still unsupported by amdgpu to "opt-in" to fglrx until AMD works out
  the all the kinks. It's as if they just don't care about end users
  whatsoever. This is the behavior one would expect of Microsoft, not
  Ubuntu. Man, am I frustrated!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jul 24 17:45:49 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:80ef]
  InstallationDate: Installed on 2016-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: HP HP ProBook 455 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed 
root=UUID=3995b7d0-4563-4eb7-b27b-220f98ff0526 ro nomodeset quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N79 Ver. 01.11
  dmi.board.name: 80EF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 92.49
  dmi.chassis.asset.tag: 5CD6216FPW
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN79Ver.01.11:bd04/11/2016:svnHP:pnHPProBook455G3:pvr:rvnHP:rn80EF:rvrKBCVersion92.49:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 455 G3
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Jul 24 21:30:05 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: fglrx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/160

[Touch-packages] [Bug 1606078] [NEW] No sound with Ubuntu 16.04

[Bashar]

Public bug reported:

After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual laptop
there was no sound from the speakers unless external speakers where
hooked to the headphones socket. This applies to the Ubuntu Mate,
Xubuntu and Lubuntu variants. This laptop was working fine for all
previous releases up to 14.04.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bashar 3263 F pulseaudio
CurrentDesktop: Unity
Date: Mon Jul 25 01:51:19 2016
InstallationDate: Installed on 2016-07-24 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bashar 3263 F pulseaudio
Symptom_Jack: Line Out, Internal
Symptom_Type: No sound at all
Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/16/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: RKYWSF0B
dmi.board.name: ROCKY
dmi.board.vendor: LG Electronics
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LG Electronics
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
dmi.product.name: S1-M401E1
dmi.product.version: Not Applicable
dmi.sys.vendor: LG Electronics

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1606078

Title:
  No sound with Ubuntu 16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual
  laptop there was no sound from the speakers unless external speakers
  where hooked to the headphones socket. This applies to the Ubuntu
  Mate, Xubuntu and Lubuntu variants. This laptop was working fine for
  all previous releases up to 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Jul 25 01:51:19 2016
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bashar 3263 F pulseaudio
  Symptom_Jack: Line Out, Internal
  Symptom_Type: No sound at all
  Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: RKYWSF0B
  dmi.board.name: ROCKY
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: S1-M401E1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+subscriptions

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

[Touch-packages] [Bug 1606071] Re: AMDGPU driver does not support graphics card A10-8700P APU "Carrizo"

[Brian]

I don't know how much good this is going to do, however, since I filed
this report from 15.10, not 16.04 where the issue occurs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1606071

Title:
  AMDGPU driver does not support graphics card A10-8700P APU "Carrizo"

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug affects me on Ubuntu 16.04, but not on 15.10 where the fglrx
  drivers are still available. I have the graphics card A10-8700P APU
  "Carrizo" on my HP ProBook 455 G3 laptop. I get a black screen
  immediately unless I set the kernel parameter nomodeset and boot into
  low graphics.

  I found a recommendation at
  https://bugzilla.kernel.org/show_bug.cgi?id=117591 Comment #7, to
  append "amdgpu.runpm=0" to the kernel command line in Grub setparams.
  I did try that with the Ubuntu 16.04 LiveUSB. The result was that it
  booted into the live Ubuntu with the correct resolution but after 5
  minutes or so, I got the black screen again.

  I wish AMD or Canonical or whoever is responsible for the decision to
  make fglrx unavailable in 16.04 would reconsider and provide for a
  smoother transition by allowing users with graphics cards that are
  still unsupported by amdgpu to "opt-in" to fglrx until AMD works out
  the all the kinks. It's as if they just don't care about end users
  whatsoever. This is the behavior one would expect of Microsoft, not
  Ubuntu. Man, am I frustrated!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jul 24 17:45:49 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.201, 4.2.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:80ef]
  InstallationDate: Installed on 2016-07-23 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: HP HP ProBook 455 G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed 
root=UUID=3995b7d0-4563-4eb7-b27b-220f98ff0526 ro nomodeset quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N79 Ver. 01.11
  dmi.board.name: 80EF
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 92.49
  dmi.chassis.asset.tag: 5CD6216FPW
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN79Ver.01.11:bd04/11/2016:svnHP:pnHPProBook455G3:pvr:rvnHP:rn80EF:rvrKBCVersion92.49:cvnHP:ct10:cvr:
  dmi.product.name: HP ProBook 455 G3
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sun Jul 24 21:30:05 2016
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: fglrx

To m

[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Jose Luis]

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454656

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1563110

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Touch-packages] [Bug 1606071] [NEW] AMDGPU driver does not support graphics card A10-8700P APU "Carrizo"

[Brian]

Public bug reported:

This bug affects me on Ubuntu 16.04, but not on 15.10 where the fglrx
drivers are still available. I have the graphics card A10-8700P APU
"Carrizo" on my HP ProBook 455 G3 laptop. I get a black screen
immediately unless I set the kernel parameter nomodeset and boot into
low graphics.

I found a recommendation at
https://bugzilla.kernel.org/show_bug.cgi?id=117591 Comment #7, to append
"amdgpu.runpm=0" to the kernel command line in Grub setparams. I did try
that with the Ubuntu 16.04 LiveUSB. The result was that it booted into
the live Ubuntu with the correct resolution but after 5 minutes or so, I
got the black screen again.

I wish AMD or Canonical or whoever is responsible for the decision to
make fglrx unavailable in 16.04 would reconsider and provide for a
smoother transition by allowing users with graphics cards that are still
unsupported by amdgpu to "opt-in" to fglrx until AMD works out the all
the kinks. It's as if they just don't care about end users whatsoever.
This is the behavior one would expect of Microsoft, not Ubuntu. Man, am
I frustrated!

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Jul 24 17:45:49 2016
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 15.201, 4.2.0-42-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:80ef]
InstallationDate: Installed on 2016-07-23 (1 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: HP HP ProBook 455 G3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed 
root=UUID=3995b7d0-4563-4eb7-b27b-220f98ff0526 ro nomodeset quiet splash 
vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2016
dmi.bios.vendor: HP
dmi.bios.version: N79 Ver. 01.11
dmi.board.name: 80EF
dmi.board.vendor: HP
dmi.board.version: KBC Version 92.49
dmi.chassis.asset.tag: 5CD6216FPW
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN79Ver.01.11:bd04/11/2016:svnHP:pnHPProBook455G3:pvr:rvnHP:rn80EF:rvrKBCVersion92.49:cvnHP:ct10:cvr:
dmi.product.name: HP ProBook 455 G3
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sun Jul 24 21:30:05 2016
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
 AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
 AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1
xserver.video_driver: fglrx

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1606071

Title:
  AMDGPU driver does not support graphics card A10-8700P APU "Carrizo"

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug affects me on Ubuntu 16.04, but not on 15.10 where the fglrx
  drivers are still available. I have the graphics card A10-8700P APU
  "Carrizo"

[Touch-packages] [Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

[Red]

One addendum to the above, as a verification process, the 16-04 64-bit
install was repeated, each time discarding any previous contents on the
drive, just the eliminate any one-time glitches that might have
occurred.

Also, only Ubuntu and updates through Software Updater have been
installed. No extra software.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1582011

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This bug has been affecting me since 15.04
  Prior to shutdown I activate debug-shell 'systemctl start debug-shell'
  I have followed bug #1464917 and installed Xenial-proposed with systemd 
229-4ubuntu5 package.  
  I have finally collected shutdown info using vt9.  
  Issues collecting info due to what I believe is a timeout where vt9 is not 
activated when ctl+alt+F9 is pressed.  I was able to collect info in vt9 to 
file "shutdown.text" I appended outputs to file "shutdown.text" the following 
commands in this order:
  systemctl list-jobs >>shutdown.text
  systemctl --failed >>shutdown.text
  uname -a >>shutdown.text
  systemd --version >>shutdown.text
  lsblk >>shutdown.text
  blkid >>shutdown.text
  journalctl -b >>shutdown.text
  systemctl -all >>shutdown.text
  journalctl -xe >>shutdown.text

  After gaining these data I was only able to finish the reboot with the 
alt+Sysrq and REISUB which forces a reboot even when I just want to shutdown
  Each output I separated upon next boot by hand with a line 
# for easier perusing.

  As a workaround for shutdown/reboot I turn swap off, 'sudo swapoff -a
  && systemctl poweroff' or 'sudo swapoff -a && reboot'  which
  occasionally fails if SWAP has more data than available RAM.  In that
  latter case I am left waiting for the hang and then using
  alt+Sysrq+REISUB to reboot then shutdown again immediately upon boot
  before SWAP has a chance to gain data, then I can use any form of
  halt, poweroff or menu to shutdown.

  I have been unable to get answers from AskUbuntu or the above listed
  bug #1464917 "Reached target Shutdown"  I am filing this bug per
  instructions requested in that bug.  Other systemd bugs I have
  researched #788303 Debian bug reports, #2930 Github and #3087 Github.

  Thanks for your time and efforts to help with this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May 15 12:08:34 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2015-06-29 (321 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Sony Corporation VGN-FW250J
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b010e611-6efb-49a9-bff0-59b9533d659b ro 
resume=UUID=8bcb4169-f5ab-4ab6-b644-23e528088d41 usbcore.autosuspend=-1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (18 days ago)
  dmi.bios.date: 07/25/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1090Y0
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1090Y0:bd07/25/2008:svnSonyCorporation:pnVGN-FW250J:pvrC6011MLK:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-FW250J
  dmi.product.version: C6011MLK
  dmi.sys.vendor: Sony Corporation

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

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

[Touch-packages] [Bug 1582011] Re: Swap Failed, Indefinite hang on reboot/shutdown "Reached target Shutdown"

[Red]

I first installed Ubuntu 32-bit desktop some years ago (I believe 11.04)
and have been upgrading it every six months. I am now up to 16.04 and
have not ever experienced this shutdown problem.

Since Chrome no longer supports 32-bit, I have downloaded 16.04 64-bit
(and verified the sha256).

I have burned the 64-bit to both DVD and thumb drives. I can boot live
from either and shutdown without a problem.

If I install to a brand new SSD, I hang during shutdown.

If I replace the SSD with the original HDD with 16.04 32-bit, I can
shutdown without problem.

I have found several suggestions on the Web to modify the
/etc/default/grub file to solve the problem. My two /etc/default/grub
files are identical so I don't see that as a problem.

None of the following work, they just hang:
  shutdown -h now
  shutdown -P now
  reboot -p
  sudo reboot -f (Just responds “Rebooting” and then nothing.)
  sudo halt
  poweroff

In summary, 11.04 (32-bit) upgraded to 11.10 upgraded to 12.04 upgraded
to ... 16.04 shuts down without a problem while 16.04 clean install
hangs.

Maybe, given time, I'll download 16.04 32-bit and do a clean install to
see what that will do.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1582011

Title:
  Swap Failed, Indefinite hang on reboot/shutdown "Reached target
  Shutdown"

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This bug has been affecting me since 15.04
  Prior to shutdown I activate debug-shell 'systemctl start debug-shell'
  I have followed bug #1464917 and installed Xenial-proposed with systemd 
229-4ubuntu5 package.  
  I have finally collected shutdown info using vt9.  
  Issues collecting info due to what I believe is a timeout where vt9 is not 
activated when ctl+alt+F9 is pressed.  I was able to collect info in vt9 to 
file "shutdown.text" I appended outputs to file "shutdown.text" the following 
commands in this order:
  systemctl list-jobs >>shutdown.text
  systemctl --failed >>shutdown.text
  uname -a >>shutdown.text
  systemd --version >>shutdown.text
  lsblk >>shutdown.text
  blkid >>shutdown.text
  journalctl -b >>shutdown.text
  systemctl -all >>shutdown.text
  journalctl -xe >>shutdown.text

  After gaining these data I was only able to finish the reboot with the 
alt+Sysrq and REISUB which forces a reboot even when I just want to shutdown
  Each output I separated upon next boot by hand with a line 
# for easier perusing.

  As a workaround for shutdown/reboot I turn swap off, 'sudo swapoff -a
  && systemctl poweroff' or 'sudo swapoff -a && reboot'  which
  occasionally fails if SWAP has more data than available RAM.  In that
  latter case I am left waiting for the hang and then using
  alt+Sysrq+REISUB to reboot then shutdown again immediately upon boot
  before SWAP has a chance to gain data, then I can use any form of
  halt, poweroff or menu to shutdown.

  I have been unable to get answers from AskUbuntu or the above listed
  bug #1464917 "Reached target Shutdown"  I am filing this bug per
  instructions requested in that bug.  Other systemd bugs I have
  researched #788303 Debian bug reports, #2930 Github and #3087 Github.

  Thanks for your time and efforts to help with this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May 15 12:08:34 2016
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2015-06-29 (321 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Sony Corporation VGN-FW250J
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=b010e611-6efb-49a9-bff0-59b9533d659b ro 
resume=UUID=8bcb4169-f5ab-4ab6-b644-23e528088d41 usbcore.autosuspend=-1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (18 days ago)
  dmi.bios.date: 07/25/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1090Y0
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 

[Touch-packages] [Bug 1577074] Re: AMDGPU driver problems on "Carrizo" APU

[Brian]

OK, I tried the "amdgpu.runpm=0" solution with the Ubuntu 16.04 LiveUSB
and while it booted in high graphics mode, I still got the black screen
after a few minutes.

Christopher, I have done as you asked in Comment #15 on this thread, and
the bug report I filed is at
https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug/34a9fa5a-
51e8-11e6-8b1c-68b5996a96c8?

However I don't know how this will do any good, as I'm running Ubuntu
15.10, not 16.04 where the problem occurs. I wish AMD or Canonical or
whoever is responsible for the decision to make fglrx unavailable in
16.04 would reconsider and provide for a smoother transition by allowing
users with graphics cards that are still unsupported by amdgpu to "opt-
in" to fglrx until AMD works out the all the kinks. It's as if they just
don't care about end users whatsoever. Man, am I frustrated!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1577074

Title:
  AMDGPU driver problems on "Carrizo" APU

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm having a hard time tracing this down.  I updated to Kubuntu 16.04
  (from Kubuntu 15.10 - that was using the Linux Crimson 15.12 driver) a
  couple days ago on my notebook (HP Pavilion, A10-8700P APU), and ever
  since I've been having random black screens.

  I started debugging the driver, then thought it might be a DPMS issue
  (it's not - I have DPMS fully disabled currently), and now I'm back to
  debugging the driver.

  I don't have any remnants of the former closed Crimson display driver
  and never had an xorg.conf file (I made a small one that I'm using at
  the moment consisting of only a server layout to ensure screen savers,
  DPMS, etc are all off).

  The Black screen can happen any time from the login screen until hours
  later.  I can ssh into the system to shut it down.  And just
  discovered that if I unplug the system from it's power brick, I can
  close the lid - the system will goto sleep.  When I flip the screen
  back up, the system wakes up and the screen works again for 1-2
  minutes.

  I don't see any errors in the log files (well, outside some nasty
  looking ACAPI errors in dmesg).

  HOT TO REPRODUCE:
  Boot system and use normally or simply leave system alone.  Blank screen will 
happen any time after x comes up.

  
  EXPECTED RESULT:
  Screen doesn't blank unless a screen saver or power saver kicks in.

  SYSTEM INFO:
  Purchased Dec 2015 (build date from BIOS - Aug 2015), HP Pavilion 15" 
notebook, AMD A10-8700P "Carrizo", 16GB RAM, 960GB SSD

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

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

[Touch-packages] [Bug 1606066] Re: package init-system-helpers 1.29ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1606066

Title:
  package init-system-helpers 1.29ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  error occurred during an update from the Software Updater -- haven't
  seen any immediately issues as a result

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: init-system-helpers 1.29ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 15:20:50 2016
  Df:
   
  Dmesg:
   
  DuplicateSignature:
   package:init-system-helpers:1.29ubuntu2
   Setting up init-system-helpers (1.29ubuntu2) ...
   /var/lib/dpkg/info/init-system-helpers.postinst: 6: 
/var/lib/dpkg/info/init-system-helpers.postinst: Cannot fork
   dpkg: error processing package init-system-helpers (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: init-system-helpers
  Title: package init-system-helpers 1.29ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1606066/+subscriptions

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

[Touch-packages] [Bug 1606066] [NEW] package init-system-helpers 1.29ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

[Chris Tanseer]

Public bug reported:

error occurred during an update from the Software Updater -- haven't
seen any immediately issues as a result

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: init-system-helpers 1.29ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jul 24 15:20:50 2016
Df:
 
Dmesg:
 
DuplicateSignature:
 package:init-system-helpers:1.29ubuntu2
 Setting up init-system-helpers (1.29ubuntu2) ...
 /var/lib/dpkg/info/init-system-helpers.postinst: 6: 
/var/lib/dpkg/info/init-system-helpers.postinst: Cannot fork
 dpkg: error processing package init-system-helpers (--configure):
  subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
InstallationDate: Installed on 2016-07-24 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: init-system-helpers
Title: package init-system-helpers 1.29ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: init-system-helpers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1606066

Title:
  package init-system-helpers 1.29ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  error occurred during an update from the Software Updater -- haven't
  seen any immediately issues as a result

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: init-system-helpers 1.29ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 15:20:50 2016
  Df:
   
  Dmesg:
   
  DuplicateSignature:
   package:init-system-helpers:1.29ubuntu2
   Setting up init-system-helpers (1.29ubuntu2) ...
   /var/lib/dpkg/info/init-system-helpers.postinst: 6: 
/var/lib/dpkg/info/init-system-helpers.postinst: Cannot fork
   dpkg: error processing package init-system-helpers (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: init-system-helpers
  Title: package init-system-helpers 1.29ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1606066/+subscriptions

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

[Touch-packages] [Bug 1577074] Re: AMDGPU driver problems on "Carrizo" APU

[Christopher M. Penalver]

Brian, it would be helpful to track your issue and hardware, if you filed a new 
report with Ubuntu by ensuring you have the package xdiagnose installed, and 
that you click the Yes button for attaching additional debugging information 
running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1577074

Title:
  AMDGPU driver problems on "Carrizo" APU

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm having a hard time tracing this down.  I updated to Kubuntu 16.04
  (from Kubuntu 15.10 - that was using the Linux Crimson 15.12 driver) a
  couple days ago on my notebook (HP Pavilion, A10-8700P APU), and ever
  since I've been having random black screens.

  I started debugging the driver, then thought it might be a DPMS issue
  (it's not - I have DPMS fully disabled currently), and now I'm back to
  debugging the driver.

  I don't have any remnants of the former closed Crimson display driver
  and never had an xorg.conf file (I made a small one that I'm using at
  the moment consisting of only a server layout to ensure screen savers,
  DPMS, etc are all off).

  The Black screen can happen any time from the login screen until hours
  later.  I can ssh into the system to shut it down.  And just
  discovered that if I unplug the system from it's power brick, I can
  close the lid - the system will goto sleep.  When I flip the screen
  back up, the system wakes up and the screen works again for 1-2
  minutes.

  I don't see any errors in the log files (well, outside some nasty
  looking ACAPI errors in dmesg).

  HOT TO REPRODUCE:
  Boot system and use normally or simply leave system alone.  Blank screen will 
happen any time after x comes up.

  
  EXPECTED RESULT:
  Screen doesn't blank unless a screen saver or power saver kicks in.

  SYSTEM INFO:
  Purchased Dec 2015 (build date from BIOS - Aug 2015), HP Pavilion 15" 
notebook, AMD A10-8700P "Carrizo", 16GB RAM, 960GB SSD

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

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

[Touch-packages] [Bug 1577162] Re: Screens briefly blacks out at lightdm prompt

[Christopher M. Penalver]

YS1, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577162/comments/30
regarding this being fixed with new install. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1577162

Title:
  Screens briefly blacks out at lightdm prompt

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  When I boot my laptop and get to the lightdm login prompt, the screen
  blacks out for a fraction of second. This happens each time, only
  once, and does not prevent logging in.

  In fact it is not only a display glitch : if I start to type my
  password before the blackout, the typed characters are lost when
  normal display resumes.

  So lightdm might be restarting.

  This is only mildly annoying, but I am also experiencing other
  graphical problems which may be or not be related (namely #1568604).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun May  1 14:55:29 2016
  InstallationDate: Installed on 2016-04-22 (8 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:062e]
 Subsystem: Dell GM108M [GeForce 840M] [1028:062e]
  InstallationDate: Installed on 2016-04-22 (82 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  LightdmDisplayLog:
   (II) AIGLX: Suspending AIGLX clients for VT switch
   (II) AIGLX: Suspending AIGLX clients for VT switch
  MachineType: Dell Inc. Latitude E7450
  NonfreeKernelModules: wl
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic 
root=UUID=479420cb-def5-46a9-907c-007c03dc04ba ro
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Tags: third-party-packages xenial possible-manual-nvidia-install ubuntu
  Uname: Linux 4.4.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0NC6G7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn0NC6G7:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1594658] Re: diskless setup with nfs mounted home hangs on shutdown/reboot

[Andy Sayler]

In our deployment, this happens on a wired ethernet connection. So it's
not wifi only for us. But since it seems like a race condition,
different environments may trigger it in different scenarios.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1594658

Title:
  diskless setup with nfs mounted home hangs on shutdown/reboot

Status in nfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 fresh install hangs when shutting down.
  The system is diskless PXE-booted with a couple of nfs mounted directories 
including homedir.

  As I have no persistent storage whatsoever, I don't have any logs, but
  in debug-shell, running journalctl -f I can see that it hangs at

  [   *] (1 of 2) A stop job running for Raise Network Interfaces (10s / 1min 
30s)Jun 20 20:23:05 $hostname kernel: nfs: server $nfs-ip-address not 
responding, still trying
  Jun 20 20:23:05 $hostname kernel: nfs: server $nfs-ip-address not responding, 
still trying
  Jun 20 20:23:14 $hostname kernel: nfs: server $nfs-ip-address not responding, 
still trying
  Jun 20 20:24:08 $hostname kernel: nfs: server $nfs-ip-address not responding, 
still trying

  Second job in "(1 of 2)" is thermald, turning it off does not fix the problem.
  Also, this counter "(10s / 1min 30s)" stops visually updating.

  server $nfs-ip-address is not responding, because, all network
  interfaces are already down at this point.

  I am not exactly sure why this happens. Looks like there is a wrong
  ordering of shutdown of systemd services, which bring down interfaces
  before something nfs-related, but I am not sure if that's the reason
  of hanging.

  
  Workaround that fixes the problem:
  In /lib/systemd/system/networking.service
  comment following line:
  ExecStop=/sbin/ifdown -a --read-environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1594658/+subscriptions

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

[Touch-packages] [Bug 1575391] Re: [PowerMac7, 3] GPU compositors do not work

[ernsteiswuerfel]

As of Yakkety's todays daily iso (24.07.2016) this bug is gone due to an
update mesa-11.2.1 -> mesa-12.0.1.

** Changed in: xorg (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1575391

Title:
  [PowerMac7,3] GPU compositors do not work

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu MATE 16.04 one can select 4 compositing modes via MATE Tweak 
(german translation):
  1. Marco (kein Komposit)
  2. Marco (Programmkomposit)
  3. Marco (Compton GPU-Komposit)
  4. Compiz (anspruchsvolle Schreibtischeffekte mit GPU-Beschleunigung)

  On my PowerMac7,3 G5 with a Radeon 9650 Pro only the 1st one works
  properly. The 2nd one works, but more sluggish and a jerkier mouse
  pointer. 3 and 4 trash the desktop showing wrong colours. Only VERY
  jerky mouse movement is possible then. The desktop is no longer in a
  usable state any longer, you can't click on anything. Restarting the
  desktop with "systemctl restart lightdm" from console returns the
  desktop usable (defaulting to 1st compositor.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-powerpc64-smp 4.4.6
  Uname: Linux 4.4.0-21-powerpc64-smp ppc64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: powerpc
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 26 23:40:25 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550/9600/X1050 Series] 
[1002:4150] (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 
9550/9600/X1050 Series] [1002:4150]
  InstallationDate: Installed on 2016-03-26 (31 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta powerpc 
(20160326)
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=d6fab932-3e79-4f5c-a392-c86c01b5a8f9 ro 
rootflags=subvol=@ radeon.agpmode=-1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 22:55:40 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputLogitech G100s Optical Gaming Mouse MOUSE, id 6
   inputHID 046a:010dKEYBOARD, id 7
   inputHID 046a:010dKEYBOARD, id 8
   inputPMU  KEYBOARD, id 9
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

[Christopher M. Penalver]

** Attachment removed: "dmesg-debug.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1568429/+attachment/4706595/+files/dmesg-debug.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1568429

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1577074] Re: AMDGPU driver problems on "Carrizo" APU

[Brian]

This bug affects me on Ubuntu 16.04, but not on 15.10 where the fglrx
drivers are still available. I have the graphics card A10-8700P APU
"Carrizo" on my HP ProBook 455 G3 laptop. Like Joshua above, but only on
16.04, I can only get past the black screen if I boot into low-graphics
mode with the nomodeset parameter.

However, in my web search regarding this issue, I found a recommendation
at https://bugzilla.kernel.org/show_bug.cgi?id=117591 Comment #7, to
append "amdgpu.runpm=0" to the kernel command line in Grub setparams.
I'm going to try that with the Ubuntu 16.04 LiveUSB and report back.

** Bug watch added: Linux Kernel Bug Tracker #117591
   http://bugzilla.kernel.org/show_bug.cgi?id=117591

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1577074

Title:
  AMDGPU driver problems on "Carrizo" APU

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm having a hard time tracing this down.  I updated to Kubuntu 16.04
  (from Kubuntu 15.10 - that was using the Linux Crimson 15.12 driver) a
  couple days ago on my notebook (HP Pavilion, A10-8700P APU), and ever
  since I've been having random black screens.

  I started debugging the driver, then thought it might be a DPMS issue
  (it's not - I have DPMS fully disabled currently), and now I'm back to
  debugging the driver.

  I don't have any remnants of the former closed Crimson display driver
  and never had an xorg.conf file (I made a small one that I'm using at
  the moment consisting of only a server layout to ensure screen savers,
  DPMS, etc are all off).

  The Black screen can happen any time from the login screen until hours
  later.  I can ssh into the system to shut it down.  And just
  discovered that if I unplug the system from it's power brick, I can
  close the lid - the system will goto sleep.  When I flip the screen
  back up, the system wakes up and the screen works again for 1-2
  minutes.

  I don't see any errors in the log files (well, outside some nasty
  looking ACAPI errors in dmesg).

  HOT TO REPRODUCE:
  Boot system and use normally or simply leave system alone.  Blank screen will 
happen any time after x comes up.

  
  EXPECTED RESULT:
  Screen doesn't blank unless a screen saver or power saver kicks in.

  SYSTEM INFO:
  Purchased Dec 2015 (build date from BIOS - Aug 2015), HP Pavilion 15" 
notebook, AMD A10-8700P "Carrizo", 16GB RAM, 960GB SSD

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

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

[Touch-packages] [Bug 1432949] Re: r300 Mesa driver not loading with KMS enabled

[ernsteiswuerfel]

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1432949

Title:
  r300 Mesa driver not loading with KMS enabled

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  I cannot get 3D acceleration to work. I was expecting to see the gears
  via the command 'glxgears' I have KMS enable on my iBook G4 by using
  the following parameter

  Linux radeon.modeset=1 video=offb:off video=1024x768-32
  video=radeonfb:off radeon.agpmode=-1

  Here are my Mesa and Xorg output

  rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e 
dri2 -e drm -e KMS
  [32.774] Kernel command line: 
root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off 
video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off 
video=1024x768-32 video=radeonfb:off radeon.agpmode=-1
  [33.203] (II) xfree86: Adding drm device (/dev/dri/card0)
  [35.011] (II) LoadModule: "radeon"
  [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
  [35.337] (II) Module radeon: vendor="X.Org Foundation"
  [35.604] (II) [KMS] Kernel modesetting enabled.
  [35.697] (II) Loading sub module "dri2"
  [35.697] (II) LoadModule: "dri2"
  [35.697] (II) Module "dri2" already built-in
  [35.870] (II) RADEON(0): KMS Color Tiling: enabled
  [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled
  [35.870] (II) RADEON(0): KMS Pageflipping: enabled
  rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render
  libGL: screen 0 does not appear to be DRI3 capable
  libGL: pci id for fd 4: 1002:4e56, driver r300
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: r300
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Error: couldn't find RGB GLX visual or fbconfig
  rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  libgl1-mesa-dr 10.5.0~rc1-0 powerpc  free implementation of the OpenGL
  rican-linux@ibookG4-UbuntuMATE:~$ 

  rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri
  libgl1-mesa-dri:
Installed: 10.5.0~rc1-0ubuntu1
Candidate: 10.5.0-0ubuntu1
Version table:
   10.5.0-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages
   *** 10.5.0~rc1-0ubuntu1 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5
  Uname: Linux 3.18.0-13-powerpc-smp ppc
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: powerpc
  CurrentDesktop: MATE
  Date: Tue Mar 17 00:58:43 2015
  InstallationDate: Installed on 2015-03-17 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha powerpc (20150225)
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1432949/+subscriptions

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

[Touch-packages] [Bug 1432949] Re: r300 Mesa driver not loading with KMS enabled

[ernsteiswuerfel]

As of Yakkety's todays daily iso (24.07.2016) this bug is gone due to an
update mesa-11.2.1 -> mesa-12.0.1.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1432949

Title:
  r300 Mesa driver not loading with KMS enabled

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  I cannot get 3D acceleration to work. I was expecting to see the gears
  via the command 'glxgears' I have KMS enable on my iBook G4 by using
  the following parameter

  Linux radeon.modeset=1 video=offb:off video=1024x768-32
  video=radeonfb:off radeon.agpmode=-1

  Here are my Mesa and Xorg output

  rican-linux@ibookG4-UbuntuMATE:~$ cat /var/log/Xorg.0.log |grep -e radeon -e 
dri2 -e drm -e KMS
  [32.774] Kernel command line: 
root=UUID=fadadc01-6fd5-49fa-85f3-9e52d0fe6155 ro quiet splash video=offb:off 
video=1024x768-32 video=radeonfb:off radeon.modeset=1 video=offb:off 
video=1024x768-32 video=radeonfb:off radeon.agpmode=-1
  [33.203] (II) xfree86: Adding drm device (/dev/dri/card0)
  [35.011] (II) LoadModule: "radeon"
  [35.012] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
  [35.337] (II) Module radeon: vendor="X.Org Foundation"
  [35.604] (II) [KMS] Kernel modesetting enabled.
  [35.697] (II) Loading sub module "dri2"
  [35.697] (II) LoadModule: "dri2"
  [35.697] (II) Module "dri2" already built-in
  [35.870] (II) RADEON(0): KMS Color Tiling: enabled
  [35.870] (II) RADEON(0): KMS Color Tiling 2D: disabled
  [35.870] (II) RADEON(0): KMS Pageflipping: enabled
  rican-linux@ibookG4-UbuntuMATE:~$ LIBGL_DEBUG=verbose glxinfo |grep render
  libGL: screen 0 does not appear to be DRI3 capable
  libGL: pci id for fd 4: 1002:4e56, driver r300
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r300_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r300_dri.so
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: r300
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
  libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Error: couldn't find RGB GLX visual or fbconfig
  rican-linux@ibookG4-UbuntuMATE:~$ dpkg -l libgl1-mesa-dri
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  libgl1-mesa-dr 10.5.0~rc1-0 powerpc  free implementation of the OpenGL
  rican-linux@ibookG4-UbuntuMATE:~$ 

  rican-linux@ibookG4-UbuntuMATE:~$ lsb_release -rd
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04

  rican-linux@ibookG4-UbuntuMATE:~$ apt-cache policy libgl1-mesa-dri
  libgl1-mesa-dri:
Installed: 10.5.0~rc1-0ubuntu1
Candidate: 10.5.0-0ubuntu1
Version table:
   10.5.0-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main powerpc Packages
   *** 10.5.0~rc1-0ubuntu1 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libgl1-mesa-dri 10.5.0~rc1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-powerpc-smp 3.18.5
  Uname: Linux 3.18.0-13-powerpc-smp ppc
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: powerpc
  CurrentDesktop: MATE
  Date: Tue Mar 17 00:58:43 2015
  InstallationDate: Installed on 2015-03-17 (0 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha powerpc (20150225)
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1432949/+subscriptions

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

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

[Christopher M. Penalver]

Charlie McMackin, to advise, the article provides information on how to
obtain details from a session when the issue occurs.

Posting logs from a working session unfortunately doesn't provide what
is needed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1568429

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Joakim Koed]

Mikko: you can just download the debs, no need to build it :)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions

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

[Touch-packages] [Bug 1606051] [NEW] dhclient fails to get address after latest patches

[Justin Alcorn]

Public bug reported:

>From ASkUbuntu entry http://askubuntu.com/questions/801136/recent-
patches-broke-dhclient/802390

Running 16.04.01 LTS recently upgraded from 15.10. System is a home firewall 
with enp1s0 as LAN interface statically assigned and enp2s0 is WAN interface 
using DHCP, connected to modem.
Ran apt-get upgrade and on reboot enp2s0 had no address. running ifdown enp2s0 
and then ifup enp2s0 gave me

root@sam:~# ifup enp2s0
Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/enp2s0/d0:50:99:21:80:f8
Sending on   LPF/enp2s0/d0:50:99:21:80:f8
Sending on   Socket/fallback
DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 3 (xid=0xd998571a)
send_packet: Network is down
dhclient.c:2098: Failed to send 300 byte long packet over enp2s0 interface.
receive_packet failed on enp2s0: Network is down
DHCPDISCOVER on enp2s0 to 255.255.255.255 port 67 interval 5 (xid=0xd998571a)
send_packet: Network is down
Running ifconfig enp2s0 up and dhclient enp2s0 gave similar results, but 
eventually /var/log/syslog showed a dhclient ipv4 lease being obtained - but 
the enp2s0 had only an IPv6 address, which appears to have come from 
avahi-daemon.

I then manually configured the enp2s0 interface with ifconfig enp2s0
xxx.xxx.xxx.xxx netmask 255.255.248.0 and put in a default route based
on the lease info in dhclient.leases and I'm back online. But if I
reboot or try to get dhclient to work, I continue to get the network is
down errors.

apparmor is disabled, so that's not it. iptables is set to allow all
DHCP traffic (67/udp and 68/udp) and all RELATED,ESTABLISHED traffic
from enp2s0.

enp2s0 and enp2s0 are the same hardware.

root@sam:~# lshw -class network
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:01:00.0
   logical name: enp1s0
   version: 01
   serial: 04:8d:38:5d:20:17
   size: 100Mbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm vpd msi pciexpress bus_master cap_list rom ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full ip=yyy.yyy.yyy.yyy latency=0 link=yes 
multicast=yes port=MII speed=100Mbit/s
   resources: irq:38 ioport:e000(size=256) memory:ffa0-ffa00fff 
memory:ffa2-ffa3
  *-network
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   logical name: enp2s0
   version: 11
   serial: d0:50:99:21:80:f8
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 
ip=xxx.xxx.xxx.xxx latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
   resources: irq:40 ioport:d000(size=256) memory:ff90-ff900fff 
memory:d080-d0803fff
Ideas? remember, this happened right after patching.

networking network-manager dhclient

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu12.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jul 24 15:33:19 2016
InstallationDate: Installed on 2016-03-01 (145 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to xenial on 2016-06-22 (32 days ago)
mtime.conffile..etc.dhcp.debug: 2016-06-28T18:13:33.371977

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1606051

Title:
  dhclient fails to get address after latest patches

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  From ASkUbuntu entry http://askubuntu.com/questions/801136/recent-
  patches-broke-dhclient/802390

  Running 16.04.01 LTS recently upgraded from 15.10. System is a home firewall 
with enp1s0 as LAN interface statically assigned and enp2s0 is WAN interface 
using DHCP, connected to modem.
  Ran apt-get upgrade and on reboot enp2s0 had no address. running ifdown 
enp2s0 and then ifup enp2s0 gave me

  root@sam:~# ifup enp2s0
  Internet Systems Cons

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

[Charlie McMackin]

I'm still unable to boot following the linked directions by removing the
vt_handoff, quiet, and splash kernel params and also setting gfxmode to
"text". It follows nearly the same behavior black screen, constant hdd
activity light on -- the monitor however still detects an input signal,
it's just black.

I can boot by using the linked method but also supplying
radeon.modeset=0 flag. I'm attaching the dmesg log from that boot up.
I'm assuming dmesg output is the "missing information" requested. If
there is something else missing please let me know.

** Attachment added: "dmesg-debug.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1568429/+attachment/4706595/+files/dmesg-debug.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1568429

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  x

[Touch-packages] [Bug 1522675] Re: /root/.synaptic/ not created due to locking status

[Deleted]

Is there a fix for this yet? It's still happening on Ubuntu 16.04 with
all updates as of 07/24/2016.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1522675

Title:
  /root/.synaptic/ not created due to locking status

Status in apt package in Ubuntu:
  Invalid
Status in synaptic package in Ubuntu:
  Confirmed
Status in synaptic package in Debian:
  New

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1569718] Re: Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] + [Power]" factory reset

[Xavier Guillot]

@PatMcGowan Thanks a lot for the answer and solution, it worked
perfectly, I was just able to reinstall Ubuntu on the E4.5, then
restart, restore contacts + messages, all seems to work.

Now, no more exotic manipulation with non-native programs !

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1569718

Title:
  Ubuntu Touch (BQ Aquaris 4.5) - Does not boot after "[Volume Up] +
  [Power]" factory reset

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Today, I tried to factory reset my BQ Aquaris 4.5 Ubuntu Touch Edition
  with the [Volume Up] + [Power] method but since then, the phone won't
  boot. It only displays the BQ logo and then a black screen (it is
  still on but it's displaying nothing). I tried to connect the phone
  with adb but it doesn't seem to be recognized by the computer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1569718/+subscriptions

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

[Touch-packages] [Bug 1584549] Re: sudoers not honoring hostnames

[oshunluvr]

New info: Using the FQDN instead of the shortened hostname version
works. As before, in 15.04 shortened hostname works in sudoers.d/ files
but in 16.04 it does not.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hostname in Ubuntu.
https://bugs.launchpad.net/bugs/1584549

Title:
  sudoers not honoring hostnames

Status in hostname package in Ubuntu:
  New

Bug description:
  New Kubuntu 16.04 install, adding features from previous 15.04
  install. Added exact copy of /etc/sudoers.d/apt from 15.04 to 16.04
  but it does not work as expected. File contents:

  myusername myhostname = NOPASSWD: /usr/bin/apt, /usr/bin/apt-get,
  /usr/bin/add-apt-repository

  results in 15.04 in user "myusername" being able to run apt, apt-get,
  and add-apt-repository from the CLI using sudo without a password
  prompt. However, same exact syntax in 16.04 results in password
  prompt.

  In the 16.04 install, changing "myhostname" to "ALL" resumes the no
  password behavior. Both installs have exact same /etc/hosts files,
  running on bare metal on the same system, and the "hostname" command
  results in the same reply with the correct hostname. I have compared
  the subject files several times and there are no differences. No
  errors editing any of the files using visudo. Permissions and syntax
  same on both systems.

  This leads me to conclude sudoers is not honoring the hostname in the
  sudoers file(s).

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

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

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

[biohazara]

Turns out what I said before isn't true. The issue still exists.

So, why was I getting a good network connection on the physical machine
I tried 16.04.1 on? Because I was connecting to WiFi via an Access Point
created on a 14.04 installation. The minute I connected directly to the
router, it started showing the network connection issues all over again.

Similarly, it seems that the network works fine in VirtualBox (14.04
host) if using a NAT network adapter. If I switch it a bridged adapter I
get the network stops working after a while, just like a physical
machine running 16.04 before.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1434986

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions

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

[Touch-packages] [Bug 1606023] [NEW] Messaging should remember which contact was open after an OOM close

[Michael Terry]

Public bug reported:

Messaging should use StateSaver to remember which contact is open. So
that if it is killed by the OOM manager, it will be restarted in the
right place.

** Affects: messaging-app (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1606023

Title:
  Messaging should remember which contact was open after an OOM close

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Messaging should use StateSaver to remember which contact is open. So
  that if it is killed by the OOM manager, it will be restarted in the
  right place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1606023/+subscriptions

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

[Touch-packages] [Bug 1606022] [NEW] problem

[xavierbazin]

Public bug reported:

stars impossible after installation

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jul 24 18:07:49 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Wrestler [Radeon HD 6310] [1025:0520]
InstallationDate: Installed on 2016-07-24 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: Packard Bell EasyNote TK13BZ
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=3c76d895-666b-49c5-b569-ac6cb2a927a6 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2011
dmi.bios.vendor: Packard Bell
dmi.bios.version: V1.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV50-BZ
dmi.board.vendor: Packard Bell
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V1.15
dmi.modalias: 
dmi:bvnPackardBell:bvrV1.15:bd08/19/2011:svnPackardBell:pnEasyNoteTK13BZ:pvrV1.15:rvnPackardBell:rnSJV50-BZ:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV1.15:
dmi.product.name: EasyNote TK13BZ
dmi.product.version: V1.15
dmi.sys.vendor: Packard Bell
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Jul 24 12:22:49 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: radeon

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1606022

Title:
  problem

Status in xorg package in Ubuntu:
  New

Bug description:
  stars impossible after installation

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jul 24 18:07:49 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Wrestler [Radeon HD 6310] [1025:0520]
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: Packard Bell EasyNote TK13BZ
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=3c76d895-666b-49c5-b569-ac6cb2a927a6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2011
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SJV50-BZ
  dmi.board.vendor: Packard Bell
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Packard Bell
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnPackardBell:bvrV1.15:bd08/19/2011:svnPackardBell:pnEasyNoteTK1

[Touch-packages] [Bug 1594658] Re: diskless setup with nfs mounted home hangs on shutdown/reboot

[Sean]

Same issue here on clean 16.04 install.  Only happens on wifi devices
doesnt seem to affect wired devices.  NFS mounts setup via fstab.
Unmounting NFS shares before shutdown allows the system to shutdown.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1594658

Title:
  diskless setup with nfs mounted home hangs on shutdown/reboot

Status in nfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 fresh install hangs when shutting down.
  The system is diskless PXE-booted with a couple of nfs mounted directories 
including homedir.

  As I have no persistent storage whatsoever, I don't have any logs, but
  in debug-shell, running journalctl -f I can see that it hangs at

  [   *] (1 of 2) A stop job running for Raise Network Interfaces (10s / 1min 
30s)Jun 20 20:23:05 $hostname kernel: nfs: server $nfs-ip-address not 
responding, still trying
  Jun 20 20:23:05 $hostname kernel: nfs: server $nfs-ip-address not responding, 
still trying
  Jun 20 20:23:14 $hostname kernel: nfs: server $nfs-ip-address not responding, 
still trying
  Jun 20 20:24:08 $hostname kernel: nfs: server $nfs-ip-address not responding, 
still trying

  Second job in "(1 of 2)" is thermald, turning it off does not fix the problem.
  Also, this counter "(10s / 1min 30s)" stops visually updating.

  server $nfs-ip-address is not responding, because, all network
  interfaces are already down at this point.

  I am not exactly sure why this happens. Looks like there is a wrong
  ordering of shutdown of systemd services, which bring down interfaces
  before something nfs-related, but I am not sure if that's the reason
  of hanging.

  
  Workaround that fixes the problem:
  In /lib/systemd/system/networking.service
  comment following line:
  ExecStop=/sbin/ifdown -a --read-environment

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1594658/+subscriptions

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

[Touch-packages] [Bug 1568429] Re: 1002:68b8 Radeon won't work with KMS enabled

[Christopher M. Penalver]

Charlie McMackin, could you please provide the missing information from
https://wiki.ubuntu.com/DebuggingKernelBoot ?

** Tags removed: regression-release
** Tags added: regression-potential

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1568429

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Xenial today and ensuring the xorg radeon driver
  was enabled, when booting both monitor lose signal input and the
  keyboard becomes unresponsive.

  My hardware:
  02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1605797] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all

[Raymond]

https://www.virtualbox.org/log/vbox/trunk/src/VBox/Devices/Audio/DevIchAc97.cpp?rev=62355

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1605797

Title:
  [ICH - Intel 82801AA-ICH, playback] No sound at all

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New ubuntu install on 2016-07-22; latest version.
  Running as virtualbox guest on latest OS X.
  Sound card recognized on mac, but not on guest.
  No sound in or out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 22 19:00:19 2016
  InstallationDate: Installed on 2016-07-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  Symptom_Type: No sound at all
  Title: [ICH - Intel 82801AA-ICH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1605797/+subscriptions

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

[Touch-packages] [Bug 1595414] Re: Awful generic selection for zh in Firefox

[Gunnar Hjalmarsson]

More input from Chinese users is needed to make progress on this one.
Feedback on my idea in comment #6 would be appreciated, as would other
ideas on the desired direction.

Removing the trusty tasks for now. Let's decide what to do in the
current development version first, and consider possible backporting
later.

** No longer affects: fonts-arphic-ukai (Ubuntu Trusty)

** No longer affects: fonts-arphic-uming (Ubuntu Trusty)

** No longer affects: language-selector (Ubuntu Trusty)

** Changed in: fonts-arphic-ukai (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: fonts-arphic-ukai (Ubuntu)
   Status: New => Incomplete

** Changed in: fonts-arphic-uming (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: fonts-arphic-uming (Ubuntu)
   Status: New => Incomplete

** Changed in: language-selector (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: language-selector (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fonts-arphic-ukai in
Ubuntu.
https://bugs.launchpad.net/bugs/1595414

Title:
  Awful generic selection for zh in Firefox

Status in fonts-arphic-ukai package in Ubuntu:
  Incomplete
Status in fonts-arphic-uming package in Ubuntu:
  Incomplete
Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  In https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/fonts-
  arphic-ukai/wily/revision/6, UMing and UKai are set as generics for
  fonts. However, this set of generics is completely intolerable --
  setting UKai as a generic is like setting Zapfino and/or Comic Sans as
  a system-wise generic, while UMing as a normal (just a bit thin) serif
  sounds a bit better. This yields terrible results on non-Chinese
  systems with non-Chinese lang-attributed websites, like Twitter, on
  Ubuntu 14.04 LTS after installing Chinese language support which
  includes the two arphic fonts mentioned in this report.

  This problem is similar to
  https://bugs.freedesktop.org/show_bug.cgi?id=20911, a long-standing
  system-global fontconfig non-latin fallback problem. See also bug
  #1560548 where these generic settings are considered as 'redundant'
  and proposed for deletion. I have mentioned a third-person report
  about such selection in #1560548 previously, but I have just
  reproduced this bug by myself by installing zh-cn support by mistake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1595414/+subscriptions

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

[Touch-packages] [Bug 1568429] Re: Radeon won't work with KMS enabled

[Christopher M. Penalver]

** Description changed:

- I have a Radeon HD 5770 GPU. After upgrading to Xenial today and
- ensuring the xorg radeon driver was enabled, my machine will no longer
- boot to a usable state. After selecting default Ubuntu option from GRUB
- menu, both monitor lose signal input and the keyboard becomes
- unresponsive. Sometimes the machine will reboot on its own, most of the
- time I have to hard reset.
+ After upgrading to Xenial today and ensuring the xorg radeon driver was
+ enabled, when booting both monitor lose signal input and the keyboard
+ becomes unresponsive.
+ 
+ My hardware:
+ 02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller])
+   Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  
  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0
  
  The machine will boot but the radeon driver will not load. Attempting to
  load radeon driver with `sudo modprobe radeon modeset=1` after booting
  with modesetting off results in the same fail state explained above.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:
  
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
  
  xserver.version: 2:1.18.3-1ubuntu2

** Summary changed:

- Radeon won't work with KMS enabled
+ 1002:68b8 Radeon won't work with KMS enabled

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1568429

Title:
  1002:68b8 Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upg

[Touch-packages] [Bug 1580472] Re: No visible cursor after logging in

[Christopher M. Penalver]

Fabio, to further clarify, if you have the nvidia card enabled, but
don't install the nvidia drivers, is this still reproducible?

** Description changed:

- After logging in, the cursor is not drawn on the screen.
- 
- I can see it's effects while moving the mouse or touchpad, as items on
- the panel gets highlighted, or my unity panel becomes visible. I can
- even click on them and everything else just works, but I have to figure
- the cursor position.
+ Only when using the nvidia drivers, after logging in, the cursor is not
+ drawn on the screen. I can see its effects while moving the mouse or
+ touchpad, as items on the panel gets highlighted, or my unity panel
+ becomes visible. I can even click on them and everything else works.
  
  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
- sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.
+ sudo service lightdm restart. Now log in again through lightdm. This works 
most of the time.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: nvidia-361 361.42-0ubuntu2
- ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
- Uname: Linux 4.4.0-21-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Wed May 11 08:53:35 2016
- EcryptfsInUse: Yes
- InstallationDate: Installed on 2015-03-21 (416 days ago)
- InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
- SourcePackage: nvidia-graphics-drivers-361
- UpgradeStatus: No upgrade log present (probably fresh install)
- modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
- --- 
+ ---
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
-  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
+  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
-  bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
-  bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
-  nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
-  nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
+  bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
+  bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
+  bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
+  nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
+  nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
-Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
+  Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
+    Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: L

[Touch-packages] [Bug 1584488] Re: lightdm: error found when loading /root/.profile

[DLCBurggraaff]

Resolved with 16.04.1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1584488

Title:
  lightdm: error found when loading /root/.profile

Status in lightdm package in Ubuntu:
  New

Bug description:
  Lightdm on Ubuntu 16.04, also with Ubuntu-Mate 16.04 and Xubuntu 16.04
  but *not* with Lubuntu 16.04

  When logging in via Other > root a popup is shown reading:
  -- Error found when loading /root/.profile
  -- mesg: ttyname failed: Inappropriate ioctl for device
  -- As result the session will not be configured correctly.
  -- You should fix the problem as soon as feasible.

  After pressing OK the session is started without problems.

  Alternatively logging in via  as root and issuing "startx
  -- :1" succeeds without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun May 22 15:58:45 2016
  LightdmConfig:
   [SeatDefaults]
   allow-guest=false
   autologin-guest=false
   autologin-user=ubuntu
   autologin-user-timeout=0
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1606002] Re: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other in

[Apport retracing service]

*** This bug is a duplicate of bug 1605911 ***
https://bugs.launchpad.net/bugs/1605911

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1605911, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1605911
   package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/bin/unity-scope-loader', which is different 
from other instances of package libunity9:i386

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1606002

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  not sure from this error message was poped up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 18:38:14 2016
  DuplicateSignature:
   package:libunity9:7.1.4+16.04.20160701-0ubuntu1
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1605911] Re: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other in

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libunity (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1605911

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  Confirmed

Bug description:
  I don't know what's going on.  All I know is that I'm trying to
  install some programs to Ubuntu and it isn't working.  I tried the
  apt-get install -f to no avail.  I'm trying to install the Chrome
  browser from Google and Tetravex plus some updates and they won't
  install.   I'm new to Ubuntu and wanted to try it out as an
  alternative to Windows.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Jul 23 13:35:07 2016
  DuplicateSignature:
   package:libunity9:7.1.4+16.04.20160701-0ubuntu1
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 923876] Re: FR: Limit and clean-up kernel images and headers automatically

[Jarno Suni]

Pxtl, in 16.04 the bug is fixed according to Bug #1357093. Please
comment there, if you believe it is not the case. I can not reopen the
bug anymore, but you may want to report a new bug against unattended-
upgrades and link it here.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/923876

Title:
  FR: Limit and clean-up kernel images and headers automatically

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Fix Released
Status in aptitude source package in Precise:
  Confirmed
Status in apt source package in Quantal:
  Fix Released
Status in aptitude source package in Quantal:
  Won't Fix

Bug description:
  Question #186146 is one among multiple where user unintentionally collects 
multiple kernel images in particular with LTS. There is no hint from relevant 
package management application GUIs which advise to clean up those images. With 
future LTS support of five years the issue presumable will extend.
  Expected.
  After installation of a newer kernel image ask the user if previous kernel 
images should be removed.
  Checkbox: yes - no
  If yes, offer a list of installed kernel images, don't list the one booted. 
Advise to keep at least the last functional one.
  Also remove -headers.

  Perhaps an additional consideration for the blueprint.
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-lts-upgrades

  There is a new Quantal blueprint regarding the subject.
  https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-clean-old-kernels

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

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

[Touch-packages] [Bug 1606002] [NEW] package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', which is different from other

[Avinash]

Public bug reported:

not sure from this error message was poped up.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jul 24 18:38:14 2016
DuplicateSignature:
 package:libunity9:7.1.4+16.04.20160701-0ubuntu1
 Unpacking libperl5.22:i386 (5.22.1-9) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', 
which is different from other instances of package libperl5.22:i386
ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
InstallationDate: Installed on 2016-07-24 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: libunity
Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libunity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check package-conflict xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunity in Ubuntu.
https://bugs.launchpad.net/bugs/1606002

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-
  loader', which is different from other instances of package
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  not sure from this error message was poped up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 18:38:14 2016
  DuplicateSignature:
   package:libunity9:7.1.4+16.04.20160701-0ubuntu1
   Unpacking libperl5.22:i386 (5.22.1-9) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other 
instances of package libperl5.22:i386
  ErrorMessage: trying to overwrite shared '/usr/bin/unity-scope-loader', which 
is different from other instances of package libunity9:i386
  InstallationDate: Installed on 2016-07-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/unity-scope-loader', 
which is different from other instances of package libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Jarno Suni]

Alan Burgess, have you tried to follow the workaround given in the
description to manually remove old kernels and to setup automatic
removal of old kernels?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/798414

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jarno Suni]

Can someone confirm that security updates are installed automatically by
default in Xenial?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jarno Suni]

Can someone tell if unattended-upgrades has purged any older kernels in
Xenial? Provided that security updates are configured to download and
install automatically in Software & Updates, and there is line

//Unattended-Upgrade::Remove-Unused-Dependencies "true";

or

Unattended-Upgrade::Remove-Unused-Dependencies "false";

and not line

Unattended-Upgrade::Remove-New-Unused-Dependencies "false"

in /etc/apt/apt.conf.d/50unattended-upgrades

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

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

[Touch-packages] [Bug 1605991] Re: Multiseat login stopped working

[Hatl]

Forgot to mention: I'm using Ubuntu 16.04.1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1605991

Title:
  Multiseat login stopped working

Status in lightdm package in Ubuntu:
  New

Bug description:
  After installing version 1.18.2-0ubuntu1 of the lightdm package, only one 
seat can login on my multiseat setup. (2 seats)
  Reverting to version 1.18.1-0ubuntu1 resolves the issue.

  syslog shows the following errors:

  console-kit-daemon[4783]: (process:16634): GLib-CRITICAL **: 
g_slice_set_config: assertion 'sys_page_size == 0' failed
  lightdm[16617]: ** (lightdm:16617): CRITICAL **: 
session_get_login1_session_id: assertion 'session != NULL' failed

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

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

[Touch-packages] [Bug 1605991] Re: Multiseat login stopped working

[Hatl]

** Attachment added: "lightdm-1.18.1.log"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1605991/+attachment/4706327/+files/lightdm-1.18.1.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1605991

Title:
  Multiseat login stopped working

Status in lightdm package in Ubuntu:
  New

Bug description:
  After installing version 1.18.2-0ubuntu1 of the lightdm package, only one 
seat can login on my multiseat setup. (2 seats)
  Reverting to version 1.18.1-0ubuntu1 resolves the issue.

  syslog shows the following errors:

  console-kit-daemon[4783]: (process:16634): GLib-CRITICAL **: 
g_slice_set_config: assertion 'sys_page_size == 0' failed
  lightdm[16617]: ** (lightdm:16617): CRITICAL **: 
session_get_login1_session_id: assertion 'session != NULL' failed

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

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

[Touch-packages] [Bug 1605991] [NEW] Multiseat login stopped working

[Hatl]

Public bug reported:

After installing version 1.18.2-0ubuntu1 of the lightdm package, only one seat 
can login on my multiseat setup. (2 seats)
Reverting to version 1.18.1-0ubuntu1 resolves the issue.

syslog shows the following errors:

console-kit-daemon[4783]: (process:16634): GLib-CRITICAL **: 
g_slice_set_config: assertion 'sys_page_size == 0' failed
lightdm[16617]: ** (lightdm:16617): CRITICAL **: session_get_login1_session_id: 
assertion 'session != NULL' failed

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "lightdm.log"
   
https://bugs.launchpad.net/bugs/1605991/+attachment/4706326/+files/lightdm.log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1605991

Title:
  Multiseat login stopped working

Status in lightdm package in Ubuntu:
  New

Bug description:
  After installing version 1.18.2-0ubuntu1 of the lightdm package, only one 
seat can login on my multiseat setup. (2 seats)
  Reverting to version 1.18.1-0ubuntu1 resolves the issue.

  syslog shows the following errors:

  console-kit-daemon[4783]: (process:16634): GLib-CRITICAL **: 
g_slice_set_config: assertion 'sys_page_size == 0' failed
  lightdm[16617]: ** (lightdm:16617): CRITICAL **: 
session_get_login1_session_id: assertion 'session != NULL' failed

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

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

[Touch-packages] [Bug 1568429] Re: Radeon won't work with KMS enabled

[Charlie McMackin]

Chistopher Penalver, it is hard to say as this is the first release
where I can no longer use Catalyst -- I have been using the the binary
drivers before this release. I remember my upgrading from 15.04 to 15.10
having a similar looking issue until I reinstalled the binary drivers. I
never tried modesetting kernel parameters at that time so I can't say
100% if the error was the same.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1568429

Title:
  Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have a Radeon HD 5770 GPU. After upgrading to Xenial today and
  ensuring the xorg radeon driver was enabled, my machine will no longer
  boot to a usable state. After selecting default Ubuntu option from
  GRUB menu, both monitor lose signal input and the keyboard becomes
  unresponsive. Sometimes the machine will reboot on its own, most of
  the time I have to hard reset.

  WORKAROUND: Use one of the following kernel parameters:
  nomodeset
  radeon.modeset=0

  The machine will boot but the radeon driver will not load. Attempting
  to load radeon driver with `sudo modprobe radeon modeset=1` after
  booting with modesetting off results in the same fail state explained
  above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,mousepoll,widget,regex,vpswitch,resize,imgpng,place,gnomecompat,wall,move,animation,fade,snap,expo,scale,unitymtgrabhandles,ezoom,session,workarounds]
  CompositorRunning: None
  Date: Sat Apr  9 20:02:22 2016
  DistUpgraded: 2016-04-09 16:49:55,340 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.12, 4.2.0-35-generic, x86_64: installed
   vboxhost, 5.0.12, 4.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Juniper XT [Radeon HD 5770] [1682:2990]
  InstallationDate: Installed on 2013-12-29 (832 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=e7310b2e-03b9-4e94-ba8a-d384330592cf ro quiet splash radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (0 days ago)
  dmi.bios.date: 04/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0519
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5N7A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0519:bd04/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N7A-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Apr  9 19:49:46 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : t

[Touch-packages] [Bug 1605989] [NEW] package account-plugin-facebook (not installed) failed to install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-options.d/www.facebook.com.conf“, který je

[Tommy_CZ]

Public bug reported:

I cannot install this package because I have KDE5 installed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-facebook (not installed)
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jul 24 14:06:56 2016
ErrorMessage: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/www.facebook.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2016-06-11 (42 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: account-plugins
Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/www.facebook.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.signon-ui.webkit-options.d.www.facebook.com.conf: 
2016-03-10T00:26:54

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1605989

Title:
  package account-plugin-facebook (not installed) failed to
  install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf“, který je také v balíku kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  I cannot install this package because I have KDE5 installed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-facebook (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 14:06:56 2016
  ErrorMessage: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/www.facebook.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-06-11 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/www.facebook.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.signon-ui.webkit-options.d.www.facebook.com.conf: 
2016-03-10T00:26:54

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1605989/+subscriptions

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

[Touch-packages] [Bug 1605990] [NEW] package account-plugin-twitter (not installed) failed to install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-options.d/api.twitter.com.conf“, který je t

[Tommy_CZ]

Public bug reported:

I cannot install this package because I have KDE5 installed.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: account-plugin-twitter (not installed)
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sun Jul 24 14:06:57 2016
ErrorMessage: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/api.twitter.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
InstallationDate: Installed on 2016-06-11 (42 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: account-plugins
Title: package account-plugin-twitter (not installed) failed to 
install/upgrade: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/api.twitter.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to account-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1605990

Title:
  package account-plugin-twitter (not installed) failed to
  install/upgrade: zkouším přepsat soubor „/etc/signon-ui/webkit-
  options.d/api.twitter.com.conf“, který je také v balíku kaccounts-
  providers 4:15.12.3-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  I cannot install this package because I have KDE5 installed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: account-plugin-twitter (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jul 24 14:06:57 2016
  ErrorMessage: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/api.twitter.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
  InstallationDate: Installed on 2016-06-11 (42 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: account-plugins
  Title: package account-plugin-twitter (not installed) failed to 
install/upgrade: zkouším přepsat soubor 
„/etc/signon-ui/webkit-options.d/api.twitter.com.conf“, který je také v balíku 
kaccounts-providers 4:15.12.3-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1605990/+subscriptions

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

[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Jarno Suni]

Oh, in contrary to previous comment, for some reason, kernel 4.4.0-28
was marked as manually installed. I changed it to be automatically
installed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Currently if one chooses to use LVM or encrypted install, a /boot
  partition is created of 236Mb

  Once kernel updates start being released this partition soon fills
  until people are left unable to upgrade.

  While you and I might know that we need to watch partition space, many
  of the people we have installing think that a windows disk is a disk
  and not a partition, education is probably the key - but in the
  meantime support venues keep needing to deal with the fact the
  partition is too small and/or old kernels are not purged as new ones
  install.

  For workaround and sytem repair, see
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

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

[Touch-packages] [Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws

[Plurtu]

Why does the GUI update-manager not update to the latest compiz package?
I noticed the unity package updated and has unity7.conf which tries to
use the compiz profile "unity-lowgfx" but it doesn't exist because
compiz is still at version 20160526. sudo apt-get upgrade/dist-upgrade
both detect and install the new compiz package but not update-manager.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nux in Ubuntu.
https://bugs.launchpad.net/bugs/1598770

Title:
  Unity in low-graphics mode has animations and unneeded redraws

Status in compiz package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in compiz source package in Xenial:
  Fix Released
Status in nux source package in Xenial:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  When unity is in Low graphics mode (because of software rendering)
  there are still window animations and fade effects which we should get
  rid of.

  
  [Test case]

  This should apply naturally to a (virtual-)machine with no hardware
  acceleration or There are multiple ways to force low-gfx mode:

  1) Add an upstart job such as:

  cat << EOF > ~/.config/upstart/lowgfx.conf
  start on starting unity7

  pre-start script
#initctl set-env --global UNITY_LOW_GFX_MODE=1
initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1
  end script
  EOF 

  
  2) Run unity with:
 COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx

  On login unity should use opaque views (dash, switcher, launcher,
  shortcut-dialogs) with no fading and reduced effects. Windows should
  also use smaller shadows.

  
  [Regression potential]

  Some settings from unity-control-center couldn't be applied to normal
  profile. Low graphics mode might be used as normal one.

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

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

[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Jarno Suni]

Pxtl, the script is explained in https://markmcb.com/2013/02/04/cleanup-
unused-linux-kernels-in-ubuntu/ I do not recommend to use it, though.
Rather use the instructions in the given workaround. (Even the script
called purge-old-kernels isn't perfect and not usable in some more
complex cases, but at least you can report bugs about it.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/798414

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions

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

[Touch-packages] [Bug 1573755] Re: Compose and dead keys stopped working with XIM after upgrade to 16.04

[Gunnar Hjalmarsson]

This bug report was one reason why I submitted
. Considering that XIM currently may
cause problems in an unpredictable manner, we'd better stop setting it
automatically in certain flavors, at least until the root cause has been
spotted and the problem fixed.

Adding xkeyboard-config and libx11 as affected packages. Don't think
that this is an ibus issue, but leaving it there for now.

** Also affects: xkeyboard-config (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: libx11 (Ubuntu)
   Importance: Undecided => High

** Changed in: libx11 (Ubuntu)
   Status: New => Confirmed

** Changed in: xkeyboard-config (Ubuntu)
   Importance: Undecided => High

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1573755

Title:
  Compose and dead keys stopped working with XIM after upgrade to 16.04

Status in firefox package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Invalid
Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 16.04, entering characters using dead keys and
  using the Compose key stopped working in Gnome Terminal, acting like
  they are normal (non-dead) keys.

  Other applications, even those who use the same libvte (e.g. ROXTerm),
  don't have this issue.

  This happens with both the "Belgian" and "English international with
  AltGr dead keys" layouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 20:45:33 2016
  InstallationDate: Installed on 2013-12-16 (857 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Touch-packages] [Bug 1546472] Re: App scope display issues

[Tim Süberkrüb]

** Attachment added: "Video"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1546472/+attachment/4706309/+files/scopes.mp4

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1546472

Title:
  App scope display issues

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I experienced some display issues with the app scope on rc-proposed.
  Please refer to the attached screenshot. I don't know yet which exact steps 
reproduce this behavior (will add the information if I find it out).
  phablet@ubuntu-phablet:~$ apt-cache policy unity8
  unity8:
Installed: 8.11+15.04.20160212-0ubuntu1
Candidate: 8.11+15.04.20160212-0ubuntu1
Version table:
   *** 8.11+15.04.20160212-0ubuntu1 0
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1546472] Re: App scope display issues

[Tim Süberkrüb]

Another way to reproduce this issue:
* Install an app from the store
* Go to the app scope (e.g. by pressing the Ubuntu-Button in the launcher if 
set as home scope)
* The app scope will reload due to the newly installed app
* while reloading, search for a random app in the app scope
krillin, rc-proposed (r392)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1546472

Title:
  App scope display issues

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I experienced some display issues with the app scope on rc-proposed.
  Please refer to the attached screenshot. I don't know yet which exact steps 
reproduce this behavior (will add the information if I find it out).
  phablet@ubuntu-phablet:~$ apt-cache policy unity8
  unity8:
Installed: 8.11+15.04.20160212-0ubuntu1
Candidate: 8.11+15.04.20160212-0ubuntu1
Version table:
   *** 8.11+15.04.20160212-0ubuntu1 0
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1509816] Re: Upgrade from 14.04 to 15.04 missed systemd-sysv and init package init 1.22ubuntu11 failed to install/upgrade: pre-dependency problem - not installing init

[Lionel Roubeyrie]

Same issue when upgrading from 14.04.4 to 16.04, with this message when doing 
an 'apt-get -f install':
Initializing machine ID from D-Bus machine ID.
Failed to mount /etc/machine-id: Not a directory

Moving /etc/machine-id away and recalling apt-get -f install does the
trick

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1509816

Title:
  Upgrade from 14.04 to 15.04 missed systemd-sysv and init package init
  1.22ubuntu11 failed to install/upgrade: pre-dependency problem - not
  installing init

Status in init-system-helpers package in Ubuntu:
  Confirmed

Bug description:
  everything was updated to 14.04
  several other failures appeared during update

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: init (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  Date: Sun Oct 25 14:57:21 2015
  DuplicateSignature: package:init:1.22ubuntu11:pre-dependency problem - not 
installing init
  ErrorMessage: pre-dependency problem - not installing init
  InstallationDate: Installed on 2015-09-04 (50 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: init-system-helpers
  Title: package init 1.22ubuntu11 failed to install/upgrade: pre-dependency 
problem - not installing init
  UpgradeStatus: Upgraded to vivid on 2015-10-25 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1509816/+subscriptions

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

[Touch-packages] [Bug 1605982] [NEW] backlight flashes at booting.

[jebin]

Public bug reported:

Backlight flashes at booting. And booting enters into black screen with
message "you need to manually fix graphics and video driver".  Unable to
fix it manually.

If the lcd screen is turned off during booting using (fn+f7) keys ,
ubuntu 16.04 boots without any trouble.

Suspend not working properly. laptop wakes automatically from sleep
after 3 seconds.

The problem start in ubuntu 14.04 & continues in 16.04 also after
downgrading to 12.04 & 13.10.


operating system :ubuntu 16.04 ,64-bit

Laptop model: HCL me laptop

$ ls /sys/class/backlight/
intel_backlight


$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog: /dev/sda5: clean, 265587/1099440 files, 1523216/4397056 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jul 24 16:12:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Pegatron 2nd Generation Core Processor Family Integrated Graphics 
Controller [1b0a:2080]
InstallationDate: Installed on 2016-07-09 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 003: ID 0e8d:2004 MediaTek Inc. 
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HCL Infosystems Limited HCL ME Laptop
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=5137acf3-f2aa-469f-b5ec-9de215734f1a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 211
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: HCL ME Laptop
dmi.board.vendor: HCL
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HCL
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr211:bd10/19/2012:svnHCLInfosystemsLimited:pnHCLMELaptop:pvr1.0:rvnHCL:rnHCLMELaptop:rvr1.0:cvnHCL:ct10:cvr1.0:
dmi.product.name: HCL ME Laptop
dmi.product.version: 1.0
dmi.sys.vendor: HCL Infosystems Limited
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Jul 24 16:04:47 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputSleep Button KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id6972 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2.2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1605982

Title:
  backlight flashes at booting.

Status in xorg package in Ubuntu:
  New

Bug description:
  Backlight flashes at booting. And booting enters into black screen
  with message "you need to manually fix graphics and video driver".
  Unable to fix it manually.

  If the lcd screen is turned off during booting using (fn+f7) keys ,
  ubuntu 16.0

[Touch-packages] [Bug 1605797] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all

[Raymond]

** Also affects: alsa-driver via
   http://www.virtualbox.org/ticket/15673
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1605797

Title:
  [ICH - Intel 82801AA-ICH, playback] No sound at all

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New ubuntu install on 2016-07-22; latest version.
  Running as virtualbox guest on latest OS X.
  Sound card recognized on mac, but not on guest.
  No sound in or out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 22 19:00:19 2016
  InstallationDate: Installed on 2016-07-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  Symptom_Type: No sound at all
  Title: [ICH - Intel 82801AA-ICH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1605797/+subscriptions

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

[Touch-packages] [Bug 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out

[Glenn Moloney]

Hi there. Is there any updates on this bug or if there's an updated
package is there anyway we can test / help? Cheers.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1542733

Title:
  Connect to Hidden Wi-Fi Network, "Connect" grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  1. Create a static, connection to hidden Wi-Fi connection using 
nm-connection-editor

  2. click nm-applet icon
  click "Connect to Hidden Wi-Fi Network"
  click pre-existing connection
  "Connect" is grayed out

  Work around is using terminal.
  nmcli c up id 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Feb  6 15:58:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.0.55  
metric 600
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  7c22db8e-2026-413b-86cd-0c796f177dd5  
802-3-ethernet   1454790964  Sat 06 Feb 2016 02:36:04 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/1  no  
--  -- -- 
   jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
802-11-wireless  1454795858  Sat 06 Feb 2016 03:57:38 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes 
wlp2s0  activated  /org/freedesktop/NetworkManager/ActiveConnection/4
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1580472] Re: No visible cursor after logging in

[Fabio]

No, to my memory I just experienced this using the nvidia drivers and
when enabling the nvidia card (I have an hybrid optimus card)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-

[Touch-packages] [Bug 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out

[florin]

There is another connected bug, not only for hidden wifi, but also for
regular wifi connections, they simply don't appear in the applet list
and the system does not auto connect as it should do.

This workaround I found yesterday works:

`sudo iwlist wlan0 scan`

where `wlan0` is the name of your wireless interface.

Doing this all wifi networks are back there and the system auto
connects.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1542733

Title:
  Connect to Hidden Wi-Fi Network, "Connect" grayed out

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Reproduce:
  1. Create a static, connection to hidden Wi-Fi connection using 
nm-connection-editor

  2. click nm-applet icon
  click "Connect to Hidden Wi-Fi Network"
  click pre-existing connection
  "Connect" is grayed out

  Work around is using terminal.
  nmcli c up id 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.0.4-0ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Feb  6 15:58:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.0.55  
metric 600
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH
   Wired connection 1  7c22db8e-2026-413b-86cd-0c796f177dd5  
802-3-ethernet   1454790964  Sat 06 Feb 2016 02:36:04 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/1  no  
--  -- -- 
   jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
802-11-wireless  1454795858  Sat 06 Feb 2016 03:57:38 PM CST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes 
wlp2s0  activated  /org/freedesktop/NetworkManager/ActiveConnection/4
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A  d57103a5-d3d7-4fb0-a2a0-469894e184ab  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp1s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

[biohazara]

I think this bug is fixed after 16.04.01. I no longer have this problem
on a fresh install of Ubuntu MATE 16.06.1 64-bit, as well as on doing an
upgrade from Ubuntu 14.04 64-bit to Ubuntu 16.06.1 64-bit.

However, my previous installations/upgrades of Ubuntu 16.04 64-bit still
have this problem even with the packages up to date.

My advice is to do a fresh install of a current 16.04.1 ISO or, in the
case of an upgrade, if you still have a backup of your 14.04
installation, try to use it to upgrade as of today and discard previous
attempts.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1434986

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.26 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Kabelnetzwerkverbindung 1  4a581685-6002-4401-a993-49aa649667eb  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions

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

[Touch-packages] [Bug 1605797] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all

[Raymond]

[ 6.559582] snd_intel8x0 :00:05.0: white list rate for 1028:0177 is
48000

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1605797

Title:
  [ICH - Intel 82801AA-ICH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New ubuntu install on 2016-07-22; latest version.
  Running as virtualbox guest on latest OS X.
  Sound card recognized on mac, but not on guest.
  No sound in or out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 22 19:00:19 2016
  InstallationDate: Installed on 2016-07-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  Symptom_Type: No sound at all
  Title: [ICH - Intel 82801AA-ICH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1605797/+subscriptions

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

[Touch-packages] [Bug 1605797] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all

[Raymond]

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/intel8x0.c?id=2b3b5485aa96d18b0025dfb2bc92c824dc81a780


ALSA: intel8x0: implement ac97_clock whitelist
The AC97 clock detection is not accurate in some cases. This patch adds
an initial whitelist for audio devices gathered from RedHat's bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?id=441087

As a side effect, white-listing might speedup kernel booting (AC97 clock
measuring code is not activated).

** Bug watch added: hacking a member #441087
   https://bugzilla.redhat.com/cgi-bin/bugreport.cgi?bug=441087

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1605797

Title:
  [ICH - Intel 82801AA-ICH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New ubuntu install on 2016-07-22; latest version.
  Running as virtualbox guest on latest OS X.
  Sound card recognized on mac, but not on guest.
  No sound in or out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 22 19:00:19 2016
  InstallationDate: Installed on 2016-07-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  Symptom_Type: No sound at all
  Title: [ICH - Intel 82801AA-ICH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1605797/+subscriptions

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

[Touch-packages] [Bug 1605960] Re: When sending an email the "From" field does not contain a valid adress

[Paul White]

** Package changed: xorg (Ubuntu) => kdepim (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1605960

Title:
  When sending an email the "From" field does not contain a valid adress

Status in kdepim package in Ubuntu:
  New

Bug description:
  I'm using kmail 5.1.3 (kubuntu 16.04 and kubuntu backports ppa).
  In kmail a gmail account is configured and is the default.
  When I create new mail only my name is shown in the "From" field: surename 
name <>
  When I reply a mail then "From" field is empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Jul 24 08:42:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-15 (8 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1489784] Re: No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10

[Bartosz Kosiorek]

** Changed in: canonical-devices-system-image
   Status: In Progress => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: Sturm Flut (sturmflut) => (unassigned)

** Description changed:

- Device Aquaris BQ45 as a buitin hardware FM tuner.
+ Device Aquaris BQ e45, e5, m10 as a buitin hardware FM tuner.
  On "factory" mode this device works.
  
  The device does not seem known by the kernel and there is no API to
  develop an FM radio application.
  
  The C code for the FM chip:
  https://github.com/Sturmflut/mtkfmcli
  Still missing Audio part.
- 
  
  Some more details from mailing list:
  
  We discussed this topic lengthily on the list some time ago :) It's
  not like we don't want to
  support FM radio, but the lack of a common Android HAL for FM radio
  access would force us to
  maintain an FM radio abstraction ourselves (more on that below). In
  addition, most of the device-specific
  radio apps require elevated privileges to run as they directly access
  the FM radio HW (not multiplexed by a system service).
  
  > For some reason Android doesn't have an FM radio API and leaves it up to
  > the manufacturers to come up with something. I've looked at several
  > devices, among them the bq Aquaris E4.5, and every SoC manufacturer
  > seems to have a different opinion on how to do it.
  >
  > Some ship no FM radio at all.
  >
  > Some seem to ship drivers for the Linux V4L subsystem.
  >
  > MediaTek (Aquaris E4.5 and E5) decided to implement custom kernel
  > drivers with a custom character device (/dev/fm) and custom ioctl
  > commands. There seem to be userspace libraries (libfm*) including a JNI
  > wrapper in /system/lib of the Android container on our Ubuntu phones.
  >
  > Because there is no standard API, there are no generic FM radio apps for
  > Android, and pretty much every manufacturer ships a custom app for his
  > own SoC(s) and/or device(s).
  >
  >
  > I'll try to come up with a piece of C code for the command line that can
  > at least initialize and tune the FM radio on the Aquaris E4.5 and E5.
  > The long-term goal could be to turn this into plugins for an extended
  > media-hub.
  >
  
  If you are interested in helping to enable the functionality, the
  correct chain for integrating the feature would be:
  
  [1.] Add a (potentially limited) API to lp:platform-api, that exposes
  a simple common C interface to the Ubuntu side.
  [2.] Provide an implementation of the API in platform-api/android (see
  
http://bazaar.launchpad.net/~phablet-team/platform-api/trunk/files/head:/android/)
  [2.1] Provide a dummy fallback implementation for devices that do not
  support FM radio of any kind.
  [3.] Expose the respective hardware functionality to media-hub.
  Multiple ways are possible, but we would need to significantly adjust
  the interfaces
  to support fm radio semantics (switching stations, rds, automatic scans etc.)
  [4.] Adjust Qt's radio abstraction and come up with a Ubuntu Touch
  specific backend implementation, that either:
    [4.1] Leverages the API in [1.] directly (would require any app to
  have special privileges in accessing the system).
    [4.2] Leverages the API in [3.] (which is the clean way of
  integration FM radio support).
  
  For starters, [1.], [2.], [2.1] and [4.1] should be good enough to get
  started.
  
  Cheers,

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1489784

Title:
  No access to the FM tuner/radio on Aquaris Bq e4.5, e5 and m10

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtmultimedia package in Ubuntu:
  Confirmed

Bug description:
  Device Aquaris BQ e45, e5, m10 as a buitin hardware FM tuner.
  On "factory" mode this device works.

  The device does not seem known by the kernel and there is no API to
  develop an FM radio application.

  The C code for the FM chip:
  https://github.com/Sturmflut/mtkfmcli
  Still missing Audio part.

  Some more details from mailing list:

  We discussed this topic lengthily on the list some time ago :) It's
  not like we don't want to
  support FM radio, but the lack of a common Android HAL for FM radio
  access would force us to
  maintain an FM radio abstraction ourselves (more on that below). In
  addition, most of the device-specific
  radio apps require elevated privileges to run as they directly access
  the FM radio HW (not multiplexed by a system service).

  > For some reason Android doesn't have an FM radio API and leaves it up to
  > the manufacturers to come up with something. I've looked at several
  > devices, among them the bq Aquaris E4.5, and every SoC manufacturer
  > seems to have a different opinion on how to do it.
  >
  > Some ship no FM radio at all.
  >
  > Some seem to ship drivers for the Linux V4L subsyste