[Desktop-packages] [Bug 1319970] Re: speed-dispatcher user needs a restricted shell (/usr/sbin/nologin or /bin/false) instead of /bin/sh.

[Bug Watch Updater]

** Changed in: speech-dispatcher (Debian)
   Status: New => Fix Committed

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

Title:
  speed-dispatcher user needs a restricted shell (/usr/sbin/nologin or
  /bin/false) instead of /bin/sh.

Status in Speech Dispatcher:
  New
Status in speech-dispatcher package in Ubuntu:
  Fix Released
Status in speech-dispatcher source package in Trusty:
  Confirmed
Status in speech-dispatcher source package in Utopic:
  Fix Released
Status in speech-dispatcher package in Debian:
  Fix Committed

Bug description:
  antarus@killbot:~$ getent passwd speech-dispatcher
  speech-dispatcher:x:113:29:Speech 
Dispatcher,,,:/var/run/speech-dispatcher:/bin/sh

  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)"
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04

  antarus@killbot:~$ apt-cache policy speech-dispatcher
  speech-dispatcher:
Installed: 0.8-5ubuntu1
Candidate: 0.8-5ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/speech-dispatcher/+bug/1319970/+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 1578260] Re: rhythmbox crashed with SIGABRT in Py_FatalError()

[Walter Garcia-Fontes]

This is a bug in rhythmbox-plugin-radio-browser. If this pluing is disabled I 
cannot reproduce it. I have reported the bug in the issue tracker for this 
plugin:
https://github.com/fossfreedom/radio-browser/issues/18

** No longer affects: rhythmbox

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

Title:
  rhythmbox crashed with SIGABRT in Py_FatalError()

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Rhythmbox crashes systematically with the following steps:

  1) Open Rhythmbox
  2) Hear a podcast and put Rhythmbox into the background
  3) When the podcast finishes, click on the app-indicator to put Rhythmbox in 
the foreground.

  What should happen?: Rhythmbox should go to the foreground.
  What happens actually? Rhythmbox crashes.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: rhythmbox 3.3-1ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  4 17:01:29 2016
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2015-10-17 (199 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: rhythmbox
  Signal: 6
  SourcePackage: rhythmbox
  StacktraceTop:
   Py_FatalError () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
   _Py_CheckRecursiveCall () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
   PyObject_Call () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
   _PyObject_CallMethodId () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
   ?? () from /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
  Title: rhythmbox crashed with SIGABRT in Py_FatalError()
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (54 days ago)
  UserGroups: adm cdrom dip lpadmin mail plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1578260/+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 1581316] [NEW] package xbrlapi 5.3.1-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Clicque Dimitri]

Public bug reported:

no idea, i follow what i'm told by ubuntu

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xbrlapi 5.3.1-2ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Thu May 12 22:22:47 2016
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-03-08 (65 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: brltty
Title: package xbrlapi 5.3.1-2ubuntu2.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to xenial on 2016-04-23 (19 days ago)

** Affects: brltty (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 brltty in Ubuntu.
https://bugs.launchpad.net/bugs/1581316

Title:
  package xbrlapi 5.3.1-2ubuntu2.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in brltty package in Ubuntu:
  New

Bug description:
  no idea, i follow what i'm told by ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xbrlapi 5.3.1-2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu May 12 22:22:47 2016
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-03-08 (65 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: brltty
  Title: package xbrlapi 5.3.1-2ubuntu2.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (19 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1581316/+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 1574347] Re: [SRU]network-manager

[Cip Man]

@Pinghao Qi, which issue did the stable version fixed for you, as there
are several bug reports merged/duplicated/etc here?

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

Title:
  [SRU]network-manager

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

  [Testcase]

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1580852] Re: not adjustable sound level

[Www]

** Package changed: plasma-workspace (Ubuntu) => pulseaudio (Ubuntu)

** Summary changed:

- not adjustable sound level
+ Xonar DSX AV200 not adjustable sound level

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

Title:
  Xonar DSX AV200 not adjustable sound level

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  sound card asus Xonar DSX AV200
  integrated sound card disable in bios

  tested bug ubuntu 16.04 and kubuntu 16.04 wich update 12.05.2016
  ubuntu 15.10 everything worked correctly

  changing the volume level in the gui, but it will not change

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 12 11:23:28 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/plasmashell
  InstallationDate: Installed on 2016-04-24 (17 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: plasma-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (process:3737): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
   (process:1876): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
   (process:4369): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
   (process:16310): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
   (process:22292): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1580852/+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 1580852] [NEW] not adjustable sound level

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

sound card asus Xonar DSX AV200
integrated sound card disable in bios

tested bug ubuntu 16.04 and kubuntu 16.04 wich update 12.05.2016
ubuntu 15.10 everything worked correctly

changing the volume level in the gui, but it will not change

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: plasma-workspace 4:5.5.5.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Thu May 12 11:23:28 2016
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/plasmashell
InstallationDate: Installed on 2016-04-24 (17 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: plasma-workspace
UpgradeStatus: No upgrade log present (probably fresh install)
XsessionErrors:
 (process:3737): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
 (process:1876): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
 (process:4369): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
 (process:16310): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
 (process:22292): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed

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


** Tags: amd64 apport-bug xenial
-- 
not adjustable sound level
https://bugs.launchpad.net/bugs/1580852
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio 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 1555528] Re: video eror

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  video eror

Status in xorg package in Ubuntu:
  Expired

Bug description:
  graphics driver trouble

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Mar 10 05:12:13 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304, 304.131, 4.2.0-30-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Super Micro Computer Inc Device [15d9:be80]
  InstallationDate: Installed on 2016-03-08 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Supermicro C2SBC-Q
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync plymouth:debug splash quiet 
drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 1.0a
  dmi.board.name: C2SBC-Q
  dmi.board.vendor: Supermicro
  dmi.board.version: PCB Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr1.0a:bd07/24/2008:svnSupermicro:pnC2SBC-Q:pvr0123456789:rvnSupermicro:rnC2SBC-Q:rvrPCBVersion:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.name: C2SBC-Q
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Mar 10 04:33:08 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Generic Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16388 
   vendor DEL
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/128/+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 1555396] Re: prolems since installing XFCE

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  prolems since installing XFCE

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Moved from 13 install to 14.04 with x package launching gone wrong
  jre  and cant get on wifi since also virgin renewed braodband to their
  wireless

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-81.125-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-81-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Mar 10 00:40:25 2016
  DistUpgraded: 2015-03-20 21:21:55,400 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Device [104d:9045]
 Subsystem: Sony Corporation Device [104d:9045]
  InstallationDate: Installed on 2013-11-04 (856 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: Sony Corporation VGN-NS30E_S
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-81-generic 
root=UUID=ed93e881-2d1e-4946-be4b-ea65464345b4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2015-03-20 (355 days ago)
  dmi.bios.date: 08/26/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R2030Y3
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR2030Y3:bd08/26/2009:svnSonyCorporation:pnVGN-NS30E_S:pvrC601HGS5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-NS30E_S
  dmi.product.version: C601HGS5
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  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: Wed Mar  9 20:42:49 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1555396/+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 1555136] Re: Trash won't empty files

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Trash won't empty files

Status in xorg package in Ubuntu:
  Expired

Bug description:
  
  Can't delete files in trash, or in video file.  
  
trash:///%5Cmedia%5Ccharles%5CWD%2520USB%25202%5C.Trash-D7BCDE0.mp4.ntfs-3g-60

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .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: None
  Date: Wed Mar  9 08:15:44 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:8175]
  InstallationDate: Installed on 2016-03-01 (8 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: HP HP 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=6c4a3056-49a0-423f-b4cc-c32ae33bd7b2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8175
  dmi.board.vendor: HP
  dmi.board.version: 37.08
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd08/27/2015:svnHP:pnHP15NotebookPC:pvrType1ProductConfigId:rvnHP:rn8175:rvr37.08:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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: Wed Mar  9 07:13:40 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20049 
   vendor SDC
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1555136/+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 1556008] Re: Resolution is incorrecrt

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Resolution is incorrecrt

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I want my resolution upto 1366 x 768 but I am unable to do it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Mar 11 15:16:58 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2002]
  InstallationDate: Installed on 2016-03-02 (9 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic 
root=UUID=465e2f14-4b70-46ba-b430-dbefef52a3b1 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0155.2012.0509.1620
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-211
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0155.2012.0509.1620:bd05/09/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-211:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-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 N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Mar 11 09:27:50 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPixArt USB Optical Mouse MOUSE, id 8
   input  USB Keyboard   KEYBOARD, id 9
   input  USB Keyboard   KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556008/+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 1556318] Re: display error on bootup

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  display error on bootup

Status in xorg package in Ubuntu:
  Expired

Bug description:
  all options followed on the net and installed intel driver problem
  still there hdmi resolution and mirror option disappear on boot

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .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
  Date: Sat Mar 12 12:06:39 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   i915-4.3.3-4.2.0, 2, 4.2.0-16-generic, x86_64: installed
   i915-4.3.3-4.2.0, 2, 4.2.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:0007]
  InstallationDate: Installed on 2016-03-07 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA PORTEGE R700
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=aab1172b-6f39-4c73-b80c-2f56c6aa9b25 ro drm.debug=0xe plymouth:debug 
splash quiet vesafb.invalid=1
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.50
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.50:bd08/26/2010:svnTOSHIBA:pnPORTEGER700:pvrPT310A-07F011:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE R700
  dmi.product.version: PT310A-07F011
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4-1intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
  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: Sat Mar 12 12:03:53 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1556318/+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 1580254] Re: Cannot change accounts images

[GSandSDS]

This bug also affects me. Fresh installed Ubuntu 16.04 followed by a
"sudo apt-get update" and a "sudo apt-get dist-upgrade".

Cannot change my own account image AND cannot change my own "full name"
(I mean the name that is displayed during login, not the real user
name). But I can change the image and full name of everyone else. If I
create a second account with administrator privileges, this account can
change my image and full name. The problem does also not occur when
using the console command "chfn -f".

If I remember correctly, I had no problems after a fresh installation
without any updates or upgrades. So maybe it has something to do with
the recent updates?

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

Title:
  Cannot change accounts images

Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  1. Go to "System Settings -> User Accounts"
  2. Click on the user image at the left of the user name, and select a new 
image.

  RESULT:
  Image isn't changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 10 18:28:06 2016
  InstallationDate: Installed on 2016-05-02 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1580254/+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 1580296] Re: Screen is blank and won't recover

[Chuck McManis]

See also 15801302 about monitor blanking. You can get the monitor back
on with xrandr --output DP1 --auto *if* you do that from an SSH session
(not from one of the alternate terminals)

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

Title:
  Screen is blank and won't recover

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running Xubuntu 16.04, I have reproduced this problem on both the
  Gigabyte Brix system and the NUC5i7RYH system. Both use integrated
  Intel graphics.

  The symptom is that after a long period of time (like overnight) the
  screen is blanked and moving the mouse or pressing keys on the
  keyboard will not switch the screen back on. Using Ctl-Alt-Fx will let
  me bring up an alternate VT however, so I can log in and look around.
  Switching back to VT7 (where Xubuntu is) the screen goes black again
  and won't wake up.

  The only error message I can find is in lightdm.log which is as
  follows:

  [160363.826] (II) intel(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 
2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
  [161295.000] (II) AIGLX: Suspending AIGLX clients for VT switch
  [161328.781] (II) AIGLX: Resuming AIGLX clients after VT switch
  [161328.781] (EE) intel(0): sna_mode_shutdown_crtc: invalid state found on 
pipe 0, disabling CRTC:21

  If I send a SIGHUP to the session manager it restarts and the screen
  wakes up with the Login screen again, that of course loses all my open
  windows from the previous session so it isn't really optimal.

  The lightdm log seems to suggest that it tried to "wake up" but that
  something happened that wasn't supposed to. When it isn't in this
  state (say for example I am up and running and I use Ctl-Alt-F2 to
  switch to Vt2 and then switch back to lightdm it works as expected and
  there is no error.

  I've set every parameter of every screen saver locker blanker etc to
  never suspend block or shutdown. And the screen still blanks. That
  makes me wonder what agency is turning off the screen.

  Let me know where to look and I'll add data to this bug. The situation
  is quite reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-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: None
  CurrentDesktop: XFCE
  Date: Tue May 10 11:30:30 2016
  DistUpgraded: 2016-04-29 22:17:07,822 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Haswell-ULT Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2016-03-18 (53 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: GIGABYTE MMLP5AP-00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=7a790f8d-8940-4397-a820-c35ca84f7696 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (10 days ago)
  dmi.bios.date: 08/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MMLP5AP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/29/2013:svnGIGABYTE:pnMMLP5AP-00:pvr1.x:rvnGIGABYTE:rnMMLP5AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: MMLP5AP-00
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  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: Tue May 10 11:00:37 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button

[Desktop-packages] [Bug 1581302] [NEW] Monitor remains blanked with Intel Graphics

[Chuck McManis]

Public bug reported:

Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port or 
HDMI
Running Xubuntu 16.04 - latest all current patches

Sometimes the monitor remains blanked even when the session has
reactivated.

I have been able to reproduce this problem by letting the monitor remain
in the 'blanked' state for > 60 minutes, or powering off the monitor.
When the monitor is powered back on and the session is woken up with
mouse or keyboard input, it does wake up but the monitor remains
blanked.

I was able to prove to myself the session was awake by leaving it with
terminal opened to full screen with VIM running on an NFS mounted file
system. I could type and save at the black monitor screen and see that
the file got updates from a different system. So the session is "live"
but the computer has forgotten to re-establish the DisplayPort link.

An error appears in the lightdm logs about setting a CRTC, if you
activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
--output DP1 --auto` it also registers that CRTC error. HOWEVER, if you
ssh in from a different machine, tell bash to export DISPLAY=:0 (set
$DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the screen
turns on again! This also happens on a Gigabyte BRIX system (same NUC
reference design but in that case a core i3 rather than a Core i7).

To reproduce, turn off the monitor, wait an hour, and turn it on again.

You can also kill HUP the lightdm process and that will restart a new
session (but open windows in the previous session are lost).

So interesting questions, why does typing xrandr "locally" give you the
error but running it from an ssh session work?

Since xrandr and restarting the session can both "fix" the problem, the
driver seems to know how to turn the display on if told correctly.

How can I find out where the code is getting the CRTC error?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu May 12 20:33:01 2016
InstallationDate: Installed on 2016-05-08 (4 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
LightdmLog:
 [+80180.09s] DEBUG: Seat seat0 changes active session to 
 [+80189.53s] DEBUG: Seat seat0 changes active session to 64
 [+80222.67s] DEBUG: Seat seat0 changes active session to c4
 [+80222.67s] DEBUG: Session c4 is already active
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/1581302

Title:
  Monitor remains blanked with Intel Graphics

Status in lightdm package in Ubuntu:
  New

Bug description:
  Running on a NUC5i7RYH, latest BIOS. ASUS Monitor connected via Display Port 
or HDMI
  Running Xubuntu 16.04 - latest all current patches

  Sometimes the monitor remains blanked even when the session has
  reactivated.

  I have been able to reproduce this problem by letting the monitor
  remain in the 'blanked' state for > 60 minutes, or powering off the
  monitor. When the monitor is powered back on and the session is woken
  up with mouse or keyboard input, it does wake up but the monitor
  remains blanked.

  I was able to prove to myself the session was awake by leaving it with
  terminal opened to full screen with VIM running on an NFS mounted file
  system. I could type and save at the black monitor screen and see that
  the file got updates from a different system. So the session is "live"
  but the computer has forgotten to re-establish the DisplayPort link.

  An error appears in the lightdm logs about setting a CRTC, if you
  activate an alternate terminal (say with CTL-ALT-F1) and try `xrandr
  --output DP1 --auto` it also registers that CRTC error. HOWEVER, if
  you ssh in from a different machine, tell bash to export DISPLAY=:0
  (set $DISPLAY to ':0') and then type 'xrandr --output DP1 --auto' the
  screen turns on again! This also happens on a Gigabyte BRIX system
  (same NUC reference design but in that case a core i3 rather than a
  Core i7).

  To reproduce, turn off the monitor, wait an hour, and turn it on
  again.

  You can also kill HUP the lightdm process and that will restart a new
  session (but open windows in the previous session are lost).

  So interesting questions, why does typing xrandr "locally" give you
  the error but running it from an ssh session work?

  Since xrandr and restarting the session can both "fix" the problem,
  the driver seems to know how to turn the display on if told correctly.

  How can I find out where the 

[Desktop-packages] [Bug 1571786] Re: Broadcom 43602 requires module to be reloaded to work

[Mike O'Connell]

Once you do this once, if you do a have a clean shutdown it continues to
work without removing and re-inserting the module.

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

Title:
  Broadcom 43602 requires module to be reloaded to work

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Running 16.04, and a recent update (last week?) introduced the
  following issue.

  I have a Broadcom wireless card:

  02:00.0 Network controller: Broadcom Corporation BCM43602 802.11ac
  Wireless LAN SoC (rev 01)

  Upon startup the network will connect fine.  Then after about a minute
  it will drop out.  Possibly related to the following in dmesg:

  [  163.870916] brcmfmac :02:00.0: Direct firmware load for
  brcm/brcmfmac43602-pcie.txt failed with error -2

  If I rmmod and re-insert  brcmfmac it works until the next reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1571786/+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 1581294] [NEW] ext4 + lukz on 1TB crashes

[Daniel Jenkins]

Public bug reported:

Drive formated as gpt. Using the whole space, on ext4 + lukz options,
the program gives segmentation fault (core violation). I can format the
drive using gparted perfectly.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-disk-utility 3.18.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu May 12 20:52:33 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-05-12 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-disk-utility (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 gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1581294

Title:
  ext4 + lukz on 1TB crashes

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Drive formated as gpt. Using the whole space, on ext4 + lukz options,
  the program gives segmentation fault (core violation). I can format
  the drive using gparted perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May 12 20:52:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-12 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1581294/+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 377172] Re: gnome-display-properties silently broke all my hardware acceleration and movie watching

[Launchpad Bug Tracker]

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

** Changed in: screen-resolution-extra (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-display-properties silently broke all my hardware acceleration
  and movie watching

Status in screen-resolution-extra package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-control-center

  After upgrading to Jaunty, I tried fiddling around with the new
  version of gnome-display-properties, with my laptop (1024x768 display)
  and an external monitor (1680x1050 display). When attempting to place
  them next to each other, gnome-display-properties displayed a cheerful
  note informing me that it couldn't do that because of a problem with
  my xorg.conf, but it could happily fix that problem and I really
  should click "Ok". So I did.

  This added a line like
Subsection "Display"
  Virtual 2704 1050
EndSubSection
  to my /etc/X11/xorg.conf

  My laptop (Thinkpad X60) has an Intel GM945, and the intel drivers top
  out at a Virtual size of 2048x2048. This configuration change made
  them very unhappy.

  The actual symptom I experienced was that some days later, after the
  next time I restarted X, I discovered that all video programs (totem,
  mplayer, etc.) that I tried to start would simply crash immediately.
  XVideo was broken, and none of them are set up to handle this
  gracefully. 3d acceleration also appears to be broken.

  I'm not sure what the best solution here is -- it seems unfortunate
  that gnome-display-properties would need to "know" that intel drivers
  have a particular limit on their Virtual size -- but the bug is easily
  triggered, and *completely* unfathomable to a naive user. At a
  minimum, the cheery message should be changed to something which
  includes a warning, so that if things do get broken the user has at
  least a chance of remembering and looking in the right place.

  (Also, on the user experience end, I am still annoyed at gnome-
  display-properties. I trusted it! It lied to me! Screw you, 'xrandr
  --auto' works better anyway! Okay, thanks for letting me get that part
  off my chest.)

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: gnome-control-center 1:2.26.0-0ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: gnome-control-center
  Uname: Linux 2.6.28-11-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/377172/+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 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable

[Alberto Salvia Novella]

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Regression: Kernel Update in 16.04 from last days renders nvidia
  driver unusable

Status in shim:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.04 since at least four months, always with the
  nvidia proprietary drivers (installed from the repository). I used
  nvidia-361 for a while with no issues (and i need it for steam
  gaming). However, an update installed on my machine yesterday breaks
  the nvidia drivers. I tried purging the driver, rebooting and
  reinstalling and i tried a newer version for the ubuntu-drivers ppa.
  Nothing helps: With the nvidia driver installed, i get a low-
  resolution login screen, but cannot login due to missing 3d
  acceleration. Running on nouveau works fine.

  This seems very strange to since everything worked until this
  afternoon. Yesterday, i was happily playing games on steam, installed
  some updates and now, my graphics are broken.


  
  $ lspci | grep NVIDIA
  01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] 
(rev a2)
  01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)

  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: Mon Apr 25 17:45:12 2016
  DistUpgraded: 2016-03-11 21:34:38,175 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Palit Microsystems Inc. GM107 [GeForce GTX 750] [1569:1381]
  InstallationDate: Installed on 2016-01-05 (110 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=ed669b2d-c3af-4570-9eb7-2978557208ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to xenial on 2016-03-11 (44 days ago)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: H97 Performance
  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.:bvrP2.30:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance: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 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: Mon Apr 25 17:44:29 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/shim/+bug/1574732/+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 1576285] Re: Error happened while installing Ubuntu Studio 16.04 - package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script r

[Alberto Salvia Novella]

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

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

Title:
  Error happened while installing Ubuntu Studio 16.04 - package
  bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 10

Status in bbswitch package in Ubuntu:
  Confirmed

Bug description:
  Specs: Acer Predator G3-710, latest BIOS, Win10, with Secure Boot
  enabled in BIOS, but requested to turn it off in the US installer. I
  don't know if this is a bug. The error pop up window brought me here
  when submitting it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bbswitch-dkms 0.8-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  Date: Thu Apr 28 15:27:25 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  LiveMediaBuild: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: bbswitch
  Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1576285/+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 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[Brian Foster]

# /etc/default/grub
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=1 radeon.drm=1 
radeon.runpm=0"
...

Result of `DRI_PRIME=1 glxgears -info` attached. Visible and smooth
animation runs (no black window).

** Attachment added: "glxgears-2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661667/+files/glxgears-2

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  New

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-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: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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: 

[Desktop-packages] [Bug 1556134] Re: obex-check-device crashed with SIGSEGV in __GI_____strtoul_l_internal()

[Alberto Salvia Novella]

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

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

Title:
  obex-check-device crashed with SIGSEGV in
  __GI_strtoul_l_internal()

Status in libopenobex package in Ubuntu:
  Confirmed

Bug description:
  on launch this crash occurs

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: libopenobex2 1.7.1-4
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar  9 16:14:37 2016
  Dependencies:
   gcc-6-base 6-20160227-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160227-0ubuntu1
   libudev1 229-2ubuntu1
   libusb-1.0-0 2:1.0.20-1
  ExecutablePath: /usr/sbin/obex-check-device
  InstallationDate: Installed on 2016-02-11 (28 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcCmdline: /usr/sbin/obex-check-device 01da
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f8783a75674 <__GI_strtoul_l_internal+68>:   
movsbq (%r14),%rax
   PC (0x7f8783a75674) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libopenobex
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x0, base=16, group=, loc=0x7f8783dff500 <_nl_global_locale>) at ../stdlib/strtol_l.c:297
   main ()
  Title: obex-check-device crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (9 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libopenobex/+bug/1556134/+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 1568429] Re: Radeon won't work with KMS enabled

[Alberto Salvia Novella]

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Radeon won't work with KMS enabled

Status in xorg package in Ubuntu:
  Confirmed

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

  If I add `nomodeset` or `radeon.modeset=0` to kernel line in GRUB, the
  machine will boot but the radeon driver will not load. Attempting to
  load radeon driver with `sudo modprobe radeon modeset=1` after booting
  with modesetting off results in the same fail state explained above.

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

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

-- 
Mailing list: https://launchpad.net/~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 1553780] Re: nautilus assert failure: ERROR:nautilus-view.c:1834:rename_newly_added_folder: code should not be reached

[Alberto Salvia Novella]

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

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

Title:
  nautilus assert failure: ERROR:nautilus-
  view.c:1834:rename_newly_added_folder: code should not be reached

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Select some files, right click- and select New Folder with Selection.
  Nautilus quits with the output `ERROR:nautilus-
  view.c:1834:rename_newly_added_folder: code should not be reached`.

  This happens when a lot of items are selected. (Might have something
  to do with the progress dialog.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar  6 14:06:12 2016
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'thumbnail-limit' b'uint64 104857600'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'242'
   b'org.gnome.nautilus.window-state' b'geometry' b"'886x829+1970+77'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2016-03-03 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160303)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1553780/+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 1574863] Re: Radeon R9 380 HDMI, Digital Out -- No sound at all

[Alberto Salvia Novella]

** Changed in: alsa-driver (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Radeon R9 380 HDMI, Digital Out -- No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Distro is Ubuntu Studio (lsb_release says 'Ubuntu 16.04 LTS')

  HDMI audio output worked in 15.10. No sound after upgrade to 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  schuyler   1729 F pulseaudio
   /dev/snd/controlC1:  schuyler   1729 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Apr 25 17:24:09 2016
  InstallationDate: Installed on 2016-02-28 (57 days ago)
  InstallationMedia: Ubuntu-Studio 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Tonga HDMI Audio [Radeon R9 285/380] - HDA ATI HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  schuyler   1729 F pulseaudio
   /dev/snd/controlC1:  schuyler   1729 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., ATI R6xx HDMI, Digital Out, HDMI] No sound at 
all
  UpgradeStatus: Upgraded to xenial on 2016-04-25 (0 days ago)
  dmi.bios.date: 07/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170-HD3P-CF
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/27/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3P-CF:rvrx.x: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: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1574863/+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 1576726] Re: [SRU]network-manager

[Aron Xu]

@yofel, I see that you've uploaded a version of networkmanager-qt for
xenial SRU, should that fix your problem?

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

Title:
  [SRU]network-manager

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-ssh package in Ubuntu:
  New
Status in network-manager-strongswan package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  New
Status in network-manager-openvpn source package in Xenial:
  New
Status in network-manager-ssh source package in Xenial:
  New
Status in network-manager-strongswan source package in Xenial:
  New
Status in network-manager-vpnc source package in Xenial:
  New

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+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 1565508] Re: Update to 2.3.0 as usb-modeswich-data needs it

[Alberto Salvia Novella]

** Changed in: usb-modeswitch (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Update to 2.3.0 as usb-modeswich-data needs it

Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  xenial has usb-modeswitch  2.2.5 , but 'proposed' archive have loaded
  usb-modeswitch-data to 20160112

  but its changelog shows:

- All Option configs updated with new OptionMode parameter from
usb-modeswitch 2.3.0
* Bump Recommends/Breaks against usb-modeswitch to 2.3.0

  
  So the upgrade wants to remove usb-modeswitch 2.2.5. So the need of at least 
2.3.0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: usb-modeswitch 2.2.5+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr  3 18:45:13 2016
  SourcePackage: usb-modeswitch
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1565508/+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 1576581] Re: New Firefox release hogging CPU

[Alberto Salvia Novella]

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

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

Title:
  New Firefox release hogging CPU

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Since the new Firefox release into 16.04 yesterday [1] Firefox is
  constantly using more than 100% CPU.

  [1]
  https://launchpad.net/ubuntu/+source/firefox/46.0+build5-0ubuntu0.16.04.2

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 46.0+build5-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michal 8674 F pulseaudio
   /dev/snd/controlC0:  michal 8674 F pulseaudio
  BrokenPermissions:
   greasefi...@b0nk3rz.net/indexes/exclude.dat (0o400)
   greasefi...@b0nk3rz.net/indexes/include.dat (0o400)
   greasefi...@b0nk3rz.net/indexes/info.ini (0o400)
   greasefi...@b0nk3rz.net/indexes/scripts.db (0o400)
  BuildID: 20160425114621
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Fri Apr 29 10:35:53 2016
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Polski Language Pack - langpack...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  Plugins:
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
   IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - 
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so 
(icedtea-8-plugin)
  PrefSources:
   prefs.js
   
[Profile]/extensions/https-everywhere-...@eff.org/defaults/preferences/preferences.js
  Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   icedtea-8-plugin  1.6.2-3ubuntu1
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1576581/+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 1581277] [NEW] fglrx failed to upgrade

[Shashwat Sridhar]

Public bug reported:

I was running apt-get update && apt-get upgrade && apt-get dist-upgrade
on a friend's ubuntu system (Trusty). The system had not been updated in
a long time, so the list of packages to be downloaded was huge (~500MB
for updates and ~300MB for upgrades) and due to a slow internet
connection, I had left it overnight to download. The updates were over
by the time I slept, the upgrades had been downloaded by the time I woke
up.

When I woke up, the setup was stuck on various fglrx configuration files
on the system which it determined had been changed, and wanted to know
whether to keep the original files or update with new ones. I chose to
keep the original files. Mid-way through the installation, apport popped
up saying an error had occured. The script in the terminal went on
running, but once I clicked on "Report Problem..." on the apport window,
the script displayed an error regarding fglrx (but continued running
till the end, after which it said "errors were encountered while
processing: fglrx" and then stopped).

[System Version] =
Distributor ID: Ubuntu
Description:Ubuntu 14.04.4 LTS
Release:14.04
Codename:   trusty

[Package Version] = fglrx 2:15.201-0ubuntu0.14.04.1

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:15.201-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.20
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 13 06:44:09 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fglrx-core, 15.201, 3.13.0-35-generic, x86_64: installed
 fglrx-core, 15.201, 3.13.0-86-generic, x86_64: installed
DuplicateSignature: package:fglrx:2:15.201-0ubuntu0.14.04.1:subprocess 
installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit 
status 2
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 05) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:22ce]
   Subsystem: Hewlett-Packard Company Device [103c:22ce]
InstallationDate: Installed on 2014-09-18 (602 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=75707d51-5441-4fff-9834-8e0ee2deaeb2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.13
SourcePackage: fglrx-installer
Title: package fglrx 2:15.201-0ubuntu0.14.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 22CE
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 93.15
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd05/30/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0990101600087:rvnHewlett-Packard:rn22CE:rvr93.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 0990101600087
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.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: Fri May 13 02:23:26 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
 AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
 AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 

[Desktop-packages] [Bug 1574123] Re: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Alberto Salvia Novella]

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

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

Title:
  package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  during upgrade bamfdaemon was noch possible to install. Now it seems
  to be missiong? how to install it now? via packet-installer or
  terminal?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Sat Apr 23 20:17:09 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-08-21 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1574123/+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.

[Alberto Salvia Novella]

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

-- 
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: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: 

[Desktop-packages] [Bug 1581277] Re: fglrx failed to upgrade

[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 fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1581277

Title:
  fglrx failed to upgrade

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  I was running apt-get update && apt-get upgrade && apt-get dist-
  upgrade on a friend's ubuntu system (Trusty). The system had not been
  updated in a long time, so the list of packages to be downloaded was
  huge (~500MB for updates and ~300MB for upgrades) and due to a slow
  internet connection, I had left it overnight to download. The updates
  were over by the time I slept, the upgrades had been downloaded by the
  time I woke up.

  When I woke up, the setup was stuck on various fglrx configuration
  files on the system which it determined had been changed, and wanted
  to know whether to keep the original files or update with new ones. I
  chose to keep the original files. Mid-way through the installation,
  apport popped up saying an error had occured. The script in the
  terminal went on running, but once I clicked on "Report Problem..." on
  the apport window, the script displayed an error regarding fglrx (but
  continued running till the end, after which it said "errors were
  encountered while processing: fglrx" and then stopped).

  [System Version] =
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Codename: trusty

  [Package Version] = fglrx 2:15.201-0ubuntu0.14.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:15.201-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.20
  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 13 06:44:09 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.201, 3.13.0-35-generic, x86_64: installed
   fglrx-core, 15.201, 3.13.0-86-generic, x86_64: installed
  DuplicateSignature: package:fglrx:2:15.201-0ubuntu0.14.04.1:subprocess 
installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:22ce]
 Subsystem: Hewlett-Packard Company Device [103c:22ce]
  InstallationDate: Installed on 2014-09-18 (602 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=75707d51-5441-4fff-9834-8e0ee2deaeb2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: fglrx-installer
  Title: package fglrx 2:15.201-0ubuntu0.14.04.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22CE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 93.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.16:bd05/30/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0990101600087:rvnHewlett-Packard:rn22CE:rvr93.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0990101600087
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.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: Fri May 13 02:23:26 2016
  

[Desktop-packages] [Bug 1572244] Re: Kubuntu 16.04 requires that the wifi password be entered twice before wifi can be used

[Mike E.]

Same here.

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

Title:
  Kubuntu 16.04 requires that the wifi password be entered twice before
  wifi can be used

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  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/ubuntu/+source/network-manager/+bug/1572244/+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 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[Brian Foster]

** Description changed:

  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).
  
- Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel.
- I've tried all combinations and same results occur.
+ Grub does pass "radeon.modeset=1" but it doesn't seem to make a
+ difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
+ the kernel, then it does not error (except for the VCE error -110, which
+ is probably harmless).
+ 
+ Running `DRI_PRIME=1 glxgears`:
+ - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
+ - with just "radeon.modeset=1", error (attached as 'glxgears').
+ 
+ Results are similar on Ubuntu GNOME 16.04, except with
+ "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
+ screen tearing.
  
  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:
  
  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).
  
  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-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: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
-Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
+    Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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
  

[Desktop-packages] [Bug 1263145] Re: Ctrl+= should work as well as Ctrl++

[Bug Watch Updater]

** Changed in: yelp
   Status: Unknown => Confirmed

** Changed in: yelp
   Importance: Unknown => Wishlist

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

Title:
  Ctrl+= should work as well as Ctrl++

Status in Yelp:
  Confirmed
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  Ctrl+= should work as well as Ctrl++

  Steps to reproduce:

  1. Run yelp with Ubuntu (Unity) session with right-up corner "Ubuntu
  Help" menu

  2. Press Ctrl+= like most (including me) do it into Firefox and other
  programms.


  Actual result:

  Nothing happens.


  Expected result:

  Ctrl+= should increase a font size like Ctrl++ and 'View->Larger Text'
  does.

  
  Additional info:
  Ctrl++  (Ctrl+shift+= button) and Ctrl+- work fine as expected: font is 
decreasing and increasing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: yelp 3.8.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Fri Dec 20 22:50:39 2013
  ExecutablePath: /usr/bin/yelp
  InstallationDate: Installed on 2013-05-02 (232 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: yelp
  UpgradeStatus: Upgraded to saucy on 2013-10-27 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/yelp/+bug/1263145/+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 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[Brian Foster]

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661631/+files/syslog

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  New

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the
  kernel. I've tried all combinations and same results occur.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-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: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
 Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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: Thu May 12 20:35:57 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product 

[Desktop-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[Brian Foster]

** Attachment added: "glxgears"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661633/+files/glxgears

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  New

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the
  kernel. I've tried all combinations and same results occur.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-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: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
 Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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: Thu May 12 20:35:57 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   

[Desktop-packages] [Bug 1581270] [NEW] Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

[Brian Foster]

Public bug reported:

dmesg shows issues with being able to use the discrete graphics card
(relevant dmesg lines attached).

Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel.
I've tried all combinations and same results occur.

Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

[   22.916285] [drm] ring test on 0 succeeded in 2 usecs
[   22.916289] [drm] ring test on 1 succeeded in 1 usecs
[   22.916292] [drm] ring test on 2 succeeded in 1 usecs
[   22.916299] [drm] ring test on 3 succeeded in 3 usecs
[   22.916304] [drm] ring test on 4 succeeded in 3 usecs
[   23.092271] [drm] ring test on 5 succeeded in 2 usecs
[   23.092276] [drm] UVD initialized successfully.
[   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
[   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
[   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
[   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
[   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
[   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
[   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

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

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-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: Thu May 12 20:43:03 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
   Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
InstallationDate: Installed on 2016-05-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P05ADH.017.140421.SH
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP680Z5E-X01US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 870Z5E/880Z5E/680Z5E
dmi.product.version: P05ADH
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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: Thu May 12 20:35:57 2016
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4845 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2

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


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

** Attachment added: "dmesg | grep drm"
   
https://bugs.launchpad.net/bugs/1581270/+attachment/4661608/+files/dmesg-grep-drm

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

Title:
  Hybrid Graphics: [drm:si_resume 

[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

[Evan Broder]

Sorry about that, Martin. Not sure what happened. Just re-uploaded
without the noise.

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

Title:
  Excessive CPU utilization

Status in ccid package in Ubuntu:
  Fix Released
Status in pcsc-lite package in Ubuntu:
  Invalid
Status in ccid source package in Xenial:
  In Progress
Status in pcsc-lite source package in Xenial:
  Invalid
Status in pcsc-lite package in Debian:
  Fix Released

Bug description:
  [Impact]

  When hotplugging a composite USB device that expose multiple
  interfaces (such as a Yubikey NEO or Yubikey 4), libccid does not
  correctly de-initialize the USB library when it skips over the non-
  CCID interface.

  This subsequently results in pcscd (or, presumably, anything that
  loads libccid, though I don't think anything else does) either using
  100% CPU or segfaulting when the device is unplugged.

  This seems worthy of an SRU as it is an easily reproducible bug with a
  simple, targeted fix.

  [Test Case]

  1. Make sure pcscd is running (sudo systemctl start pcscd; possibly sudo 
systemctl restart pcscd if a potentially fixed package has just been installed)
  2. Plug and then unplug a composite USB device that includes a CCID interface 
(such as a Yubikey NEO)
  3. Observe that pcscd has crashed with a segfault (sudo systemctl status 
pcscd)

  [Regression Potential]

  The patch is quite narrow, and thus the potential for regression
  should be limited. The new code adds calls to close_libusb_if_needed,
  which is already written to be fairly conservative.

  The worst case here is likely an unexpected call to libusb_exit, which
  could cause libusb to get into an inconsistent state. However, in
  practice the call seems quite safe, and the likelihood of regression
  low.

  ==
  Original bug description:

  In xenial, pcscd CPU utilization occasionally goes haywire:

    PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1551897/+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 1580917] Re: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  All was working fine, then one day it goes silent when plugging in my
  speakers to the headphone socket, and forever after with something
  plugged in (internal speakers still work fine).

  Looking at pavucontrol and/or "Sound settings" under Gnome it shows
  that the sound should be playing on the Headphones output port - the
  VU meter is bouncing up and down ok, but it's silent. Pull out the
  wire (or select internal speakers for the Output) and the sound
  switches to the internal speakers OK.

  Last time this happened I fiddled for ages and then got distorted
  sound (sounds like some sort of cross-channel thing) and this only
  went a away with a complete re-install of Ubuntu (which I did to try
  to fix a separate bug but am not willing to do again!).

  I ran alsa-info.sh from the command line and uploaded the info. Here's
  the URL it gave me to share: http://www.alsa-
  project.org/db/?f=06...3f7ebb379442a7

  It's now happened again, having spent all Friday enjoying music,
  Monday morning turn on and silence! I've not done any upgrades since.

  
  I have tried completely reinstalling pulseaudio (based on suggestions found 
on the ubuntu wiki) to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.4.8-040408-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rich   7826 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 12 09:31:00 2016
  InstallationDate: Installed on 2016-04-22 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rich   7826 F...m pulseaudio
   /dev/snd/controlC0:  rich   7826 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-05-09T13:36:55.718771

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580917/+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 1574347] Re: [SRU]network-manager

[Pinghao Qi]

I'm running the newest versions in stable, just upgraded the applet yesterday:
network-manager 1.1.93-0ubuntu4
network-manager-gnome 1.2.0-0ubuntu0.16.04.1
For me, the issue is already fixed somehow, without needing to update to 
proposed.

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

Title:
  [SRU]network-manager

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

  [Testcase]

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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

[Bug Watch Updater]

** Changed in: gnome-settings-daemon
   Status: Unknown => Fix Released

** Changed in: gnome-settings-daemon
   Importance: Unknown => Medium

-- 
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 linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress

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 1263145] Re: Ctrl+= should work as well as Ctrl++

[Jeremy Bicha]

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

** Also affects: yelp via
   https://bugzilla.gnome.org/show_bug.cgi?id=763964
   Importance: Unknown
   Status: Unknown

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

Title:
  Ctrl+= should work as well as Ctrl++

Status in Yelp:
  Unknown
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  Ctrl+= should work as well as Ctrl++

  Steps to reproduce:

  1. Run yelp with Ubuntu (Unity) session with right-up corner "Ubuntu
  Help" menu

  2. Press Ctrl+= like most (including me) do it into Firefox and other
  programms.


  Actual result:

  Nothing happens.


  Expected result:

  Ctrl+= should increase a font size like Ctrl++ and 'View->Larger Text'
  does.

  
  Additional info:
  Ctrl++  (Ctrl+shift+= button) and Ctrl+- work fine as expected: font is 
decreasing and increasing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: yelp 3.8.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Fri Dec 20 22:50:39 2013
  ExecutablePath: /usr/bin/yelp
  InstallationDate: Installed on 2013-05-02 (232 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: yelp
  UpgradeStatus: Upgraded to saucy on 2013-10-27 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/yelp/+bug/1263145/+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 1263145] Re: Ctrl+= should work as well as Ctrl++

[Launchpad Bug Tracker]

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

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

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

Title:
  Ctrl+= should work as well as Ctrl++

Status in Yelp:
  Unknown
Status in yelp package in Ubuntu:
  Confirmed

Bug description:
  Ctrl+= should work as well as Ctrl++

  Steps to reproduce:

  1. Run yelp with Ubuntu (Unity) session with right-up corner "Ubuntu
  Help" menu

  2. Press Ctrl+= like most (including me) do it into Firefox and other
  programms.


  Actual result:

  Nothing happens.


  Expected result:

  Ctrl+= should increase a font size like Ctrl++ and 'View->Larger Text'
  does.

  
  Additional info:
  Ctrl++  (Ctrl+shift+= button) and Ctrl+- work fine as expected: font is 
decreasing and increasing.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: yelp 3.8.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Fri Dec 20 22:50:39 2013
  ExecutablePath: /usr/bin/yelp
  InstallationDate: Installed on 2013-05-02 (232 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: yelp
  UpgradeStatus: Upgraded to saucy on 2013-10-27 (53 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/yelp/+bug/1263145/+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 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Bug Watch Updater]

** Changed in: gnome-system-monitor
   Status: Unknown => Confirmed

** Changed in: gnome-system-monitor
   Importance: Unknown => Medium

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

[Desktop-packages] [Bug 1568056] Re: Official Package-Names Not Shown in Gnome-Software

[martyj]

100 % Agreed with Lonnie Lee Best.

My opinion is every user should known what package is going to install.
It is our right.

And there is no reason to hide that information. It is ONE line, ONE
name. Nothing more, nothing less.


@ Lonnie Lee Best

Better use [b]Aptik[/b] for your SW reinstall.

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

Title:
  Official Package-Names Not Shown in Gnome-Software

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The names of a packages (as you would type them when installing via a
  command prompt) are not indicated in gnome-software.

  Even when I use gnome-software to locate a package, I still want to
  know the package's official Ubuntu name, because I usually want to add
  that package-name to an command install list (sudo apt-get install
  package1 package2 package3), so that I can install all my packages at
  once the next time I do a fresh install.

  That fact that gnome-software can locate packages for me is great. The
  fact that it doesn't reveal the official name of the packages is
  lacking (for me).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1~git20160331.78d1aab-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  8 12:18:43 2016
  InstallationDate: Installed on 2016-03-14 (25 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1568056/+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 1580146] Re: Internet connection stops working while WiFi is still connected

[Tony Espy]

@Andrea

One last thing... did you check for crash files?

-- 
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:
  Internet connection stops working while WiFi is still connected

Status in network-manager package in Ubuntu:
  Incomplete

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:
  Not sure yet...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+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 1580146] Re: Internet connection stops working while WiFi is still connected

[Tony Espy]

@Andrea

Re: comment #3, please review bug #1533508, to see if your hitting the
same.  If not, please file a new bug and include output from
/usr/share/ofono/scripts/list-modems and list-contexts.

-- 
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:
  Internet connection stops working while WiFi is still connected

Status in network-manager package in Ubuntu:
  Incomplete

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:
  Not sure yet...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+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 1580146] Re: Internet connection stops working while WiFi is still connected

[Tony Espy]

@Andrea

Finally, you might also want to consider "forgetting" some of the saved
access points on your device.  NetworkManager shows a seriously long
list of WiFi connections.

-- 
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:
  Internet connection stops working while WiFi is still connected

Status in network-manager package in Ubuntu:
  Incomplete

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:
  Not sure yet...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+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 1580146] Re: Internet connection stops working while WiFi is still connected

[Tony Espy]

@Andrea

Let's keep this bug specific to the original problem described.

Does this problem only occur at the office?

Can you reproduce it reliably?  If so, how long after you initially
connect does it take to manifest itself?

>From what you provided in your initial pastebin, both the indicator and
NetworkManager show  wlan0 connected to the office access point.  You
also stated that you could ping 8.8.8.8, but that 'ping google.com'
returned 'unknown host'.

The new version of NM now logs the IPv4 details when an IP address is
assigned and/or renewed.  One possibility here is that lease renewal is
not working properly.  So, if/when this problem happens again, please
provide the following:

1) the entire syslog

2) the output of 'iw add show wlan0'

3) the output of 'ip route'

If you again can ping IPv4 addresses on the internet, but can't resolve
hostnames, then let's checkout the dnsmasq configuration.  To do this,
run the following command:

$ sudo kill -SIGUSR1 `pidof dnsmasq`

This causes dnsmasq to write its current configured nameservers to the
syslog, so after sending the signal, grep for "dnsmasq" in syslog and
look for the lines like these:

May 12 19:55:35 ubuntu-phablet dnsmasq[2048]: server 192.168.1.1#53:
queries sent 19, retried or failed 0

Also, in the future, it's better to include requested information (
output from commands, syslog, ... ) directly in comments or attachments
vs. using pastebin.

-- 
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:
  Internet connection stops working while WiFi is still connected

Status in network-manager package in Ubuntu:
  Incomplete

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:
  Not sure yet...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+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 1511735] Re: libnl: fail to bind() netlink sockets

[Daniel Holz]

This update broke Network-Manager on my system. Used these steps to
manually downgrade libnl to get network connections working again.

http://askubuntu.com/questions/727127/last-upgrade-crashes-network-
manager-no-internet-connection-no-applet

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

Title:
  libnl: fail to bind() netlink sockets

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Trusty:
  Fix Released
Status in libnl3 package in Debian:
  Fix Released

Bug description:
  [Triage Notes]

  The proposed fix for this bug in libnl3 caused a regression in trusty-
  proposed, tracked in bug 1539634. The regression is caused by a latent
  bug in Network Manager. We expect to fix this by landing a fix for the
  bug in Network Manager in trusty-updates at the same time as this fix.

  [Impact]

   * Applications in Trusty using libnl-3-200 which frequently open and
     close netlink sockets can easily fail when attempting to bind the
     local socket.  The problem happens when libnl choose a port id
     already used by another application and subsequently libnl fails
     instead of trying another port id.

     The original bug was discovered when attempting to start a virtual
     machine under libvirt, which is a user of this library.

   * Backporting fixes from upstream release fixes a real bug in the
     current version of the library in Trusty.  The alternative is for all
     applications to manually manage their local port allocation, or as
     upstream has accepted allowing libnl to attempt to try for other
     local ports.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

  [Test Case]

   * On a Trusty 14.04 system
     1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \
     libnl-genl-3-dev libnl-route-3-200 \
     make gcc build-essential libnl1
     2. download and unpack attachment: lp_1511735_test.tar
     3. Run testcases:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 6975 (pid: 6974)
  local port has been set by the libnl to 6975 (pid: 6975)
  ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975)
  libnl FAILED
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=6978
  TEST (a)...
  Traceback (most recent call last):
    File "libnl3-test-rh1249158.py", line 226, in 
  locals()["TEST_" + arg]()
    File "libnl3-test-rh1249158.py", line 140, in TEST_a
  sk = nl_get_socket()
    File "libnl3-test-rh1249158.py", line 115, in nl_get_socket
  raise IOError(-err, _nl_geterror())
  OSError: [Errno 6] b'Unspecific failure'

     4. After applying the updated packages:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 11295 (pid: 11294)
  local port has been set by the libnl to 2894081055 (pid: 11295)
  libnl OK
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=11296
  TEST (a)...
  ...done
  TEST (b)...
  ...done
  TEST (c)...
  ...done
  TEST (d)...
  ...done

  [Regression Potential]

   * There are quite a few high profile packages that depend on this package,
     notably libvirt and network-manager.  The complete list is here:

     # on Trusty
  % apt-rdepends -r libnl-3-200 | head -n 33
  libnl-3-200
    Reverse Depends: batctl (>= 2013.4.0-2)
    Reverse Depends: bmon (>= 1:3.1-1)
    Reverse Depends: crda (>= 1.1.2-1ubuntu2)
    Reverse Depends: hostapd (>= 1:2.1-0ubuntu1)
    Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1)
    Reverse Depends: iw (>= 3.4-1)
    Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1)
    Reverse Depends: kismet (>= 2013.03.R1b-3)
    Reverse Depends: knemo (>= 0.7.6-2)
    Reverse Depends: libfsobasics3 (>= 0.12.0-4)
    Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1)
    Reverse Depends: libnl-3-200-dbg (= 3.2.21-1)
    Reverse Depends: libnl-3-dev (= 3.2.21-1)
    Reverse Depends: libnl-cli-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-genl-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-nf-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-route-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-utils (>= 3.2.21-1)
    Reverse Depends: libnss-gw-name (>= 0.3-2)
    Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13)
    Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13)
    Reverse Depends: lowpan-test-tools (>= 0.3-1)
    

[Desktop-packages] [Bug 1555170] Re: [SRU] Bad icon for bluetooth sound device

[Launchpad Bug Tracker]

This bug was fixed in the package adwaita-icon-theme - 3.18.0-2ubuntu4

---
adwaita-icon-theme (3.18.0-2ubuntu4) yakkety; urgency=medium

  * debian/control.in, debian/not-in-humanity.txt:
- Include audio-speakers in the non-full theme, it's used by
  unity-control-center to represent bluetooth speakers
  (LP: #1555170)

 -- Will Cooke   Thu, 12 May 2016 21:33:48 +0100

** Changed in: adwaita-icon-theme (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [SRU] Bad icon for bluetooth sound device

Status in adwaita-icon-theme package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * Bluetooth connected speakers appear in the Bluetooth settings and
  the Sound settings of System Settings with a broken icon.

   * This change simply moves the missing icon in to the default set.

  
  [Test Case]

   * Pair a Bluetooth speaker via the Bluetooth section of System Settings.
   * Once paired note that the icon appears as a small speaker and not a black 
square with a red warning symbol in (indicating a missing icon)
   * Once paired open the Sound Settings of System Settings and note that the 
Bluetooth speaker is displayed with the same speaker icon and not the broken 
icon.

  [Regression Potential]

   * Very low.  This patch simply adds the missing icon to the default
  set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1555170/+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 1580146] Re: Internet connection stops working while WiFi is still connected

[Tony Espy]

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

-- 
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:
  Internet connection stops working while WiFi is still connected

Status in network-manager package in Ubuntu:
  Incomplete

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:
  Not sure yet...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+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 1577170] Re: [solved] screen cannot be turned back on after being switched off after some time of inactivity

[C de-Avillez]

this is the patch in the link above:

diff --git a/src/drmmode_display.c b/src/drmmode_display.c
index 4c66ca7..a848345 100644
--- a/src/drmmode_display.c
+++ b/src/drmmode_display.c
@@ -288,6 +288,7 @@ static void
 drmmode_do_crtc_dpms(xf86CrtcPtr crtc, int mode)
 {
drmmode_crtc_private_ptr drmmode_crtc = crtc->driver_private;
+   drmmode_ptr drmmode = drmmode_crtc->drmmode;
ScrnInfoPtr scrn = crtc->scrn;
RADEONInfoPtr info = RADEONPTR(scrn);
CARD64 ust;
@@ -296,6 +297,11 @@ drmmode_do_crtc_dpms(xf86CrtcPtr crtc, int mode)
if (drmmode_crtc->dpms_mode == DPMSModeOn && mode != DPMSModeOn) {
drmVBlank vbl;
 
+   /* Wait for any pending flip to finish */
+   do {} while (drmmode_crtc->flip_pending &&
+drmHandleEvent(drmmode->fd,
+   >event_context) > 0);
+
/*
 * On->Off transition: record the last vblank time,
 * sequence number and frame period.

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

Title:
  [solved] screen cannot be turned back on after being switched off
  after some time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset
  -display :0.0 dpms force off" in a terminal. Moreover typing gnome-
  screensaver-command -a in a terminal turns my screen off and after
  typing this line, the screen can be woken up by moving the mouse or by
  hitting a key. I'm confused.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+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 1577170] Re: [solved] screen cannot be turned back on after being switched off after some time of inactivity

[C de-Avillez]

 tabs were lost in translation.

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

Title:
  [solved] screen cannot be turned back on after being switched off
  after some time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset
  -display :0.0 dpms force off" in a terminal. Moreover typing gnome-
  screensaver-command -a in a terminal turns my screen off and after
  typing this line, the screen can be woken up by moving the mouse or by
  hitting a key. I'm confused.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+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 1409032] Re: gvfsd-smb: very high CPU utilisation

[Nick W]

I used the terminal to back up the gvfsd-smb-browse, then removed it. I
think I do not use this file for anything. It looks like the system is
still running fine as far as I can see. The CPU has a normal load after
boot up...

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

Title:
  gvfsd-smb: very high CPU utilisation

Status in gvfs package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in samba package in Fedora:
  Unknown

Bug description:
  Example:

  I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb
  (browsing within Gnome to find the share), gvfsd-smb uses up to 50%
  CPU which slows down the entire system when accessing the network
  share. Mounting using sudo ($ sudo mount -t smbfs -o
  guest,nounix,noperm //server/share /media/share) so that cifs is used
  uses around 8% CPU. The difference is dramatic!

  If I didn't have sudo access my machine would grind to a halt when
  trying to use the remote share.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Fri Jan  9 14:32:20 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+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 1577170] Re: screen cannot be turned back on after being switched off after some time of inactivity

[Christophe]

Thanks to the guys in the #radeon channel on irc, I found a way to solve the 
problem. 
You have to apply this patch to the source of the video driver 
(xfree86-video-ati-7.7.0) : https://paste.debian.net/plain/682956
and compile then install it (using --prefix=/usr for the configure process).


** Summary changed:

- screen cannot be turned back on after being switched off after some time of 
inactivity
+ [solved] screen cannot be turned back on after being switched off after some 
time of inactivity

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

Title:
  [solved] screen cannot be turned back on after being switched off
  after some time of inactivity

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  I did a fresh install of ubuntu 16.04 on my old dell computer in which
  there is an ati radeon X1300 graphics card.

   Whenever the screen turns off due to inactivity, it cannot be woken
  up by moving the mouse or by hitting a key.

  When I kill the Xorg process via ssh with another computer, the screen
  then comes to life again and I can log back in.

  When I remove the graphic card from the computer and use the built in
  graphic card instead, the bug doesn't occur. So I guess it is related
  to the radeon driver.

  Oddly enough, there is no problem waking the screen when I type "xset
  -display :0.0 dpms force off" in a terminal. Moreover typing gnome-
  screensaver-command -a in a terminal turns my screen off and after
  typing this line, the screen can be woken up by moving the mouse or by
  hitting a key. I'm confused.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1577170/+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 1581245] [NEW] unity-settings-daemon crashes every time T450s laptop is un-docked

[Christopher Barrington-Leigh]

Public bug reported:

Every time I undock my Lenovo T450s from its superdock, unity-settings-
daemon crashes (producing a crash dialog) and various things stop
working as a result, e.g. some of my keyboard shortcuts, functionality
on the OS status bar/panel, and normal shutdown.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: unity-settings-daemon 15.04.1+15.10.20151029-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
Uname: Linux 4.2.0-36-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 12 18:55:10 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-02-12 (90 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: unity-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

** Summary changed:

- unity-settings-daemon crashes every time lapto is un-docked
+ unity-settings-daemon crashes every time T450s laptop is un-docked

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

Title:
  unity-settings-daemon crashes every time T450s laptop is un-docked

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  Every time I undock my Lenovo T450s from its superdock, unity-
  settings-daemon crashes (producing a crash dialog) and various things
  stop working as a result, e.g. some of my keyboard shortcuts,
  functionality on the OS status bar/panel, and normal shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity-settings-daemon 15.04.1+15.10.20151029-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 12 18:55:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-12 (90 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: unity-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1581245/+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 1581106] Re: [yakkety regression] lightdm fails to install

[Robert Ancell]

This might have been triggered in bug 1292990. This changed:

 override_dh_installinit:
-   dh_installinit --no-start
+   dh_installinit --no-restart-on-upgrade

Perhaps this is the wrong change?

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

Title:
  [yakkety regression] lightdm fails to install

Status in lightdm package in Ubuntu:
  New

Bug description:
  systemd's cmdline-upstart-boot autopkgtest started to fail in yakkety
  [1] due to

  Setting up lightdm (1.19.0-0ubuntu1) ...
  Adding group `lightdm' (GID 116) ...
  Done.
  Adding system user `lightdm' (UID 112) ...
  Adding new user `lightdm' (UID 112) with group `lightdm' ...
  Creating home directory `/var/lib/lightdm' ...
  usermod: no changes
  usermod: no changes
  usermod: no changes
  Adding group `nopasswdlogin' (GID 117) ...
  Done.
  Job for lightdm.service failed because the control process exited with error 
code. See "systemctl status lightdm.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lightdm, action "start" failed.
  dpkg: error processing package lightdm (--configure):
   subprocess installed post-installation script returned error exit status 1

  This is reproducible in a cloud instance/VM (or a server install, etc)
  with

sudo apt-get install lightdm --no-install-recommends

  $ sudo lightdm -d
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.19.0, UID=0 PID=2262
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.02s] DEBUG: Registered seat module xlocal
  [+0.02s] DEBUG: Registered seat module xremote
  [+0.02s] DEBUG: Registered seat module unity
  [+0.03s] DEBUG: Monitoring logind for seats
  [+0.03s] DEBUG: New seat added from logind: seat0
  [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
  [+0.03s] DEBUG: Seat seat0: Starting
  [+0.03s] DEBUG: Seat seat0: Creating greeter session
  [+0.04s] DEBUG: Seat seat0: Failed to find session configuration default
  [+0.04s] DEBUG: Seat seat0: Failed to create greeter session
  [+0.04s] DEBUG: Failed to start seat: seat0

  So apparently something in 1.19 changed the handling of seats and now
  fails if there is no seat. That makes automated testing much harder as
  we don't have seats in these environments.

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/s/systemd/20160512_140212@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 17:49:55 2016
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581106/+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 1581238] Re: Update to 3.20

[Robert Ancell]

Requires GTK+ 3.20 (bug 1576576)

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

Title:
  Update to 3.20

Status in gnome-contacts package in Ubuntu:
  Triaged

Bug description:
  Update to 3.20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1581238/+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 1581238] Re: Update to 3.20

[Robert Ancell]

Note, current latest release is still 3.19.91

** Changed in: gnome-contacts (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-contacts (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Update to 3.20

Status in gnome-contacts package in Ubuntu:
  Triaged

Bug description:
  Update to 3.20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1581238/+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 1581238] [NEW] Update to 3.20

[Robert Ancell]

Public bug reported:

Update to 3.20

** Affects: gnome-contacts (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version

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

Title:
  Update to 3.20

Status in gnome-contacts package in Ubuntu:
  Triaged

Bug description:
  Update to 3.20

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1581238/+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 131289] Re: Allow to add and remove screensavers to the shortlist of screensaver theme

[Pander]

** Changed in: gnome-screensaver (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Allow to add and remove screensavers to the shortlist of screensaver
  theme

Status in GNOME Screensaver:
  Expired
Status in gnome-screensaver package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-screensaver

  The gnome-screensaver has a list called 'Screensaver theme' which
  contains a shortlist with 'Black screen' and 'Random', a separator bar
  and then all installed screensavers.

  At the moment the list has become so long that it takes a long time to
  find, that particular screen saver you would like to see or show to
  others, that it is desirable to allow the user to add and remove
  screensavers to the shortlist. This can be achieved by offering the
  following functionality.

  With a mouse right click on a screensaver in the long list, a menu
  should pop up with the action 'Add to shortlist' and when clicked that
  particular screensaver will also be listed in the short list above the
  separator bar. With a mouse right click on a screensaver in the short
  list (i.e. not on 'Black screen' and 'Random'), a menu should pop up
  with the actions 'Remove from shortlist' and when clicked that
  particular screensaver will have to be removed from the short list.

  Implementing this feature will allow users to more actively switch
  between favorite screensavers enabling them to quickly demonstrate
  what are, according to them, the most awesome screensavers Linux has
  to offer. And in turn making a nice showcase for GNU/Linux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/131289/+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 1574020] Re: Can't use networkmanager from lightdm

[Joakim Koed]

@seb128 Do you know how I could debug it for you? I would be glad to
help, just don't know where to start.

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

Title:
  Can't use networkmanager from lightdm

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

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

** Also affects: gnome-system-monitor via
   https://bugzilla.gnome.org/show_bug.cgi?id=766352
   Importance: Unknown
   Status: Unknown

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Gnome System Monitor:
  Unknown
Status in Ubuntu GNOME:
  New
Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content 

[Desktop-packages] [Bug 1581106] Re: [yakkety regression] lightdm fails to install

[Martin Pitt]

> I'm not sure how this would have worked in the past.

Ah, I know now -- when I do "sudo apt-get install --no-install-
recommends lightdm" in xenial, lightdm.service is not started at all
right after package installation.

So I think that's the regression -- I don't think it's a good idea to
start a DM right after package installation, it might interfere with
other DMs or running X sessions? Was  that done on purpose?

> What's pulling in LightDM? Perhaps we should change that depends.

Some systemd autopkgtests pull in lightdm, mostly to ensure that boot
works and lightdm comes up. In the "real" tests X.org gets configured
with the dummy driver and the VM gets rebooted, so lightdm starts up
fine. In the test that failed (cmdline-upstart-boot) I don't do this.
But I don't install recommends there, thus I run into the "missing
greeter" issue.

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

Title:
  [yakkety regression] lightdm fails to install

Status in lightdm package in Ubuntu:
  New

Bug description:
  systemd's cmdline-upstart-boot autopkgtest started to fail in yakkety
  [1] due to

  Setting up lightdm (1.19.0-0ubuntu1) ...
  Adding group `lightdm' (GID 116) ...
  Done.
  Adding system user `lightdm' (UID 112) ...
  Adding new user `lightdm' (UID 112) with group `lightdm' ...
  Creating home directory `/var/lib/lightdm' ...
  usermod: no changes
  usermod: no changes
  usermod: no changes
  Adding group `nopasswdlogin' (GID 117) ...
  Done.
  Job for lightdm.service failed because the control process exited with error 
code. See "systemctl status lightdm.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lightdm, action "start" failed.
  dpkg: error processing package lightdm (--configure):
   subprocess installed post-installation script returned error exit status 1

  This is reproducible in a cloud instance/VM (or a server install, etc)
  with

sudo apt-get install lightdm --no-install-recommends

  $ sudo lightdm -d
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.19.0, UID=0 PID=2262
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.02s] DEBUG: Registered seat module xlocal
  [+0.02s] DEBUG: Registered seat module xremote
  [+0.02s] DEBUG: Registered seat module unity
  [+0.03s] DEBUG: Monitoring logind for seats
  [+0.03s] DEBUG: New seat added from logind: seat0
  [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
  [+0.03s] DEBUG: Seat seat0: Starting
  [+0.03s] DEBUG: Seat seat0: Creating greeter session
  [+0.04s] DEBUG: Seat seat0: Failed to find session configuration default
  [+0.04s] DEBUG: Seat seat0: Failed to create greeter session
  [+0.04s] DEBUG: Failed to start seat: seat0

  So apparently something in 1.19 changed the handling of seats and now
  fails if there is no seat. That makes automated testing much harder as
  we don't have seats in these environments.

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/s/systemd/20160512_140212@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 17:49:55 2016
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581106/+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 1581229] Re: "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

** Summary changed:

- Start time for processes not displayed when column is enabled in settings
+ "Started" column not displayed for processes when column is enabled in 
settings

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Ubuntu GNOME:
  New
Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  I have recently noticed that in the gnome-system-monitor if I go into
  the settings and tick the box for "Started" in the "Information
  fields" section of that the "Processes" tab that the "Started" column
  is not added and in fact this information is not seemingly displayed
  anywhere except for in the "Properties" window for a process. But it
  would be really useful if it did actually appear as a column so that
  you could easily view the start times for multiple processes at the
  same time and to also sort them in terms of that. I am running Ubuntu
  GNOME 15.10 with GNOME 3.18 but I have also experienced the behaviour
  on Ubuntu GNOME 16.04 with GNOME 3.20, in fact when running it on that
  system through Terminal this was the output (the exact moment I
  checked the "Started" box in the settings to add that column I got the
  first bit of output and then very quickly the other output followed):

  (gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)
  
  (gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

To 

[Desktop-packages] [Bug 1581231] [NEW] segfault while scanning

[Marcin B]

Public bug reported:

May 12 23:56:17  kernel: [ 9108.800356] scan-thread[8894]: segfault at
14 ip 7f95b9cda347 sp 7f95ba6eae00 error 4 in libsane-
hpaio.so.1.0.0[7f95b9cc7000+25000]


and HP OfficeJet 6500A Plus stopped to work.
$ dpkg -l | grep sane
ii  libksane-data   4:4.14.0-1  
 all  scanner library (data files)
ii  libksane0   4:4.14.0-1  
 amd64scanner library (runtime)
ii  libsane:amd64   1.0.24-8+deb8u1 
 amd64API library for scanners
ii  libsane-common  1.0.24-8+deb8u1 
 all  API library for scanners -- documentation and 
support files
ii  libsane-extras:amd641.0.22.3
 amd64API library for scanners -- extra backends
ii  libsane-extras-common   1.0.22.3
 amd64API library for scanners -- documentation and 
support files
ii  libsane-extras-dev  1.0.22.3
 amd64API development library for scanners 
[development files]
ii  libsane-hpaio   3.14.6-1+b2 
 amd64HP SANE backend for multi-function peripherals
ii  sane-utils  1.0.24-8+deb8u1 
 amd64API library for scanners -- utilities
ii  xsane   0.998-6+b1  
 amd64featureful graphical frontend for SANE 
(Scanner Access Now Easy)
ii  xsane-common0.998-6 
 all  featureful graphical frontend for SANE 
(Scanner Access Now Easy)


$ dpkg -l | grep hp
ii  hp-ppd  0.9-0.2 
 all  HP Postscript Printer Definition (PPD) files
ii  hplip   3.14.6-1+b2 
 amd64HP Linux Printing and Imaging System (HPLIP)
ii  hplip-data  3.14.6-1
 all  HP Linux Printing and Imaging - data files
ii  hplip-gui   3.14.6-1
 all  HP Linux Printing and Imaging - GUI utilities 
(Qt-based)
ii  libhpmud0   3.14.6-1+b2 
 amd64HP Multi-Point Transport Driver (hpmud) 
run-time libraries
ii  libsane-hpaio   3.14.6-1+b2 
 amd64HP SANE backend for multi-function peripherals
ii  libshp2:amd64   1.3.0-4 
 amd64Library for reading and writing ESRI 
Shapefiles
ii  printer-driver-hpcups   3.14.6-1+b2 
 amd64HP Linux Printing and Imaging - CUPS Raster 
driver (hpcups)
ii  printer-driver-hpijs3.14.6-1+b2 
 amd64HP Linux Printing and Imaging - printer 
driver (hpijs)
ii  printer-driver-postscript-hp3.14.6-1
 all  HP Printers PostScript Descriptions

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  segfault while scanning

Status in sane-backends package in Ubuntu:
  New

Bug description:
  May 12 23:56:17  kernel: [ 9108.800356] scan-thread[8894]: segfault at
  14 ip 7f95b9cda347 sp 7f95ba6eae00 error 4 in libsane-
  hpaio.so.1.0.0[7f95b9cc7000+25000]

  
  and HP OfficeJet 6500A Plus stopped to work.
  $ dpkg -l | grep sane
  ii  libksane-data   4:4.14.0-1
   all  scanner library (data files)
  ii  libksane0   4:4.14.0-1
   amd64scanner library (runtime)
  ii  libsane:amd64   
1.0.24-8+deb8u1  amd64API library for scanners
  ii  libsane-common  
1.0.24-8+deb8u1  all  API library for scanners -- 
documentation and support files
  ii  libsane-extras:amd64 

[Desktop-packages] [Bug 1581229] [NEW] "Started" column not displayed for processes when column is enabled in settings

[Nikita Yerenkov-Scott]

Public bug reported:

I have recently noticed that in the gnome-system-monitor if I go into
the settings and tick the box for "Started" in the "Information fields"
section of that the "Processes" tab that the "Started" column is not
added and in fact this information is not seemingly displayed anywhere
except for in the "Properties" window for a process. But it would be
really useful if it did actually appear as a column so that you could
easily view the start times for multiple processes at the same time and
to also sort them in terms of that. I am running Ubuntu GNOME 15.10 with
GNOME 3.18 but I have also experienced the behaviour on Ubuntu GNOME
16.04 with GNOME 3.20, in fact when running it on that system through
Terminal this was the output (the exact moment I checked the "Started"
box in the settings to add that column I got the first bit of output and
then very quickly the other output followed):

(gnome-system-monitor:2252): GLib-CRITICAL **: Source ID 73 was not found 
when attempting to remove it

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

(gnome-system-monitor:2252): Gtk-WARNING **: Negative content width -12 
(allocation 1, extents 6x7) while allocating gadget (node button, owner 
GtkButton)

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

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


** Tags: wily xenial

** Also affects: ubuntu-gnome
   Importance: Undecided
   Status: New

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

Title:
  "Started" column not displayed for processes when column is enabled in
  settings

Status in Ubuntu GNOME:
  New
Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  I have 

[Desktop-packages] [Bug 1577246] Re: Ubuntu 16.04 Unity : gedit window has no shadow

[Coeur Noir]

…and it came back !
http://hpics.li/76c2d7a

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

Title:
  Ubuntu 16.04 Unity : gedit window has no shadow

Status in gedit package in Ubuntu:
  Invalid

Bug description:
  Hi,

  as described in title.

  The gedit window has no shadow around its borders, which is quite
  annoying when opened above other white or light background window(s).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1577246/+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 1547135] Re: Support purchasing software

[keshavbhatt]

I have developed my own personal client to allow all my customers install apps 
they purchased from Ubuntu software center .
the client cost 15$ and it allow users install all apps developed by me for 
free lots of other features are to be planned in future .
details and updates :- 

14.04  - www.ktechpit.com/ubuntu/ktechpit-com-released-ubuntu-play-
store-ubuntu-14-04/

16.04  - http://www.ktechpit.com/ubuntu/ktechpit-com-released-ubuntu-
play-store-ubuntu-16-04/

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

Title:
  Support purchasing software

Status in GNOME Software:
  In Progress
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Eventually people will be able to buy software with money.  This means
  that the prices will need to be displayed in the UI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1547135/+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 1581187] Re: AppArmor parser error for /etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session at line 14: Could not open 'abstractions/fcitx'

[Robert Ancell]

This change was added in bug 1509829. I couldn't find any documentation
on what apparmor would do if the abstraction doesn't exist. Do you know
how we can have optional includes?

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

Title:
  AppArmor parser error for /etc/apparmor.d/lightdm-guest-session in
  /etc/apparmor.d/lightdm-guest-session at line 14: Could not open
  'abstractions/fcitx'

Status in lightdm package in Ubuntu:
  New

Bug description:
  The current yakkety lightdm version has a regression in its AppArmor
  profile:

  $ sudo systemctl status apparmor.service
  ● apparmor.service - LSB: AppArmor initialization
 Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2016-05-12 18:03:37 CEST; 3h 
17min ago
   Docs: man:systemd-sysv-generator(8)

  May 12 18:03:37 autopkgtest apparmor[493]:  * Starting AppArmor profiles
  May 12 18:03:37 autopkgtest apparmor[493]: AppArmor parser error for 
/etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session 
at line 14: Could not open 'abstractions/fcitx'
  May 12 18:03:37 autopkgtest apparmor[493]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 12 18:03:37 autopkgtest apparmor[493]: AppArmor parser error for 
/etc/apparmor.d/lightdm-guest-session in /etc/apparmor.d/lightdm-guest-session 
at line 14: Could not open 'abstractions/fcitx'
  May 12 18:03:37 autopkgtest apparmor[493]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  May 12 18:03:37 autopkgtest apparmor[493]:...fail!
  May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Control process 
exited, code=exited status=123
  May 12 18:03:37 autopkgtest systemd[1]: Failed to start LSB: AppArmor 
initialization.
  May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Unit entered failed 
state.
  May 12 18:03:37 autopkgtest systemd[1]: apparmor.service: Failed with result 
'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 21:20:13 2016
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581187/+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 1579415] Re: Ubuntu Software Center does not display third party apps or all installed apps

[Matthias Klumpp]

Yeah, the old Ubuntu Software Center was designed to also replace Synaptic, 
while the new GNOME Software is for applications / fonts / other visible stuff 
only (the same as KDE Discover does).
Advanced users are encouraged to use Synaptic, Muon or the command-line 
directly.

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

Title:
  Ubuntu Software Center does not display third party apps or all
  installed apps

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  gnome-software:
    Installed: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Candidate: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Version table:
   *** 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  The new Ubuntu Software Center does not display all software. For
  example no third party repo applications are displayed.

  Search for example:

  Ubuntu-restricted-extras - no results
  muon - no results
  krita - no results
  samba - no results

  These do not show under installed either, though they are installed.

  However, all are shown in Synaptic Package Manager and MUON

  Additional:

  I have installed the old Ubuntu Software Center and can confirm that
  ALL applications are correctly listed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1579415/+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 1581106] Re: [yakkety regression] lightdm fails to install

[Robert Ancell]

The seat is being added, but it's failing to start a greeter (since you
don't have one installed). I'm not sure how this would have worked in
the past.

Not sure the correct behaviour should be here? It is valid to have
lightdm installed without a greeter if appropriately configured (e.g. if
you have autologin enabled).

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

Title:
  [yakkety regression] lightdm fails to install

Status in lightdm package in Ubuntu:
  New

Bug description:
  systemd's cmdline-upstart-boot autopkgtest started to fail in yakkety
  [1] due to

  Setting up lightdm (1.19.0-0ubuntu1) ...
  Adding group `lightdm' (GID 116) ...
  Done.
  Adding system user `lightdm' (UID 112) ...
  Adding new user `lightdm' (UID 112) with group `lightdm' ...
  Creating home directory `/var/lib/lightdm' ...
  usermod: no changes
  usermod: no changes
  usermod: no changes
  Adding group `nopasswdlogin' (GID 117) ...
  Done.
  Job for lightdm.service failed because the control process exited with error 
code. See "systemctl status lightdm.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lightdm, action "start" failed.
  dpkg: error processing package lightdm (--configure):
   subprocess installed post-installation script returned error exit status 1

  This is reproducible in a cloud instance/VM (or a server install, etc)
  with

sudo apt-get install lightdm --no-install-recommends

  $ sudo lightdm -d
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.19.0, UID=0 PID=2262
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.02s] DEBUG: Registered seat module xlocal
  [+0.02s] DEBUG: Registered seat module xremote
  [+0.02s] DEBUG: Registered seat module unity
  [+0.03s] DEBUG: Monitoring logind for seats
  [+0.03s] DEBUG: New seat added from logind: seat0
  [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
  [+0.03s] DEBUG: Seat seat0: Starting
  [+0.03s] DEBUG: Seat seat0: Creating greeter session
  [+0.04s] DEBUG: Seat seat0: Failed to find session configuration default
  [+0.04s] DEBUG: Seat seat0: Failed to create greeter session
  [+0.04s] DEBUG: Failed to start seat: seat0

  So apparently something in 1.19 changed the handling of seats and now
  fails if there is no seat. That makes automated testing much harder as
  we don't have seats in these environments.

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/s/systemd/20160512_140212@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 17:49:55 2016
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581106/+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 1581106] Re: [yakkety regression] lightdm fails to install

[Robert Ancell]

What's pulling in LightDM? Perhaps we should change that depends.

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

Title:
  [yakkety regression] lightdm fails to install

Status in lightdm package in Ubuntu:
  New

Bug description:
  systemd's cmdline-upstart-boot autopkgtest started to fail in yakkety
  [1] due to

  Setting up lightdm (1.19.0-0ubuntu1) ...
  Adding group `lightdm' (GID 116) ...
  Done.
  Adding system user `lightdm' (UID 112) ...
  Adding new user `lightdm' (UID 112) with group `lightdm' ...
  Creating home directory `/var/lib/lightdm' ...
  usermod: no changes
  usermod: no changes
  usermod: no changes
  Adding group `nopasswdlogin' (GID 117) ...
  Done.
  Job for lightdm.service failed because the control process exited with error 
code. See "systemctl status lightdm.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lightdm, action "start" failed.
  dpkg: error processing package lightdm (--configure):
   subprocess installed post-installation script returned error exit status 1

  This is reproducible in a cloud instance/VM (or a server install, etc)
  with

sudo apt-get install lightdm --no-install-recommends

  $ sudo lightdm -d
  [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.00s] DEBUG: Starting Light Display Manager 1.19.0, UID=0 PID=2262
  [+0.00s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.02s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.02s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.02s] DEBUG: Registered seat module xlocal
  [+0.02s] DEBUG: Registered seat module xremote
  [+0.02s] DEBUG: Registered seat module unity
  [+0.03s] DEBUG: Monitoring logind for seats
  [+0.03s] DEBUG: New seat added from logind: seat0
  [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:*
  [+0.03s] DEBUG: Seat seat0: Starting
  [+0.03s] DEBUG: Seat seat0: Creating greeter session
  [+0.04s] DEBUG: Seat seat0: Failed to find session configuration default
  [+0.04s] DEBUG: Seat seat0: Failed to create greeter session
  [+0.04s] DEBUG: Failed to start seat: seat0

  So apparently something in 1.19 changed the handling of seats and now
  fails if there is no seat. That makes automated testing much harder as
  we don't have seats in these environments.

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-yakkety/yakkety/amd64/s/systemd/20160512_140212@/log.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu3
  Architecture: amd64
  Date: Thu May 12 17:49:55 2016
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581106/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Arup]

Thanks Richard and Till, I for one sincerely hope to see this bug fixed
soon as it affects not only Epson but many other printers as well due to
missing lsb package.

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Committed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+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 1579415] Re: Ubuntu Software Center does not display third party apps or all installed apps

[pst007x]

http://news.softpedia.com/news/canonical-needs-your-help-to-make-gnome-
software-look-beautiful-in-ubuntu-16-04-501741.shtml

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

Title:
  Ubuntu Software Center does not display third party apps or all
  installed apps

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  gnome-software:
    Installed: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Candidate: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Version table:
   *** 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  The new Ubuntu Software Center does not display all software. For
  example no third party repo applications are displayed.

  Search for example:

  Ubuntu-restricted-extras - no results
  muon - no results
  krita - no results
  samba - no results

  These do not show under installed either, though they are installed.

  However, all are shown in Synaptic Package Manager and MUON

  Additional:

  I have installed the old Ubuntu Software Center and can confirm that
  ALL applications are correctly listed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1579415/+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 1579415] Re: Ubuntu Software Center does not display third party apps or all installed apps

[pst007x]

Ok, thanks for the info.

Samba, for example, did appear in the old Ubuntu Software Center so
to understand you the METADATA info hasn't been updated to work with the
new Software Center in ubuntu...

So this includes already installed software too

Ok thanks for helping me to understand...

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

Title:
  Ubuntu Software Center does not display third party apps or all
  installed apps

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  gnome-software:
    Installed: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Candidate: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Version table:
   *** 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  The new Ubuntu Software Center does not display all software. For
  example no third party repo applications are displayed.

  Search for example:

  Ubuntu-restricted-extras - no results
  muon - no results
  krita - no results
  samba - no results

  These do not show under installed either, though they are installed.

  However, all are shown in Synaptic Package Manager and MUON

  Additional:

  I have installed the old Ubuntu Software Center and can confirm that
  ALL applications are correctly listed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1579415/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Till Kamppeter]

Richard, this will get fixed in any case.

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Committed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+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 1555170] Re: Bad icon for bluetooth sound device

[Sebastien Bacher]

Thanks Will, I tweaked a bit the description to be a bit more detailed
and updated the breaks/replaces versions in debian/control.in (forgot
that was needed, I though it was doing automatically on the current
version to avoid to manually do it/reminder to update) and I'm
sponsoring the change

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

Title:
  [SRU] Bad icon for bluetooth sound device

Status in adwaita-icon-theme package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * Bluetooth connected speakers appear in the Bluetooth settings and
  the Sound settings of System Settings with a broken icon.

   * This change simply moves the missing icon in to the default set.

  
  [Test Case]

   * Pair a Bluetooth speaker via the Bluetooth section of System Settings.
   * Once paired note that the icon appears as a small speaker and not a black 
square with a red warning symbol in (indicating a missing icon)
   * Once paired open the Sound Settings of System Settings and note that the 
Bluetooth speaker is displayed with the same speaker icon and not the broken 
icon.

  [Regression Potential]

   * Very low.  This patch simply adds the missing icon to the default
  set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1555170/+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 1555170] Re: Bad icon for bluetooth sound device

[Will Cooke]

** Description changed:

- 1) The release of Ubuntu I am using
- Description:  Ubuntu 15.10
- Release:  15.10
+ [Impact]
  
- 2) The version of the package I am using
- unity-control-center:
-   Installé : 15.04.0+15.10.20150923-0ubuntu1
-   Candidat : 15.04.0+15.10.20150923-0ubuntu1
-  Table de version :
-  *** 15.04.0+15.10.20150923-0ubuntu1 0
- 500 http://fr.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
- 100 /var/lib/dpkg/status
-  
- 3) What I expected to happen
- Get a BT icon
+  * Bluetooth connected speakers appear in the Bluetooth settings and the
+ Sound settings of System Settings with a broken icon.
  
- 4) What happened instead
- A default icon (see attachment)
+  * This change simply moves the missing icon in to the default set.
  
  
- Thanks
+ [Test Case]
+ 
+  * Pair a Bluetooth speaker via the Bluetooth section of System Settings.
+  * Once paired note that the icon appears as a small speaker and not a black 
square with a red warning symbol in (indicating a missing icon)
+  * Once paired open the Sound Settings of System Settings and note that the 
Bluetooth speaker is displayed with the same speaker icon and not the broken 
icon.
+ 
+ [Regression Potential]
+ 
+  * Very low.  This patch simply adds the missing icon to the default
+ set.

** Summary changed:

- Bad icon for bluetooth sound device
+ [SRU] Bad icon for bluetooth sound device

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

Title:
  [SRU] Bad icon for bluetooth sound device

Status in adwaita-icon-theme package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  [Impact]

   * Bluetooth connected speakers appear in the Bluetooth settings and
  the Sound settings of System Settings with a broken icon.

   * This change simply moves the missing icon in to the default set.

  
  [Test Case]

   * Pair a Bluetooth speaker via the Bluetooth section of System Settings.
   * Once paired note that the icon appears as a small speaker and not a black 
square with a red warning symbol in (indicating a missing icon)
   * Once paired open the Sound Settings of System Settings and note that the 
Bluetooth speaker is displayed with the same speaker icon and not the broken 
icon.

  [Regression Potential]

   * Very low.  This patch simply adds the missing icon to the default
  set.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1555170/+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 49521] Re: Screen locks up black on laptop lid close.

[.]

I fixed my problem on Dell laptop by changing Screensaver (XScreenSaver 5.34) 
settings. 
Display Modes
Mode: Blank Screen Only or Disable Screen Saver

I guess the screen saver program was not working well. I glimpsed the
monitor had weird colors.

Laptop Lid is closed: both Switch off display and Lock screen work after
the change.

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

Title:
  Screen locks up black on laptop lid close.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Binary package hint: acpi

  On my Dell 640C laptop, my screen locks up black whenever I close the
  lid.

  Doesn't matter if I have it set to sleep/suspend, blank screen, or
  just no event. Whenever I close the lid, it locks up black and nothing
  short of restarting Gnome or rebooting can get my screen back.

  Thanks for any fixes/suggestions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/49521/+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 1555170] Re: Bad icon for bluetooth sound device

[Sebastien Bacher]

** Changed in: unity-control-center (Ubuntu)
 Assignee: Will Cooke (willcooke) => (unassigned)

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

Title:
  Bad icon for bluetooth sound device

Status in adwaita-icon-theme package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu I am using
  Description:  Ubuntu 15.10
  Release:  15.10

  2) The version of the package I am using
  unity-control-center:
Installé : 15.04.0+15.10.20150923-0ubuntu1
Candidat : 15.04.0+15.10.20150923-0ubuntu1
   Table de version :
   *** 15.04.0+15.10.20150923-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status
   
  3) What I expected to happen
  Get a BT icon

  4) What happened instead
  A default icon (see attachment)

  
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1555170/+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 1574347] Re: [SRU]network-manager

[Marcin Sochacki]

For me, the version 1.2.0-0ubuntu0.16.04.2 fixes the issue with wifi not
visible after fresh boot. Now it works fine.

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

Title:
  [SRU]network-manager

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

  [Testcase]

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1555170] Re: Bad icon for bluetooth sound device

[Will Cooke]

Move audio-speakers from the full theme to the default one.


** Patch added: "debdiff.patch"
   
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1555170/+attachment/4661513/+files/debdiff.patch

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

Title:
  Bad icon for bluetooth sound device

Status in adwaita-icon-theme package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu I am using
  Description:  Ubuntu 15.10
  Release:  15.10

  2) The version of the package I am using
  unity-control-center:
Installé : 15.04.0+15.10.20150923-0ubuntu1
Candidat : 15.04.0+15.10.20150923-0ubuntu1
   Table de version :
   *** 15.04.0+15.10.20150923-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status
   
  3) What I expected to happen
  Get a BT icon

  4) What happened instead
  A default icon (see attachment)

  
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1555170/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Richard Elkins]

Thanks for your efforts, Till.  Sounds reasonable to me.

Can I assume that someone has or will have it on their list to
reintegrate lsb into 16.10?

Until I am contacted during the 16.04 Stable Release Update (SRU)
process, I will go back to using Trusty for the lsb modules:

---
1) Append

 deb http://cz.archive.ubuntu.com/ubuntu trusty main

to /etc/apt/sources.list.

2) sudo apt update; sudo apt install lsb

3) Install the Epson printer driver that I need (Epson XP-410).
---

If there is anything else that I need to do, please let me know.

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Committed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+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 1579415] Re: Ubuntu Software Center does not display third party apps or all installed apps

[Matthias Klumpp]

Synaptic and Muon look at packages, which is something different than 
applications.
Applications and software with much metadata is in a different file. We 
generate the data from packages, but it is not the same as a package. In order 
to get enough metadata out, the packages must match some criteria, and meeting 
those is the job of the individual package maintainers.
So, your bug against gnome-software is actually a bug against Krita, bug 
#1576827 in particular.

Since samba is a technical thing, it will likely never be shown in a
tool like GNOME Software, instead it will be installed in an app
actually wants it.

3rd-party repos not being able to display apps is another, different
bug, bug#1576780

So, yeah, that's the whole story. Maybe this issue can be closed in GS
as invalid.

The "nobody cared enough" statement was basically me being frustrated with not 
enough people caring to fix their metadata, something which will improve in 
future, fortunately.
(We will also have more visible diagnostic messages in Debian soon, which 
should help fixing this issue. See 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806740 )

** Bug watch added: Debian Bug tracker #806740
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806740

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

Title:
  Ubuntu Software Center does not display third party apps or all
  installed apps

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  gnome-software:
    Installed: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Candidate: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Version table:
   *** 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  The new Ubuntu Software Center does not display all software. For
  example no third party repo applications are displayed.

  Search for example:

  Ubuntu-restricted-extras - no results
  muon - no results
  krita - no results
  samba - no results

  These do not show under installed either, though they are installed.

  However, all are shown in Synaptic Package Manager and MUON

  Additional:

  I have installed the old Ubuntu Software Center and can confirm that
  ALL applications are correctly listed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1579415/+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 1581205] Re: Inconsistent naming of application binary, package and self description

[Sebastien Bacher]

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Inconsistent naming of application binary, package and self
  description

Status in nautilus package in Ubuntu:
  New

Bug description:
  When clicking on the about dialog in the help menus you will see the
  following message:

  Files

  3.14.3

  Access and organizer files.

  
  This a very dumbed down message in sake of simplicity which leaves the users 
wondering which package installs this application. I don't care if GNOME dev's 
want to make life harder for their users. Ubuntu should strive for a better 
solution. 
  Binary and the source packages are called nautilus, and the binary program 
file is also called nautilus. 

  The name nautilus itself isn't very descriptive, and maybe bad for
  marketing (what does nautilus Cephalopoda has to do with files???).
  However, the about dialog should refer to the name of the binary
  program. It should display something like:

  
  Nautilus File Manager

  3.14.3

  Access and organizer files.

  This message is more helpful when searching for help about the program
  itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1581205/+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 1574347] Re: [SRU]network-manager

[Sebastien Bacher]

the issues reported there could be different one, no point trying to
make the SRU perfect before landing or it's never going to move to
update, if you still have issue with that new version better to open a
new bug and use that for debugging

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

Title:
  [SRU]network-manager

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

  [Testcase]

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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

[Sebastien Bacher]

the log doesn't seem to have useful clue ... could you "stop unity-
settings-daemon" and lock/unlock the screen, just to see if that's also
doing it without usd?

-- 
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:
  Unknown
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress

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 1555170] Re: Bad icon for bluetooth sound device

[Sebastien Bacher]

** Package changed: ubuntu-themes (Ubuntu) => adwaita-icon-theme
(Ubuntu)

** Changed in: adwaita-icon-theme (Ubuntu)
 Assignee: (unassigned) => Will Cooke (willcooke)

** Changed in: adwaita-icon-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: unity-control-center (Ubuntu)
   Status: New => Invalid

** Changed in: adwaita-icon-theme (Ubuntu)
   Status: New => In Progress

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

Title:
  Bad icon for bluetooth sound device

Status in adwaita-icon-theme package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  1) The release of Ubuntu I am using
  Description:  Ubuntu 15.10
  Release:  15.10

  2) The version of the package I am using
  unity-control-center:
Installé : 15.04.0+15.10.20150923-0ubuntu1
Candidat : 15.04.0+15.10.20150923-0ubuntu1
   Table de version :
   *** 15.04.0+15.10.20150923-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status
   
  3) What I expected to happen
  Get a BT icon

  4) What happened instead
  A default icon (see attachment)

  
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1555170/+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 1581208] [NEW] "Choose file from local disk" window keeps selecting with rectangle selection

[Piotr]

Public bug reported:

Whenever I try to choose some files to upload from my local disk, the
window that shows up doesn't let me choose files. It's like my left
mouse button was always pressed and it's showing rectangular selection.
Also I'm not able to press column headers to sort by. This started to
happen after I upgraded to latest firefox 46. I did "refresh" firefox
after upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 46.0+build5-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  peter  2664 F pulseaudio
BuildID: 20160425115534
Channel: Unavailable
CurrentDesktop: KDE
Date: Thu May 12 22:15:59 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 2016-01-25 (108 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
IpRoute:
 default via 192.168.0.1 dev wlan0  proto static 
 192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.14  metric 9
Locales: extensions.sqlite corrupt or missing
Plugins:
 Java(TM) Plug-in 11.45.2 - [HomeDir]/jdk1.8.0_45/jre/lib/amd64/libnpjp2.so
 Shockwave Flash - [HomeDir]/.mozilla/plugins/libflashplayer.so
PrefSources:
 prefs.js
 
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
ProcEnviron:
 LANGUAGE=pl
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=46.0/20160425115534 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0NJT03
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L502X
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  "Choose file from local disk" window keeps selecting with rectangle
  selection

Status in firefox package in Ubuntu:
  New

Bug description:
  Whenever I try to choose some files to upload from my local disk, the
  window that shows up doesn't let me choose files. It's like my left
  mouse button was always pressed and it's showing rectangular
  selection. Also I'm not able to press column headers to sort by. This
  started to happen after I upgraded to latest firefox 46. I did
  "refresh" firefox after upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 46.0+build5-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  peter  2664 F pulseaudio
  BuildID: 20160425115534
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Thu May 12 22:15:59 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 2016-01-25 (108 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.14  metric 
9
  Locales: extensions.sqlite corrupt or missing
  Plugins:
   Java(TM) Plug-in 11.45.2 - [HomeDir]/jdk1.8.0_45/jre/lib/amd64/libnpjp2.so
   Shockwave Flash - [HomeDir]/.mozilla/plugins/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
  ProcEnviron:
   LANGUAGE=pl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=46.0/20160425115534 (In use)
  

[Desktop-packages] [Bug 1511735] Re: libnl: fail to bind() netlink sockets

[Galen Thurber]

yet another bullshit fix

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

Title:
  libnl: fail to bind() netlink sockets

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Trusty:
  Fix Released
Status in libnl3 package in Debian:
  Fix Released

Bug description:
  [Triage Notes]

  The proposed fix for this bug in libnl3 caused a regression in trusty-
  proposed, tracked in bug 1539634. The regression is caused by a latent
  bug in Network Manager. We expect to fix this by landing a fix for the
  bug in Network Manager in trusty-updates at the same time as this fix.

  [Impact]

   * Applications in Trusty using libnl-3-200 which frequently open and
     close netlink sockets can easily fail when attempting to bind the
     local socket.  The problem happens when libnl choose a port id
     already used by another application and subsequently libnl fails
     instead of trying another port id.

     The original bug was discovered when attempting to start a virtual
     machine under libvirt, which is a user of this library.

   * Backporting fixes from upstream release fixes a real bug in the
     current version of the library in Trusty.  The alternative is for all
     applications to manually manage their local port allocation, or as
     upstream has accepted allowing libnl to attempt to try for other
     local ports.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

  [Test Case]

   * On a Trusty 14.04 system
     1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \
     libnl-genl-3-dev libnl-route-3-200 \
     make gcc build-essential libnl1
     2. download and unpack attachment: lp_1511735_test.tar
     3. Run testcases:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 6975 (pid: 6974)
  local port has been set by the libnl to 6975 (pid: 6975)
  ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975)
  libnl FAILED
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=6978
  TEST (a)...
  Traceback (most recent call last):
    File "libnl3-test-rh1249158.py", line 226, in 
  locals()["TEST_" + arg]()
    File "libnl3-test-rh1249158.py", line 140, in TEST_a
  sk = nl_get_socket()
    File "libnl3-test-rh1249158.py", line 115, in nl_get_socket
  raise IOError(-err, _nl_geterror())
  OSError: [Errno 6] b'Unspecific failure'

     4. After applying the updated packages:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 11295 (pid: 11294)
  local port has been set by the libnl to 2894081055 (pid: 11295)
  libnl OK
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=11296
  TEST (a)...
  ...done
  TEST (b)...
  ...done
  TEST (c)...
  ...done
  TEST (d)...
  ...done

  [Regression Potential]

   * There are quite a few high profile packages that depend on this package,
     notably libvirt and network-manager.  The complete list is here:

     # on Trusty
  % apt-rdepends -r libnl-3-200 | head -n 33
  libnl-3-200
    Reverse Depends: batctl (>= 2013.4.0-2)
    Reverse Depends: bmon (>= 1:3.1-1)
    Reverse Depends: crda (>= 1.1.2-1ubuntu2)
    Reverse Depends: hostapd (>= 1:2.1-0ubuntu1)
    Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1)
    Reverse Depends: iw (>= 3.4-1)
    Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1)
    Reverse Depends: kismet (>= 2013.03.R1b-3)
    Reverse Depends: knemo (>= 0.7.6-2)
    Reverse Depends: libfsobasics3 (>= 0.12.0-4)
    Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1)
    Reverse Depends: libnl-3-200-dbg (= 3.2.21-1)
    Reverse Depends: libnl-3-dev (= 3.2.21-1)
    Reverse Depends: libnl-cli-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-genl-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-nf-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-route-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-utils (>= 3.2.21-1)
    Reverse Depends: libnss-gw-name (>= 0.3-2)
    Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13)
    Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13)
    Reverse Depends: lowpan-test-tools (>= 0.3-1)
    Reverse Depends: lowpan-tools (>= 0.3-1)
    Reverse Depends: neard (>= 0.11-1)
    Reverse Depends: neard-tools (>= 0.11-1)
    Reverse Depends: network-manager (>= 0.9.8.8-0ubuntu7)
    Reverse Depends: 

[Desktop-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm

[Sebastien Bacher]

setting back to new, it works for me and I've no idea offhand, needs
debugging (ideally by somebody getting the bug)

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => 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/1574020

Title:
  Can't use networkmanager from lightdm

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04  desktop (unity) (clean install) from 14.04,
  (so not really upgrading, but you get the point) I noticed that
  lightdm with unity-greeter (all stock, nothing changed) can't connect
  to WiFi with network-manager.

  WiFi works after loggin it, but it should be working before also, if
  not, what's the point in having an icon there :)

  I get the following message: Failed to add/activate connection. - (1) 
Insufficient privileges. - see image.
  This worked fine in 14.04.

  I have noticed this problem in both my desktop (Broadcom WiFi) and
  Laptop (Intel WiFi) - So it has nothing to be with the chip.

  Feel free to ask for more info.

  Edit:

  From syslog:

  Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: 
assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed
  Apr 23 16:50:46 desktop NetworkManager[979]:   [1461423046.1662] audit: 
op="connection-add-activate" pid=1275 uid=108 result="fail" 
reason="Insufficient privileges."
  Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): 
GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' 
failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/+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 1575555] Re: Chrome/Chromium use "Thin" as default font weight

[Gunnar Hjalmarsson]

On 2016-05-12 21:03, Dhoulmagus wrote:
> For example, in this page:
> https://www.google.com/?ion=1=2#q=%E9%97%A8 I want "门" in SC
> instead of JP.

Then a stupid question from someone who doesn't understand any CJK
characters: How significant is the difference in appearance?

Another question: Does also Firefox fall back to JP when rendering pages
which are not language specified?

> Is there any way the user can manually set the CJK fallback font(in
> Chrome, or in somewhere else)?

Yes, there are such ways. Actually, if your session language is
zh_CN.UTF-8, then the fontconfig configuration makes SC the default.

However, if I understand it correctly, Chrome doesn't care about
fontconfig. OTOH you can specify the font in Chrome's "Settings"
(advanced).

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

Title:
  Chrome/Chromium use "Thin" as default font weight

Status in fonts-noto-cjk package in Ubuntu:
  Fix Released
Status in fonts-noto-cjk source package in Xenial:
  Fix Committed
Status in fonts-noto-cjk package in Debian:
  Fix Released

Bug description:
  [Impact]

  Chromium and Google Chrome use "Thin" as the default Noto Sans CJK
  font weight, which makes some Chinese and Japanese web pages difficult
  to read, and thus gives a bad user experience.

  The fonts-noto-cjk version in the PPA

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fonts-noto-cjk

  installs 7 weight specific font files instead of a single "super"
  file. This works around the Chromium/Chrome issue.

  Note: It has been fixed in yakkety via autosync, so "backporting"
  yakkety (as an SRU) instead of uploading from the PPA is an option.

  [Test Case]

  To reproduce the bug:

  * Install Chromium or Google Chrome.
  * Go to  and notice the very thin characters.
  * Install fonts-noto-cjk from the PPA and notice the difference.

  [Regression Potential]

  This is about another font packaging form, without any change in glyph
  coverage, so the the regression risk should be low.

  [Original description]

  The package seems to only "thin" variant of the font, which makes it
  very unreadable in applications such as Chrome (when it has to fall
  back on Chinese fonts on a mostly-English page). I had to remove the
  package and then manually download the font from Google website and
  install it to make the regular weight available

  Release: 16.04 LTS
  Package Version: 1.004+repack1-1
  Expected: All weights of the noto cjk font to be installed
  Happened: Only the "thin" weight of the font seems to be installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/157/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Till Kamppeter]

Richard, I cannot directly upload the lsb source package, this has to be
done by an appropriate maintainer or a Ubuntu core developer. In
addition, the package would go into the development branch of the next
Ubuntu release, 16.10 or Yakkety Yak. To get it installable into Xenial
via apt, an SRU (Stable Release Update) is needed.

I have attached the patch to this bug report so that Adam Conrad and/or
Steve Langasek can upload the package to Yakkety and after that do the
SRU. During the SRU process you will get asked for testing the fixed
package, here in this bug report.

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Committed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+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 1536353] Re: [regression] Printer drivers install is broken as lsb package is not available anymore

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  [regression] Printer drivers install is broken as lsb package is not
  available anymore

Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Committed
Status in system-config-printer package in Ubuntu:
  Invalid

Bug description:
  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1536353/+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

[Mario Limonciello]

Sure.  Here you go.


** Attachment added: "usd.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510344/+attachment/4661498/+files/usd.txt

-- 
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:
  Unknown
Status in One Hundred Papercuts:
  Confirmed
Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  In Progress

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 1555170] Re: Bad icon for bluetooth sound device

[Will Cooke]

Turns out we just need to add the audio-speakers icon from the full icon
set to our default on.

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

Title:
  Bad icon for bluetooth sound device

Status in ubuntu-themes package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu I am using
  Description:  Ubuntu 15.10
  Release:  15.10

  2) The version of the package I am using
  unity-control-center:
Installé : 15.04.0+15.10.20150923-0ubuntu1
Candidat : 15.04.0+15.10.20150923-0ubuntu1
   Table de version :
   *** 15.04.0+15.10.20150923-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status
   
  3) What I expected to happen
  Get a BT icon

  4) What happened instead
  A default icon (see attachment)

  
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1555170/+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 1578127] Re: Sometimes WLAN detects no SSID after s3

[Sebastien Bacher]

Could you try with the new version in proposed? it include an extra
bugfix that might fix that issue

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

Title:
  Sometimes WLAN detects no SSID after s3

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  [Steps to reproduce]
  1. Boot into OS
  2. Do s3 a few times
  3. Check if wifi is still working after s3

  [Expected results]
  wifi still working correctly after s3

  [Actual results]
  1. Wifi shows "disconnected" in network-manager (both in applet and from 
command "nmcli d status")
  2. Only one random SSID is displayed in network-manager applet, but wifi 
connection cannot be established at all with this SSID. Clicking on the SSID 
results in pop up window in the comment #2 below
  3. "nmcli d wifi rescan" does not resolve issue
  4.  "iwlist [interface] scan" returns nothing and does not reolve issue
  5. "nmcli d wifi connect [any SSID that you know should exist]" results in 
SSID not found and does not resolve issue
  6. "sudo service network-manager restart", warm boot, cold boot resolves issue

  [Details]
  OS: Xenial based OEM image
  WLAN module: Marvel [11ab:2b38]
  network-manager:
  - 1.2.0-0ubuntu0.16.04.1 (fail rate 1/20~ 1/15)
  - 1.1.93 (fail rate 1/15)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1578127/+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 1579415] Re: Ubuntu Software Center does not display third party apps or all installed apps

[pst007x]

So, this is not normal and is a bug however, this is not the place
to report this bug?

"not enough people caring about it." so what you are saying that using
this as a package manager is not high on the list of importance.

It is just strange that if the fault was with the packages then why are
ALL applications listed in Synaptic and MUON?

Anyway clearly no one seems that worried that it is currently broken
so best to not use it and stick to alternatives No probs... Thanks

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

Title:
  Ubuntu Software Center does not display third party apps or all
  installed apps

Status in gnome-software package in Ubuntu:
  Opinion

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  gnome-software:
    Installed: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Candidate: 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1
    Version table:
   *** 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  The new Ubuntu Software Center does not display all software. For
  example no third party repo applications are displayed.

  Search for example:

  Ubuntu-restricted-extras - no results
  muon - no results
  krita - no results
  samba - no results

  These do not show under installed either, though they are installed.

  However, all are shown in Synaptic Package Manager and MUON

  Additional:

  I have installed the old Ubuntu Software Center and can confirm that
  ALL applications are correctly listed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1579415/+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