[Desktop-packages] [Bug 1562219] Re: xinit will not work as non-root.

[Aaron Peromsik]

Never mind: if I am reading correctly it seems those commits I mentioned
in #10 are already included upstream and in Ubuntu as well.

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

Title:
  xinit will not work as non-root.

Status in xinit package in Ubuntu:
  Confirmed

Bug description:
  When attempting to run xinit or startx after upgrading from 14.04 to
  16.04 it will not work.  There seems to be some sort of permission
  issue.  I have seen another person with this issue as well here:

  http://askubuntu.com/questions/749370/ubuntu-16-04-xf86openconsole-
  cannot-open-virtual-console-2?newreg=ba376d7a182d44608ed4675346b1ed74

  An example is when attempting to launch kodi, which worked prior to
  the upgrade:

  xinit /usr/bin/kodi --standalone -- -nocursor :0

  
  X.Org X Server 1.18.1
  Release Date: 2016-02-08
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.13.0-79-generic x86_64 Ubuntu
  Current Operating System: Linux hostname 4.4.0-15-generic #31-Ubuntu SMP Fri 
Mar 18 19:08:31 UTC 2016 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text
  Build Date: 11 March 2016  07:43:21AM
  xorg-server 2:1.18.1-1ubuntu4 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/home/arch/.local/share/xorg/Xorg.0.log", Time: Fri Mar 25 
20:14:07 2016
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  (EE) 
  Fatal server error:
  (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at 
"/home/arch/.local/share/xorg/Xorg.0.log" for additional information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  xinit: giving up
  xinit: unable to connect to X server: Connection refused

  
  I have tried numerous workarounds including reinstalling xorg, removing all 
x-related files in my profile, and creating a new user.  Unfortunately none of 
these worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xinit 1.3.4-3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 25 20:14:18 2016
  DistUpgraded: 2016-03-25 09:16:37,728 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: oem-audio-hda-daily, 0.201412181801~ubuntu14.04.1, 
3.13.0-83-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/xinit
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1849:0402]
  InstallationDate: Installed on 2014-12-14 (467 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text
  SourcePackage: xinit
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (0 days ago)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: H97M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4
  version.xserver-xorg-input-evdev: 

[Desktop-packages] [Bug 1583881] Re: package texlive-latex-base-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in p

[Alberto Salvia Novella]

** Changed in: texlive-base (Ubuntu)
   Importance: Undecided => High

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-base in Ubuntu.
https://bugs.launchpad.net/bugs/1583881

Title:
  package texlive-latex-base-doc (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/doc/texlive-
  doc/latex/url/url.tex.gz', which is also in package texlive-latex-
  recommended-doc 2013.20140215-1

Status in One Hundred Papercuts:
  Confirmed
Status in texlive-base package in Ubuntu:
  Confirmed

Bug description:
  This is occurred after upgrading to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: texlive-latex-base-doc (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 19 11:06:01 2016
  ErrorMessage: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
  InstallationDate: Installed on 2015-12-26 (145 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: texlive-base
  Title: package texlive-latex-base-doc (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/doc/texlive-doc/latex/url/url.tex.gz', which is also in package 
texlive-latex-recommended-doc 2013.20140215-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1585476] Re: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to install/upgrade: a tentar sobre-escrever '/etc/sane.d/hp.conf', que também está no pacote libsane:i386

[Alberto Salvia Novella]

** Changed in: sane-backends (Ubuntu)
   Importance: Undecided => High

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1585476

Title:
  package libsane-common 1.0.25+git20150528-1ubuntu2 failed to
  install/upgrade: a tentar sobre-escrever '/etc/sane.d/hp.conf', que
  também está no pacote libsane:i386 1.0.23-3ubuntu3.1

Status in One Hundred Papercuts:
  Confirmed
Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  This error apear when updating ubuntu 14.04 to 16.04.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsane-common 1.0.25+git20150528-1ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-60.67~14.04.1-generic 3.19.8-ckt21
  Uname: Linux 3.19.0-60-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  Date: Wed May 25 06:32:45 2016
  DuplicateSignature: package:libsane-common:1.0.25+git20150528-1ubuntu2:a 
tentar sobre-escrever '/etc/sane.d/hp.conf', que também está no pacote 
libsane:i386 1.0.23-3ubuntu3.1
  ErrorMessage: a tentar sobre-escrever '/etc/sane.d/hp.conf', que também está 
no pacote libsane:i386 1.0.23-3ubuntu3.1
  InstallationDate: Installed on 2016-04-18 (36 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: sane-backends
  Title: package libsane-common 1.0.25+git20150528-1ubuntu2 failed to 
install/upgrade: a tentar sobre-escrever '/etc/sane.d/hp.conf', que também está 
no pacote libsane:i386 1.0.23-3ubuntu3.1
  UpgradeStatus: Upgraded to xenial on 2016-05-22 (2 days ago)
  modified.conffile..etc.sane.d.epsonds.conf: [deleted]

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

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

[Desktop-packages] [Bug 1577377] Re: package libgdk-pixbuf2.0-0:amd64 2.32.2-1ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Alberto Salvia Novella]

** Changed in: gdk-pixbuf (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1577377

Title:
  package libgdk-pixbuf2.0-0:amd64 2.32.2-1ubuntu1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  occured since upgrading to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgdk-pixbuf2.0-0:amd64 2.32.2-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
  Date: Sat Apr 30 23:58:12 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-01-30 (93 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf2.0-0:amd64 2.32.2-1ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1577377/+subscriptions

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

[Desktop-packages] [Bug 1598519] Re: regression: page scrolling jumps to top of page spontaneously

[Alberto Salvia Novella]

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

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Changed in: webkit (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  regression: page scrolling jumps to top of page spontaneously

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in webkit package in Ubuntu:
  Confirmed

Bug description:
  I switched to chromium-browser from Google Chrome when, 1-2 months
  ago, Chrome began to misbehave on all pages. It spontaneously jumped
  to the top of the page when I continue scrolling downwards (using a
  touchpad).

   As of a July 1 update to
  chromium-browser:amd64 (50.0.2661.102-0ubuntu0.16.04.1.1237, 
51.0.2704.79-0ubuntu0.16.04.1.1242)

  chromium-browser now has the same bug! Chris Down, in comments below,
  says the bug is affecting most webkit-based apps.

  He and I are both on higher-end Lenovo thinkpads (T450s, T460s), (and
  I believe this also affects T410s -- to confirm)).

  To reproduce this, I scroll half-way down a page (using a touchpad?)
  and then click on something (e.g. blank space, which has no effect, or
  ctrl-click on a link to open it in a new tab) with a mouse button.
  Next, as soon as I touch the touchpad to continue scrolling, the page
  jumps to the top.

  Makes browsing near impossible. Very frustrating to have this bug
  arrive at this browser after I already left Chrome (whose latest
  version on Ubuntu also still has this bug) to avoid it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 51.0.2704.79-0ubuntu0.16.04.1.1242
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-DP-1:
   edid-base64:
   dpms: Off
   modes:
   enabled: disabled
   status: disconnected
  DRM.card0-DP-2:
   edid-base64: 
AP///wAebYhO5woAAAoSAQNqLx546mBFplZKnCUSUFSna4CVD5UAgYCBQHFPAQEBAQEBfC6QoGAaHkAwIDYA2igRAAAaITmQMGIaJ0BosDYA2igRAAAc/QA4Sx5TDwAKICAgICAg/ABXMjA1MgogICAgICAgABc=
   dpms: On
   modes: 1680x1050 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 
1152x864 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 
720x400
   enabled: enabled
   status: connected
  DRM.card0-HDMI-A-1:
   edid-base64:
   dpms: Off
   modes:
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64:
   dpms: Off
   modes:
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo=
   dpms: On
   modes: 1920x1080
   enabled: enabled
   status: connected
  Date: Sat Jul  2 21:54:54 2016
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:

  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-02-12 (141 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Load-Avg-1min: 0.72
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=ea2fb511-8d62-4b96-bdaa-4b3f7bf79cc6 ro noprompt quiet splash 
vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (39 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go 

[Desktop-packages] [Bug 1441296] Re: Nautilus invisible focused item when selecting files with Ctrl and arrow keys

[Alberto Salvia Novella]

** Changed in: light-themes (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to light-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1441296

Title:
  Nautilus invisible focused item when selecting files with Ctrl and
  arrow keys

Status in Ubuntu theme:
  Confirmed
Status in light-themes package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 15.04 beta2 I noticed that selecting files with
  Ctrl and the arrow keys in Nautilus became more difficult since the
  active item had no decorations. I'm sure before there was some sort of
  dashed line around the active item's name, so this may be a
  regression.

  I have searched for any other bug report on this, or any other person
  complaining about it, without success. I tried using the guest account
  to confirm it wasn't a previous configuration on my regular account,
  and the issue is also present. Maybe it is uncommon for people to
  select items in nautilus with the keyboard arrows?

  I fixed it on my system for Ambiance by adding a dashed line
  decoration to

  /usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css

  NautilusWindow * {
  -GtkPaned-handle-size: 1;
  outline-color: @selected_bg_color;
  outline-style: dashed;
  outline-width: 1px;
  outline-radius: 4px;
  outline-offset: -1px;
  }

  This may need to go in other selector properties, but it worked like
  this and I couldn't make it to work on any other selector.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1441296/+subscriptions

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

[Desktop-packages] [Bug 1553211] Re: Ubuntu should provide a default graphical method to install technical packages (plugins, kernels, terminal apps)

[Alberto Salvia Novella]

** Changed in: ubuntu-gnome-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-gnome-meta (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1553211

Title:
  Ubuntu should provide a default graphical method to install technical
  packages (plugins, kernels, terminal apps)

Status in GNOME Software:
  Invalid
Status in gnome-software package in Ubuntu:
  Won't Fix
Status in ubuntu-gnome-meta package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 will be useless for "normal" people if they can't find every 
software package as they did before.
  To force users to use gnome-software will be a regression!

  Examples:

  In old Software Center, you could add gimp plug-ins (plug-ins are recommends 
and suggests packages of gimp) by going in gimp description and check the 
plug-ins you want!
  In old Software Center, you could install another version of linux kernel by 
typing "linux" then click at bottom left to show the packages.

  Now, they have to use apt-get or install synaptic!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar  4 15:06:20 2016
  InstallationDate: Installed on 2016-01-07 (57 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160105)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1553211/+subscriptions

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

[Desktop-packages] [Bug 1600086] Re: package libxdamage-dev (not installed) failed to install/upgrade: no package named `libxdamage-dev' is installed, cannot configure

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libxdamage-dev (not installed) failed to install/upgrade: no
  package named `libxdamage-dev' is installed, cannot configure

Status in libxdamage package in Ubuntu:
  New

Bug description:
  happened right after a reboot

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libxdamage-dev (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  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
  Date: Thu Jul  7 22:02:44 2016
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:libxdamage-dev:(not installed):no package named 
`libxdamage-dev' is installed, cannot configure
  ErrorMessage: no package named `libxdamage-dev' is installed, cannot configure
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0641]
  InstallationDate: Installed on 2016-03-08 (121 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5448
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic 
root=UUID=838e0ab3-bb20-413d-8673-32a8616985e6 ro locale=en_US quiet splash 
pcie_aspm=default radeon.modeset=0 nouveau.modeset=0 
video.use_native_backlight=1 vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: libxdamage
  Title: package libxdamage-dev (not installed) failed to install/upgrade: no 
package named `libxdamage-dev' is installed, cannot configure
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 02VKX1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/27/2015:svnDellInc.:pnInspiron5448:pvrA05:rvnDellInc.:rn02VKX1:rvrA02:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 5448
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Jul  7 23:42:10 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1519 
   vendor BOE
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Desktop-packages] [Bug 1600086] [NEW] package libxdamage-dev (not installed) failed to install/upgrade: no package named `libxdamage-dev' is installed, cannot configure

[Guilherme]

Public bug reported:

happened right after a reboot

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libxdamage-dev (not installed)
ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
Uname: Linux 3.13.0-91-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
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
Date: Thu Jul  7 22:02:44 2016
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DistroCodename: trusty
DistroVariant: ubuntu
DuplicateSignature: package:libxdamage-dev:(not installed):no package named 
`libxdamage-dev' is installed, cannot configure
ErrorMessage: no package named `libxdamage-dev' is installed, cannot configure
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0641]
InstallationDate: Installed on 2016-03-08 (121 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
MachineType: Dell Inc. Inspiron 5448
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic 
root=UUID=838e0ab3-bb20-413d-8673-32a8616985e6 ro locale=en_US quiet splash 
pcie_aspm=default radeon.modeset=0 nouveau.modeset=0 
video.use_native_backlight=1 vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: libxdamage
Title: package libxdamage-dev (not installed) failed to install/upgrade: no 
package named `libxdamage-dev' is installed, cannot configure
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/27/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 02VKX1
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A05
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/27/2015:svnDellInc.:pnInspiron5448:pvrA05:rvnDellInc.:rn02VKX1:rvrA02:cvnDellInc.:ct8:cvrA05:
dmi.product.name: Inspiron 5448
dmi.product.version: A05
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Jul  7 23:42:10 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1519 
 vendor BOE
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: amd64 apport-package compiz-0.9 trusty ubuntu

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

Title:
  package libxdamage-dev (not installed) failed to install/upgrade: no
  package named `libxdamage-dev' is installed, cannot configure

Status in libxdamage package in Ubuntu:
  New

Bug description:
  happened right after a reboot

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libxdamage-dev (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.21
  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
  Date: Thu Jul  7 22:02:44 2016
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: package:libxdamage-dev:(not installed):no package named 
`libxdamage-dev' is installed, cannot configure
  ErrorMessage: no package named `libxdamage-dev' is installed, cannot configure
  GraphicsCard:
   Intel Corporation Broadwell-U 

[Desktop-packages] [Bug 1581913] Re: touchpad not working or recognized (ASUS UX305)

[Christopher M. Penalver]

Kelley, as per https://www.asus.com/us/Notebooks/ASUS-ZenBook-
UX305CA/HelpDesk_Download/ an update to your computer's buggy, insecure,
and outdated BIOS is available (300). When you update to this following
https://help.ubuntu.com/community/BIOSUpdate how does this improve the
situation?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your help.

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

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

Title:
  touchpad not working or recognized (ASUS UX305)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  (8/7/16) My touchpad was once working and now it has stopped again.
  I'm still using Ubuntu 16.04 LTS

  **Update: I have since installed version 16.04 of Ubuntu and this is
  what my terminal brings up. I have no idea what this means considering
  I am currently using Ubuntu 16.04 LTS as I type this. The OS is
  working fine as far as I can tell. However, my touchpad is now
  working. Going forward for the Linux community, it is my
  recommendation that anyone with an ASUS Zenbook UX305 upgrade to 16.04
  LTS in order to avoid the bug found in 14.04 so their touchpads
  actually work with the Ubuntu OS.

  kelley-rose@Zenbook:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kelley-rose@Zenbook:~$ /proc/bus/input/devices
  bash: /proc/bus/input/devices: Permission denied
  kelley-rose@Zenbook:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  kelley-rose@Zenbook:~$

  -

  kelley-rose@Zenbook:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kelley-rose@Zenbook:~$

  kelley-rose@Zenbook:~$ lsb_release -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04

  My apple mouse works for both Windows 10 and Ubuntu, but the trackpad
  only works in Windows.

  kelley-rose@Zenbook:~$ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=064e Product=9700 Version=0101
  N: Name="USB2.0 UVC HD Webcam"
  P: Phys=usb-:00:14.0-5/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input4
  U: Uniq=
  H: Handlers=kbd event4
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  U: Uniq=
  H: Handlers=kbd event5
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: Sysfs=/devices/platform/asus-nb-wmi/input/input6
  U: Uniq=
  H: Handlers=rfkill kbd event6
  B: PROP=0
  B: EV=100013
  B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
  B: MSC=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7
  U: Uniq=
  H: Handlers=event7
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= 

[Desktop-packages] [Bug 1581913] Re: touchpad not working or recognized (ASUS UX305)

[Kelley]

** Description changed:

+ (8/7/16) My touchpad was once working and now it has stopped again. I'm
+ still using Ubuntu 16.04 LTS
+ 
  **Update: I have since installed version 16.04 of Ubuntu and this is
  what my terminal brings up. I have no idea what this means considering I
  am currently using Ubuntu 16.04 LTS as I type this. The OS is working
  fine as far as I can tell. However, my touchpad is now working. Going
  forward for the Linux community, it is my recommendation that anyone
  with an ASUS Zenbook UX305 upgrade to 16.04 LTS in order to avoid the
  bug found in 14.04 so their touchpads actually work with the Ubuntu OS.
  
  kelley-rose@Zenbook:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kelley-rose@Zenbook:~$ /proc/bus/input/devices
  bash: /proc/bus/input/devices: Permission denied
  kelley-rose@Zenbook:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
- kelley-rose@Zenbook:~$ 
+ kelley-rose@Zenbook:~$
  
  -
  
  kelley-rose@Zenbook:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  kelley-rose@Zenbook:~$
  
  kelley-rose@Zenbook:~$ lsb_release -rd
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  
  My apple mouse works for both Windows 10 and Ubuntu, but the trackpad
  only works in Windows.
  
  kelley-rose@Zenbook:~$ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0
  B: PROP=0
  B: EV=21
  B: SW=1
  
  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0
  
  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2
  B: PROP=0
  B: EV=3
  B: KEY=10 0
  
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7
  
  I: Bus=0003 Vendor=064e Product=9700 Version=0101
  N: Name="USB2.0 UVC HD Webcam"
  P: Phys=usb-:00:14.0-5/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-5/1-5:1.0/input/input4
  U: Uniq=
  H: Handlers=kbd event4
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0
  
  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
  U: Uniq=
  H: Handlers=kbd event5
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0
  
  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: Sysfs=/devices/platform/asus-nb-wmi/input/input6
  U: Uniq=
  H: Handlers=rfkill kbd event6
  B: PROP=0
  B: EV=100013
  B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
  B: MSC=10
  
  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7
  U: Uniq=
  H: Handlers=event7
  B: PROP=0
  B: EV=21
  B: SW=4
  
  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8
  U: Uniq=
  H: Handlers=event8
  B: PROP=0
  B: EV=21
  B: SW=140
  
  I: Bus=0003 Vendor=05ac Product=0304 Version=0110
  N: Name="Primax Electronics Apple Optical USB Mouse"
  P: Phys=usb-:00:14.0-1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:05AC:0304.0004/input/input12
  U: Uniq=
  H: Handlers=mouse0 event9
  B: PROP=0
  B: EV=100017
  B: KEY=f 0 0 0 0
  B: REL=143
  B: MSC=10
  
  kelley-rose@Zenbook:~$
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-59.65~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  .tmp.unity.support.test.0:
  
  ApportVersion: 2.14.1-0ubuntu3.19
  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
  Date: Sat May 14 22:17:15 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated 

[Desktop-packages] [Bug 1578011] Re: Laptop sometimes doesn't detect external monitor when docked

[vik]

I can try to update the BIOS, but given that the BIOS release notes (see
below) don't mention anything regarding this, it's not likely to fix
anything. The issue disappeared for a while, but has returned in the
past month or so; I'm guess a kernel driver update fixed it, then
regressed.

BIOS 1.29 release notes:
[Important updates]
  Nothing.

[New functions or enhancements]
-  Updated Realtek v2.06 PXE rom and v2.016 UNDI driver.

[Problem fixes]
  Nothing.

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

Title:
  Laptop sometimes doesn't detect external monitor when docked

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when
  docked with a Onelink Pro dock. Problem has also occurred on a non-Pro
  OneLink dock.

  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
  Architecture: amd64
  BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 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
  Date: Wed May  4 11:47:20 2016
  DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217]
  InstallationDate: Installed on 2015-12-02 (153 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20C0S1CWAU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago)
  dmi.bios.date: 01/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GQET48WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C0S1CWAU
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C0S1CWAU
  dmi.product.version: ThinkPad S1 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  4 08:27:55 2016
  xserver.configfile: default
  xserver.errors:
   Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
   Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1079
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1579182] Re: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A

[Christopher M. Penalver]

Marcelo Fernandez, to see if this fixed in Intel upstream, could you
please test http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
nightly/ and advise to the results?

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

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

Title:
  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 upgraded from Ubuntu 14.04 on a Dell Inspiron 14z, w
  /Intel-ATI hybrid graphics (but DIS card is OFF through
  vgaswitcheroo).

  Just like bug no. #1525390 [1], Chrome shows some artifacts randomly
  and I have the same kernel trace but from 10 days ago (I use this
  system everyday and it didn't happened since then).

  [1] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525390

  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
  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
  Date: Fri May  6 15:17:08 2016
  DistUpgraded: 2016-04-25 18:04:08,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.20, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057f]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2013-08-12 (997 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmDisplayLog:
   [dix] EventToCore: Not implemented yet 
   [dix] EventToCore: Not implemented yet
  MachineType: Dell Inc. Inspiron 5423
  ProcEnviron:
   LANGUAGE=es_AR:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (10 days ago)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05WDP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/18/2013:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn05WDP7:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May  6 09:34:55 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9020 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager

[Alexander Borovsky]

This modem require configuration loaded in order to work. One of the
options is loading Windows, waiting while it configure modem and then
restart.

Other option is described here: https://abarouski.blogspot.com/2016/07
/configuring-hp-lt4120-in-linux-as-i.html

This solution not yet in upstream (but I'm working on it).

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

Title:
  HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-
  manager

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  USB modem not recognized by network-manager. Modem information in
  attached

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  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
  Date: Mon Apr 25 11:14:04 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.106.36.1 dev wlp2s0  proto static  metric 600 
   1.1.1.1 via 10.106.36.1 dev wlp2s0  proto dhcp  metric 600 
   10.106.36.0/22 dev wlp2s0  proto kernel  scope link  src 10.106.39.123  
metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH   

   wlp2s0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/1  IQORAMS_REPAIR  
3b1e13ff-f9c9-4a49-a576-465bc2713e21  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enxb2e41f35ffe1  ethernet  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   enp0s31f6ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/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/ubuntu/+source/network-manager/+bug/1574582/+subscriptions

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

[Desktop-packages] [Bug 1600057] [NEW] Sender Display Name with comm appears as two senders

[Link Porterfield]

Public bug reported:

Symptom sounds similar to that described in Bug 1166206
https://bugzilla.mozilla.org/show_bug.cgi?id=1166206

When email sender display name contains a comma, it appears as if it
were sent from two senders.

Example:

Message source: From: Something, Something Darkside 

Thunderbird: From Something <>, Something Darkside 

I had 38.8.0 from trusty-updates installed when I noticed this problem
and added the thunderbird-next PPA to see if it had been fixed. The
symptom still persists.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: thunderbird 1:45.2~b1+build2-0ubuntu0.14.04.1 [origin: 
LP-PPA-mozillateam-thunderbird-next]
ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
Uname: Linux 3.13.0-91-generic x86_64
NonfreeKernelModules: wl nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  artgravity   3427 F pulseaudio
 /dev/snd/controlC0:  artgravity   3427 F pulseaudio
BuildID: 20160602231857
Channel: beta
CurrentDesktop: Unity
Date: Thu Jul  7 17:56:32 2016
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2013-07-27 (1076 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
 default via 10.26.0.1 dev wlan0  proto static 
 10.26.0.0/24 dev wlan0  proto kernel  scope link  src 10.26.0.141  metric 9 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
Locales: extensions.sqlite corrupt or missing
Profiles: Profile0 (Default) - LastVersion=45.2/20160602231857
RelatedPackageVersions:
 totem-mozilla 3.10.1-1ubuntu4
 rhythmbox-mozilla 3.0.2-0ubuntu2
 icedtea-7-plugin  1.5.3-0ubuntu0.14.04.1
 google-talkplugin 5.41.3.0-1
 adobe-flashplugin 1:20160616.1-0ubuntu0.14.04.1
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to trusty on 2014-04-19 (810 days ago)
dmi.bios.date: 12/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0K42JR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6410
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug beta-channel third-party-packages trusty

** Attachment removed: "IpAddr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1600057/+attachment/4697203/+files/IpAddr.txt

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

Title:
  Sender Display Name with comm appears as two senders

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Symptom sounds similar to that described in Bug 1166206
  https://bugzilla.mozilla.org/show_bug.cgi?id=1166206

  When email sender display name contains a comma, it appears as if it
  were sent from two senders.

  Example:

  Message source: From: Something, Something Darkside 

  Thunderbird: From Something <>, Something Darkside 

  I had 38.8.0 from trusty-updates installed when I noticed this problem
  and added the thunderbird-next PPA to see if it had been fixed. The
  symptom still persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:45.2~b1+build2-0ubuntu0.14.04.1 [origin: 
LP-PPA-mozillateam-thunderbird-next]
  ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-91-generic x86_64
  NonfreeKernelModules: wl nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  artgravity   3427 F pulseaudio
   /dev/snd/controlC0:  artgravity   3427 F pulseaudio
  BuildID: 20160602231857
  Channel: beta
  CurrentDesktop: Unity
  Date: Thu Jul  7 17:56:32 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2013-07-27 (1076 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 10.26.0.1 dev wlan0  proto static 
   

[Desktop-packages] [Bug 1599874] Re: no rear sound creative sound blaster Z ssid: 1102:0023

[Olcay Korkmaz]

Hi,

as windows and freebsd did work with generic driver so I disabled ca0132 
enabled pure generic module (no fancy patch_ca0132.c)
here is generic driver's alsa-info and details

pin configs detected correctly and same as windows/freebsd pinconfigs
but ca0132 detects wrong pin numbers

headphone(front) and rear jack sensation works with ubuntu-sound-
settings but no sound from both sides

** Attachment added: "generic driver"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1599874/+attachment/4697197/+files/alsa-info-generic.txt

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

Title:
   no rear sound creative sound blaster Z ssid: 1102:0023

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

Bug description:
  Hi,

  it's long standing bug we can't use Z series cards properly on linux 
  only front panel work 
  rest of ports are not working

  I extracted latest firmware from windows driver but no luck 
  here are extra details from windows and freebsd drivers both are works fine

  freebsd pin configs;
  hdaa0: Patched pins configuration:
  hdaa0: nid   0xas seq device   conn  jackloccolor   misc
  hdaa0: 11 410140f0 15 0  Line-out  None  1/8 Rear   Green   0 DISA
  hdaa0: 12 014520f0 15 0  SPDIF-out Jack  Optical Rear   Grey0
  hdaa0: 13 010170f0 15 0  Line-out  Jack  1/8 Rear   Yellow  0
  hdaa0: 14 01c510f0 15 0  SPDIF-in  Jack  Optical Rear   Black   0
  hdaa0: 15 412000f0 15 0  HeadphonesNone  Unknown Rear   Unknown 0 DISA
  hdaa0: 16 022140f0 15 0  HeadphonesJack  1/8 Front  Green   0
  hdaa0: 17 418120f0 15 0  Line-in   None  1/8 Rear   Grey0 DISA
  hdaa0: 18 01a190f0 15 0  Mic   Jack  1/8 Rear   Pink0
  hdaa0: 19 50d000f0 15 0  Digital-inNone  Unknown Internal   Unknown 0 DISA
  hdaa0: 24 50f0 15 0  Line-out  None  Unknown Internal   Unknown 0 DISA

  pin configs from windows driver
  NID: 11
  Node: 0x0b
  Pin: 0x410140f0
  Verb 00B71CF0 00B71D40 00B71E01 00B71F41 

  NID: 12
  Node: 0x0c
  Pin: 0x014520f0
  Verb 00C71CF0 00C71D20 00C71E45 00C71F01 

  NID: 13
  Node: 0x0d
  Pin: 0x010171f0
  Verb 00D71CF0 00D71D71 00D71E01 00D71F01 

  NID: 14
  Node: 0x0e
  Pin: 0x01c510f0
  Verb 00E71CF0 00E71D10 00E71EC5 00E71F01 

  NID: 15
  Node: 0x0f
  Pin: 0x412000f0
  Verb 00F71CF0 00F71D00 00F71E20 00F71F41 

  NID: 16
  Node: 0x10
  Pin: 0x022140f0
  Verb 01071CF0 01071D40 01071E21 01071F02 

  NID: 17
  Node: 0x11
  Pin: 0x418120f0
  Verb 01171CF0 01171D20 01171E81 01171F41 

  NID: 18
  Node:0x12
  Pin:0x01a190f0
  Verb 01271CF0 01271D90 01271EA1 01271F01 

  NID: 19
  Node:0x13
  Pin:0x50d000f0
  Verb 01371CF0 01371D00 01371ED0 01371F50 

  NID: 24
  Node:0x18
  Pin:0x50f0
  Verb 01871CF0 01871D00 01871E00 01871F50

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olci   1701 F pulseaudio
   /dev/snd/controlC0:  olci   1701 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  7 16:48:52 2016
  InstallationDate: Installed on 2016-06-25 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 7 (MS-7916)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd02/16/2016:svnMSI:pnMS-7916:pvr1.0:rvnMSI:rnZ97GAMING7(MS-7916):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7916
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1600053] [NEW] system scaling factor ignored for page rendering

[Donald Pellegrino]

Public bug reported:

Mozilla Firefox has a layout.css.dpi preference with a default value of
-1. This preference is documented as:

"Use the host system’s logical resolution or 96, whichever is greater,
for interpreting dimensions specified in absolute units. (Default)" as
per http://kb.mozillazine.org/Layout.css.dpi

On Linux, the value of -1 should cause Firefox to use the GTK scaling
factor. Additional details are available in Mozilla Bug 712898
(https://bugzilla.mozilla.org/show_bug.cgi?id=712898).

Unity System Settings -> Displays includes a slider for "Scale for menu
and title bars." When set to 1.12 instead of the default value of 1, the
text on all GTK dialogs including body text, menus, and title bars are
all scaled. In addition, the text in Terminal is scaled. In Firefox, the
text in about:preferences is scaled consistent with the elements of
other applications. However, the page rendering is not scaled. Page
scaling seems to be unaffected by the system setting.

The expected behavior is that the scale value set in System Settings ->
Displays should affect Firefox page rendering when the Firefox
layout.css.dpi preference has its default value of -1.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 47.0+build3-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  donald 1749 F pulseaudio
BuildID: 20160606113944
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Jul  7 19:26:57 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/firefox/firefox
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
IpRoute:
 default via 192.168.1.1 dev wlp2s0  proto static  metric 600 
 169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
 192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.240  metric 
600
LocalLibraries: 
/home/donald/.mozilla/firefox/438tbwje.default/extensions/supp...@lastpass.com/platform/Linux_x86_64-gcc3/components/lpxpcom_x86_64.so
Locales: extensions.sqlite corrupt or missing
PrefSources:
 prefs.js
 [Profile]/extensions/supp...@lastpass.com/defaults/preferences/defaults.js
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=47.0/20160606113944 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.06RS76
dmi.board.asset.tag: Tag 12345
dmi.board.name: Lemur
dmi.board.vendor: System76, Inc.
dmi.board.version: lemu6
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
dmi.product.name: Lemur
dmi.product.version: lemu6
dmi.sys.vendor: System76, Inc.

** Affects: firefox
 Importance: Undecided
 Status: New

** Affects: unity-control-center
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug local-libs xenial

** Also affects: firefox
   Importance: Undecided
   Status: New

** Also affects: unity-control-center
   Importance: Undecided
   Status: New

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

Title:
  system scaling factor ignored for page rendering

Status in Mozilla Firefox:
  New
Status in Unity Control Center:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Mozilla Firefox has a layout.css.dpi preference with a default value
  of -1. This preference is documented as:

  "Use the host system’s logical resolution or 96, whichever is greater,
  for interpreting dimensions specified in absolute units. (Default)" as
  per http://kb.mozillazine.org/Layout.css.dpi

  On Linux, the value of -1 should cause Firefox to use the GTK scaling
  factor. Additional details are available in Mozilla Bug 712898
  (https://bugzilla.mozilla.org/show_bug.cgi?id=712898).

  Unity System Settings -> Displays includes a slider for "Scale for
  menu and title bars." When set to 1.12 instead of the default value of
  1, the text on all GTK dialogs including body text, menus, and title
  bars are all scaled. In addition, the text in Terminal is scaled. In
  

[Desktop-packages] [Bug 1589056] Re: HDMI does not work

[Christopher M. Penalver]

Jarno Suni, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel by following
the instructions verbatim at http://nouveau.freedesktop.org/wiki/Bugs/ ?

Please provide a direct URL to your bug report once you have made it so
that it may be tracked.

Thank you for your help.

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

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

Title:
  HDMI does not work

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  xrandr displays "HDMI-1 disconnected (normal left inverted right x
  axis y axis)" even if it is connected using a HDMI cable to a Samsung
  monitor (model S27B350H) that has both HDMI and VGA connectors.

  WORKAROUND: Use the Nvidia proprietary driver.

  Graphics by lspci -vvv:
  01:00.0 VGA compatible controller: NVIDIA Corporation G84GLM [Quadro FX 570M] 
(rev a1) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device 30c5
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
   Capabilities: 
   Kernel driver in use: nouveau

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   root: clean, 247512/1281120 files, 1867600/512 blocks
   [FAILED] Failed to start Automatically refresh installed snaps.
   See 'systemctl status snapd.refresh.service' for details.
   [  OK  ] Started Authenticate and Authorize Users to Run 
Privileged Tasks.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: 2016-06-24 18:11:48,939 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2015-11-21 (228 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (12 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  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/1589056/+subscriptions

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

[Desktop-packages] [Bug 1579182] Re: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A

[Marcelo Fernandez]

Still don't know what triggers the error.

The last error log appeared just after I've unlocked the lightdm screen
lock. I'm using two monitors: the one in my laptop and an external one
(FullHD resolution) plugged through HDMI, nothing unusual.

Regards

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

Title:
  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 upgraded from Ubuntu 14.04 on a Dell Inspiron 14z, w
  /Intel-ATI hybrid graphics (but DIS card is OFF through
  vgaswitcheroo).

  Just like bug no. #1525390 [1], Chrome shows some artifacts randomly
  and I have the same kernel trace but from 10 days ago (I use this
  system everyday and it didn't happened since then).

  [1] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525390

  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
  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
  Date: Fri May  6 15:17:08 2016
  DistUpgraded: 2016-04-25 18:04:08,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.20, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057f]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2013-08-12 (997 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmDisplayLog:
   [dix] EventToCore: Not implemented yet 
   [dix] EventToCore: Not implemented yet
  MachineType: Dell Inc. Inspiron 5423
  ProcEnviron:
   LANGUAGE=es_AR:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (10 days ago)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05WDP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/18/2013:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn05WDP7:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May  6 09:34:55 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9020 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1579182] Re: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A

[Marcelo Fernandez]

Ok, today I have this error twice with 4.7.0-040700rc5-generic kernel:

Jul  7 10:01:24 marcelo-notebook kernel: [ 5823.037058] 
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B 
(start=349135 end=349136) time 293 us, min 1073, max 1079, scanline start 1046, 
end 1080
Jul  7 20:23:15 marcelo-notebook kernel: [43135.652121] 
[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A 
(start=723134 end=723135) time 208 us, min 763, max 767, scanline start 760, 
end 766
root@marcelo-notebook:~# uname -a
Linux marcelo-notebook 4.7.0-040700rc5-generic #201606262232 SMP Mon Jun 27 
02:34:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Regards

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.7-rc5

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

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

Title:
  [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
  pipe A

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 upgraded from Ubuntu 14.04 on a Dell Inspiron 14z, w
  /Intel-ATI hybrid graphics (but DIS card is OFF through
  vgaswitcheroo).

  Just like bug no. #1525390 [1], Chrome shows some artifacts randomly
  and I have the same kernel trace but from 10 days ago (I use this
  system everyday and it didn't happened since then).

  [1] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525390

  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
  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
  Date: Fri May  6 15:17:08 2016
  DistUpgraded: 2016-04-25 18:04:08,937 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 5.0.20, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:057f]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2013-08-12 (997 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  LightdmDisplayLog:
   [dix] EventToCore: Not implemented yet 
   [dix] EventToCore: Not implemented yet
  MachineType: Dell Inc. Inspiron 5423
  ProcEnviron:
   LANGUAGE=es_AR:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (10 days ago)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 05WDP7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd05/18/2013:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn05WDP7:rvrA13:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5423
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May  6 09:34:55 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9020 
   vendor AUO
  xserver.version: 2:1.18.3-1ubuntu2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post 

[Desktop-packages] [Bug 1583246] Re: System freezes after returning from locked screen

[Christopher M. Penalver]

Rob Moore, in order to allow additional upstream developers to examine the 
issue, at your earliest convenience, could you please test the latest upstream 
kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? 
Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

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

Title:
  System freezes after returning from locked screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Quite frequently when I lock my screen (or it locks itself) and I
  unlock it the system is responsive for a few seconds but then
  completely freezes. I can't reboot but have to turn off the power on
  the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Wed May 18 11:24:59 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-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: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2016-04-10 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  

[Desktop-packages] [Bug 1576747] Re: Network manager applet unable to control wifi after suspend in 16.04

[Dave Chiluk]

** Summary changed:

- Network manager unable to control wifi after suspend in 16.04
+ Network manager applet unable to control wifi after suspend in 16.04

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

Title:
  Network manager applet unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1690] device 
(wlp4s0): state change: disconnected -> 

[Desktop-packages] [Bug 1573206] Re: GNOME Software does not install third-party .deb packages

[Luis van den Bussche]

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

Being new to Ubuntu and already facing things like wont be able to
install such things as Google Chrome and other 3rd party soft,  and
can't manage why is difficult. Hope this changes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1573206

Title:
  GNOME Software does not install third-party .deb packages

Status in GNOME Software:
  New
Status in Ubuntu GNOME:
  Triaged
Status in Ubuntu Studio:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 LTS (clean install). 64-bit. Final release.
  Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
    Version table:
   *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I intended to install MEGA Sync Client, Google Chrome and Dropbox by
  downloading the needed packages from their websites (respectively
  https://mega.nz/#sync and https://www.google.com/chrome/ and
  https://www.dropbox.com/install?os=lnx ). I opened the packages one by
  one with gnome-software and pressed Install - nothing, except for a
  super-quick progress bar animation, happened. No matter how many times
  I tried, same result. Also, an icon pops up on the panel saying
  "Waiting to install", but nothing seems to happen.

  This only seems to happen with third-party packages; installing a
  random deb from packages.ubuntu.com/xenial worked.

  I even tried to reinstall the system to make this work, but same
  problem.

  Gdebi, however, installs the packages as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-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: Thu Apr 21 21:01:52 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nn_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1573206/+subscriptions

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

[Desktop-packages] [Bug 1573206] Re: GNOME Software does not install third-party .deb packages

[Luis van den Bussche]

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

** Description changed:

  Ubuntu 16.04 LTS (clean install). 64-bit. Final release.
  Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
-   Version table:
-  *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
- 500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Version table:
+  *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
+ 500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
- 
- I intended to install MEGA Sync Client, Google Chrome and Dropbox by 
downloading the needed packages from their websites (respectively 
https://mega.nz/#sync and https://www.google.com/chrome/ and 
https://www.dropbox.com/install?os=lnx ). I opened the packages one by one with 
gnome-software and pressed Install - nothing, except for a super-quick progress 
bar animation, happened. No matter how many times I tried, same result. Also, 
an icon pops up on the panel saying "Waiting to install", but nothing seems to 
happen.
+ I intended to install MEGA Sync Client, Google Chrome and Dropbox by
+ downloading the needed packages from their websites (respectively
+ https://mega.nz/#sync and https://www.google.com/chrome/ and
+ https://www.dropbox.com/install?os=lnx ). I opened the packages one by
+ one with gnome-software and pressed Install - nothing, except for a
+ super-quick progress bar animation, happened. No matter how many times I
+ tried, same result. Also, an icon pops up on the panel saying "Waiting
+ to install", but nothing seems to happen.
  
  This only seems to happen with third-party packages; installing a random
  deb from packages.ubuntu.com/xenial worked.
  
  I even tried to reinstall the system to make this work, but same
  problem.
  
  Gdebi, however, installs the packages as expected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-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: Thu Apr 21 21:01:52 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
-  LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=nn_NO.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=nn_NO.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1573206

Title:
  GNOME Software does not install third-party .deb packages

Status in GNOME Software:
  New
Status in Ubuntu GNOME:
  Triaged
Status in Ubuntu Studio:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 LTS (clean install). 64-bit. Final release.
  Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
    Version table:
   *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I intended to install MEGA Sync Client, Google Chrome and Dropbox by
  downloading the needed packages from their websites (respectively
  https://mega.nz/#sync and https://www.google.com/chrome/ and
  https://www.dropbox.com/install?os=lnx ). I opened the packages one by
  one with gnome-software and pressed Install - nothing, except for a
  super-quick progress bar animation, happened. No matter how many times
  I tried, same result. Also, an icon pops up on the panel saying
  "Waiting to install", but nothing seems to happen.

  This only seems to happen with third-party packages; installing a
  random deb from packages.ubuntu.com/xenial worked.

  I even tried to reinstall the system to make this work, but same
  problem.

  Gdebi, however, installs the packages as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-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: Thu Apr 21 21:01:52 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Richard van der Hoff]

> Bug repro'd here after upgrade to 16

Thank goodness you told everyone. With it only affecting 350 other
people, your particular workaround is of critical importance.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1568604

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Cursor is visible at unlock screen either after returning from suspend
  or just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1589658] Re: Ubuntu 16.04 The AlwaysShared option for lightdm does not work.

[Robert Ancell]

When you run Xvnc on its own, it allows n clients to connect to it. When
LightDM runs it, it listens on the VNC port, and spawns an Xvnc for each
connection (using the -inetd flag). In this way, there is only one
connection per Xvnc instance. So the connections are unshareable.

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

Title:
  Ubuntu 16.04 The AlwaysShared option for lightdm does not work.

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  Setup lightdm on Ubuntu 16.04 s390x GA. Successfully updated software. 
Changed lightdm.conf to use the AlwaysShared option so that I could share a VNC 
session. This did not work.
  [LightDM]
  start-default-seat=seat0

  [VNCServer]
  enabled=true
   command=/usr/bin/Xvnc -rfbauth /etc/vncpasswd -AlwaysShared
  #command=/usr/bin/Xvnc -rfbauth /etc/vncpasswd
  port=5901
  width=1280
  height=800
  depth=24

  [Seat:*]
  #[SeatDefaults]
  user-session=default

  Started two sessions but the second session does not mirror the first.

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

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

[Desktop-packages] [Bug 1589658] Re: Ubuntu 16.04 The AlwaysShared option for lightdm does not work.

[Robert Ancell]

If you want multiple connections to an existing session using LightDM,
then you need to run a VNC server inside that sesion (e.g. Vino).

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

Title:
  Ubuntu 16.04 The AlwaysShared option for lightdm does not work.

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  Setup lightdm on Ubuntu 16.04 s390x GA. Successfully updated software. 
Changed lightdm.conf to use the AlwaysShared option so that I could share a VNC 
session. This did not work.
  [LightDM]
  start-default-seat=seat0

  [VNCServer]
  enabled=true
   command=/usr/bin/Xvnc -rfbauth /etc/vncpasswd -AlwaysShared
  #command=/usr/bin/Xvnc -rfbauth /etc/vncpasswd
  port=5901
  width=1280
  height=800
  depth=24

  [Seat:*]
  #[SeatDefaults]
  user-session=default

  Started two sessions but the second session does not mirror the first.

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

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

[Desktop-packages] [Bug 1589056] Re: HDMI does not work

[Jarno Suni]

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.7-rc6

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

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

Title:
  HDMI does not work

Status in xorg package in Ubuntu:
  New

Bug description:
  xrandr displays "HDMI-1 disconnected (normal left inverted right x
  axis y axis)" even if it is connected using a HDMI cable to a Samsung
  monitor (model S27B350H) that has both HDMI and VGA connectors.

  WORKAROUND: Use the Nvidia proprietary driver.

  Graphics by lspci -vvv:
  01:00.0 VGA compatible controller: NVIDIA Corporation G84GLM [Quadro FX 570M] 
(rev a1) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device 30c5
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
   Capabilities: 
   Kernel driver in use: nouveau

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   root: clean, 247512/1281120 files, 1867600/512 blocks
   [FAILED] Failed to start Automatically refresh installed snaps.
   See 'systemctl status snapd.refresh.service' for details.
   [  OK  ] Started Authenticate and Authorize Users to Run 
Privileged Tasks.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: 2016-06-24 18:11:48,939 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2015-11-21 (228 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (12 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  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/1589056/+subscriptions

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

[Desktop-packages] [Bug 1600003] [NEW] package texlive-latex-base-doc 2015.20160320-1 failed to install/upgrade: intentando sobreescribir `/usr/share/doc/texlive-doc/latex/url/url.tex.gz', que está ta

[Juan Murcia]

Public bug reported:

i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: texlive-latex-base-doc 2015.20160320-1
ProcVersionSignature: Ubuntu 4.4.0-28.47-lowlatency 4.4.13
Uname: Linux 4.4.0-28-lowlatency i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Tue Jul  5 14:43:34 2016
DpkgTerminalLog:
 Preparando para desempaquetar 
.../texlive-latex-base-doc_2015.20160320-1_all.deb ...
 Desempaquetando texlive-latex-base-doc (2015.20160320-1) sobre 
(2013.20140215-1) ...
 dpkg: error al procesar el archivo 
/var/cache/apt/archives/texlive-latex-base-doc_2015.20160320-1_all.deb 
(--unpack):
  intentando sobreescribir `/usr/share/doc/texlive-doc/latex/url/url.tex.gz', 
que está también en el paquete texlive-latex-recommended-doc 2013.20140215-1
ErrorMessage: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/url/url.tex.gz', que está también en el 
paquete texlive-latex-recommended-doc 2013.20140215-1
InstallationDate: Installed on 2014-09-09 (666 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: texlive-base
Title: package texlive-latex-base-doc 2015.20160320-1 failed to 
install/upgrade: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/url/url.tex.gz', que está también en el 
paquete texlive-latex-recommended-doc 2013.20140215-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-base in Ubuntu.
https://bugs.launchpad.net/bugs/163

Title:
  package texlive-latex-base-doc 2015.20160320-1 failed to
  install/upgrade: intentando sobreescribir `/usr/share/doc/texlive-
  doc/latex/url/url.tex.gz', que está también en el paquete texlive-
  latex-recommended-doc 2013.20140215-1

Status in texlive-base package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: texlive-latex-base-doc 2015.20160320-1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-lowlatency 4.4.13
  Uname: Linux 4.4.0-28-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Tue Jul  5 14:43:34 2016
  DpkgTerminalLog:
   Preparando para desempaquetar 
.../texlive-latex-base-doc_2015.20160320-1_all.deb ...
   Desempaquetando texlive-latex-base-doc (2015.20160320-1) sobre 
(2013.20140215-1) ...
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/texlive-latex-base-doc_2015.20160320-1_all.deb 
(--unpack):
intentando sobreescribir `/usr/share/doc/texlive-doc/latex/url/url.tex.gz', 
que está también en el paquete texlive-latex-recommended-doc 2013.20140215-1
  ErrorMessage: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/url/url.tex.gz', que está también en el 
paquete texlive-latex-recommended-doc 2013.20140215-1
  InstallationDate: Installed on 2014-09-09 (666 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: texlive-base
  Title: package texlive-latex-base-doc 2015.20160320-1 failed to 
install/upgrade: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/url/url.tex.gz', que está también en el 
paquete texlive-latex-recommended-doc 2013.20140215-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/163/+subscriptions

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

[Desktop-packages] [Bug 1599995] [NEW] Ability to refresh/rescan individual subdirectories without rescanning the whole file system

[EliCoten]

Public bug reported:

It would be really helpful it was possible to right click on a folder
and rescan just that folder as opposed to clicking the refresh button in
the top right hand corner which refreshes the entire file system.

The use case for this is when trying to free up some space, you use the
tool to identify where the best space savings can be made and then do
some clearing up in the folder, then you want to refresh that part of
the tree to see how it now fits into the overall picture.

I hope that's clear

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

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

Title:
  Ability to refresh/rescan individual subdirectories without rescanning
  the whole file system

Status in baobab package in Ubuntu:
  New

Bug description:
  It would be really helpful it was possible to right click on a folder
  and rescan just that folder as opposed to clicking the refresh button
  in the top right hand corner which refreshes the entire file system.

  The use case for this is when trying to free up some space, you use
  the tool to identify where the best space savings can be made and then
  do some clearing up in the folder, then you want to refresh that part
  of the tree to see how it now fits into the overall picture.

  I hope that's clear

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

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

[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11

[Pete Woods]

Tony, if I remember correctly, gdbus proxies all inherit from the
GDBusProxy class. I *think* you should be able to use the method
g_dbus_proxy_set_default_timeout(...) on the proxy instance you use to
talk to the secret agent, so that all subsequent IPC method calls use
the larger timeout. I would also suggest a much larger timeout than 2
minutes.

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

Title:
  Wi-Fi passphrase limit introduced in OTA-11

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS
  12.4-25d.JA2) stopped working, possibly due to the length of the WPA
  pass-phrase, which was 29 characters long.  The pass-phrase
  requirement is from 8 to 63 characters.  After reducing the pass-
  phrase to 14 (and sometimes 15) characters connectivity is restored.

  Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both
  802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it
  cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and
  although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot
  connect.  The pass-phrase length requirement on both radios is 18 to
  128 characters.

  In both cases the Cisco APs do not log any event.

  Prior to OTA 11 connectivity worked normally on OTA 10.1

  OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5

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

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

[Desktop-packages] [Bug 1563155] Re: No Application Data Found

[Don Esposito]

I tried everything suggested but nothing works for me.

Attached is output of gnome-software --verbose

Everything seems to go bad at line 32713

** Attachment added: "output of command gnome-software --verbose"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1563155/+attachment/4697138/+files/software.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1563155

Title:
  No Application Data Found

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I installed ubuntu 16.04 and when I go to the gnome software, it says
  "No Application Data Found". It is all greyed out and no apps are
  available for download.

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

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

[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11

[Pat McGowan]

** Tags added: hotfix

** Changed in: canonical-devices-system-image
Milestone: backlog => 13

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

Title:
  Wi-Fi passphrase limit introduced in OTA-11

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS
  12.4-25d.JA2) stopped working, possibly due to the length of the WPA
  pass-phrase, which was 29 characters long.  The pass-phrase
  requirement is from 8 to 63 characters.  After reducing the pass-
  phrase to 14 (and sometimes 15) characters connectivity is restored.

  Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both
  802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it
  cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and
  although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot
  connect.  The pass-phrase length requirement on both radios is 18 to
  128 characters.

  In both cases the Cisco APs do not log any event.

  Prior to OTA 11 connectivity worked normally on OTA 10.1

  OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5

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

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

[Desktop-packages] [Bug 1589489] Re: cannot connect to known Wi-Fi after OTA-11

[Tony Espy]

I just updated bug #1593686 ( WPA-PSK limit introduced in OTA11 ) with
the root cause which confirms Pete's theory about timeouts.

That said, *if* a user had successfully connected to an AP prior to the
update to OTA11.  This *shouldn't* have caused issues, as the psk would
already have been present in the connection file, and it should've just
worked.

If further problems are reported, checking the length of the user's
passphrase should be suggested.

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

Title:
  cannot connect to known Wi-Fi after OTA-11

Status in Canonical System Image:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  We're receiving many customer cases where after updating to OTA-11
  they cannot connect to their known or saved Wi-FI AP's. The most
  common behaviour is that M10 ask indefinitely for password when it is
  supoused to be saved previously. I guess this is about network manager
  that has been updated in OTA-11

  What we are asking the customer for:

  1º Forget the network through the UI Settings>Wi-Fi and connect to it again 
as if was the first time.
  2º Try to connect another Wi-Fi AP not saved previously
  3º Factory data reset(but we haven't recommend it yet)

  Please let us know which logs do you need and we'll try to reproduce
  it with our units.

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

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

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

[Cyril Humbert]

Same issue with the folowing BT headphones:

 * Plantronic BackBeat FIT.

 * Plantronic BackBeat PRO.

 * B Beoplay H8.

The computer has a BT USB dongle:

  Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
  CSR8510 A10
  USB ID = 0a12:0001

The following procedure solved the problem for us:

 1. Purge Ubuntu pulseaudio packages and conf files. Backup and purge
pulseaudio user conf files too.

 2. Install the corresponding packages from Debian testing (June 2016).
See attached script (get-pulseaudio8-debian-amd64.sh).

 3. Restart.

 4. A2DP profile should now work as expected with the default
bluez/pulseaudio configuration (Use pavucontrol to select A2DP
if needed).


Since Debian Testing (June 2016) and Ubuntu 16.04 are based on the
same pulseaudio upstream version (8.0) this suggests that this
regression is maybe due to a difference in Debian and Ubuntu
packaging: either the compilation options, the default conf or the
specific patches (e.g. Ubuntu packages include more specific patches).

** Attachment added: "get-pulseaudio8-debian-amd64.sh"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1438510/+attachment/4697122/+files/get-pulseaudio8-debian-amd64.sh

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Desktop-packages] [Bug 1583246] Re: System freezes after returning from locked screen

[Rob Moore]

I experienced this issue (or something similar) yesterday. I used the
alt-sysrq-1 and alt-sysrq-t combo mentioned in the document linked to in
the last comment and after sometime the machine started responding
again. I captured the kern.log and will attach it here in case it's
useful.

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1583246/+attachment/4697121/+files/kern.log

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

Title:
  System freezes after returning from locked screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Quite frequently when I lock my screen (or it locks itself) and I
  unlock it the system is responsive for a few seconds but then
  completely freezes. I can't reboot but have to turn off the power on
  the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02: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.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  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: Wed May 18 11:24:59 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-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: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2016-04-10 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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

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

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

[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11

[Tony Espy]

I just confirmed that this is a regression is caused by the final
deprecation of dbus-glib in NM 1.2x, and it's replacement by gdbus.  As
part of this work, the code which requests secrets from a secret-agent,
now uses code generated from the introspection XML to make the actual
DBus method call.  As this generated function doesn't have a parameter
to allow the client to specify a timeout, the default ( ~25s ) gets
used.  This contrasts to the old code which explicitly specified a 120s
timeout as a parameter to dbus_g_proxy_begin_call_with_timeout().

So, if the user types the passphrase ( or 64-char hex key ) in < ~25s,
the connection should work.  The maximum length passphrase ( repeating
blocks of '1234567890' ) is ~40 characters before the timeout makes it
impossible to type anything longer.

An upstream bug had been reported and is currently in-progress:

https://bugzilla.gnome.org/show_bug.cgi?id=767321

Currently the only workaround for this is to manually update the system
connection file for the AP with the psk and restart the device.  It then
should be possible to tap the access point in the WiFi list, and as long
as the passphrase is correct in the connection file, NM should reconnect
to the network automatically when available.  You can accomplish this by
stopping NM on the device and editing the connection file directly, or
copying the connection file from the device, editing, and pushing it
back ( via adb ).  System connection files are found in the directory
/etc/NetworkManager/system-connections.

I've verified with a krillin running OTA11 that passphrases up to 63
characters work correctly once they've been pre-populated in a
connection file.  I haven't yet verified a 64-character hex key, but
will make sure this is tested as well before we release the final fix.




** Bug watch added: GNOME Bug Tracker #767321
   https://bugzilla.gnome.org/show_bug.cgi?id=767321

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

Title:
  Wi-Fi passphrase limit introduced in OTA-11

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS
  12.4-25d.JA2) stopped working, possibly due to the length of the WPA
  pass-phrase, which was 29 characters long.  The pass-phrase
  requirement is from 8 to 63 characters.  After reducing the pass-
  phrase to 14 (and sometimes 15) characters connectivity is restored.

  Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both
  802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it
  cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and
  although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot
  connect.  The pass-phrase length requirement on both radios is 18 to
  128 characters.

  In both cases the Cisco APs do not log any event.

  Prior to OTA 11 connectivity worked normally on OTA 10.1

  OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5

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

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

[Desktop-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

[Jonathan Polak]

Yes Mike, Lenovo X230 still affected by this bug. Both in ubuntu and in
vanilla debian. This problem is upstream from ubuntu for sure.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1510344

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Desktop-packages] [Bug 1593686] Re: Wi-Fi passphrase limit introduced in OTA-11

[Tony Espy]

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: canonical-devices-system-image
   Status: Incomplete => Confirmed

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

Title:
  Wi-Fi passphrase limit introduced in OTA-11

Status in Canonical System Image:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS
  12.4-25d.JA2) stopped working, possibly due to the length of the WPA
  pass-phrase, which was 29 characters long.  The pass-phrase
  requirement is from 8 to 63 characters.  After reducing the pass-
  phrase to 14 (and sometimes 15) characters connectivity is restored.

  Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both
  802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it
  cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and
  although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot
  connect.  The pass-phrase length requirement on both radios is 18 to
  128 characters.

  In both cases the Cisco APs do not log any event.

  Prior to OTA 11 connectivity worked normally on OTA 10.1

  OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5

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

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

[Desktop-packages] [Bug 1563155] Re: No Application Data Found

[Jeromie Rand]

I tracked my problem down to a bad entry in /usr/local/share/mime/globs
(and /usr/local/share/mime/globs2). The application go-gui had
registered files of type *.xml to x-go+xml.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1563155

Title:
  No Application Data Found

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I installed ubuntu 16.04 and when I go to the gnome software, it says
  "No Application Data Found". It is all greyed out and no apps are
  available for download.

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

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

[Desktop-packages] [Bug 1078068] Re: Video blinking blue during incoming call

[cement_head]

System76 Lemur6 laptop.

I'll try the new one when you get it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1078068

Title:
  Video blinking blue during incoming call

Status in skype package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  Hallo
  I upgraded to ubuntu 12.04LTS and Skype 4.0. When I make a video call I can 
ear and see the other person fine, but when I start my video, the image of the 
incoming video call starts flashing between blue and normal video( the same for 
my mirror image in the little square). The other person sees me fine.
  I didn't have this problem with the previous version of Skype. I tried to 
desinstall and install Skype form the Ubuntu Softwer Center but no change. The 
webcam is a Logitech. after the upgrade it didn't work anymore with Cheese, but 
works fine with another program called guvcview.
  Thank in advance for your help

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

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

[Desktop-packages] [Bug 1576747] Re: Network manager unable to control wifi after suspend in 16.04

[Dave Chiluk]

Not a duplicate of 1585863, as 
$ sudo wpa_cli scan
does not recover nm-applet functionality.  There seem to be a number of similar 
but different issues related to wifi. 

** This bug is no longer a duplicate of bug 1585863
   WiFi malfunction after suspend & resume stress

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

Title:
  Network manager unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  

[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running

[Flames_in_Paradise]

Various bugfixes were implemented in LightDM V. 1.18.2-0ubuntu1 [1]

This package is still awaiting approval as it covers a few issues...


The bugs are referenced there. Hope this helps.


[1] https://launchpad.net/ubuntu/+source/lightdm/1.18.2-0ubuntu1


found via Pending Ubuntu SRU's: 
http://people.canonical.com/~ubuntu-archive/pending-sru

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

Title:
  "low-graphics mode" in VirtualBox guest, but X server running

Status in lightdm package in Ubuntu:
  New

Bug description:
  I sometimes get the "low-graphics mode" message when starting an
  Ubuntu 16.04 virtual machine inside of VirtualBox (current development
  code trunk, somewhere past version 5.1 beta 3 and a debug build).
  When I switch to VT-7 I find the X server running without any visible
  issues (I am the upstream developer of the guest graphics drivers, so
  I have a reasonable but not infallible understanding of the X server).

  The virtual machine has Guest Additions installed, same vintage and
  also a debug build.  Two screens are enabled as is 3D acceleration.
  The host system is also Ubuntu 16.04.  I am still trying to work out
  what triggers the message, but in my last attempts a cold boot failed
  to produce it, while a clean reboot did, but only when the host system
  was not under load (under load as in building VirtualBox).

  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

  IRC discussion at:

https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52

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

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

[Desktop-packages] [Bug 1562219] Re: xinit will not work as non-root.

[Aaron Peromsik]

Two relevant-looking Fedora patches which I haven't tried yet:

http://pkgs.fedoraproject.org/cgit/rpms/xorg-x11-server.git/commit/?h=f22=943ff7334233f04fc2311945822cac537673a493

http://pkgs.fedoraproject.org/cgit/rpms/xorg-x11-server.git/commit/?h=f22=9d0fee062d4fbc0bee08db4fb8461c3d7f9ee0f5

related to this bug https://bugzilla.redhat.com/show_bug.cgi?id=1203780

** Bug watch added: Red Hat Bugzilla #1203780
   https://bugzilla.redhat.com/show_bug.cgi?id=1203780

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

Title:
  xinit will not work as non-root.

Status in xinit package in Ubuntu:
  Confirmed

Bug description:
  When attempting to run xinit or startx after upgrading from 14.04 to
  16.04 it will not work.  There seems to be some sort of permission
  issue.  I have seen another person with this issue as well here:

  http://askubuntu.com/questions/749370/ubuntu-16-04-xf86openconsole-
  cannot-open-virtual-console-2?newreg=ba376d7a182d44608ed4675346b1ed74

  An example is when attempting to launch kodi, which worked prior to
  the upgrade:

  xinit /usr/bin/kodi --standalone -- -nocursor :0

  
  X.Org X Server 1.18.1
  Release Date: 2016-02-08
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.13.0-79-generic x86_64 Ubuntu
  Current Operating System: Linux hostname 4.4.0-15-generic #31-Ubuntu SMP Fri 
Mar 18 19:08:31 UTC 2016 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text
  Build Date: 11 March 2016  07:43:21AM
  xorg-server 2:1.18.1-1ubuntu4 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/home/arch/.local/share/xorg/Xorg.0.log", Time: Fri Mar 25 
20:14:07 2016
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  (EE) 
  Fatal server error:
  (EE) xf86OpenConsole: Cannot open virtual console 2 (Permission denied)
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at 
"/home/arch/.local/share/xorg/Xorg.0.log" for additional information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  xinit: giving up
  xinit: unable to connect to X server: Connection refused

  
  I have tried numerous workarounds including reinstalling xorg, removing all 
x-related files in my profile, and creating a new user.  Unfortunately none of 
these worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xinit 1.3.4-3
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Mar 25 20:14:18 2016
  DistUpgraded: 2016-03-25 09:16:37,728 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: oem-audio-hda-daily, 0.201412181801~ubuntu14.04.1, 
3.13.0-83-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/xinit
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1849:0402]
  InstallationDate: Installed on 2014-12-14 (467 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=6f2e8267-1240-4f7b-9889-42e65d74767e ro biosdevname=0 text
  SourcePackage: xinit
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (0 days ago)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.90
  dmi.board.name: H97M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  

[Desktop-packages] [Bug 1580146] Re: [touch] Internet connection stops working while WiFi is still connected

[Tony Espy]

@Andrea

Can you provide the info requested on comment #25 too?

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

Title:
  [touch] Internet connection stops working while WiFi is still
  connected

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  krillin, rc-proposed, r329

  Description:
  It often happens that the internet connection stops working while the device 
is still connected to a (working) WiFi AP.
  The indicator shows that the phone is connected to the AP, here's the ouput 
of "nmcli d" and "nmcli c" http://pastebin.ubuntu.com/16344985/

  Tapping on the AP in the network indicator resets the connection and
  fixes the issue, which however reappears after a while.

  Here's also a "grep NetworkManager" from syslog
  http://pastebin.ubuntu.com/16344990/

  How to reproduce:
  I don't have a recipe, but here's what usually happens on my phone
  1) I connect to the office WiFi (Canonical's HQ, BlueFin office)
  2) Use browser, perform random google searches to check internet is working
  3) After a while (sometimes I put the phone to sleep, sometimes I checked the 
Updates from system settings a few times), I go back to the browser, and it 
starts returning "Network Error". NM, as you can see from the logs, says WiFi 
is "connected"
  4) At this point I use Terminal app and discover that "ping 8.8.8.8" is 
working correctly, "ping google.com" immediately returns "unkown host", i.e. it 
doesn't seem to be waiting for a timeout, it returns pretty fast.

  There are no related crash files in /var/crash

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

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

[Desktop-packages] [Bug 1594715] Re: wifi does not work roughly half of the times

[Alan Pater]

In my case, it usually helps to run the following command to restore
functionality.

~$ sudo systemctl restart network-manager.service

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

Title:
  wifi does not work roughly half of the times

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After booting, roughly half of the times, wifi doesn't work: The nm-
  applet menu looks as if no wifi would exist. Instead, it lists the a
  non-existing cable network device called "Marvell 88W8897 [AVASTAR]
  802.11ac Wireless". (The network manager seems to be trying to connect
  to that device, but fails.)

  After doing
/etc/init.d/network-manager restart
  the wifi device is always recognized properly, so I guess it's something 
happening in the wrong order during booting. (Alternatively, unloading and 
reloading the kernel module mwifiex_pcie also always helps.)

  The problem did not exist in ubuntu 15.10.

  
  Some more information:

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


  When the bug is there:

  $ nmcli d show wlp1s0
  GENERAL.DEVICE: wlp1s0
  GENERAL.TYPE:   ethernet
  GENERAL.HWADDR: 50:1A:C5:E8:2F:09
  GENERAL.MTU:1500
  GENERAL.STATE:  70 (connecting (getting IP 
configuration))
  GENERAL.CONNECTION: Kabelnetzwerkverbindung 2
  GENERAL.CON-PATH:   
/org/freedesktop/NetworkManager/ActiveConnection/7
  WIRED-PROPERTIES.CARRIER:   on

  $ ifconfig -a
  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:3380 errors:0 dropped:0 overruns:0 frame:0
TX packets:3380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1 
RX bytes:251184 (251.1 KB)  TX bytes:251184 (251.1 KB)

  wlp1s0Link encap:Ethernet  HWaddr 50:1a:c5:e8:2f:09  
UP BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  
  After restarting the network manager:

  immi@flunder:~$ nmcli d show wlp1s0
  GENERAL.DEVICE: wlp1s0
  GENERAL.TYPE:   wifi
  GENERAL.HWADDR: 50:1A:C5:E8:2F:09
  GENERAL.MTU:0
  GENERAL.STATE:  100 (connected)
  GENERAL.CONNECTION: virginmedia4709476
  GENERAL.CON-PATH:   
/org/freedesktop/NetworkManager/ActiveConnection/8
  IP4.ADDRESS[1]: 192.168.0.3/24
  IP4.GATEWAY:192.168.0.1
  IP4.ROUTE[1]:   dst = 169.254.0.0/16, nh = 0.0.0.0, 
mt = 1000
  IP4.DNS[1]: 194.168.4.100
  IP4.DNS[2]: 194.168.8.100
  IP6.ADDRESS[1]: fe80::521a:c5ff:fee8:2f09/64
  IP6.GATEWAY:

  (...)

  wlp1s0Link encap:Ethernet  HWaddr 50:1a:c5:e8:2f:09  
inet6 addr: fe80::521a:c5ff:fee8:2f09/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:304 (304.0 B)  TX bytes:680 (680.0 B)

  
  $ dmesg
  (...)
  [7.850180] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.850263] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.859773] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.869408] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  (...)

  
  I'm happy to try to fix the bug myself, but I could need some help: I don't 
know how to change booting order or something like that.

  I could also temporarily insert some commands into /etc/init.d
  /network-manager printing some status information about the wifi, but
  I don't know how to get such status information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 21 09:35:14 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-19 (579 days ago)
  InstallationMedia: Ubuntu 14.10 

[Desktop-packages] [Bug 1594715] Re: wifi does not work roughly half of the times

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  wifi does not work roughly half of the times

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After booting, roughly half of the times, wifi doesn't work: The nm-
  applet menu looks as if no wifi would exist. Instead, it lists the a
  non-existing cable network device called "Marvell 88W8897 [AVASTAR]
  802.11ac Wireless". (The network manager seems to be trying to connect
  to that device, but fails.)

  After doing
/etc/init.d/network-manager restart
  the wifi device is always recognized properly, so I guess it's something 
happening in the wrong order during booting. (Alternatively, unloading and 
reloading the kernel module mwifiex_pcie also always helps.)

  The problem did not exist in ubuntu 15.10.

  
  Some more information:

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


  When the bug is there:

  $ nmcli d show wlp1s0
  GENERAL.DEVICE: wlp1s0
  GENERAL.TYPE:   ethernet
  GENERAL.HWADDR: 50:1A:C5:E8:2F:09
  GENERAL.MTU:1500
  GENERAL.STATE:  70 (connecting (getting IP 
configuration))
  GENERAL.CONNECTION: Kabelnetzwerkverbindung 2
  GENERAL.CON-PATH:   
/org/freedesktop/NetworkManager/ActiveConnection/7
  WIRED-PROPERTIES.CARRIER:   on

  $ ifconfig -a
  loLink encap:Local Loopback  
inet addr:127.0.0.1  Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING  MTU:65536  Metric:1
RX packets:3380 errors:0 dropped:0 overruns:0 frame:0
TX packets:3380 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1 
RX bytes:251184 (251.1 KB)  TX bytes:251184 (251.1 KB)

  wlp1s0Link encap:Ethernet  HWaddr 50:1a:c5:e8:2f:09  
UP BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

  
  After restarting the network manager:

  immi@flunder:~$ nmcli d show wlp1s0
  GENERAL.DEVICE: wlp1s0
  GENERAL.TYPE:   wifi
  GENERAL.HWADDR: 50:1A:C5:E8:2F:09
  GENERAL.MTU:0
  GENERAL.STATE:  100 (connected)
  GENERAL.CONNECTION: virginmedia4709476
  GENERAL.CON-PATH:   
/org/freedesktop/NetworkManager/ActiveConnection/8
  IP4.ADDRESS[1]: 192.168.0.3/24
  IP4.GATEWAY:192.168.0.1
  IP4.ROUTE[1]:   dst = 169.254.0.0/16, nh = 0.0.0.0, 
mt = 1000
  IP4.DNS[1]: 194.168.4.100
  IP4.DNS[2]: 194.168.8.100
  IP6.ADDRESS[1]: fe80::521a:c5ff:fee8:2f09/64
  IP6.GATEWAY:

  (...)

  wlp1s0Link encap:Ethernet  HWaddr 50:1a:c5:e8:2f:09  
inet6 addr: fe80::521a:c5ff:fee8:2f09/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:304 (304.0 B)  TX bytes:680 (680.0 B)

  
  $ dmesg
  (...)
  [7.850180] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.850263] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.859773] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  [7.869408] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
  (...)

  
  I'm happy to try to fix the bug myself, but I could need some help: I don't 
know how to change booting order or something like that.

  I could also temporarily insert some commands into /etc/init.d
  /network-manager printing some status information about the wifi, but
  I don't know how to get such status information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 21 09:35:14 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-11-19 (579 days ago)
  InstallationMedia: 

[Desktop-packages] [Bug 1599952] [NEW] i915 driver not supported in kernels after 4.2.x

[RD]

Public bug reported:

Have used Ubuntu or its flavors for 3 years with no issues on this
machine.  Installed Ubuntu 16.04 64-bit lts, and successively xubuntu
16.04, ubuntuMATE 16.04, and lubuntu 16.04.  Each installed, but with
blurred images.  Could not get native 1920x1080 resolution to display.
Would like to use one of these, but am relegated to Debian or Debian
derivatives using older kernels and packages that support the driver.
Sandy Bridge integrated graphics with my i5 cpu were manufactured in
2011 -- in my opinion not too old to still work or at least be supported
somehow.  A patch or updated driver would be great.  There were a bunch
of these Asus cm6850 machines made.

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

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

Title:
  i915 driver not supported in kernels after 4.2.x

Status in xorg package in Ubuntu:
  New

Bug description:
  Have used Ubuntu or its flavors for 3 years with no issues on this
  machine.  Installed Ubuntu 16.04 64-bit lts, and successively xubuntu
  16.04, ubuntuMATE 16.04, and lubuntu 16.04.  Each installed, but with
  blurred images.  Could not get native 1920x1080 resolution to display.
  Would like to use one of these, but am relegated to Debian or Debian
  derivatives using older kernels and packages that support the driver.
  Sandy Bridge integrated graphics with my i5 cpu were manufactured in
  2011 -- in my opinion not too old to still work or at least be
  supported somehow.  A patch or updated driver would be great.  There
  were a bunch of these Asus cm6850 machines made.

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

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

[Desktop-packages] [Bug 1519120] Re: NetworkManager VLAN support fails unless vlan package is manually installed

[Mathew Hodson]

** No longer affects: vlan (Ubuntu)

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

Title:
  NetworkManager VLAN support fails unless vlan package is manually
  installed

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I tried to use the network manager UI to define a VLAN interface, and
  nothing happened. There are a few bugs here:

  (1) When creating a VLAN interface through the UI, the "vlan interface
  name" must be filled in. This should just default to ., rather than being a required field. (I typed in "vlan100"
  to get the "Save" button to activate.)

  (2) After creating my VLAN interface, nothing happened. No new
  interface appeared. I then realized that I had not installed the
  "vlan" package, and assumed that NetworkManager therefore could not
  complete configuration of the interface.

  (3) After installing the 'vlan' package (and then telling
  NetworkManager to disconnect and reconnect my Ethernet interface from
  the UI, just for good measure), still no VLAN interfaces were present
  on my system.

  I also tried editing the VLAN interface in the UI, and specifying
  "enp4s0f1.100", but still no VLAN interface came online.

  # apt-cache policy network-manager
  network-manager:
Installed: 1.0.4-0ubuntu6
Candidate: 1.0.4-0ubuntu6
Version table:
   *** 1.0.4-0ubuntu6 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy vlan
  vlan:
Installed: 1.9-3.2ubuntu1
Candidate: 1.9-3.2ubuntu1
Version table:
   *** 1.9-3.2ubuntu1 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1599264] Re: [SRU] "When power is critically low" setting does nothing

[Gunnar Hjalmarsson]

On 2016-07-07 00:27, Alberto Salvia Novella wrote:
> The official held criteria for setting if a bug fix should go into a
> stable release update ...

There are no general criteria for determining when a bug fix *should* be
backported. The purpose of the SRU criteria is to make clear under which
circumstances backporting *may* take place. Obviously they don't
override 'cost-benefit' considerations.

** Changed in: ubuntu-docs (Ubuntu Xenial)
   Importance: Medium => Undecided

** Changed in: ubuntu-docs (Ubuntu Xenial)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1599264

Title:
  [SRU] "When power is critically low" setting does nothing

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Triaged
Status in ubuntu-docs source package in Xenial:
  Won't Fix
Status in unity-control-center source package in Xenial:
  Triaged
Status in ubuntu-docs source package in Yakkety:
  Triaged
Status in unity-control-center source package in Yakkety:
  Triaged

Bug description:
  [Impact]

  In unity-control-center (u-c-c) there is an option for taking an
  action when "Power is critically low".  The choices are "Hibernate" or
  "Power off".  Often Hibernate is a disabled option because of problems
  with hibernate on various systems.

  However - what to do in the event of a critically low power situation
  is now handled by Upowerd automatically and so making a choice in
  u-c-c does nothing at all.

  As such, leaving that option accessible to users will lead to
  confusion.

  This patch removes the option from the UI.

  [Test Case]

  On an unpatched machine with a battery (i.e. laptop) open the power
  panel in u-c-c (Power/Settings menu in the top right corner -> System
  Settings -> Power.  Note that the 2nd option down is "When power is
  critically low".

  Once this update is applied and u-c-c is closed and reopened, this
  option is no longer present.

  [Regression Potential]
  There are some deletions from the ui file and some corresponding code 
deletions from the associated c file (cc-power-panel.c).

  It is possible that extra code has been removed that could cause a
  crash or affect other options in the power panel.

  However, the changes are fairly small and easy to review.  Nothing
  looks out of place.  Also testing has not shown any problems.

  [Other Info]

  Verbal (IRC) +1 from design via mpt.
  +1 from docs team via mailing list.

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

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

Re: [Desktop-packages] [Bug 1078068] Re: Video blinking blue during incoming call

[Nish Aravamudan]

On 07.07.2016 [17:31:15 -], cement_head wrote:
> Non-responsive to Fn+ and to other keyboard input.

How very strange. I guess there must be a side-effect in the xorg intel
driver that tries to handle those keys, but seems odd that'd be the
case. Or it could be very specific to the hardware. My fn keys and other
input work. What machine are you seeing this on?

> Purging permits it to behave as per expected.

I'm glad I didn't permanently break your system! I assume your tests are
occurring each time after restarting X/your system?

Note that this was just a build of the version of in Yakkety already
at the time. It looks like a new Yakkety upload has occurred and I'm
pushing a rebuild to my PPA (2.99.917+git20160706-1ubuntu1~16.04ppa1),
can you test that one too once it has finisehd buiding?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1078068

Title:
  Video blinking blue during incoming call

Status in skype package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  Hallo
  I upgraded to ubuntu 12.04LTS and Skype 4.0. When I make a video call I can 
ear and see the other person fine, but when I start my video, the image of the 
incoming video call starts flashing between blue and normal video( the same for 
my mirror image in the little square). The other person sees me fine.
  I didn't have this problem with the previous version of Skype. I tried to 
desinstall and install Skype form the Ubuntu Softwer Center but no change. The 
webcam is a Logitech. after the upgrade it didn't work anymore with Cheese, but 
works fine with another program called guvcview.
  Thank in advance for your help

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

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

[Desktop-packages] [Bug 1599941] [NEW] data disks created with brasero can't be read

[Karl Lindheimer]

Public bug reported:

I recently copied several directories from a hard drive rescued from a
dead computer to my NAS.  I can open all of the files fine in Ubuntu.  I
attempted to use brasero to burn the windows files to a CD and DVD.
Everything went through the proper steps, and I could see a burned area
on the DVD, however when the disk is inserted in Ubuntu or a windows
computer, it appears empty, except for 1 checksum file.  When I used a
working windows computer to burn the data disk, the resulting DVD or CD
can be read fine in Windows computer, or Windows in VirtualBox under
Ubuntu, but not in Ubuntu itself.  This is an insideous bug, because I
attempted to burn several Ubuntu Directories with photos onto a CD using
Brasero, and the CD's were read just fine in Ubuntu.  The windows
program I used to burn the successful disk said that it was using the
Joliet filesystem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: brasero 3.12.1-1ubuntu3~16.04
ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
Uname: Linux 4.4.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul  7 13:38:05 2016
ExecutablePath: /usr/bin/brasero
InstallationDate: Installed on 2016-03-09 (119 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=
SourcePackage: brasero
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  data disks created with brasero can't be read

Status in brasero package in Ubuntu:
  New

Bug description:
  I recently copied several directories from a hard drive rescued from a
  dead computer to my NAS.  I can open all of the files fine in Ubuntu.
  I attempted to use brasero to burn the windows files to a CD and DVD.
  Everything went through the proper steps, and I could see a burned
  area on the DVD, however when the disk is inserted in Ubuntu or a
  windows computer, it appears empty, except for 1 checksum file.  When
  I used a working windows computer to burn the data disk, the resulting
  DVD or CD can be read fine in Windows computer, or Windows in
  VirtualBox under Ubuntu, but not in Ubuntu itself.  This is an
  insideous bug, because I attempted to burn several Ubuntu Directories
  with photos onto a CD using Brasero, and the CD's were read just fine
  in Ubuntu.  The windows program I used to burn the successful disk
  said that it was using the Joliet filesystem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: brasero 3.12.1-1ubuntu3~16.04
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 13:38:05 2016
  ExecutablePath: /usr/bin/brasero
  InstallationDate: Installed on 2016-03-09 (119 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  SourcePackage: brasero
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1078068] Re: Video blinking blue during incoming call

[cement_head]

Non-responsive to Fn+ and to other keyboard input.

Purging permits it to behave as per expected.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1078068

Title:
  Video blinking blue during incoming call

Status in skype package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  Hallo
  I upgraded to ubuntu 12.04LTS and Skype 4.0. When I make a video call I can 
ear and see the other person fine, but when I start my video, the image of the 
incoming video call starts flashing between blue and normal video( the same for 
my mirror image in the little square). The other person sees me fine.
  I didn't have this problem with the previous version of Skype. I tried to 
desinstall and install Skype form the Ubuntu Softwer Center but no change. The 
webcam is a Logitech. after the upgrade it didn't work anymore with Cheese, but 
works fine with another program called guvcview.
  Thank in advance for your help

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

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

[Desktop-packages] [Bug 1598519] Re: regression: page scrolling jumps to top of page spontaneously

[Kuba]

I have an X220 and the same issue - and I'm on Arch. It only happens when I 
scroll using the Touchpad (edge scroll), not when I use a mousewheel.
Tried disabling smooth scrolling (Re: that Chromium bug report) - still there, 
even if the jump sometimes seems less high. Weird.

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

Title:
  regression: page scrolling jumps to top of page spontaneously

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in webkit package in Ubuntu:
  New

Bug description:
  I switched to chromium-browser from Google Chrome when, 1-2 months
  ago, Chrome began to misbehave on all pages. It spontaneously jumped
  to the top of the page when I continue scrolling downwards (using a
  touchpad).

   As of a July 1 update to
  chromium-browser:amd64 (50.0.2661.102-0ubuntu0.16.04.1.1237, 
51.0.2704.79-0ubuntu0.16.04.1.1242)

  chromium-browser now has the same bug! Chris Down, in comments below,
  says the bug is affecting most webkit-based apps.

  He and I are both on higher-end Lenovo thinkpads (T450s, T460s), (and
  I believe this also affects T410s -- to confirm)).

  To reproduce this, I scroll half-way down a page (using a touchpad?)
  and then click on something (e.g. blank space, which has no effect, or
  ctrl-click on a link to open it in a new tab) with a mouse button.
  Next, as soon as I touch the touchpad to continue scrolling, the page
  jumps to the top.

  Makes browsing near impossible. Very frustrating to have this bug
  arrive at this browser after I already left Chrome (whose latest
  version on Ubuntu also still has this bug) to avoid it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 51.0.2704.79-0ubuntu0.16.04.1.1242
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-DP-1:
   edid-base64:
   dpms: Off
   modes:
   enabled: disabled
   status: disconnected
  DRM.card0-DP-2:
   edid-base64: 
AP///wAebYhO5woAAAoSAQNqLx546mBFplZKnCUSUFSna4CVD5UAgYCBQHFPAQEBAQEBfC6QoGAaHkAwIDYA2igRAAAaITmQMGIaJ0BosDYA2igRAAAc/QA4Sx5TDwAKICAgICAg/ABXMjA1MgogICAgICAgABc=
   dpms: On
   modes: 1680x1050 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 
1152x864 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 
720x400
   enabled: enabled
   status: connected
  DRM.card0-HDMI-A-1:
   edid-base64:
   dpms: Off
   modes:
   enabled: disabled
   status: disconnected
  DRM.card0-HDMI-A-2:
   edid-base64:
   dpms: Off
   modes:
   enabled: disabled
   status: disconnected
  DRM.card0-eDP-1:
   edid-base64: 
AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo=
   dpms: On
   modes: 1920x1080
   enabled: enabled
   status: connected
  Date: Sat Jul  2 21:54:54 2016
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
  DetectedPlugins:

  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2016-02-12 (141 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Load-Avg-1min: 0.72
  Load-Processes-Running-Percent:   0.1%
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=ea2fb511-8d62-4b96-bdaa-4b3f7bf79cc6 ro noprompt quiet splash 
vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to xenial on 2016-05-24 (39 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Samuel Hokin]

Bug repro'd here after upgrade to 16. Dell Latitude E5530. I solve it by
hitting CR in a terminal after login, which I usually have up. If not, I
can use the invisible pointer to launch the terminal.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1568604

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Confirmed
Status in X.Org X server:
  Confirmed
Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  Cursor is visible at unlock screen either after returning from suspend
  or just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1599930] [NEW] libqt4-core dependents does not install

[Cesar Telmo Oliveira Costa]

Public bug reported:

I wind up using Synaptic to mark and upgrade the system. Synaptic is installed 
as Software doesn't display all available packages.
"Important OS updates" does nothing for hours.
I cannot install midlleware of my smartcard (Portugal) - "Cartao Cidadao" for 
the first time with Ubuntu 16.04.
Instead of libqt4-core I have libqtcore4. 
I appreciate the efforts for all involved in the Ubuntu project.

** Affects: gnome-software (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1599930

Title:
  libqt4-core dependents does not install

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I wind up using Synaptic to mark and upgrade the system. Synaptic is 
installed as Software doesn't display all available packages.
  "Important OS updates" does nothing for hours.
  I cannot install midlleware of my smartcard (Portugal) - "Cartao Cidadao" for 
the first time with Ubuntu 16.04.
  Instead of libqt4-core I have libqtcore4. 
  I appreciate the efforts for all involved in the Ubuntu project.

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

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

Re: [Desktop-packages] [Bug 1078068] Re: Video blinking blue during incoming call

[Nish Aravamudan]

On 07.07.2016 [02:43:49 -], cement_head wrote:
> @nacc
> 
> Patch messed up my machine - all the Fn buttons stopped working and got
> non-responsive

Hrm, that seems sort of surprising as my package would have done that.
It's purely a drop-in replacement for the intel X video driver.  You
rebooted after installation (or restarted X)?

Non-responsive in what sense? Your system hung/crashed?

Can you confirm that ppa-purge'ing my PPA results in your system
working? You're sure it wasn't something else that happened to install
simultaneously?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1078068

Title:
  Video blinking blue during incoming call

Status in skype package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  Hallo
  I upgraded to ubuntu 12.04LTS and Skype 4.0. When I make a video call I can 
ear and see the other person fine, but when I start my video, the image of the 
incoming video call starts flashing between blue and normal video( the same for 
my mirror image in the little square). The other person sees me fine.
  I didn't have this problem with the previous version of Skype. I tried to 
desinstall and install Skype form the Ubuntu Softwer Center but no change. The 
webcam is a Logitech. after the upgrade it didn't work anymore with Cheese, but 
works fine with another program called guvcview.
  Thank in advance for your help

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

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

[Desktop-packages] [Bug 1599264] Re: [SRU] "When power is critically low" setting does nothing

[Will Cooke]

Update description to be SRU compliant.

** Description changed:

- Since the move to systemd (I think) the setting in unity-control-center
- under "Power" that says:
+ [Impact]
  
- When power is critically low: [Hibernate | Power Off]
+ In unity-control-center (u-c-c) there is an option for taking an action
+ when "Power is critically low".  The choices are "Hibernate" or "Power
+ off".  Often Hibernate is a disabled option because of problems with
+ hibernate on various systems.
  
- doesn't actually do anything any more.
+ However - what to do in the event of a critically low power situation is
+ now handled by Upowerd automatically and so making a choice in u-c-c
+ does nothing at all.
  
- That action is now controlled by Upower config in
- /etc/UPower/UPower.conf.  At the end of that file you can see:
+ As such, leaving that option accessible to users will lead to confusion.
  
- # The action to take when "TimeAction" or "PercentageAction" above has been
- # reached for the batteries (UPS or laptop batteries) supplying the computer
- # 
- # Possible values are:
- # PowerOff
- # Hibernate
- # HybridSleep
- #
- # If HybridSleep isn't available, Hibernate will be used
- # If Hibernate isn't available, PowerOff will be used
- CriticalPowerAction=HybridSleep
+ This patch removes the option from the UI.
  
+ [Test Case]
  
- So the default action is HybridSleep and is not configurable by the user in 
the control center anymore.
+ On an unpatched machine with a battery (i.e. laptop) open the power
+ panel in u-c-c (Power/Settings menu in the top right corner -> System
+ Settings -> Power.  Note that the 2nd option down is "When power is
+ critically low".
  
- FWIW - I think the best thing to do is just remove that setting from
- u-c-c altogether.
+ Once this update is applied and u-c-c is closed and reopened, this
+ option is no longer present.
+ 
+ [Regression Potential]
+ There are some deletions from the ui file and some corresponding code 
deletions from the associated c file (cc-power-panel.c).
+ 
+ It is possible that extra code has been removed that could cause a crash
+ or affect other options in the power panel.
+ 
+ However, the changes are fairly small and easy to review.  Nothing looks
+ out of place.  Also testing has not shown any problems.

** Description changed:

  [Impact]
  
  In unity-control-center (u-c-c) there is an option for taking an action
  when "Power is critically low".  The choices are "Hibernate" or "Power
  off".  Often Hibernate is a disabled option because of problems with
  hibernate on various systems.
  
  However - what to do in the event of a critically low power situation is
  now handled by Upowerd automatically and so making a choice in u-c-c
  does nothing at all.
  
  As such, leaving that option accessible to users will lead to confusion.
  
  This patch removes the option from the UI.
  
  [Test Case]
  
  On an unpatched machine with a battery (i.e. laptop) open the power
  panel in u-c-c (Power/Settings menu in the top right corner -> System
  Settings -> Power.  Note that the 2nd option down is "When power is
  critically low".
  
  Once this update is applied and u-c-c is closed and reopened, this
  option is no longer present.
  
  [Regression Potential]
  There are some deletions from the ui file and some corresponding code 
deletions from the associated c file (cc-power-panel.c).
  
  It is possible that extra code has been removed that could cause a crash
  or affect other options in the power panel.
  
  However, the changes are fairly small and easy to review.  Nothing looks
  out of place.  Also testing has not shown any problems.
+ 
+ [Other Info]
+ 
+ Verbal (IRC) +1 from design via mpt.
+ +1 from docs team via mailing list.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1599264

Title:
  [SRU] "When power is critically low" setting does nothing

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Triaged
Status in ubuntu-docs source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Triaged
Status in ubuntu-docs source package in Yakkety:
  Triaged
Status in unity-control-center source package in Yakkety:
  Triaged

Bug description:
  [Impact]

  In unity-control-center (u-c-c) there is an option for taking an
  action when "Power is critically low".  The choices are "Hibernate" or
  "Power off".  Often Hibernate is a disabled option because of problems
  with hibernate on various systems.

  However - what to do in the event of a critically low power situation
  is now handled by Upowerd automatically and so making a choice in
  u-c-c does nothing at all.

  As such, leaving that option accessible to users will lead to
  confusion.

  This patch removes the option from the UI.

  [Test Case]

[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error

[Laurent Bonnaud]

> -rw-r- 1 root shadow 1096 июля 5 09:49 /etc/shadow

This is the standard GID on Debian/Ubuntu system.

> -rw-r- 1 root root 1096 июля 5 09:49 /etc/shadow

That was an anomaly on your system.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1085706

Title:
  pam_ecryptfs: seteuid error

Status in eCryptfs:
  Confirmed
Status in GNOME Screensaver:
  New
Status in ubuntu-mate:
  New
Status in ecryptfs-utils package in Ubuntu:
  Triaged
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in gnome-screensaver package in Debian:
  New

Bug description:
  I get this error message in the syslog when I authenticate succesfully
  in the screensaver.

  ---
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2012-06-13 (172 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  Package: gnome-screensaver 3.6.0-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1596200] Re: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

[Federico Leoni]

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

** This bug has been marked a duplicate of bug 1599306
   16.04:  i8042 need to start early after grub

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

Title:
  Ubuntu 16.04: unresponsive keyboard (15 sec) after grub

Status in kbd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New
Status in xinput package in Ubuntu:
  New

Bug description:
  I've upgraded my notebook with an SSD. All works fine and I can reach
  the login in less than 10 seconds. Problem is I can't use the internal
  keyboard (perfectly working on grub) for at least 10-15 seconds, then
  it starts to working just fine. The touchpad and capacitive buttons
  are working without issues.

  Luckily I have a second HDD on my machine and I've made some tests
  with the old mechanical drive, with this unit I can input my password
  on LightDM without any delay.

  The issue is not (only) related to Xorg or LightDM, because starting in 
recovery mode shown the same issue with both disks: if I use an external 
keyboard (a Logitech k400r in my case) I have no issue at all on both login and 
recovery mode. 
  Seems kdb needs some time to be up and running.

  Here's a video showing a full cycle of boots:

  https://youtu.be/yseDPvqWNw4

  And here a video of the recovery mode:

  https://youtu.be/vbsD9tb-Dn8

  Fresh install of Ubuntu 16.04 LTS without any other packages.

  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
  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: Sat Jun 25 12:01:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [103c:30cd]
 Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [103c:30cd]
  InstallationDate: Installed on 2016-06-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2B
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2B
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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-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 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jun 25 12:00:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19778 
   vendor SEC
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1599877] Re: lentitud

[Paul White]

** Description changed:

  error tengo una portatil vit con tarjeta de video intel hd 4000 y 8gb en
  ram la siento lenta en video y procesamiento
+ 
+ 
+ Translation uisng translate.google.com:
+ Error vit have a portable video card intel hd 4000 and 8gb RAM feel slow and 
processing video
+ 
  
  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
  Architecture: amd64
  BootLog:
-  
+ 
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul  7 09:59:16 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Elitegroup Computer Systems 3rd Gen Core processor Graphics 
Controller [1019:9991]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Elitegroup Computer Systems 3rd Gen Core processor Graphics 
Controller [1019:9991]
  InstallationDate: Installed on 2016-07-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: VIT VIT P3400
  ProcEnviron:
-  LANGUAGE=es_VE:es
-  PATH=(custom, no user)
-  LANG=es_VE.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=es_VE:es
+  PATH=(custom, no user)
+  LANG=es_VE.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=d4101f36-777e-4a43-ab97-625d9011264a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 2.00.01.IP_T4
  dmi.board.asset.tag: NULL
  dmi.board.name: VIT P3400
  dmi.board.vendor: VIT
  dmi.board.version: Not applicable
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: VIT
  dmi.chassis.version: Not applicable
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr2.00.01.IP_T4:bd03/25/2013:svnVIT:pnVITP3400:pvr1.0:rvnVIT:rnVITP3400:rvrNotapplicable:cvnVIT:ct9:cvrNotapplicable:
  dmi.product.name: VIT P3400
  dmi.product.version: 1.0
  dmi.sys.vendor: VIT
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-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
  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: Thu Jul  7 09:29:11 2016
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id1479 
-  vendor BOE
+  product id1479
+  vendor BOE
  xserver.version: 2:1.18.3-1ubuntu2

** Summary changed:

- lentitud
+ lentitud (slowness)

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

Title:
  lentitud (slowness)

Status in xorg package in Ubuntu:
  New

Bug description:
  error tengo una portatil vit con tarjeta de video intel hd 4000 y 8gb
  en ram la siento lenta en video y procesamiento

  
  Translation uisng translate.google.com:
  Error vit have a portable video card intel hd 4000 and 8gb RAM feel slow and 
processing video
  

  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
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul  7 09:59:16 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     

[Desktop-packages] [Bug 1599264] Re: [SRU] "When power is critically low" setting does nothing

[Will Cooke]

** Summary changed:

- "When power is critically low" setting does nothing
+ [SRU] "When power is critically low" setting does nothing

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1599264

Title:
  [SRU] "When power is critically low" setting does nothing

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Triaged
Status in ubuntu-docs source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Triaged
Status in ubuntu-docs source package in Yakkety:
  Triaged
Status in unity-control-center source package in Yakkety:
  Triaged

Bug description:
  Since the move to systemd (I think) the setting in unity-control-
  center under "Power" that says:

  When power is critically low: [Hibernate | Power Off]

  doesn't actually do anything any more.

  That action is now controlled by Upower config in
  /etc/UPower/UPower.conf.  At the end of that file you can see:

  # The action to take when "TimeAction" or "PercentageAction" above has been
  # reached for the batteries (UPS or laptop batteries) supplying the computer
  # 
  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep
  #
  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used
  CriticalPowerAction=HybridSleep

  
  So the default action is HybridSleep and is not configurable by the user in 
the control center anymore.

  FWIW - I think the best thing to do is just remove that setting from
  u-c-c altogether.

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

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

[Desktop-packages] [Bug 1599792] Re: Can't install nvidia driver for gtx970 card

[Paul White]

** Summary changed:

- bug report
+ Can't install nvidia driver for gtx970 card

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

Title:
  Can't install nvidia driver for gtx970 card

Status in xorg package in Ubuntu:
  New

Bug description:
  Cant install nvidia driver for gtx970 card.after install and restart
  display gets to low graphics mode and cant login.need a fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Thu Jul  7 15:57:43 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] 
[19da:1366]
  InstallationDate: Installed on 2016-07-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=fcd176d6-6b12-4613-995f-3864ac4a59d1 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  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: Thu Jul  7 15:52:15 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1380480] Re: network disabled after suspend - resume

[Hans Deragon]

Ubuntu (Unity) does not work perfectly.  I have this problem using
Ubuntu 16.04 LTS Xenial Xerus with Unity.

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

Title:
  network disabled after suspend - resume

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

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

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

[Desktop-packages] [Bug 1599874] Re: no rear sound creative sound blaster Z ssid: 1102:0023

[Olcay Korkmaz]

** Tags added: alsa ca0132

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

Title:
   no rear sound creative sound blaster Z ssid: 1102:0023

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

Bug description:
  Hi,

  it's long standing bug we can't use Z series cards properly on linux 
  only front panel work 
  rest of ports are not working

  I extracted latest firmware from windows driver but no luck 
  here are extra details from windows and freebsd drivers both are works fine

  freebsd pin configs;
  hdaa0: Patched pins configuration:
  hdaa0: nid   0xas seq device   conn  jackloccolor   misc
  hdaa0: 11 410140f0 15 0  Line-out  None  1/8 Rear   Green   0 DISA
  hdaa0: 12 014520f0 15 0  SPDIF-out Jack  Optical Rear   Grey0
  hdaa0: 13 010170f0 15 0  Line-out  Jack  1/8 Rear   Yellow  0
  hdaa0: 14 01c510f0 15 0  SPDIF-in  Jack  Optical Rear   Black   0
  hdaa0: 15 412000f0 15 0  HeadphonesNone  Unknown Rear   Unknown 0 DISA
  hdaa0: 16 022140f0 15 0  HeadphonesJack  1/8 Front  Green   0
  hdaa0: 17 418120f0 15 0  Line-in   None  1/8 Rear   Grey0 DISA
  hdaa0: 18 01a190f0 15 0  Mic   Jack  1/8 Rear   Pink0
  hdaa0: 19 50d000f0 15 0  Digital-inNone  Unknown Internal   Unknown 0 DISA
  hdaa0: 24 50f0 15 0  Line-out  None  Unknown Internal   Unknown 0 DISA

  pin configs from windows driver
  NID: 11
  Node: 0x0b
  Pin: 0x410140f0
  Verb 00B71CF0 00B71D40 00B71E01 00B71F41 

  NID: 12
  Node: 0x0c
  Pin: 0x014520f0
  Verb 00C71CF0 00C71D20 00C71E45 00C71F01 

  NID: 13
  Node: 0x0d
  Pin: 0x010171f0
  Verb 00D71CF0 00D71D71 00D71E01 00D71F01 

  NID: 14
  Node: 0x0e
  Pin: 0x01c510f0
  Verb 00E71CF0 00E71D10 00E71EC5 00E71F01 

  NID: 15
  Node: 0x0f
  Pin: 0x412000f0
  Verb 00F71CF0 00F71D00 00F71E20 00F71F41 

  NID: 16
  Node: 0x10
  Pin: 0x022140f0
  Verb 01071CF0 01071D40 01071E21 01071F02 

  NID: 17
  Node: 0x11
  Pin: 0x418120f0
  Verb 01171CF0 01171D20 01171E81 01171F41 

  NID: 18
  Node:0x12
  Pin:0x01a190f0
  Verb 01271CF0 01271D90 01271EA1 01271F01 

  NID: 19
  Node:0x13
  Pin:0x50d000f0
  Verb 01371CF0 01371D00 01371ED0 01371F50 

  NID: 24
  Node:0x18
  Pin:0x50f0
  Verb 01871CF0 01871D00 01871E00 01871F50

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olci   1701 F pulseaudio
   /dev/snd/controlC0:  olci   1701 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  7 16:48:52 2016
  InstallationDate: Installed on 2016-06-25 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 7 (MS-7916)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd02/16/2016:svnMSI:pnMS-7916:pvr1.0:rvnMSI:rnZ97GAMING7(MS-7916):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7916
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1594814] Re: NetworkManager looking for signal strength in 'wlan0' instead of the apropriate 'wlxc46e1f1abe34"

[Bug Watch Updater]

** Changed in: network-manager
   Status: Incomplete => Confirmed

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

Title:
  NetworkManager looking for signal strength in 'wlan0' instead of the
  apropriate 'wlxc46e1f1abe34"

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

Bug description:
  I get this error in my log a lot:
  "Jun 21 15:04:00 basspistol NetworkManager[834]:   [1466514240.9769] 
(wlan0): error getting signal strength: No such device"

  My wireless device (TP-Link 150Mbps Wireless N Nano USB Adapter) is
  getting a very funky name: "wlxc46e1f1abe34". It's not too much of a
  problem since the connection is established and working, but it
  renders the wifi-strength icon as if it was receiving maximum signal
  strength.

  Restarting the network-manager with: "sudo systemctl restart network-
  manager.service" solves the problem.

  Not sure if it is related, but i am also affected by this bug:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401
  Even after upgrading to: network-manager-gnome:amd64 (1.2.0-0ubuntu0.16.04.1, 
1.2.0-0ubuntu0.16.04.3) on 2016-06-19

  Let me know if there is any complementary information i can provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-lowlatency 4.4.10
  Uname: Linux 4.4.0-24-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 21 15:04:46 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-21 (60 days ago)
  InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 10.42.0.1 dev wlxc46e1f1abe34  proto static  metric 600
   10.42.0.0/24 dev wlxc46e1f1abe34  proto kernel  scope link  src 10.42.0.22  
metric 600
   169.254.0.0/16 dev wlxc46e1f1abe34  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:

  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION   CON-UUID  CON-PATH
   wlxc46e1f1abe34  wifi  connected
/org/freedesktop/NetworkManager/Devices/0  sakrecoer 1  
7bfae379-b282-4335-8bfe-f1f55229ad51  
/org/freedesktop/NetworkManager/ActiveConnection/0
   enp3s0   ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/2  --   --  
  --
  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/1594814/+subscriptions

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

[Desktop-packages] [Bug 1599874] [NEW] no rear sound creative sound blaster Z ssid: 1102:0023

[Olcay Korkmaz]

Public bug reported:

Hi,

it's long standing bug we can't use Z series cards properly on linux 
only front panel work 
rest of ports are not working

I extracted latest firmware from windows driver but no luck 
here are extra details from windows and freebsd drivers both are works fine

freebsd pin configs;
hdaa0: Patched pins configuration:
hdaa0: nid   0xas seq device   conn  jackloccolor   misc
hdaa0: 11 410140f0 15 0  Line-out  None  1/8 Rear   Green   0 DISA
hdaa0: 12 014520f0 15 0  SPDIF-out Jack  Optical Rear   Grey0
hdaa0: 13 010170f0 15 0  Line-out  Jack  1/8 Rear   Yellow  0
hdaa0: 14 01c510f0 15 0  SPDIF-in  Jack  Optical Rear   Black   0
hdaa0: 15 412000f0 15 0  HeadphonesNone  Unknown Rear   Unknown 0 DISA
hdaa0: 16 022140f0 15 0  HeadphonesJack  1/8 Front  Green   0
hdaa0: 17 418120f0 15 0  Line-in   None  1/8 Rear   Grey0 DISA
hdaa0: 18 01a190f0 15 0  Mic   Jack  1/8 Rear   Pink0
hdaa0: 19 50d000f0 15 0  Digital-inNone  Unknown Internal   Unknown 0 DISA
hdaa0: 24 50f0 15 0  Line-out  None  Unknown Internal   Unknown 0 DISA

pin configs from windows driver
NID: 11
Node: 0x0b
Pin: 0x410140f0
Verb 00B71CF0 00B71D40 00B71E01 00B71F41 

NID: 12
Node: 0x0c
Pin: 0x014520f0
Verb 00C71CF0 00C71D20 00C71E45 00C71F01 

NID: 13
Node: 0x0d
Pin: 0x010171f0
Verb 00D71CF0 00D71D71 00D71E01 00D71F01 

NID: 14
Node: 0x0e
Pin: 0x01c510f0
Verb 00E71CF0 00E71D10 00E71EC5 00E71F01 

NID: 15
Node: 0x0f
Pin: 0x412000f0
Verb 00F71CF0 00F71D00 00F71E20 00F71F41 

NID: 16
Node: 0x10
Pin: 0x022140f0
Verb 01071CF0 01071D40 01071E21 01071F02 

NID: 17
Node: 0x11
Pin: 0x418120f0
Verb 01171CF0 01171D20 01171E81 01171F41 

NID: 18
Node:0x12
Pin:0x01a190f0
Verb 01271CF0 01271D90 01271EA1 01271F01 

NID: 19
Node:0x13
Pin:0x50d000f0
Verb 01371CF0 01371D00 01371ED0 01371F50 

NID: 24
Node:0x18
Pin:0x50f0
Verb 01871CF0 01871D00 01871E00 01871F50

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  olci   1701 F pulseaudio
 /dev/snd/controlC0:  olci   1701 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul  7 16:48:52 2016
InstallationDate: Installed on 2016-06-25 (11 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.12
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 7 (MS-7916)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd02/16/2016:svnMSI:pnMS-7916:pvr1.0:rvnMSI:rnZ97GAMING7(MS-7916):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7916
dmi.product.version: 1.0
dmi.sys.vendor: MSI

** Affects: alsa-driver
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug xenial

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

** Also affects: alsa-driver via
   http://bugzilla.kernel.org/show_bug.cgi?id=120491
   Importance: Unknown
   Status: Unknown

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

Title:
   no rear sound creative sound blaster Z ssid: 1102:0023

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

Bug description:
  Hi,

  it's long standing bug we can't use Z series cards properly on linux 
  only front panel work 
  rest of ports are not working

  I extracted latest firmware from windows driver but no luck 
  here are extra details from windows and freebsd drivers both are works fine

  freebsd pin configs;
  hdaa0: Patched pins configuration:
  hdaa0: nid   0xas seq device   conn  jackloccolor   misc
  hdaa0: 11 410140f0 15 0  Line-out  None  1/8 Rear   Green   0 DISA
  hdaa0: 12 014520f0 15 0  SPDIF-out Jack  Optical Rear   Grey0
  hdaa0: 13 010170f0 15 0  Line-out  Jack  1/8 Rear   Yellow  0
  hdaa0: 14 01c510f0 15 0  SPDIF-in  Jack  Optical Rear   Black   0
  hdaa0: 15 412000f0 15 0  HeadphonesNone  Unknown Rear   Unknown 0 DISA
  hdaa0: 16 022140f0 15 0  HeadphonesJack  1/8 Front  Green   0
  hdaa0: 17 418120f0 15 0  Line-in   None  1/8 Rear   Grey0 

[Desktop-packages] [Bug 1599877] [NEW] lentitud

[Ing. Wilmer Lopez]

Public bug reported:

error tengo una portatil vit con tarjeta de video intel hd 4000 y 8gb en
ram la siento lenta en video y procesamiento

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
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jul  7 09:59:16 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems 3rd Gen Core processor Graphics 
Controller [1019:9991]
InstallationDate: Installed on 2016-07-05 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: VIT VIT P3400
ProcEnviron:
 LANGUAGE=es_VE:es
 PATH=(custom, no user)
 LANG=es_VE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=d4101f36-777e-4a43-ab97-625d9011264a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 2.00.01.IP_T4
dmi.board.asset.tag: NULL
dmi.board.name: VIT P3400
dmi.board.vendor: VIT
dmi.board.version: Not applicable
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: VIT
dmi.chassis.version: Not applicable
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr2.00.01.IP_T4:bd03/25/2013:svnVIT:pnVITP3400:pvr1.0:rvnVIT:rnVITP3400:rvrNotapplicable:cvnVIT:ct9:cvrNotapplicable:
dmi.product.name: VIT P3400
dmi.product.version: 1.0
dmi.sys.vendor: VIT
version.compiz: compiz 1:0.9.12.2+16.04.20160415-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
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: Thu Jul  7 09:29:11 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1479 
 vendor BOE
xserver.version: 2:1.18.3-1ubuntu2

** 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 Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1599877

Title:
  lentitud

Status in xorg package in Ubuntu:
  New

Bug description:
  error tengo una portatil vit con tarjeta de video intel hd 4000 y 8gb
  en ram la siento lenta en video y procesamiento

  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
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul  7 09:59:16 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems 3rd Gen Core processor Graphics 
Controller [1019:9991]
  InstallationDate: Installed on 2016-07-05 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: VIT VIT P3400
  ProcEnviron:
   LANGUAGE=es_VE:es
   PATH=(custom, no user)
   LANG=es_VE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=d4101f36-777e-4a43-ab97-625d9011264a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 2.00.01.IP_T4
  dmi.board.asset.tag: NULL
  dmi.board.name: VIT P3400
  dmi.board.vendor: VIT
  dmi.board.version: Not 

[Desktop-packages] [Bug 1571640] Re: lightdm changing resolution

[Launchpad Bug Tracker]

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

** Changed in: unity-greeter (Ubuntu Xenial)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1571640

Title:
  lightdm changing resolution

Status in unity-greeter package in Ubuntu:
  Fix Committed
Status in unity-greeter source package in Xenial:
  Confirmed
Status in unity-greeter source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

   * Unity Greeter does not have the right scale at the beginning, after
  a short delay, it changes to the right scale.

  [Test Case]

   * It can be easily observed on HiDPI display, when Unity Greeter is
  starting.

  [Regression Potential]

   * If u-s-d failed to launch, Unity Greeter stuck at waiting u-s-d's
  signal and failed to proceed. But it's not likely to happen.

  

  Just after the upgrade to ubuntu 16.04, when lightdm starts the
  resolution is 2560x1600. Then, after about half a second it is
  automatically changed to 1280x800. This happens systematically at each
  boot. No external monitor is connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 18 14:39:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-09 (525 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running

[Will Cooke]

Added to Trello: https://trello.com/c/Un8N5Pfs/16-bug-1599775-low-
graphics-mode-in-virtualbox-guest-but-x-server-running

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

Title:
  "low-graphics mode" in VirtualBox guest, but X server running

Status in lightdm package in Ubuntu:
  New

Bug description:
  I sometimes get the "low-graphics mode" message when starting an
  Ubuntu 16.04 virtual machine inside of VirtualBox (current development
  code trunk, somewhere past version 5.1 beta 3 and a debug build).
  When I switch to VT-7 I find the X server running without any visible
  issues (I am the upstream developer of the guest graphics drivers, so
  I have a reasonable but not infallible understanding of the X server).

  The virtual machine has Guest Additions installed, same vintage and
  also a debug build.  Two screens are enabled as is 3D acceleration.
  The host system is also Ubuntu 16.04.  I am still trying to work out
  what triggers the message, but in my last attempts a cold boot failed
  to produce it, while a clean reboot did, but only when the host system
  was not under load (under load as in building VirtualBox).

  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

  IRC discussion at:

https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52

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

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

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

[Kevin DuBois]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358

Title:
  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 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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running

[Paul Sladen]

** Description changed:

  I sometimes get the "low-graphics mode" message when starting an Ubuntu
  16.04 virtual machine inside of VirtualBox (current development code
  trunk, somewhere past version 5.1 beta 3 and a debug build).  When I
  switch to VT-7 I find the X server running without any visible issues (I
  am the upstream developer of the guest graphics drivers, so I have a
  reasonable but not infallible understanding of the X server).
  
  The virtual machine has Guest Additions installed, same vintage and also
  a debug build.  Two screens are enabled as is 3D acceleration.  The host
  system is also Ubuntu 16.04.  I am still trying to work out what
  triggers the message, but in my last attempts a cold boot failed to
  produce it, while a clean reboot did, but only when the host system was
  not under load (under load as in building VirtualBox).
  
  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:
  
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ IRC discussion at:
+ 
+   https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52

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

Title:
  "low-graphics mode" in VirtualBox guest, but X server running

Status in lightdm package in Ubuntu:
  New

Bug description:
  I sometimes get the "low-graphics mode" message when starting an
  Ubuntu 16.04 virtual machine inside of VirtualBox (current development
  code trunk, somewhere past version 5.1 beta 3 and a debug build).
  When I switch to VT-7 I find the X server running without any visible
  issues (I am the upstream developer of the guest graphics drivers, so
  I have a reasonable but not infallible understanding of the X server).

  The virtual machine has Guest Additions installed, same vintage and
  also a debug build.  Two screens are enabled as is 3D acceleration.
  The host system is also Ubuntu 16.04.  I am still trying to work out
  what triggers the message, but in my last attempts a cold boot failed
  to produce it, while a clean reboot did, but only when the host system
  was not under load (under load as in building VirtualBox).

  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

  IRC discussion at:

https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52

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

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

[Desktop-packages] [Bug 1572855] Re: libgbm.so.1: cannot open shared object file

[jvh]

I tried the xserver-xorg-core-lts-utopic package (which is the transitional i 
needed) and also the manual fix (using dpkg-divert), but it *still* doesn't 
work. The error I get is:
  rhythmbox: error while loading shared libraries: libgbm.so.1: cannot open 
shared object file: No such file or directory

The output of `dpkg -L libgbm1` is:
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0
/usr/share
/usr/share/bug
/usr/share/bug/libgbm1
/usr/share/bug/libgbm1/control
/usr/share/bug/libgbm1/script
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libgbm1
/usr/share/doc
/usr/share/doc/libgbm1
/usr/share/doc/libgbm1/copyright
/usr/share/doc/libgbm1/changelog.Debian.gz
/usr/lib/x86_64-linux-gnu/libgbm.so.1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-lts-transitional in Ubuntu.
https://bugs.launchpad.net/bugs/1572855

Title:
  libgbm.so.1: cannot open shared object file

Status in xorg-lts-transitional package in Ubuntu:
  Fix Released

Bug description:
  After upgrading from 14.04 -> 16.04, there are still some dpkg-diverts
  left in place. This stops gdm/gnome-shell from booting up at all.

  Apr 20 23:22:12 ubuntu gnome-session[1018]: gnome-shell: error while loading 
shared libraries: libgbm.so.1: cannot open shared object file: No such file or 
directory
  Apr 20 23:22:12 ubuntu gnome-session[1018]: gnome-session-binary[1018]: 
WARNING: App 'gnome-shell-wayland.desktop' exited with code 127
  Apr 20 23:22:12 ubuntu gnome-session-binary[1018]: WARNING: App 
'gnome-shell-wayland.desktop' exited with code 127
  Apr 20 23:22:13 ubuntu gnome-session[1213]: gnome-shell: error while loading 
shared libraries: libgbm.so.1: cannot open shared 

  $dpkg -L libgbm1
  /usr
  /usr/lib
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0
  diverted by libgbm1-lts-wily to: /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0

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

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

[Desktop-packages] [Bug 1599846] [NEW] package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

[mahowi]

Public bug reported:

Update failed while upgrading from xenial to yakkety.

mahowi@T60:~$ lsb_release -rd
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10

mahowi@T60:~$ apt-cache policy bamfdaemon
bamfdaemon:
  Installiert:   0.5.3~bzr0+16.10.20160705-0ubuntu1
  Installationskandidat: 0.5.3~bzr0+16.10.20160705-0ubuntu1
  Versionstabelle:
 *** 0.5.3~bzr0+16.10.20160705-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
Uname: Linux 4.4.0-30-generic i686
ApportVersion: 2.20.2-0ubuntu1
Architecture: i386
Date: Thu Jul  7 13:39:38 2016
ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
InstallationDate: Installed on 2016-07-06 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
RelatedPackageVersions:
 dpkg 1.18.9ubuntu1
 apt  1.3~exp1
SourcePackage: bamf
Title: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to 
install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
UpgradeStatus: Upgraded to yakkety on 2016-07-07 (0 days ago)

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


** Tags: apport-package i386 yakkety

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

Title:
  package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to
  install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

Status in bamf package in Ubuntu:
  New

Bug description:
  Update failed while upgrading from xenial to yakkety.

  mahowi@T60:~$ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

  mahowi@T60:~$ apt-cache policy bamfdaemon
  bamfdaemon:
Installiert:   0.5.3~bzr0+16.10.20160705-0ubuntu1
Installationskandidat: 0.5.3~bzr0+16.10.20160705-0ubuntu1
Versionstabelle:
   *** 0.5.3~bzr0+16.10.20160705-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic i686
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: i386
  Date: Thu Jul  7 13:39:38 2016
  ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  InstallationDate: Installed on 2016-07-06 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu1
   apt  1.3~exp1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to 
install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  UpgradeStatus: Upgraded to yakkety on 2016-07-07 (0 days ago)

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

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

[Desktop-packages] [Bug 1589658] Re: Ubuntu 16.04 The AlwaysShared option for lightdm does not work.

[mikenash]

I use a vncserver on Red Hat and Suse dirstributions where I am able to
share a session using the option alwaysshared.  The alwaysshared option
is to always treat incoming connections as shared, regardless of the
client-specified setting (default is off).

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

Title:
  Ubuntu 16.04 The AlwaysShared option for lightdm does not work.

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  Setup lightdm on Ubuntu 16.04 s390x GA. Successfully updated software. 
Changed lightdm.conf to use the AlwaysShared option so that I could share a VNC 
session. This did not work.
  [LightDM]
  start-default-seat=seat0

  [VNCServer]
  enabled=true
   command=/usr/bin/Xvnc -rfbauth /etc/vncpasswd -AlwaysShared
  #command=/usr/bin/Xvnc -rfbauth /etc/vncpasswd
  port=5901
  width=1280
  height=800
  depth=24

  [Seat:*]
  #[SeatDefaults]
  user-session=default

  Started two sessions but the second session does not mirror the first.

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

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

[Desktop-packages] [Bug 1599834] [NEW] package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

[RaphaëlPLE]

Public bug reported:

I had an issue by executing the do-release-upgrade command. I had to
reboot, then I execute apt-get install -f and I updated the system
before rebooting again.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: hicolor-icon-theme 0.15-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Jul  7 11:54:13 2016
Dependencies:
 
ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
InstallationDate: Installed on 2015-05-28 (405 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
UpgradeStatus: Upgraded to xenial on 2016-07-07 (0 days ago)

** Affects: hicolor-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hicolor-icon-theme in Ubuntu.
https://bugs.launchpad.net/bugs/1599834

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  bloqué en boucle sur le traitement des actions différées (« triggers
  »), abandon

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  I had an issue by executing the do-release-upgrade command. I had to
  reboot, then I execute apt-get install -f and I updated the system
  before rebooting again.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jul  7 11:54:13 2016
  Dependencies:
   
  ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  InstallationDate: Installed on 2015-05-28 (405 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
  UpgradeStatus: Upgraded to xenial on 2016-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1599834/+subscriptions

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

[Desktop-packages] [Bug 1589893] Re: Xorg crashes

[Christopher M. Penalver]

Kevin, the next step is to fully reverse commit bisect from kernel 4.4
to 4.7-rc5 in order to identify the last bad commit, followed
immediately by the first good one. Once this good commit has been
identified, it may be reviewed for backporting. Could you please do this
following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?

Please note, finding adjacent kernel versions is not fully commit
bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

After the fix commit (not kernel version) has been identified, then
please mark this report Status Confirmed.

Thank you for your help.

** Description changed:

+ Xorg crashes about every 45 minutes.
+ 
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471186] Freezing of tasks 
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471220] XorgD 
880089ccfa78 0  1109   1099 0x0044
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471230]  880089ccfa78 
812cbfa8 880264d99b80 88025d45
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471237]  880089cd 
880089ccfab0 88026ec8dd00 88026ec8dd00
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471242]  0001 
880089ccfa90 81821205 00010018eca0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471248] Call Trace:
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471263]  [] 
? __ext4_handle_dirty_metadata+0x48/0x1f0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471272]  [] 
schedule+0x35/0x80
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471278]  [] 
schedule_timeout+0x129/0x270
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471287]  [] 
? trace_event_raw_event_tick_stop+0x120/0x120
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471370]  [] 
intel_crtc_wait_for_pending_flips+0xa6/0x240 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471378]  [] 
? wake_atomic_t_function+0x60/0x60
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471425]  [] 
intel_pre_plane_update+0x111/0x140 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471469]  [] 
intel_atomic_commit+0x352/0x6f0 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471520]  [] 
? drm_atomic_check_only+0x18e/0x590 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471551]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471575]  [] 
drm_atomic_helper_disable_plane+0xa9/0xf0 [drm_kms_helper]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471605]  [] 
__setplane_internal+0x169/0x250 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471638]  [] 
? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471669]  [] 
drm_mode_setplane+0x136/0x1b0 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471692]  [] 
drm_ioctl+0x152/0x540 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471719]  [] 
? drm_plane_check_pixel_format+0x50/0x50 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471726]  [] 
do_vfs_ioctl+0x29f/0x490
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471734]  [] 
? __sb_end_write+0x21/0x30
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471740]  [] 
? vfs_write+0x15d/0x1a0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471744]  [] 
SyS_ioctl+0x79/0x90
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471753]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471857]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471860] Restarting tasks ... 
done.
- 
  
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.433922] [ cut 
here ]
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434020] WARNING: CPU: 2 PID: 
1109 at 
/build/linux-FvcHlK/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3963 
intel_crtc_wait_for_pending_flips+0x1e2/0x240 [i915]()
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434025] 
WARN_ON(wait_event_timeout(dev_priv->pending_flip_queue, 
!intel_crtc_has_pending_flip(crtc), 60*HZ) == 0)
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434028] Modules linked in: 
drbg ansi_cprng nvram rfcomm cdc_ether usbnet r8152 mii bnep xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp 
joydev input_leds btusb btrtl pci_stub btbcm btintel bluetooth vboxpci(OE) 
bcm5974 vboxnetadp(OE) vboxnetflt(OE) bridge vboxdrv(OE) stp llc iptable_filter 
msr ip_tables x_tables nls_iso8859_1 applesmc input_polldev 
snd_hda_codec_cirrus snd_hda_codec_hdmi snd_hda_codec_generic brcmfmac brcmutil 
cfg80211 thunderbolt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
bdc_pci kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_intel 

[Desktop-packages] [Bug 1589893] Re: Xorg crashes

[Kevin]

Xorg crashed about ~10 times a working day. (every ~45min)

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

Title:
  Xorg crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471186] Freezing of tasks 
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471220] XorgD 
880089ccfa78 0  1109   1099 0x0044
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471230]  880089ccfa78 
812cbfa8 880264d99b80 88025d45
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471237]  880089cd 
880089ccfab0 88026ec8dd00 88026ec8dd00
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471242]  0001 
880089ccfa90 81821205 00010018eca0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471248] Call Trace:
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471263]  [] 
? __ext4_handle_dirty_metadata+0x48/0x1f0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471272]  [] 
schedule+0x35/0x80
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471278]  [] 
schedule_timeout+0x129/0x270
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471287]  [] 
? trace_event_raw_event_tick_stop+0x120/0x120
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471370]  [] 
intel_crtc_wait_for_pending_flips+0xa6/0x240 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471378]  [] 
? wake_atomic_t_function+0x60/0x60
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471425]  [] 
intel_pre_plane_update+0x111/0x140 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471469]  [] 
intel_atomic_commit+0x352/0x6f0 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471520]  [] 
? drm_atomic_check_only+0x18e/0x590 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471551]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471575]  [] 
drm_atomic_helper_disable_plane+0xa9/0xf0 [drm_kms_helper]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471605]  [] 
__setplane_internal+0x169/0x250 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471638]  [] 
? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471669]  [] 
drm_mode_setplane+0x136/0x1b0 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471692]  [] 
drm_ioctl+0x152/0x540 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471719]  [] 
? drm_plane_check_pixel_format+0x50/0x50 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471726]  [] 
do_vfs_ioctl+0x29f/0x490
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471734]  [] 
? __sb_end_write+0x21/0x30
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471740]  [] 
? vfs_write+0x15d/0x1a0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471744]  [] 
SyS_ioctl+0x79/0x90
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471753]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471857]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471860] Restarting tasks ... 
done.

  
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.433922] [ cut 
here ]
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434020] WARNING: CPU: 2 PID: 
1109 at 
/build/linux-FvcHlK/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3963 
intel_crtc_wait_for_pending_flips+0x1e2/0x240 [i915]()
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434025] 
WARN_ON(wait_event_timeout(dev_priv->pending_flip_queue, 
!intel_crtc_has_pending_flip(crtc), 60*HZ) == 0)
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434028] Modules linked in: 
drbg ansi_cprng nvram rfcomm cdc_ether usbnet r8152 mii bnep xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp 
joydev input_leds btusb btrtl pci_stub btbcm btintel bluetooth vboxpci(OE) 
bcm5974 vboxnetadp(OE) vboxnetflt(OE) bridge vboxdrv(OE) stp llc iptable_filter 
msr ip_tables x_tables nls_iso8859_1 applesmc input_polldev 
snd_hda_codec_cirrus snd_hda_codec_hdmi snd_hda_codec_generic brcmfmac brcmutil 
cfg80211 thunderbolt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
bdc_pci kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event 
snd_rawmidi intel_pch_thermal snd_seq lpc_ich snd_seq_device snd_timer snd 
mei_me mei shpchp soundcore sbs sbshc a
 cpi_als kfifo_buf industrialio spi_pxa2xx_platform apple_bl mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic hid_apple usbhid hid uas usb_storage i915 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt 

[Desktop-packages] [Bug 1589893] Re: Xorg crashes

[Christopher M. Penalver]

Kevin, to clarify, how often would the crashing happen if you were using
the default Ubuntu kernel?

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

Title:
  Xorg crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471186] Freezing of tasks 
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471220] XorgD 
880089ccfa78 0  1109   1099 0x0044
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471230]  880089ccfa78 
812cbfa8 880264d99b80 88025d45
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471237]  880089cd 
880089ccfab0 88026ec8dd00 88026ec8dd00
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471242]  0001 
880089ccfa90 81821205 00010018eca0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471248] Call Trace:
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471263]  [] 
? __ext4_handle_dirty_metadata+0x48/0x1f0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471272]  [] 
schedule+0x35/0x80
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471278]  [] 
schedule_timeout+0x129/0x270
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471287]  [] 
? trace_event_raw_event_tick_stop+0x120/0x120
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471370]  [] 
intel_crtc_wait_for_pending_flips+0xa6/0x240 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471378]  [] 
? wake_atomic_t_function+0x60/0x60
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471425]  [] 
intel_pre_plane_update+0x111/0x140 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471469]  [] 
intel_atomic_commit+0x352/0x6f0 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471520]  [] 
? drm_atomic_check_only+0x18e/0x590 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471551]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471575]  [] 
drm_atomic_helper_disable_plane+0xa9/0xf0 [drm_kms_helper]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471605]  [] 
__setplane_internal+0x169/0x250 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471638]  [] 
? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471669]  [] 
drm_mode_setplane+0x136/0x1b0 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471692]  [] 
drm_ioctl+0x152/0x540 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471719]  [] 
? drm_plane_check_pixel_format+0x50/0x50 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471726]  [] 
do_vfs_ioctl+0x29f/0x490
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471734]  [] 
? __sb_end_write+0x21/0x30
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471740]  [] 
? vfs_write+0x15d/0x1a0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471744]  [] 
SyS_ioctl+0x79/0x90
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471753]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471857]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471860] Restarting tasks ... 
done.

  
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.433922] [ cut 
here ]
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434020] WARNING: CPU: 2 PID: 
1109 at 
/build/linux-FvcHlK/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3963 
intel_crtc_wait_for_pending_flips+0x1e2/0x240 [i915]()
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434025] 
WARN_ON(wait_event_timeout(dev_priv->pending_flip_queue, 
!intel_crtc_has_pending_flip(crtc), 60*HZ) == 0)
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434028] Modules linked in: 
drbg ansi_cprng nvram rfcomm cdc_ether usbnet r8152 mii bnep xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp 
joydev input_leds btusb btrtl pci_stub btbcm btintel bluetooth vboxpci(OE) 
bcm5974 vboxnetadp(OE) vboxnetflt(OE) bridge vboxdrv(OE) stp llc iptable_filter 
msr ip_tables x_tables nls_iso8859_1 applesmc input_polldev 
snd_hda_codec_cirrus snd_hda_codec_hdmi snd_hda_codec_generic brcmfmac brcmutil 
cfg80211 thunderbolt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
bdc_pci kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event 
snd_rawmidi intel_pch_thermal snd_seq lpc_ich snd_seq_device snd_timer snd 
mei_me mei shpchp soundcore sbs sbshc a
 cpi_als kfifo_buf industrialio spi_pxa2xx_platform apple_bl mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic hid_apple usbhid hid uas usb_storage i915 
i2c_algo_bit drm_kms_helper 

[Desktop-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

[Christopher M. Penalver]

Roger Merritt:
>"successfully installed the mainline kernel 4.6-rc6"

Did you test 4.7-rc6, or 4.6-rc6?

>"Apparently the problem is not in the kernel."

The test you did wasn't enough to conclude that.

Despite this, could you please test 4.4.13 (this is the kernel that
Xenial is based off of) and advise to the results?

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

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .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
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  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: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
 

[Desktop-packages] [Bug 1599792] [NEW] bug report

[Chandrashekar]

Public bug reported:

Cant install nvidia driver for gtx970 card.after install and restart
display gets to low graphics mode and cant login.need a fix.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Thu Jul  7 15:57:43 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:1366]
InstallationDate: Installed on 2016-07-07 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=fcd176d6-6b12-4613-995f-3864ac4a59d1 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A99FX PRO R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
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: Thu Jul  7 15:52:15 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install ubuntu 
xenial

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

Title:
  bug report

Status in xorg package in Ubuntu:
  New

Bug description:
  Cant install nvidia driver for gtx970 card.after install and restart
  display gets to low graphics mode and cant login.need a fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Thu Jul  7 15:57:43 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] 
[19da:1366]
  InstallationDate: Installed on 2016-07-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=fcd176d6-6b12-4613-995f-3864ac4a59d1 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  

[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running

[Michael Thayer]

Actually, perhaps I misunderstand the lightdm log rotation and the .1
logfile does contain the relevant log.  I assume the lightdm developers
will know.

My uneducated guess is that there is some sort of race here between
lightdm and logind which needs better dependency specification.

And I just checked that I do not always see this on a clean reboot
either.

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

Title:
  "low-graphics mode" in VirtualBox guest, but X server running

Status in lightdm package in Ubuntu:
  New

Bug description:
  I sometimes get the "low-graphics mode" message when starting an
  Ubuntu 16.04 virtual machine inside of VirtualBox (current development
  code trunk, somewhere past version 5.1 beta 3 and a debug build).
  When I switch to VT-7 I find the X server running without any visible
  issues (I am the upstream developer of the guest graphics drivers, so
  I have a reasonable but not infallible understanding of the X server).

  The virtual machine has Guest Additions installed, same vintage and
  also a debug build.  Two screens are enabled as is 3D acceleration.
  The host system is also Ubuntu 16.04.  I am still trying to work out
  what triggers the message, but in my last attempts a cold boot failed
  to produce it, while a clean reboot did, but only when the host system
  was not under load (under load as in building VirtualBox).

  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/1599775/+subscriptions

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

[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running

[Michael Thayer]

Just checked, I do not have that message in the current log file,
attached the file from yesterday containing the message.

I asked about this on #ubuntu-devel, here are the relevant logs:

(17:09:06) michael-vb: Afternoon.  Not sure if this is the right place to ask, 
but someone will probably know what is.
(17:09:06) michael-vb: I have the following problem with my VirtualBox Ubuntu 
16.04 guest with development Guest Additions installed: when I start the guest 
I get the message "The system is running in low-graphics mode" (on VT 2) even 
though the X server is running fine (on VT 7).
(17:09:06) michael-vb: I would very much like to know exactly what logic 
triggers that message so I can work out why I am triggering it and change 
whatever is responsible (I am the developer of the VirtualBox guest driver and 
Additions installer).

(18:04:34) michael-vb: Interesting - I just booted the guest system
twice with a loaded host (rebuilding VirtualBox) and did not get the
"low-graphics mode" message.

(18:27:01) michael-vb: CRITICAL: session_get_login1_session_id:
assertion 'session != NULL' failed in the lightdm log file.

(18:31:13) michael-vb: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=814760

(09:57:21) sladen: michael-vb: 
http://askubuntu.com/questions/141606/how-to-fix-the-system-is-running-in-low-graphics-mode-error
(09:57:35) michael-vb: Found that already.

(09:57:50) michael-vb: I am wanting to understand this as a developer,
not as a user.

(09:59:07) michael-vb: sladen: it was following from that askubuntu question 
that I found the system log entry.
(09:59:34) michael-vb: The session clearly gets started just after lightdm 
checks whether it is running.
(10:01:04) michael-vb: As I said, this does not happen under high load.  I 
suppose the question is, who would understand this stuff well enough to tell me 
how I can avoid triggering it.
(10:01:15) michael-vb: Or what causes the session to start too late, or lightdm 
too early.
(10:03:00) michael-vb: I assume that some dependency is not specified well 
enough somewhere.
(10:03:31) sladen: michael-vb: apt-get source lightdm && grep -r "Error 
message"   is probably the most effective way of identifing the logic causing 
the error (if it is coming from lightdm)
(10:03:31) michael-vb: But it is annoying, because if it hits users they will 
blame us first, not you!

(10:04:15) sladen: michael-vb: I'm not too familiar with the inner workings of 
lightdm; the developer was Robert Ancell in the DX team
(10:04:57) sladen: michael-vb: if it's happening so of the time (seemingly 
randomly), then there's probably a race condition
(10:06:33) michael-vb: I'm sort of suspecting that it is related to the change 
to systemd which upset some expectation in lightdm.
(10:08:13) sladen: willcooke: if you're around later, could you get in contact 
with michael-vb (upstream developer of VirtualBox guest driver), about 
debugging and resolving the "The system is running in low-graphics mode" 
message.  https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 
onwards
(10:08:50) michael-vb: willcooke: and michael dot thayer at oracle if I am not 
on IRC at that time.
(10:08:56) michael-vb: sladen, willcooke: thanks.
(10:10:59) willcooke: Trevinho, is this something you can help with? ^
(10:11:09) willcooke: It looks like it's a problem with X rather than Unity 
though
(10:11:13) willcooke: "problem"
(10:11:22) willcooke: maybe tjaalton knows what triggers it? ^
(10:13:46) talatb [~talatb@137.158.22.10] entered the room.
(10:14:23) tjaalton: I don't, if lightdm is randomly not starting on debian 
(which doesn't have "failsafe-x")
(10:15:20) tjaalton: sounds like a lightdm bug to me
(10:16:59) willcooke: oki
(10:17:04) willcooke: thanks tjaalton
(10:30:07) willcooke: michael-vb, Hmm, I can't see anything obvious here.  
Please log a bug in Ubuntu against lightdm if there isn't already one, and we 
take take a look.
(10:30:54) michael-vb: willcooke: to me it sounds like an init dependency 
problem.
(10:31:18) sladen: michael-vb: can we get as much of the (known good) 
information into a Launchpad bug report
(10:31:34) michael-vb: If I understood all this GNOME-systemd-login stuff 
better...
(10:31:41) michael-vb: sladen: sounds reasonable.
(10:31:44) sladen: michael-vb: and then get that linked to/from the debbugs and 
Askubuntu pages
(10:33:25) michael-vb: Oh how nice, for reasons unknown I can no longer trigger 
it.
(10:33:34) willcooke: \o/
(10:33:47) willcooke: fixed!
(10:34:00) willcooke: certainly smells like a race then
(10:34:23) michael-vb: I think that is clear enough from the Debian bug.
(10:34:47) michael-vb: I think that someone from the systemd camp would be best 
placed to solve it.
(10:36:07) michael-vb: But before I open a bug report I will at least try to 
track down the error in the lightdm sources.
(10:39:45) sladen: yes, it would be good to point in the bug report exactly 
where the origin of the assert is coming from, but if it 

[Desktop-packages] [Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running

[Michael Thayer]

** Attachment added: "The log file from yesterday."
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+attachment/4696780/+files/lightdm.log.1

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

Title:
  "low-graphics mode" in VirtualBox guest, but X server running

Status in lightdm package in Ubuntu:
  New

Bug description:
  I sometimes get the "low-graphics mode" message when starting an
  Ubuntu 16.04 virtual machine inside of VirtualBox (current development
  code trunk, somewhere past version 5.1 beta 3 and a debug build).
  When I switch to VT-7 I find the X server running without any visible
  issues (I am the upstream developer of the guest graphics drivers, so
  I have a reasonable but not infallible understanding of the X server).

  The virtual machine has Guest Additions installed, same vintage and
  also a debug build.  Two screens are enabled as is 3D acceleration.
  The host system is also Ubuntu 16.04.  I am still trying to work out
  what triggers the message, but in my last attempts a cold boot failed
  to produce it, while a clean reboot did, but only when the host system
  was not under load (under load as in building VirtualBox).

  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/1599775/+subscriptions

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

[Desktop-packages] [Bug 1599775] [NEW] "low-graphics mode" in VirtualBox guest, but X server running

[Michael Thayer]

Public bug reported:

I sometimes get the "low-graphics mode" message when starting an Ubuntu
16.04 virtual machine inside of VirtualBox (current development code
trunk, somewhere past version 5.1 beta 3 and a debug build).  When I
switch to VT-7 I find the X server running without any visible issues (I
am the upstream developer of the guest graphics drivers, so I have a
reasonable but not infallible understanding of the X server).

The virtual machine has Guest Additions installed, same vintage and also
a debug build.  Two screens are enabled as is 3D acceleration.  The host
system is also Ubuntu 16.04.  I am still trying to work out what
triggers the message, but in my last attempts a cold boot failed to
produce it, while a clean reboot did, but only when the host system was
not under load (under load as in building VirtualBox).

Searching the lightdm log files led me to the message "CRITICAL **:
session_get_login1_session_id: assertion 'session != NULL' failed",
which in turn led me to this similar-looking Debian bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul  7 10:49:27 2016
InstallationDate: Installed on 2016-06-08 (28 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  "low-graphics mode" in VirtualBox guest, but X server running

Status in lightdm package in Ubuntu:
  New

Bug description:
  I sometimes get the "low-graphics mode" message when starting an
  Ubuntu 16.04 virtual machine inside of VirtualBox (current development
  code trunk, somewhere past version 5.1 beta 3 and a debug build).
  When I switch to VT-7 I find the X server running without any visible
  issues (I am the upstream developer of the guest graphics drivers, so
  I have a reasonable but not infallible understanding of the X server).

  The virtual machine has Guest Additions installed, same vintage and
  also a debug build.  Two screens are enabled as is 3D acceleration.
  The host system is also Ubuntu 16.04.  I am still trying to work out
  what triggers the message, but in my last attempts a cold boot failed
  to produce it, while a clean reboot did, but only when the host system
  was not under load (under load as in building VirtualBox).

  Searching the lightdm log files led me to the message "CRITICAL **:
  session_get_login1_session_id: assertion 'session != NULL' failed",
  which in turn led me to this similar-looking Debian bug:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul  7 10:49:27 2016
  InstallationDate: Installed on 2016-06-08 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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/1599775/+subscriptions

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

[Desktop-packages] [Bug 1582803] Re: [SRU]bug report script uses invalid nm options

[Aron Xu]

@pitti, it's committed to git, needs an upload.

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

Title:
  [SRU]bug report script uses invalid nm options

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]
  Xenial reports have those warnings "Error: Object 'nm' is unknown, try 'nmcli 
help'." the "nm-cli" syntax changed and the hook needs to be updated

  [Test Case]
  Future apport report to errors.ubuntu.com should have proper information 
output from nmcli command, rather than throwing an error message.

  [Regression Potential]
  This is a simple change of the command line option on information collection, 
which should be safe.

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

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

[Desktop-packages] [Bug 1387011] Re: llvm cmake files incorrectly generated

[Paweł Bylica]

The same is for llvm-dev 3.8 in Ubuntu 16.04.

CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 (include):
  include could not find load file:

/usr/share/llvm/cmake/LLVMExports.cmake

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.5 in Ubuntu.
https://bugs.launchpad.net/bugs/1387011

Title:
  llvm cmake files incorrectly generated

Status in LLVM:
  Confirmed
Status in llvm package in Ubuntu:
  Confirmed
Status in llvm-defaults package in Ubuntu:
  Confirmed
Status in llvm-toolchain-3.5 package in Ubuntu:
  Confirmed

Bug description:
  CMake Error at /usr/share/llvm-3.5/cmake/LLVMExports.cmake:6 (set_property):
set_property could not find TARGET LLVMSupport.  Perhaps it has not yet
been created.
  Call Stack (most recent call first):
/usr/share/llvm-3.5/cmake/LLVMConfig.cmake:50 (include)
CMakeLists.txt:129 (find_package)

  this message is repeated (many times) for each library/target
  referenced in the LLVMExports.cmake file.

  upstream say they fixed it in svn revision 217484:
  http://llvm.org/viewvc/llvm-project?view=revision=217484

  affects utopic.

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

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

[Desktop-packages] [Bug 1582430] Re: spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already playing music

[Amr Ibrahim]

** Package changed: unity (Ubuntu) => bamf (Ubuntu)

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

Title:
  spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is
  already playing music

Status in bamf package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1. Start Rhythmbox.
  2. Play some music.
  3. Close the Rhythmbox window.
  4. Open Rhythmbox from Dash or Launcher (if Rhythmbox is locked to it).
  5. Admire annoying spinning wheel for about 13 seconds.

  
  If Rhythmbox is reopened from the sound tray menu it is ok, no spinning wheel.

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

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

[Desktop-packages] [Bug 1557026] Re: [SRU]Network Manager sets powersave off by default in xenial

[Martin Pitt]

** Changed in: network-manager (Ubuntu Yakkety)
   Status: In Progress => Fix Released

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

Title:
  [SRU]Network Manager sets powersave off by default in xenial

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  NetworkManager consumes more power than previous releases because powersave 
support is not updated.

  [Test Case]
  With the patch applied, network device power management should be on when 
supported, for example:

  $ sudo iwconfig wlan0 | grep "Power Management"
Power Management:on

  [Regression Potential]
  Regression may happen when the power management feature of certain device 
isn't implemented properly in kernel, but since we are quite conservative on 
enabling power management in kernel development such case should be rare.

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

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

[Desktop-packages] [Bug 1582803] Re: [SRU]bug report script uses invalid nm options

[Martin Pitt]

Please fix this in yakkety first, as per SRU rules.

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  [SRU]bug report script uses invalid nm options

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]
  Xenial reports have those warnings "Error: Object 'nm' is unknown, try 'nmcli 
help'." the "nm-cli" syntax changed and the hook needs to be updated

  [Test Case]
  Future apport report to errors.ubuntu.com should have proper information 
output from nmcli command, rather than throwing an error message.

  [Regression Potential]
  This is a simple change of the command line option on information collection, 
which should be safe.

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

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

[Desktop-packages] [Bug 1582430] [NEW] spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already playing music

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Steps to reproduce:

1. Start Rhythmbox.
2. Play some music.
3. Close the Rhythmbox window.
4. Open Rhythmbox from Dash or Launcher (if Rhythmbox is locked to it).
5. Admire annoying spinning wheel for about 13 seconds.


If Rhythmbox is reopened from the sound tray menu it is ok, no spinning wheel.

** Affects: bamf (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress


** Tags: bot-comment
-- 
spinning wheel when opening Rhythmbox from Dash/Launcher WHEN it is already 
playing music
https://bugs.launchpad.net/bugs/1582430
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to bamf in Ubuntu.

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

[Desktop-packages] [Bug 1599759] [NEW] Hi, good day. Please add 3D Warehouse webapp of Sketchup. thank you very much

[Richard Hanz Kalaw]

Public bug reported:

Hi, good day. Please add 3D Warehouse webapp of Sketchup. thank you very
much

** Affects: webapps-applications (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webapps-applications in Ubuntu.
https://bugs.launchpad.net/bugs/1599759

Title:
  Hi, good day. Please add 3D Warehouse webapp of Sketchup. thank you
  very much

Status in webapps-applications package in Ubuntu:
  New

Bug description:
  Hi, good day. Please add 3D Warehouse webapp of Sketchup. thank you
  very much

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1599759/+subscriptions

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

[Desktop-packages] [Bug 1339820] Re: Preventing fraudulent flash memory

[Bug Watch Updater]

** Changed in: gnome-disk-utility
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1339820

Title:
  Preventing fraudulent flash memory

Status in GNOME Disks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  Do a simple Google search or eBay search for microSD or FLASH memory
  and you'll quickly realize something: There are some great prices out
  there! That is, until you actually get the memory device in your
  hands, test it out, and it fails within a matter of hours. There needs
  to be something out there, a common technology practice, to correctly
  and accurately test these memory modules the first time the user plugs
  in the device in order to prevent imminent data failure at an
  unexpected moment.

  I have the idea for the GNOME Disk Utility in Ubuntu -- To accurately
  test any new memory module installed with the consent of the user the
  second the module is plugged in and allowed to gain ROOT access to the
  filesystem. A simple test like this can save the general public tonnes
  of money when it comes to buying memory, keep malicious codes from
  entering our loved computer systems, and help educate us on how to
  choose the correct memory technology, where to buy it, and what to
  look for, etc.. Included in this idea I have is an optional form to
  report certain module types into a larger database that is
  interconnected between all computers using the GNOME Disk Utility and
  connected to the internet for even faster emergency diagnosis with
  instant fraudulent device recognition that will then push a warning to
  the user to remove the module at once and a set of instructions on how
  to properly request a refund for their counterfeit device.

  Something like this has never before been integrated into mainstream
  computing methods, and it's about time a smart, automated, self-
  learning, user-teaching system like this is implemented.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-disk-utility 3.10.0-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul  9 13:15:58 2014
  InstallationDate: Installed on 2014-02-19 (140 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (82 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1339820/+subscriptions

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

[Desktop-packages] [Bug 1589893] Re: Xorg crashes

[Kevin]

Hi,

Im working now with 4.7.0-040700rc5-generic on Ubuntu 16.04 LTS.

no crashes since 4 days. Hurray!

Cheers,
Kevin

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

Title:
  Xorg crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471186] Freezing of tasks 
failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0):
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471220] XorgD 
880089ccfa78 0  1109   1099 0x0044
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471230]  880089ccfa78 
812cbfa8 880264d99b80 88025d45
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471237]  880089cd 
880089ccfab0 88026ec8dd00 88026ec8dd00
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471242]  0001 
880089ccfa90 81821205 00010018eca0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471248] Call Trace:
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471263]  [] 
? __ext4_handle_dirty_metadata+0x48/0x1f0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471272]  [] 
schedule+0x35/0x80
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471278]  [] 
schedule_timeout+0x129/0x270
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471287]  [] 
? trace_event_raw_event_tick_stop+0x120/0x120
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471370]  [] 
intel_crtc_wait_for_pending_flips+0xa6/0x240 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471378]  [] 
? wake_atomic_t_function+0x60/0x60
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471425]  [] 
intel_pre_plane_update+0x111/0x140 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471469]  [] 
intel_atomic_commit+0x352/0x6f0 [i915]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471520]  [] 
? drm_atomic_check_only+0x18e/0x590 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471551]  [] 
drm_atomic_commit+0x37/0x60 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471575]  [] 
drm_atomic_helper_disable_plane+0xa9/0xf0 [drm_kms_helper]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471605]  [] 
__setplane_internal+0x169/0x250 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471638]  [] 
? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471669]  [] 
drm_mode_setplane+0x136/0x1b0 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471692]  [] 
drm_ioctl+0x152/0x540 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471719]  [] 
? drm_plane_check_pixel_format+0x50/0x50 [drm]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471726]  [] 
do_vfs_ioctl+0x29f/0x490
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471734]  [] 
? __sb_end_write+0x21/0x30
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471740]  [] 
? vfs_write+0x15d/0x1a0
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471744]  [] 
SyS_ioctl+0x79/0x90
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471753]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471857]
  Jun  7 11:40:18 kevin-MacBookPro kernel: [ 6818.471860] Restarting tasks ... 
done.

  
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.433922] [ cut 
here ]
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434020] WARNING: CPU: 2 PID: 
1109 at 
/build/linux-FvcHlK/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:3963 
intel_crtc_wait_for_pending_flips+0x1e2/0x240 [i915]()
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434025] 
WARN_ON(wait_event_timeout(dev_priv->pending_flip_queue, 
!intel_crtc_has_pending_flip(crtc), 60*HZ) == 0)
  Jun  7 11:41:55 kevin-MacBookPro kernel: [ 6833.434028] Modules linked in: 
drbg ansi_cprng nvram rfcomm cdc_ether usbnet r8152 mii bnep xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp 
joydev input_leds btusb btrtl pci_stub btbcm btintel bluetooth vboxpci(OE) 
bcm5974 vboxnetadp(OE) vboxnetflt(OE) bridge vboxdrv(OE) stp llc iptable_filter 
msr ip_tables x_tables nls_iso8859_1 applesmc input_polldev 
snd_hda_codec_cirrus snd_hda_codec_hdmi snd_hda_codec_generic brcmfmac brcmutil 
cfg80211 thunderbolt intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
bdc_pci kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event 
snd_rawmidi intel_pch_thermal snd_seq lpc_ich snd_seq_device snd_timer snd 
mei_me mei shpchp soundcore sbs sbshc a
 cpi_als kfifo_buf industrialio spi_pxa2xx_platform apple_bl mac_hid parport_pc 
ppdev lp parport autofs4 hid_generic hid_apple usbhid hid uas usb_storage i915 
i2c_algo_bit 

Re: [Desktop-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

[Roger Merritt]

Luckily I had a 32 GB SanDisk USB 3.0 flash drive on hand (the one that was
farkled by trying to upgrade 15.10 to 16.04), so I installed 15.10 on it
and upgraded. I didn't add any programs, so this is vanilla 15.10. I
followed the instructions at the link you gave and successfully installed
the mainline kernel 4.6-rc6. Restarting, I successfully used the new kernel
to boot into 15.10. I don't have any complex programs other than Mozilla
Firefox to run on this installation, but it seems to be working fine.
Apparently the problem is not in the kernel.

On Tue, Jul 5, 2016 at 6:15 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Roger Merritt, to further narrow this down, could you please test the
> latest mainline kernel (4.7-rc6) following
> https://wiki.ubuntu.com/Kernel/MainlineBuilds and advise to the results?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1584284
>
> Title:
>   Ubuntu 16.04 LiveCD does not boot on AMD A10 chip
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD
> A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no
> graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I
> try to boot I get an error message, "ERROR: no UMS support in radeon
> module." When I edit the boot command line to add the parameter 'nomodeset'
> I first get an error message, "No UMS support on radeon module," then the
> familiar aubergine background with the ubuntu logo and the five dots below
> it changing from white to red and back again. After twenty or thirty
> seconds the background goes to black, I get the error message "No UMS
> support in radeon module," and the ubuntu logo disappears but the five dots
> continue. After another twenty or thirty seconds of that the screen clears,
> at the top is a line: "ubuntu 16.04 ubuntu LTS tty1," below that the line
> "ubuntu login:" and after a second or less the screen goes black and I
> can't do anything except reboot. I've tried old Live CDs, from 10.10 to
> 15.10, and they all boot fine.
>   ---
>   .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
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroRelease: Ubuntu 15.10
>   DistroVariant: ubuntu
>   DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D]
> [1002:9901] (prog-if 00 [VGA controller])
>  Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD
> 7660D] [1002:9901]
>   InstallationDate: Installed on 2016-06-07 (27 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
>   Package: xorg 1:7.7+7ubuntu4
>   PackageArchitecture: amd64
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic
> root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
>   Tags:  wily ubuntu compiz-0.9
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   Uname: Linux 4.2.0-36-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   _MarkForUpload: True
>   dmi.bios.date: 03/18/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: F4
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: F2A75M-HD2
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: To be filled by O.E.M.
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.chassis.version: To Be Filled By O.E.M.
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
>   dmi.product.name: To be filled by O.E.M.
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>   version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
>   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
>   

[Desktop-packages] [Bug 1598102] Re: Xorg crashed with SIGABRT in OsAbort()

[Launchpad Bug Tracker]

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

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

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1598102

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in nvidia-graphics-drivers package in Ubuntu:
  Confirmed

Bug description:
  from update and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: xserver-xorg-core 2:1.18.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.6.0-7.8-generic 4.6.0
  Uname: Linux 4.6.0-7-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.27  Thu Jun  9 18:53:27 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-4ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Jun 28 14:59:16 2016
  DistUpgraded: 2016-06-13 21:19:44,198 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.6.0-7-generic, x86_64: installed
   nvidia-367, 367.27, 4.6.0-7-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] 
[19da:1375]
  InstallationDate: Installed on 2016-06-06 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-7-generic 
root=UUID=17c413ea-eca0-4425-9b8f-8b77561bd0fa ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x561b36c411c0, argc=11, argv=0x7fffa27e4948, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffa27e4938) at ../csu/libc-start.c:291
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to yakkety on 2016-06-14 (17 days ago)
  UserGroups:
   
  dmi.bios.date: 05/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/28/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.0+16.10.20160628-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.68+git1606300630.7996a8~gd~x
  version.libgl1-mesa-dri: libgl1-mesa-dri 
12.1~git160618002200.6b0ac95c~x~padoka0
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
12.1~git160618002200.6b0ac95c~x~padoka0
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.7.99+git1606280732.3be841~gd~x
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1606251933.cac7c8~gd~x
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Desktop-packages] [Bug 1563155] Re: No Application Data Found

[Jeromie Rand]

None of the above worked for me. Instead, there were several plugins
that gave the following error:

Failed to parse /usr/share/app-info/xmls/org.freedesktop.fwupd.xml file:
cannot process file of type application/x-go+xml

I later got a similar error at /var/cache/app-info/xmls/fwupd.xml

For the time being, I removed the fwupd.xml files (after making a
backup) and all works fine again. When I check the mimetype it shows
application/xml; I'm not sure where the application/x-go+xml is coming
from.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1563155

Title:
  No Application Data Found

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I installed ubuntu 16.04 and when I go to the gnome software, it says
  "No Application Data Found". It is all greyed out and no apps are
  available for download.

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

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