[Desktop-packages] [Bug 1537065] Re: XRandR Error

2016-10-21 Thread Launchpad Bug Tracker
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  XRandR Error

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  XRandR returned error code 1: X Error of failed request: Bad Value (integer 
parameter out of range for operation)
  Major opcode of failed request: 140 (RANDR)
  Minor opcode of failed request: 7 (RRSetScreenSize)
  Value in failed request: 0x0
  Serial number of failed request: 49
  Current serial number in output stream: 50

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: arandr 0.1.8-1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jan 22 15:34:00 2016
  InstallationDate: Installed on 2012-05-25 (1336 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  PackageArchitecture: all
  SourcePackage: arandr
  UpgradeStatus: Upgraded to wily on 2015-10-26 (87 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1537065/+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 1607711] Re: Starting nautilus crashes with Segmentation Fault

2016-10-21 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Starting nautilus crashes with Segmentation Fault

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  After last updates to my Ubuntu 16.04 x64 nautilus crashes with the
  following message:

  misel@misel-amphinicy[~]:
  [11:44:18]  $ nautilus
  Maximum number of clients reached
  ** (nautilus:25112): WARNING **: Could not open X display
  sys:1: PyGIWarning: Nautilus was imported without specifying a version first. 
Use gi.require_version('Nautilus', '3.0') before import to ensure that the 
right version gets loaded.
  [Errno 2] No translation file found for domain: 'nautilus-image-tools'
  Initializing nautilus-image-converter extension
  Initializing nautilus-dropbox 2.10.0

  ** (nautilus:25112): CRITICAL **:
  nautilus_menu_provider_get_background_items: assertion
  'NAUTILUS_IS_MENU_PROVIDER (provider)' failed

  ** (nautilus:25112): CRITICAL **: 
nautilus_menu_provider_get_background_items: assertion 
'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
  Maximum number of clients reached
  (nautilus:25112): GnomeDesktop-WARNING **: Unable to open display ':0' when 
setting background pixmap

  Segmentation fault (core dumped)
  misel@misel-amphinicy[~]:
  [11:44:20]

  backtrace:

  misel@misel-amphinicy[/usr/bin]:
  [11:46:17]  $ LC_ALL=EN_US gdb nautilus
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from nautilus...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /usr/bin/nautilus
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (EN_US)
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  (nautilus:26865): Gtk-WARNING **: Locale not supported by C library.
  Using the fallback 'C' locale.
  [New Thread 0x7fffe8b3f700 (LWP 26869)]
  [New Thread 0x7fffe3fff700 (LWP 26870)]
  [New Thread 0x7fffe37fe700 (LWP 26871)]
  [New Thread 0x7fffe2997700 (LWP 26872)]
  Maximum number of clients reached
  ** (nautilus:26865): WARNING **: Could not open X display
  sys:1: PyGIWarning: Nautilus was imported without specifying a version first. 
Use gi.require_version('Nautilus', '3.0') before import to ensure that the 
right version gets loaded.
  [Errno 2] No translation file found for domain: 'nautilus-image-tools'
  Initializing nautilus-image-converter extension
  Initializing nautilus-dropbox 2.10.0
  [New Thread 0x7fffc96ef700 (LWP 26883)]
  [New Thread 0x7fffc3d96700 (LWP 26884)]

  ** (nautilus:26865): CRITICAL **: 
nautilus_menu_provider_get_background_items: assertion 
'NAUTILUS_IS_MENU_PROVIDER (provider)' failed
  Maximum number of clients reached
  (nautilus:26865): GnomeDesktop-WARNING **: Unable to open display ':0' when 
setting background pixmap

  Thread 1 "nautilus" received signal SIGSEGV, Segmentation fault.
  0x75bd3c10 in cairo_surface_set_device_scale () from 
/usr/lib/x86_64-linux-gnu/libcairo.so.2
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1607711/+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 1584367] Re: Samsung printer automatically disabled; cannot print

2016-10-21 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Samsung printer automatically disabled; cannot print

Status in cups package in Ubuntu:
  Expired

Bug description:
  Samsung ML-1660 laser printer is found and installed, but cannot print
  as it is automatically disabled. CUPS error log is filled with the
  following:

  E [21/May/2016:10:55:13 -0600] [cups-deviced] PID 26623
  (gutenprint52+usb) stopped with status 1!

  This behaviour is new in Xenial, it worked fine in Trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1584367/+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 1615423] Re: it was working fine from original install, one day it just stopped! sounds like a cocked up update by someone

2016-10-21 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  it was working fine from original install, one day it just stopped!
  sounds like a cocked up update by someone

Status in cups package in Ubuntu:
  Expired

Bug description:
  from install it was fine, but all of a sudden it lost all printers and
  will not add any

  16.04.1
  chris@chris-Aspire-ES1-531:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 21 19:16:31 2016
  InstallationDate: Installed on 2016-05-08 (105 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire ES1-531
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=10bd2765-6533-408d-9409-e1af69fef990 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire ES1-531
  dmi.board.vendor: Acer
  dmi.board.version: V1.11
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd07/21/2015:svnAcer:pnAspireES1-531:pvrV1.11:rvnAcer:rnAspireES1-531:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.name: Aspire ES1-531
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1615423/+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 1615395] Re: Ubuntu 16.04 no sound devices showing

2016-10-21 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Ubuntu 16.04 no sound devices showing

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I recently upgraded my laptop from Ubuntu 15.04 to 16.04. After that
  no sound is working, there is no sound devices listed in sound
  settings. Please help to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Aug 21 20:52:55 2016
  InstallationDate: Installed on 2015-05-28 (451 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to xenial on 2016-08-20 (1 days ago)
  dmi.bios.date: 08/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 02RD2H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd08/05/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn02RD2H:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1615395/+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 1615465] Re: Missing icons when using i3 window manager

2016-10-21 Thread Launchpad Bug Tracker
[Expired for unity-control-center (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unity-control-center (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Missing icons when using i3 window manager

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

Bug description:
  New Ubuntu 16.04, when using i3 instead of the default window manager
  most of the icons are missing. see picture -
  https://cloud.githubusercontent.com/assets/6517/17843460/14034200-67e3-11e6
  -998e-88e2d5f37539.png

  Also, I see this output in the terminal: '(unity-control-
  center:30149): WARNING **: Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus-C0aH1WkQr3: Connection refused'

  I reported it to i3 (https://github.com/i3/i3/issues/2430) but I was
  told it's unity-control-center issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04.1
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  Uname: Linux 4.4.0-34-generic x86_64
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 21 21:25:59 2016
  SourcePackage: unity-control-center

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1615465/+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 1635774] Re: package libflite1 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to '/usr/lib/x8

2016-10-21 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: flite (Ubuntu)
   Status: New => Invalid

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

Title:
  package libflite1 (not installed) failed to install/upgrade: cannot
  copy extracted data for './usr/lib/x86_64-linux-
  gnu/libflite_cmu_us_rms.so.1.4' to '/usr/lib/x86_64-linux-
  gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end of file or
  stream

Status in flite package in Ubuntu:
  Invalid

Bug description:
  This happened while installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libflite1 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct 21 19:50:59 2016
  DuplicateSignature: package:libflite1:(not installed):cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
  InstallationDate: Installed on 2016-10-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: flite
  Title: package libflite1 (not installed) failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' 
to '/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1635774/+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 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update

2016-10-21 Thread quequotion
>Nazar
Unfortunately not. That package could be recompiled for newer versions of 
Ubuntu, but the code itself is from gnome-settings-daemon 3.6.4 and will never 
be updated. It should really be released in it's own PPA, but I could never 
grasp debian packaging--it is more difficult to package programs for Ubunu than 
to write them.

Some other gnome-derivative desktops have followed gnome's example by
incorporating the media-keys listening service into their own desktop
shell.

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

Title:
  Volume up/down keyboard keys stoped working after gnome-settings-
  daemon package update

Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4
  to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not
  working.

  Pressing the keys does not produce the volume OSD, neither the volume
  is increased or decreased.

  The following packages were updated by synaptic:
  cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise
  duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3
  gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa
  gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa
  gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5
  libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise
  libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa
  xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5
  xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 
2:1.13.0-0ubuntu6.5~precise1
  xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 
2:1.13.0-0ubuntu6.5~precise1

  I suspected that the bug might be in xkb-data and/or gnome-settings-daemon.
  Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't 
work.
  Downgrading the gnome-settings-daemon package to the previous version 
(3.4.2-0ubuntu0.6.4) worked!
  Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and 
left gnome-settings-daemon package to the previous version 
(3.4.2-0ubuntu0.6.4). And this works!!!

  In conclusion there is some regression introduced into gnome-settings-
  daemon 3.4.2-0ubuntu0.6.5.

  lsb_release -rd
  Description:  Ubuntu 12.04.3 LTS
  Release:  12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+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 1635774] [NEW] package libflite1 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to '/usr/lib/

2016-10-21 Thread Thomas Beltran
Public bug reported:

This happened while installing updates

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libflite1 (not installed)
ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
Uname: Linux 3.13.0-100-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Fri Oct 21 19:50:59 2016
DuplicateSignature: package:libflite1:(not installed):cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
InstallationDate: Installed on 2016-10-22 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.15
SourcePackage: flite
Title: package libflite1 (not installed) failed to install/upgrade: cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package libflite1 (not installed) failed to install/upgrade: cannot
  copy extracted data for './usr/lib/x86_64-linux-
  gnu/libflite_cmu_us_rms.so.1.4' to '/usr/lib/x86_64-linux-
  gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end of file or
  stream

Status in flite package in Ubuntu:
  New

Bug description:
  This happened while installing updates

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libflite1 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Fri Oct 21 19:50:59 2016
  DuplicateSignature: package:libflite1:(not installed):cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' to 
'/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected end 
of file or stream
  InstallationDate: Installed on 2016-10-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.15
  SourcePackage: flite
  Title: package libflite1 (not installed) failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4' 
to '/usr/lib/x86_64-linux-gnu/libflite_cmu_us_rms.so.1.4.dpkg-new': unexpected 
end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1635774/+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 1635773] [NEW] fonts in the address bar of chrome/chromium are too small

2016-10-21 Thread RCV
Public bug reported:

After upgrade to 16.10 fonts in address bar of chromium/chrome are too
small and cannot be tune by unity tweak tool.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  fonts in the address bar of chrome/chromium are too small

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  After upgrade to 16.10 fonts in address bar of chromium/chrome are too
  small and cannot be tune by unity tweak tool.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1635773/+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 1373070] Re: full fix for disconnected path (paths)

2016-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  full fix for disconnected path (paths)

Status in cups package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  With the apparmor 3 RC1 upload, there is an incomplete bug fix for
  disconnected paths. This bug is to track that work.

  This denial may be related:
  Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 
audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed 
name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" 
name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  This is related to bug 1375410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+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 1360342] Re: Add Multi-arch support in libxi-dev

2016-10-21 Thread Bug Watch Updater
** Changed in: libxi (Debian)
   Status: Unknown => New

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

Title:
  Add Multi-arch support in libxi-dev

Status in libxi package in Ubuntu:
  Confirmed
Status in libxi package in Debian:
  New

Bug description:
  Please add Multi-arch support in libxi-dev. Would really help in
  crosscompiling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/1360342/+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 1631191] Re: Display backlight won't turn on after screen timeout

2016-10-21 Thread Aaron Dhiman
Hi, I have the same issue with this setup:


Ubuntu 16.04.1 LTS (64-bit)
3.5 GHz i7-6700HQ (6 MB Cache – 4 Cores – 8 Threads)
6 GB GTX 1060 with 1280 CUDA Cores

+-+
| NVIDIA-SMI 367.44 Driver Version: 367.44|
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  GeForce GTX 1060Off  | :01:00.0  On |  N/A |
| N/A   47CP226W /  N/A |202MiB /  6063MiB |  0%  Default |
+---+--+--+

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

Title:
  Display backlight won't turn on after screen timeout

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  Using nVidia driver 367.44 on Skylake Intel Processors, with 1000
  series graphics, the backlight won't turn on after turned off by gnome
  session idle delay (org.gnome.desktop.session idle-delay). or by `xset
  dpms force off`

  Resume from suspend is unaffected.

  This is on a clean install of 16.10 with the 367.44 nVidia driver.
  This is a regression from the 367.35 driver.  367.48 and 370.28 also
  exhibit this behavior.

  This is confirmed on the following hardware:

  Oryx Pro 2 (oryp2) i7-6700HQ with 1070
  Serval 10 (serw10) i7-6700 with 1060
  Bonobo 11 (bonw11) i7-6700K with dual 1070

  Steps to reproduce:

  1. Install a fresh image of Yakkety and 367.44 from the graphics driver 
team's PPA.
  2. Log in to Unity shell
  3. Lock screen and wait for dimming.
  4. Move the mouse to 'resume'
  5. The screen will turn on, but the backlight is still off

  The current workaround:

  1. Hit tty1 (Ctrl+Alt+F1)
  2. Hit tty7 (Ctrl+Alt+F7)

  This will bring Unity back to life.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.44-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct  6 16:17:11 2016
  SourcePackage: nvidia-graphics-drivers-367
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1631191/+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 1635753] [NEW] After Installing Ubuntu

2016-10-21 Thread Joshua Arnejo
Public bug reported:

My further request for any crashing applications and errors, please that
I promise when I use this Operating System after I installed types of
applications.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
BootLog: /dev/sda5: clean, 312852/12214272 files, 4583018/48827904 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Oct 22 07:21:26 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-10-12 (9 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=e31e261f-58b4-4524-974a-ad1958cf37e5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: H55M-LE
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.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE: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.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Oct 22 06:00:57 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSIGMACHIP Usb Mouse  MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.1
xserver.video_driver: nouveau

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


** Tags: apport-bug compiz-0.9 i386 possible-manual-nvidia-install ubuntu xenial

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

Title:
  After Installing Ubuntu

Status in xorg package in Ubuntu:
  New

Bug description:
  My further request for any crashing applications and errors, please
  that I promise when I use this Operating System after I installed
  types of applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  BootLog: /dev/sda5: clean, 312852/12214272 files, 4583018/48827904 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Oct 22 07:21:26 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2016-10-12 (9 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_PH:en
  

[Desktop-packages] [Bug 1634802] Re: Could not insert module

2016-10-21 Thread Ricardo Almeida
Not working for me either :(

Is this the same issue that got fixed in Debian (https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=809324)? How can we get this to be patched in
Ubuntu? My machine is not very usable at the moment :(

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

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

Title:
  Could not insert module

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu release: 16.10 Yakkety Yak
  Kernel version: 4.8.0-22-generic x86_64
  Package version: 304.132-0ubuntu1

  The nvidia module cannot be loaded. The following errors are reported:
  Could not insert module Unknown symbol in module

  and:

  nvidia: Unknown symbol mtrr_del (err 0)
  nvidia: Unknown symbol mtrr_add (err 0)

  It looks like the buildfix_kernel_4.3.patch, which is supposed to be
  dealing with those calls, is not applied in this release of the
  package.

  The package was working fine with the previous fully updated Ubuntu
  version 16.04 prior to the upgrade to 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+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 1326817] Re: No multi-arch information in libgtksourceview2.0 control files

2016-10-21 Thread Bug Watch Updater
** Changed in: gtksourceview2 (Debian)
   Status: New => Fix Released

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

Title:
  No multi-arch information in libgtksourceview2.0 control files

Status in gtksourceview2 package in Ubuntu:
  New
Status in gtksourceview2 package in Debian:
  Fix Released

Bug description:
  I am trying to install the i386 version of libgtksourceview2.0-0 on my
  64-bit Trusty Tahr installation, but when I run

  apt-get install libgtksourceview2.0-0:i386

  I get:

  [...]
  The following packages have unmet dependencies:
   libgtksourceview2.0-0:i386 : Depends: libgtksourceview2.0-common:i386 (>= 
2.10) but it is not installable
    Depends: libgtksourceview2.0-common:i386 (< 
2.11) but it is not installable
  E: Unable to correct problems, you have held broken packages.

  When looking at the package page of libgtksourceview2.0-common, it
  appears the package is universal (not for any specific architecture),
  hence I cannot install an i386-specific version of it.

  If I tell apt-get to ignore dependencies, libgtksourceview2.0-0:i386
  installs just fine and appears to be working correctly (so far).

  Based on the comments I received on Question #249755, it appears this
  is because "there is no multi-arch information in the control file [of
  the libgtksourceview2.0 package(s)]".

  Please see
  https://answers.launchpad.net/ubuntu/+source/gtksourceview2/+question/249755
  for more information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1326817/+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 1635715] Re: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020

2016-10-21 Thread chris pollock
I forgot to add the package

** Package changed: ubuntu => gnome-settings-daemon (Ubuntu)

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

Title:
  failed to connect to device: Failed to connect to missing device
  /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020

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

Bug description:
  The complete errors that are shown together are:

  Oct 18 08:20:51 localhost systemd[1]: Started CUPS Scheduler.
  Oct 18 08:20:51 localhost gnome-session[1504]: (gnome-settings-daemon:1533): 
color-plugin-WARNING **: failed to connect to device: Failed to connect to 
missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
  Oct 18 08:20:51 localhost gnome-session[1504]: (gnome-settings-daemon:1533): 
color-plugin-WARNING **: failed to connect to device: Failed to connect to 
missing device /org/freedesktop/ColorManager/devices/cups_PDF

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  gnome-settings-daemon:
Installed: 3.18.2-0ubuntu3.1
Candidate: 3.18.2-0ubuntu3.1
Version table:
   *** 3.18.2-0ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.2-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  This happens quite frequently and I'm not sure of the cause.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1635715/+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 1635715] [NEW] failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020

2016-10-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The complete errors that are shown together are:

Oct 18 08:20:51 localhost systemd[1]: Started CUPS Scheduler.
Oct 18 08:20:51 localhost gnome-session[1504]: (gnome-settings-daemon:1533): 
color-plugin-WARNING **: failed to connect to device: Failed to connect to 
missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
Oct 18 08:20:51 localhost gnome-session[1504]: (gnome-settings-daemon:1533): 
color-plugin-WARNING **: failed to connect to device: Failed to connect to 
missing device /org/freedesktop/ColorManager/devices/cups_PDF

Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

gnome-settings-daemon:
  Installed: 3.18.2-0ubuntu3.1
  Candidate: 3.18.2-0ubuntu3.1
  Version table:
 *** 3.18.2-0ubuntu3.1 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 3.18.2-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

This happens quite frequently and I'm not sure of the cause.

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


** Tags: bot-comment
-- 
failed to connect to device: Failed to connect to missing device 
/org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
https://bugs.launchpad.net/bugs/1635715
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-settings-daemon 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 1635730] [NEW] Online Account integration does not work behind proxy

2016-10-21 Thread Swaraj Mohapatra
Public bug reported:

Behind a proxy (in my case a college proxy), Account integration does
not work. Although authorisation with Google Accounts is complete,
email, calendar, documents etc. data does not show up on the respective
default applications.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity-control-center 15.04.0+16.10.20161003.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 22 02:44:39 2016
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2016-10-18 (3 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  Online Account integration does not work behind proxy

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

Bug description:
  Behind a proxy (in my case a college proxy), Account integration does
  not work. Although authorisation with Google Accounts is complete,
  email, calendar, documents etc. data does not show up on the
  respective default applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity-control-center 15.04.0+16.10.20161003.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 22 02:44:39 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-10-18 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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/1635730/+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 1635719] [NEW] package nvidia-304 304.132-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

2016-10-21 Thread Ricardo Almeida
Public bug reported:

Upgrade made graphic card not being detected. Tried uninstall nvidia
driver and says it is broken...

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: nvidia-304 304.132-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Oct 21 21:11:23 2016
DistUpgraded: 2016-10-21 18:55:14,578 INFO cache.commit()
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 nvidia-304, 304.132, 4.8.0-26-generic, x86_64: built
 virtualbox, 5.1.6, 4.4.0-45-generic, x86_64: installed
 virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed
DpkgTerminalLog:
 dpkg: error processing package nvidia-304 (--remove):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
GraphicsCard: NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2011-02-12 (2078 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=7c4525ef-0529-40ec-ad85-5064582e9351 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: nvidia-graphics-drivers-304
Title: package nvidia-304 304.132-0ubuntu1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
a removal
UnitySupportTest:
 Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with 
exit code 5: Xlib:  extension "GLX" missing on display ":0".
 Error: GLX is not available on the system
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago)
dmi.bios.date: 09/07/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: M3A770DE
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.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE: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.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Fri Oct 21 20:09:43 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputgspca_zc3xx  KEYBOARD, id 8
 inputUSB OPTICAL MOUSEMOUSE, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6

** Affects: nvidia-graphics-drivers-304 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package ubuntu yakkety

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

Title:
  package nvidia-304 304.132-0ubuntu1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting a removal

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  New

Bug description:
  Upgrade made graphic card not being detected. Tried uninstall nvidia
  driver and says it is broken...

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: nvidia-304 304.132-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Oct 21 21:11:23 2016
  DistUpgraded: 2016-10-21 18:55:14,578 INFO cache.commit()
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.132, 

[Desktop-packages] [Bug 1611821] Re: Dell XPS One 27: Headphone jack and speakers mutuated after upgrade to 16.04

2016-10-21 Thread Rubeosis
As a workarount use hda-jack-retask

http://askubuntu.com/questions/832248/sound-is-not-working-in-dell-xps-
all-in-one-2710-running-ubuntu-16-04

"Praise of God i could solving the problem by installing "hda-jack-
retask" - open the terminal and post: [ sudo apt-get install alsa-tools-
gui ] - then post: [ hdajackretask ] in the gui of "jack retasking" i
found "green Headphone" set as "headphone" i checked "override" and
choose "internal speaker" then i pressed the button "apply now" then
"install boot override" then reboot finally, the problem solved ... I'm
happy now ... thanks for every one tried to help me ... thank you very
much"

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

Title:
  Dell XPS One 27: Headphone jack and speakers mutuated after upgrade to
  16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Dell XPS One 27: Sound working correctly in 14.04. After complete
  reinstall of 16.04 headphone jack and speakers are mutuated. Manual
  correction of output level (headphones) with alsamixer leads to a
  correct sound output.

  
  Same problem here: 
http://askubuntu.com/questions/810053/speaker-and-headphone-ports-are-switched

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   fabian 3570 F...m pulseaudio
   /dev/snd/controlC0:  fabian 3570 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 10 17:21:18 2016
  InstallationDate: Installed on 2016-08-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 02XMCT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd08/03/2012:svnDellInc.:pnXPSOne2710:pvr00:rvnDellInc.:rn02XMCT:rvrA01:cvnDellInc.:ct13:cvr00:
  dmi.product.name: XPS One 2710
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1611821/+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 1635376] Re: double-clicking on an executable created with gcc6 opens an error message

2016-10-21 Thread Hadrien
I opened that bug for gcc: https://bugs.launchpad.net/ubuntu/+source
/gcc-defaults/+bug/1635706

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

Title:
  double-clicking on an executable created with gcc6 opens an error
  message

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 x64 with Nautilus 3.20.3

  * Open a terminal
  * Install gcc: sudo apt install build-essential
  * Build an executable: printf "int main() { return 1; }" | gcc -x c -
  * Open a Nautilus window on the current directory: nautilus .
  * Double-click on the generated executable: a.out

  Expected result: Nautilus starts the executable. No error is displayed.
  Actual result: Nautilus displays an error message:

     Could not display "a.out".
     There is no application installed for shared library files.
     Do you want to search for an application to open this file?

  Also, all executable files compiled with gcc6 have a generic icon
  instead of the purple lozenge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635376/+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 1634651] Re: Ubuntu gnome-software won't let login to ubuntu one account

2016-10-21 Thread Enrique Agustini
*** This bug is a duplicate of bug 1616943 ***
https://bugs.launchpad.net/bugs/1616943

** Summary changed:

- Ubuntu software-center won't let login to ubuntu one account
+ Ubuntu gnome-software won't let login to ubuntu one account

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

Title:
  Ubuntu gnome-software won't let login to ubuntu one account

Status in gnome-software package in Ubuntu:
  New

Bug description:
  In order to install a proprietary snap package Software Center
  requires a Ubuntu One account in Ubuntu 16.10 however no matter how
  you enter your password and account's e-mail or choose "forgot
  password" option it won't let you log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-center (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 18 18:26:36 2016
  InstallationDate: Installed on 2016-10-18 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-center
  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/1634651/+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 1635376] Re: double-clicking on an executable created with gcc6 opens an error message

2016-10-21 Thread Hadrien
I did a test. I built the same program with gcc5 and gcc6, then I
compared the output of "readelf -a". It happens that Nautilus is right.
gcc on Ubuntu 16.10 creates a shared library by default instead of an
executable (the Type field in the ELF header is different).

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

Title:
  double-clicking on an executable created with gcc6 opens an error
  message

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 x64 with Nautilus 3.20.3

  * Open a terminal
  * Install gcc: sudo apt install build-essential
  * Build an executable: printf "int main() { return 1; }" | gcc -x c -
  * Open a Nautilus window on the current directory: nautilus .
  * Double-click on the generated executable: a.out

  Expected result: Nautilus starts the executable. No error is displayed.
  Actual result: Nautilus displays an error message:

     Could not display "a.out".
     There is no application installed for shared library files.
     Do you want to search for an application to open this file?

  Also, all executable files compiled with gcc6 have a generic icon
  instead of the purple lozenge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635376/+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 1351286] Re: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->sta

2016-10-21 Thread Sergey Saraev
I installed gnome-color-manager. It does not work completely. Error
appears periodically on Ubuntu 16.04.1 LTS.

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

Title:
  colord-sane assert failure: colord-sane: simple-watch.c:454:
  avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT ||
  s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 14.04 to 14.10 alpha.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: colord 1.2.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu2
  Architecture: amd64
  AssertionMessage: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: 
Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state 
== STATE_FAILURE' failed.
  Date: Fri Aug  1 14:00:57 2014
  ExecutablePath: /usr/lib/colord/colord-sane
  InstallationDate: Installed on 2013-12-26 (217 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/colord/colord-sane
  ProcEnviron:
   
  Signal: 6
  SourcePackage: colord
  StacktraceTop:
   __assert_fail_base (fmt=0x7fcda3d688b0 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fcd926f9fb0 "s->state == STATE_INIT 
|| s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", 
file=file@entry=0x7fcd926f9ee8 "simple-watch.c", line=line@entry=454, 
function=function@entry=0x7fcd926fa140 "avahi_simple_poll_prepare") at 
assert.c:92
   __GI___assert_fail (assertion=0x7fcd926f9fb0 "s->state == STATE_INIT || 
s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=0x7fcd926f9ee8 
"simple-watch.c", line=454, function=0x7fcd926fa140 
"avahi_simple_poll_prepare") at assert.c:101
   avahi_simple_poll_prepare () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
   avahi_simple_poll_iterate () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-kodakaio.so.1
  Title: colord-sane assert failure: colord-sane: simple-watch.c:454: 
avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == 
STATE_DISPATCHED || s->state == STATE_FAILURE' failed.
  UpgradeStatus: Upgraded to utopic on 2014-07-31 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1351286/+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 1471123] Re: suddenly tabulator-key stops working normally

2016-10-21 Thread Aapo Rantalainen
After fresh install on Ubuntu 16.04 I found this will break tab key instantly:
xmodmap -e 'clear Mod4'


My goal was to remap Super_L to be additional Alt_L (and not affect tab key at 
all):

This works for me on Ubuntu 16.04 (with xfce):
xmodmap -e 'remove mod4 = Super_L'
xmodmap -e 'remove mod4 = Hyper_L'
xmodmap -e 'keycode 133 = Alt_L'
xmodmap -e 'add mod4 = Super_L Hyper_L'

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

Title:
  suddenly tabulator-key stops working normally

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.04
  xserver-xorg: 1:7.7+1ubuntu8.1

  I don't know how to trigger this bug, but I have seen it now more than
  ten times.

  "Suddenly" = I can't figure pattern how this triggers. Sometimes it
  happens when computer just idles

  'stops working normally' = tab-key alone doesn't do anything.

  --
  When tab-key is working normally, xev reports:

  KeyPress event, serial 37, synthetic NO, window 0x241,
  root 0x290, subw 0x0, time 2088488, (164,-6), root:(1515,797),
  state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
  XLookupString gives 1 bytes: (09) " "
  XmbLookupString gives 1 bytes: (09) " "
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x241,
  root 0x290, subw 0x0, time 2088509, (164,-6), root:(1515,797),
  state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES,
  XLookupString gives 1 bytes: (09) " "
  XFilterEvent returns: False

  --
  When this bug triggers, xev reports (when tab-key pressed and released):

  FocusOut event, serial 37, synthetic NO, window 0x561,
  mode NotifyGrab, detail NotifyAncestor

  FocusIn event, serial 37, synthetic NO, window 0x561,
  mode NotifyUngrab, detail NotifyAncestor

  KeymapNotify event, serial 37, synthetic NO, window 0x0,
  keys: 4294967184 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
     0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

  --
  When this bug triggers, xev reports (when holding CTRL and tab-key pressed 
and released):

  KeyPress event, serial 37, synthetic NO, window 0x561,
  root 0x290, subw 0x0, time 261350060, (172,-19), root:(1523,784),
  state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyPress event, serial 37, synthetic NO, window 0x561,
  root 0x290, subw 0x0, time 261350228, (172,-19), root:(1523,784),
  state 0x4, keycode 23 (keysym 0xff09, Tab), same_screen YES,
  XLookupString gives 1 bytes: (09) " "
  XmbLookupString gives 1 bytes: (09) " "
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x561,
  root 0x290, subw 0x0, time 261350276, (172,-19), root:(1523,784),
  state 0x4, keycode 23 (keysym 0xff09, Tab), same_screen YES,
  XLookupString gives 1 bytes: (09) " "
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x561,
  root 0x290, subw 0x0, time 261350572, (172,-19), root:(1523,784),
  state 0x4, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
  ---
  And behaviour is like xev reports: tab pressed alone doesn't do anything, but 
with any modifier it works as expected:
  alt+tab = change window
  shift+tab = previous element (e.g. fields in browser)
  ctrl+tab = change tab (e.g. in firefox)

  -
  I have ~/.Xmodmap and it contains line:
  keycode 23 = Tab ISO_Left_Tab Tab ISO_Left_Tab Tab ISO_Left_Tab

  Running xmodmap ~/.Xmodmap will not fix.

  ---
  Attaching new usb-keyboard doesn't help.
  ---
  Reboot helps.
  Restarting xorg helps.
  ---
  Changing to virtual terminal -> tab is working. But after returning to xorg, 
tab is still broken.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-15 (740 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags: trusty third-party-packages
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-05-13 (561 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1471123/+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 1617468] Re: Package contains files in /usr/@DATADIRNAME@/locale

2016-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-system-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Package contains files in /usr/@DATADIRNAME@/locale

Status in gnome-system-tools package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Version: 3.0.0-4ubuntu3

  The package gnome-system-tools contains files in
  /usr/@DATADIRNAME@/locale which is probably wrong. It is the only
  package that has files there. Looks like a variable name from a
  template engine.

  marc@ellen:~$ dpkg -S /usr/@DATADIRNAME@/
  gnome-system-tools: /usr/@DATADIRNAME@

  marc@ellen:~$ dpkg -L gnome-system-tools | fgrep -e DATA
  /usr/@DATADIRNAME@
  /usr/@DATADIRNAME@/locale
  /usr/@DATADIRNAME@/locale/af
  /usr/@DATADIRNAME@/locale/af/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/af/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/am
  /usr/@DATADIRNAME@/locale/am/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/am/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/ar
  /usr/@DATADIRNAME@/locale/ar/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/ar/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/as
  /usr/@DATADIRNAME@/locale/as/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/as/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/ast
  /usr/@DATADIRNAME@/locale/ast/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/ast/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/az
  /usr/@DATADIRNAME@/locale/az/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/az/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/be
  /usr/@DATADIRNAME@/locale/be/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/be/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/be@latin
  /usr/@DATADIRNAME@/locale/be@latin/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/be@latin/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/bg
  /usr/@DATADIRNAME@/locale/bg/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/bg/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/bn
  /usr/@DATADIRNAME@/locale/bn/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/bn/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/bn_IN
  /usr/@DATADIRNAME@/locale/bn_IN/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/bn_IN/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/br
  /usr/@DATADIRNAME@/locale/br/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/br/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/ca
  /usr/@DATADIRNAME@/locale/ca/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/ca/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/ca@valencia
  /usr/@DATADIRNAME@/locale/ca@valencia/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/ca@valencia/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/cs
  /usr/@DATADIRNAME@/locale/cs/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/cs/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/cy
  /usr/@DATADIRNAME@/locale/cy/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/cy/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/da
  /usr/@DATADIRNAME@/locale/da/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/da/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/de
  /usr/@DATADIRNAME@/locale/de/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/de/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/dz
  /usr/@DATADIRNAME@/locale/dz/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/dz/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/el
  /usr/@DATADIRNAME@/locale/el/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/el/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/en@shaw
  /usr/@DATADIRNAME@/locale/en@shaw/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/en@shaw/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/en_CA
  /usr/@DATADIRNAME@/locale/en_CA/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/en_CA/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/en_GB
  /usr/@DATADIRNAME@/locale/en_GB/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/en_GB/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/eo
  /usr/@DATADIRNAME@/locale/eo/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/eo/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/es
  /usr/@DATADIRNAME@/locale/es/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/es/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/et
  /usr/@DATADIRNAME@/locale/et/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/et/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/eu
  /usr/@DATADIRNAME@/locale/eu/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/eu/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/fa
  /usr/@DATADIRNAME@/locale/fa/LC_MESSAGES
  /usr/@DATADIRNAME@/locale/fa/LC_MESSAGES/gnome-system-tools.mo
  /usr/@DATADIRNAME@/locale/fi
  

[Desktop-packages] [Bug 1635376] Re: double-clicking on an executable created with gcc6 opens an error message

2016-10-21 Thread Hadrien
@Khurshid Alam:
 - a.out has execution permission
 - the expected result is: no error message (I updated the bug description)

Obviously the a.out does nothing. I gave the most minimal way to
reproduce the problem. I could put an example of a program that opens a
window I you think it would make the bug easier to understand.

I have several projects I built recently since I installed Ubuntu 16.10
and they all gave me executables I cannot launch from Nautilus. There is
no problem when I launch them from a terminal.

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

Title:
  double-clicking on an executable created with gcc6 opens an error
  message

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 x64 with Nautilus 3.20.3

  * Open a terminal
  * Install gcc: sudo apt install build-essential
  * Build an executable: printf "int main() { return 1; }" | gcc -x c -
  * Open a Nautilus window on the current directory: nautilus .
  * Double-click on the generated executable: a.out

  Expected result: Nautilus starts the executable. No error is displayed.
  Actual result: Nautilus displays an error message:

     Could not display "a.out".
     There is no application installed for shared library files.
     Do you want to search for an application to open this file?

  Also, all executable files compiled with gcc6 have a generic icon
  instead of the purple lozenge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635376/+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 1635378] Re: Clicking a bookmark located on another partition gives an error message

2016-10-21 Thread Hadrien
** Attachment added: "Error message (in french)"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635378/+attachment/4765041/+files/nautilus-partition-bookmark.png

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

Title:
  Clicking a bookmark located on another partition gives an error
  message

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 x64 with Nautilus 3.20.3

  * Have a secondary disk on my computer formated as ntfs.
  * Have a bookmark in Nautilus to one of the directory of that secondary disk.
  * Click on the bookmark

  Expected result: Nautilus opens the directory the bookmark points to
  Actual result: Nautilus gives me an error message

  It worked fine on Ubuntu 16.04. Now I have to go to the "other
  locations" view, click on the disk icon, and then click on my
  bookmark.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635378/+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 1635376] Re: double-clicking on an executable created with gcc6 opens an error message

2016-10-21 Thread Hadrien
** Description changed:

  Ubuntu 16.10 x64 with Nautilus 3.20.3
  
  * Open a terminal
  * Install gcc: sudo apt install build-essential
  * Build an executable: printf "int main() { return 1; }" | gcc -x c -
  * Open a Nautilus window on the current directory: nautilus .
  * Double-click on the generated executable: a.out
  
- Expected result: Nautilus starts the executable
+ Expected result: Nautilus starts the executable. No error is displayed.
  Actual result: Nautilus displays an error message:
  
     Could not display "a.out".
     There is no application installed for shared library files.
     Do you want to search for an application to open this file?

** Description changed:

  Ubuntu 16.10 x64 with Nautilus 3.20.3
  
  * Open a terminal
  * Install gcc: sudo apt install build-essential
  * Build an executable: printf "int main() { return 1; }" | gcc -x c -
  * Open a Nautilus window on the current directory: nautilus .
  * Double-click on the generated executable: a.out
  
  Expected result: Nautilus starts the executable. No error is displayed.
  Actual result: Nautilus displays an error message:
  
     Could not display "a.out".
     There is no application installed for shared library files.
     Do you want to search for an application to open this file?
+ 
+ Also, all executable files compiled with gcc6 have a generic icon
+ instead of the purple lozenge.

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

Title:
  double-clicking on an executable created with gcc6 opens an error
  message

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 x64 with Nautilus 3.20.3

  * Open a terminal
  * Install gcc: sudo apt install build-essential
  * Build an executable: printf "int main() { return 1; }" | gcc -x c -
  * Open a Nautilus window on the current directory: nautilus .
  * Double-click on the generated executable: a.out

  Expected result: Nautilus starts the executable. No error is displayed.
  Actual result: Nautilus displays an error message:

     Could not display "a.out".
     There is no application installed for shared library files.
     Do you want to search for an application to open this file?

  Also, all executable files compiled with gcc6 have a generic icon
  instead of the purple lozenge.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635376/+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 1635375] Re: First letter doubled in Facebook posts.

2016-10-21 Thread Callista Graves
Thank you!

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

Title:
  First letter doubled in Facebook posts.

Status in elementary OS:
  New
Status in epiphany-browser package in Ubuntu:
  Confirmed

Bug description:
  I am running elementary OS Loki right now, and have been struggling
  with justifying using the Epiphany browser as my default, but with
  this bug it is simply impossible.

  When on Facebook, and typing the first word in a post, or in a
  sentence, the letter is always doubled, when using the shift key.

  It is nearly impossible to find any information on the internet about
  this, and while I would prefer to run Epiphany as default browser,
  this is a deal breaker for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1635375/+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 1635691] Re: Hardware backlight / brightness keys cause erratic, stuttered and seeming race-condition on DELL Inspiron 14-3452 (3000 series) laptop

2016-10-21 Thread Chris Rainey
*** TEMPORARY WORK-AROUND ***

Disable usd-backlight-helper via:

$ sudo chmod -x /usr/lib/unity-settings-daemon/usd-backlight-helper

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

Title:
  Hardware backlight / brightness keys cause erratic, stuttered and
  seeming race-condition on DELL Inspiron 14-3452 (3000 series) laptop

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

Bug description:
  Symptoms appeared after clean-installing Ubuntu 16.10. Worked
  perfectly using 15.10 & 16.04.

  
  DELL Inspiron 14-3452 (3000 series) laptop

  Latest BIOS ver:  4.0.11

  
  Upon pressing either the XF86monBrightnessUp or XF86monBrightnessDown keys in 
a Unity-7 session, the OSD appears, sometimes delayed, and begins to lower or 
raise the backlight level, repeatedly, to the maximum or minimum level. The 
system comes under load and is less responsive to any input or attempts to 
cancel / counteract the action.

  Manual adjustments via the echoing of numbers-in-range to the
  /sys/class/backlight/intel_backlight/brightness work normally and as
  expected.

  Possible relation or hang-on to bug:
  https://bugs.launchpad.net/ubuntu/+source/unity-settings-
  daemon/+bug/1626651

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity-settings-daemon 15.04.1+16.10.20161003-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 21 12:52:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-20 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  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/1635691/+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 1635691] [NEW] Hardware backlight / brightness keys cause erratic, stuttered and seeming race-condition on DELL Inspiron 14-3452 (3000 series) laptop

2016-10-21 Thread Chris Rainey
Public bug reported:

Symptoms appeared after clean-installing Ubuntu 16.10. Worked perfectly
using 15.10 & 16.04.


DELL Inspiron 14-3452 (3000 series) laptop

Latest BIOS ver:  4.0.11


Upon pressing either the XF86monBrightnessUp or XF86monBrightnessDown keys in a 
Unity-7 session, the OSD appears, sometimes delayed, and begins to lower or 
raise the backlight level, repeatedly, to the maximum or minimum level. The 
system comes under load and is less responsive to any input or attempts to 
cancel / counteract the action.

Manual adjustments via the echoing of numbers-in-range to the
/sys/class/backlight/intel_backlight/brightness work normally and as
expected.

Possible relation or hang-on to bug:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-
daemon/+bug/1626651

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity-settings-daemon 15.04.1+16.10.20161003-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Oct 21 12:52:31 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-20 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
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 yakkety

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

Title:
  Hardware backlight / brightness keys cause erratic, stuttered and
  seeming race-condition on DELL Inspiron 14-3452 (3000 series) laptop

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

Bug description:
  Symptoms appeared after clean-installing Ubuntu 16.10. Worked
  perfectly using 15.10 & 16.04.

  
  DELL Inspiron 14-3452 (3000 series) laptop

  Latest BIOS ver:  4.0.11

  
  Upon pressing either the XF86monBrightnessUp or XF86monBrightnessDown keys in 
a Unity-7 session, the OSD appears, sometimes delayed, and begins to lower or 
raise the backlight level, repeatedly, to the maximum or minimum level. The 
system comes under load and is less responsive to any input or attempts to 
cancel / counteract the action.

  Manual adjustments via the echoing of numbers-in-range to the
  /sys/class/backlight/intel_backlight/brightness work normally and as
  expected.

  Possible relation or hang-on to bug:
  https://bugs.launchpad.net/ubuntu/+source/unity-settings-
  daemon/+bug/1626651

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity-settings-daemon 15.04.1+16.10.20161003-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 21 12:52:31 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-20 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  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/1635691/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

2016-10-21 Thread Jorge Niedbalski
** Changed in: libnl3 (Ubuntu Trusty)
   Status: New => In Progress

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

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  In Progress

Bug description:
  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  The library release is the 3.2.21-1 and the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

2016-10-21 Thread Matt Raines
I see this immediately after upgrading from 16.04 to 16.10. It's also
the case with the result area in gnome-calculator. A screenshot is
attached.

** Attachment added: "Screenshot from 2016-10-21 18-55-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1620806/+attachment/4764943/+files/Screenshot%20from%202016-10-21%2018-55-22.png

** Information type changed from Public to Public Security

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

Status in gedit package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  In a freshly booted and fully updated Ubuntu 16.10 the edit window of
  gedit is transparent using the *Classic* colour scheme. Other colour
  schemes seem to work as intended.

  The text of loaded files shows against the desktop wallpaper but when
  no files are loaded gedit displays its edit window or pane as it
  should do.

  To clarify this bug is only apparent when a file is loaded.

  I don't know when this started as I don't normally used gedit to edit
  files. I haven't found any other application affected by this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.20.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 21:01:35 2016
  InstallationDate: Installed on 2016-03-11 (179 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+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 1635689] [NEW] Firefox slow, crashing, behaving worst!

2016-10-21 Thread Soumitra Roy
Public bug reported:

Firefox bcum slower than ever!!!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 49.0+build4-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
Uname: Linux 4.4.0-43-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  soumitra   2459 F pulseaudio
BuildID: 20160920074044
Channel: Unavailable
CurrentDesktop: Unity
Date: Fri Oct 21 23:26:25 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-10-17 (4 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.43.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
 192.168.43.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.43.26  
metric 600
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=49.0/20160920074044 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.15
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EG50_HC_HR
dmi.board.vendor: Gateway
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.15
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.15:bd03/11/2013:svnGateway:pnNE56R:pvrV2.15:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.15:
dmi.product.name: NE56R
dmi.product.version: V2.15
dmi.sys.vendor: Gateway

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

Title:
  Firefox slow,crashing,behaving worst!

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox bcum slower than ever!!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 49.0+build4-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  soumitra   2459 F pulseaudio
  BuildID: 20160920074044
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Fri Oct 21 23:26:25 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-10-17 (4 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.43.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.43.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.43.26  
metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=49.0/20160920074044 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Gateway
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.15:bd03/11/2013:svnGateway:pnNE56R:pvrV2.15:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.15:
  dmi.product.name: NE56R
  dmi.product.version: V2.15
  dmi.sys.vendor: Gateway

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1379678] Re: [needs-packaging] Package or include pycamberra.py script by default in app

2016-10-21 Thread Angel Guzman Maeso
Any update with this? It would be nice have this in the next release of
Ubuntu, since it still not present in Ubuntu 16.10

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

Title:
  [needs-packaging] Package or include pycamberra.py script by default
  in app

Status in pitivi package in Ubuntu:
  Confirmed

Bug description:
  As you warning starting Pitivi:

  pycanberra not found on the system

  This is considered a "soft dependency". But the users are consufed,
  because there are not a package in Ubuntu, Linux Mint or other distro
  with this name or similar, because it is a simple script as wrapper of
  libcamberra:

  https://github.com/psykoyiko/pycanberra/blob/master/pycanberra.py

  So please, explain where this file should be installed, or provide a
  package or include this file in the source code

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pitivi 0.93-4ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 10 09:34:16 2014
  InstallationDate: Installed on 2014-05-08 (154 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: pitivi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1379678/+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 1635681] [NEW] font related bug

2016-10-21 Thread imran
Public bug reported:

i upgrade 16.04 to 16.10 after upgrading it occurs fonts related
bugs.please fix it.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
BootLog:
 [  OK  ] Started LSB: Speech Dispatcher.
 [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
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: Fri Oct 21 22:54:23 2016
DistUpgraded: 2016-10-21 19:00:00,788 DEBUG running apport_crash()
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
InstallationDate: Installed on 2016-10-16 (5 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 003: ID 17ef:4810 Lenovo Integrated Webcam [R5U877]
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 0585DG2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=16572a56-8faa-4a65-ab95-b5efced0cc37 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago)
dmi.bios.date: 01/11/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 81ET49WW (1.25 )
dmi.board.name: 0585DG2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr81ET49WW(1.25):bd01/11/2011:svnLENOVO:pn0585DG2:pvrThinkPadL412:rvnLENOVO:rn0585DG2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 0585DG2
dmi.product.version: ThinkPad L412
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Fri Oct 21 22:17:26 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 fonts ubuntu yakkety

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

Title:
  font related bug

Status in xorg package in Ubuntu:
  New

Bug description:
  i upgrade 16.04 to 16.10 after upgrading it occurs fonts related
  bugs.please fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  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: Fri Oct 21 22:54:23 2016
  DistUpgraded: 2016-10-21 19:00:00,788 DEBUG running apport_crash()
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-10-16 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 003: ID 17ef:4810 

[Desktop-packages] [Bug 1635677] [NEW] Right click rename: auto emptying file name is counter-productive.

2016-10-21 Thread Jiawen Chen
Public bug reported:

When I rename in nautilus, the file name (not including extension name)
will be cleared automatically. It is counter-productive when I want do
make minor change to the file name, for example pluralizing.
Unfortunately this case is one big use case.

Auto clearing the filename do not help users much. If I want to clear
the file name I just do it with one keystroke.

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

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

Title:
  Right click rename: auto emptying file name is counter-productive.

Status in nautilus package in Ubuntu:
  New

Bug description:
  When I rename in nautilus, the file name (not including extension
  name) will be cleared automatically. It is counter-productive when I
  want do make minor change to the file name, for example pluralizing.
  Unfortunately this case is one big use case.

  Auto clearing the filename do not help users much. If I want to clear
  the file name I just do it with one keystroke.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635677/+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 1635668] [NEW] [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted

2016-10-21 Thread Jim Tarvid
Public bug reported:

This defect is not apparent on two other Ubuntu 16.04 machines. The
upgrade to 16.10 did not change the symptoms.

lsb_release -rd
Description:Ubuntu 16.10
Release:16.10

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 21 11:53:54 2016
InstallationDate: Installed on 2016-09-22 (29 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - HDA 
ATI HDMI
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Digital clip or distortion, or "overdriven" sound
Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0773VG
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 7010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This defect is not apparent on two other Ubuntu 16.04 machines. The
  upgrade to 16.10 did not change the symptoms.

  lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 21 11:53:54 2016
  InstallationDate: Installed on 2016-09-22 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] - 
HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [OptiPlex 7010, ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (0 days ago)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0773VG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex7010:pvr01:rvnDellInc.:rn0773VG:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635668/+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 1630453] Re: [Yakkety +1] Sync lirc 0.9.4b-0.1 (main) from Debian experimental (main)

2016-10-21 Thread LocutusOfBorg
I hope to fix the FTBFS soon, I already asked the maintainer

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

Title:
  [Yakkety +1] Sync lirc 0.9.4b-0.1 (main) from Debian experimental
  (main)

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  [Yakkety +1] Please sync lirc 0.9.4b-0.1 (main) from Debian
  experimental (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Multiarchify the library packages.
* Multiarchify the library packages.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix a bug that causes transmitter device/driver settings to always be
  cleared on config change.
* Adjust lircd handling for multiple devices so that events for all of
  them will appear on /dev/lircd as intended.  Thanks to Joel Ebel for
  the patch.  LP: #697999.
* Use /run/lirc, the canonical name for /var/run/lirc.  LP: #474701.
* Fix the init script to not report failures when stopping an
  already-stopped daemon.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix a bug that causes transmitter device/driver settings to always be
  cleared on config change.
* Adjust lircd handling for multiple devices so that events for all of
  them will appear on /dev/lircd as intended.  Thanks to Joel Ebel for
  the patch.  LP: #697999.
* Use /run/lirc, the canonical name for /var/run/lirc.  LP: #474701.
* Fix the init script to not report failures when stopping an
  already-stopped daemon.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix a bug that causes transmitter device/driver settings to always be
  cleared on config change.
* Adjust lircd handling for multiple devices so that events for all of
  them will appear on /dev/lircd as intended.  Thanks to Joel Ebel for
  the patch.  LP: #697999.
* Use /run/lirc, the canonical name for /var/run/lirc.  LP: #474701.
* Fix the init script to not report failures when stopping an
  already-stopped daemon.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix a bug that causes transmitter device/driver settings to always be
  cleared on config change.
* Adjust lircd handling for multiple devices so that events for all of
  them will appear on /dev/lircd 

[Desktop-packages] [Bug 1630453] Re: [Yakkety +1] Sync lirc 0.9.4b-0.1 (main) from Debian experimental (main)

2016-10-21 Thread Jeremy Bicha
This bug was fixed in the package lirc - 0.9.4b-0.3
Sponsored for LocutusOfBorg (costamagnagianfranco)

---
lirc (0.9.4b-0.3) experimental; urgency=medium

  * Non-maintainer upload.

  [ Gianfranco Costamagna ]
  * fix arch:all build.

  [ Alec Leamas ]
  * Fix build errors on non-linux kernels.
(conditionalize udev dependency)

 -- Gianfranco Costamagna   Wed, 05 Oct 2016
19:30:47 +0200

lirc (0.9.4b-0.2) experimental; urgency=medium

  * Non-maintainer upload.
  * Fix build errors on non-linux kernels.
  * Declare liblirc0 as multi-arch; Closes: #812947.

 -- Alec Leamas   Wed, 05 Oct 2016 06:07:40 +0200

lirc (0.9.4b-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * First shot on major upstream updates.
- Re-packaged from scratch based on new dh primitives.
- Thanks for help on debian-mentors!
  * New upstream release 0.9.4
- Release 0.9.1 .. 0.9.3 was never packaged.
- Old 'lirc' service split into separate systemd services:
  lircd.service, lircmd.service and irexec.service.
- Remote definitions moved out of lirc to new project
  lirc-remotes; affects large number of LP issues.
- Builds also on FreeBSD 10.3.
- Fixes "Not updated to last version" (Closes: #777199),
  LP: #1443590.
- Fixes "Default device for mode2 is /dev/lirc" (Closes: #702140).
- Fixes "/var/run/lirc contents disappear..." (Closes: #676343).
- Fixes "lircrcd segfaults" (Closes: #780062).
- Fixes "'/etc/init.d/lirc restart' is broken" (Closes: #782091).
- Fixes "Prompting due to modified conffiles..." (Closes: #655969).
- Fixes "LIRC installs bad udev rule" (Closes: #804397),
  users depending on this rule will need to explicitly start lircd.
- Fixes "lirc init script can create circular symlinks", LP: #698007.
- Fixes "Update Uploaders List (Closes: #762554).
- Fixes "Please switch to libftdi1" (Closes:  #810370).
- Fixes LP: #153457 "iguanaIR support not functional".
- Fixes LP: #460027 "using lirc init script restart function fails
  sometimes".
- Fixes LP: #499588 "lirc udev rule causes unreliable startup".
- Fixes LP: #567519 "lircd(8) mentions non-existent
  /dev/input/uinput".
- Fixes LP: #1029604 "mce remote doesn't work due to out of date
  lircd.conf.devinput".
- Fixes LP: #1312287 "lircd start problem".
  * The built-in irman support is moved to the lirc-drv-irman package.
  * Revised package structure: keep old liblircclient0 (renamed to
liblirc-client0). Adding new packages liblirc0, liblirc-dev and
lirc-doc. Former liblircclient-dev merged into new liblirc-dev.
  * Don't overwrite existing lircd.conf file.
  * Ship sysV scripts from the svn tree [Stefan Lippers-Hollmann]
  * Add handling of obsolete 0.9.0 udev rule restarting lircd
  * Old lircd output socket link /dev/lirc dropped. Use
/var/run/lirc/lircd.
  * Updated copyright
  * Update compiler flags: -Wl,as-needed + hardening
[Stefan Lippers-Hollmann]
  * Avoid negative architecture deps like [!hurd] (Closes: #634807)
[Stefan Lippers-Hollmann]
  * Add patch 0007-tools-remove-configs-symlink.patch + explicit link
to walk around #801719 (dh_python3 shortcomings).
  * Last parts of libirman dependencies removed.
  * Changing Vcs-* headers to point to upstream packaging branch.
  * Fixes existing large number of upgrade bugs.
  * Enhance hardening flags.
  * Add a lintian pbuilder test, this requires --hookdir and B92-test-pkg
therein.
  * Tested (build-wise) on stretch and sid.

 -- Alec Leamas    Thu, 26 May 2016 11:14:25
+0100

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

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

Title:
  [Yakkety +1] Sync lirc 0.9.4b-0.1 (main) from Debian experimental
  (main)

Status in lirc package in Ubuntu:
  Fix Released

Bug description:
  [Yakkety +1] Please sync lirc 0.9.4b-0.1 (main) from Debian
  experimental (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Multiarchify the library packages.
* Multiarchify the library packages.
* debian/lirc.postinst, debian/lirc.templates, debian/po: drop a number of
  debconf templates that are no longer being prompted for at all due to
  the dropping of the lirc-modules-source package and the lirc.config some
  time ago.
* debian/lirc.postinst: clean up the remaining debconf handling to not
  override settings in /etc/lirc/hardware.conf.
* debian/lirc.postinst: drop code for removing /var/log/lircd, which has
  been gone for more than a decade.
* fix blacklist handling, which creates files not used by modprobe, and
  doesn't put all the contents in a single file.
* drop obsolete Ubuntu migration code that dates from jaunty and lucid.
* fix 

[Desktop-packages] [Bug 1347305] Re: Address fields are grey when composing messages

2016-10-21 Thread Andrej
Actually, problem has diminished:
- Active fields can be found by hovering the mouse.
- When creating new message, first "To:" field is selected by default.
- If you forget to add "Subject:" line, you are reminded.

Personally i got used to new interface and always remember to change 
To:, Subject: etc. when i reply or forward message.
So, this bug no longer affects me.

Also, didn't heard any complains from new users.

May-be this bug should be closed?

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

Title:
  Address fields are grey when composing messages

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When composing a message, any address field that does not have the
  cursor is shown as grey. While this is at first only a cosmetic
  glitch, it is also serious usability issue: Usually any field that can
  be edited is white and text that can't be edited is simply drawn grey.
  Now it looks like Thunderbird does not allow editing of the recipient
  addresses. Only when you try it regardless you discover that it is
  still editible.

  I attached a screenshot showing a stuffed up composer window.

  This bug appeared with the latest update of Thunderbird that was
  installed today.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:31.0+build1-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kaymes 2516 F pulseaudio
  BuildID: 20140721092545
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Wed Jul 23 10:37:17 2014
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-07-02 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 10.33.0.1 dev eth0  proto static 
   10.33.0.0/22 dev eth0  proto kernel  scope link  src 10.33.1.197  metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  LocalLibraries: 
/home/kaymes/.thunderbird/dymzcbig.default/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/components/Linux_x86_64-gcc3/libcalbasecomps.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=31.0/20140721092545 (In use)
  RelatedPackageVersions:
   rhythmbox-mozilla 3.0.2-0ubuntu2
   totem-mozilla 3.10.1-1ubuntu4
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   Jul 23 08:56:13 uqbox kernel: [427030.548782] [drm] Setting output timings 
on SDVOB failed
   Jul 23 09:37:38 uqbox kernel: [429515.541016] [drm] Setting output timings 
on SDVOB failed
   Jul 23 10:06:02 uqbox kernel: [431219.445267] [drm] Setting output timings 
on SDVOB failed
   Jul 23 10:07:12 uqbox kernel: [431289.957320] [drm] Setting output timings 
on SDVOB failed
   Jul 23 10:23:06 uqbox kernel: [432243.381132] MATLAB[25882]: segfault at 8 
ip 7f2f4507bcfe sp 7f2f06cc5320 error 4
  dmi.bios.date: 10/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 0J468K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd10/27/2011:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0J468K:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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


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

2016-10-21 Thread Alessio Tona
I applied both solution of #5 and #45. After running the python script
my headset started working correctly. I don't know if it is solution of
#45 or the combination of #5 and #45, but it works now. Thanks!

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial

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

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

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

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

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

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

  The bug is still present in 16.04 LTS.

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

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


[Desktop-packages] [Bug 1622880] Re: nautilus crashes on Ubuntu 16.10

2016-10-21 Thread alvaro.rogar
Same here: I solved the issue #4 described, by following instructions in #5.
Thanks to you all.

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

Title:
  nautilus crashes on Ubuntu 16.10

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  nautilus crashes on Ubuntu 16.10

  nautilus

  (nautilus:16009): Gtk-WARNING **: Theme parsing error: :1:0: 
Failed to import: The resource at '/org/gnome/libgd/tagged-entry/default.css' 
does not exist
  Nautilus-Share-Message: Called "net usershare info" but it failed: Failed to 
execute child process "net" (No such file or directory)
  **
  ERROR:nautilus-canvas-container.c:6021:finish_adding_new_icons: assertion 
failed: (!container->details->auto_layout)
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1622880/+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 1631188] Re: Regression - moving file/folder icon over another folder icon no longer opens folder

2016-10-21 Thread Rainer Rohde
Thanks for the info! I agree with adding this to the Nautilus behavior
settings; such option is to useful to fall by the wayside; I use it all
the time!

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

Title:
  Regression - moving file/folder icon over another folder icon no
  longer opens folder

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04< I was able to grab any file or folder icon, and then
  drag it onto another folder icon (without letting go the mouse
  button), and that folder would open up. I could repeat this until the
  desired location has opened, and then let go of the mouse button and
  drop the file there.

  Now, with 16.10 (beta), this behavior is currently not available,
  which is a huge inconvenience considering how awesome the default
  behavior in 16.04 was.

  Hope this will get fixed asap. :)

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct  6 17:20:02 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'867x440+339+80'"
  InstallationDate: Installed on 2016-10-06 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161006)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   dropbox2015.10.28
   gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1631188/+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 1635637] Re: nautilus crashed with SIGSEGV in g_main_context_dispatch()

2016-10-21 Thread Apport retracing service
*** This bug is a duplicate of bug 1546141 ***
https://bugs.launchpad.net/bugs/1546141

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1635637/+attachment/4764857/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1635637/+attachment/4764859/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1635637/+attachment/4764863/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1635637/+attachment/4764864/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1635637/+attachment/4764865/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1635637/+attachment/4764866/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1635637/+attachment/4764867/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1546141

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in g_main_context_dispatch()

Status in nautilus package in Ubuntu:
  New

Bug description:
  I renamed a file from search

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  Uname: Linux 4.7.0-040700-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 21 19:40:35 2016
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2015-12-02 (323 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151027)
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x4bcbd2:  mov0x88(%rdx),%edx
   PC (0x004bcbd2) ok
   source "0x88(%rdx)" (0x0088) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635637/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

2016-10-21 Thread Jorge Niedbalski
** Changed in: libnl3 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: libnl3 (Ubuntu)
 Assignee: Jorge Niedbalski (niedbalski) => (unassigned)

** Changed in: libnl3 (Ubuntu Trusty)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

** Changed in: libnl3 (Ubuntu Precise)
 Assignee: (unassigned) => Jorge Niedbalski (niedbalski)

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  New

Bug description:
  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  The library release is the 3.2.21-1 and the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1635638] [NEW] nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build

2016-10-21 Thread Tony C.
Public bug reported:

Doing a straight upgrade ..

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: nvidia-367 367.57-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-lowlatency 4.8.0
Uname: Linux 4.8.0-22-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 4.8.0-26-lowlatency
Date: Fri Oct 21 07:33:44 2016
InstallationDate: Installed on 2016-10-18 (2 days ago)
InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
PackageVersion: 367.57-0ubuntu3
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: nvidia-graphics-drivers-367
Title: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-367 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package yakkety

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

Title:
  nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  New

Bug description:
  Doing a straight upgrade ..

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: nvidia-367 367.57-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-lowlatency 4.8.0
  Uname: Linux 4.8.0-22-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 4.8.0-26-lowlatency
  Date: Fri Oct 21 07:33:44 2016
  InstallationDate: Installed on 2016-10-18 (2 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  PackageVersion: 367.57-0ubuntu3
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu3: nvidia-367 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1635638/+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 1567578] Re: libnl should be updated to support up to 63 VFs per single PF

2016-10-21 Thread Louis Bouchard
** Also affects: libnl3 (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: libnl3 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
   libnl should be updated to support up to 63 VFs per single PF

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Precise:
  New
Status in libnl3 source package in Trusty:
  New

Bug description:
  Ubuntu 14.04.4 and SRIOV settings.

  As already documented in https://bugs.launchpad.net/mos/+bug/1501738
  there is a bug in the default libnl library release installed on
  Ubuntu 14.04.4

  The library release is the 3.2.21-1 and the bug is impacting on the
  maximum VFs number that can be enabled (up to 30) even if the PF
  supports up to 63 VFs in an Openstack SRIOV configuration

  The workaround is to install a newer library release, the 3.2.24-2:

  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-genl-3-200_3.2.24-2_amd64.deb
  wget 
https://launchpad.net/ubuntu/+archive/primary/+files/libnl-route-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-genl-3-200_3.2.24-2_amd64.deb
  dpkg -i libnl-route-3-200_3.2.24-2_amd64.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1567578/+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 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume

2016-10-21 Thread Ugnius
Also having the issue on a fresh 16.04.1. init-headphone 0.11 gets EBUSY
on the first write to SMBus (modified to print out errno, diff below).
Used to work on 15.04-15.10 on the same laptop.


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial


$ sudo init-headphone-errno
INFO:root:Version: 0.11
INFO:root:Trying to add module to the kernel: i2c_dev
INFO:root:Trying to add module to the kernel: i2c_i801
DEBUG:root:Available i2c busses: ['i915 gmbus ssc', 'i915 gmbus vga', 'i915 
gmbus panel', 'i915 gmbus dpc', 'i915 gmbus dpb', 'i915 gmbus dpd', 'DPDDC-A', 
'SMBus I801 adapter at f040']
DEBUG:root:Supported i2c bus names: ['SMBus I801 adapter']
DEBUG:root:Selected i2c bus: SMBus I801 adapter at f040
INFO:SMBus:Opening I2C bus: /dev/i2c-7
INFO:SMBus:Setting I2C slave address: 115
INFO:SMBus:Writing byte data on I2C bus: (device_cmd: 0xa, value: 0x41)
ERROR:SMBus:Can't transfer data on I2C bus [EBUSY]
INFO:SMBus:Closing I2C bus
ERROR:root:Operation failed
DEBUG:root:Exception occurred:
Traceback (most recent call last):
  File "/usr/sbin/init-headphone-errno", line 329, in 
main()
  File "/usr/sbin/init-headphone-errno", line 315, in main
init()
  File "/usr/sbin/init-headphone-errno", line 247, in init
set_effect(DEFAULT_EFFECT)
  File "/usr/sbin/init-headphone-errno", line 263, in set_effect
DATA_ENABLE_OUTPUT)
  File "/usr/sbin/init-headphone-errno", line 241, in write_data_to_device
write_prolog(i2c_bus)
  File "/usr/sbin/init-headphone-errno", line 232, in write_prolog
i2c_bus.write_byte_data(0x0a, 0x41)
  File "/usr/sbin/init-headphone-errno", line 149, in write_byte_data
self.__access(I2C_SMBUS_WRITE, device_cmd, I2C_SMBUS_BYTE_DATA, data)
  File "/usr/sbin/init-headphone-errno", line 141, in __access
raise RuntimeError("Can't transfer data on I2C bus [{}]".format(e))
RuntimeError: Can't transfer data on I2C bus [EBUSY]


$ sudo i2cdetect 7
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-7.
I will probe address range 0x03-0x77.
Continue? [Y/n] 
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --


$ diff -u /usr/sbin/init-headphone /usr/sbin/init-headphone-errno 
--- /usr/sbin/init-headphone2016-05-08 10:27:04.0 +0300
+++ /usr/sbin/init-headphone-errno  2016-10-21 16:58:45.292881695 +0300
@@ -82,6 +82,12 @@
 ("size", ctypes.c_uint),
 ("data", ctypes.POINTER(i2c_smbus_data))]
 
+_errno = ctypes.cdll.LoadLibrary("libc.so.6").__errno_location
+_errno.restype = ctypes.POINTER(ctypes.c_int)
+
+def get_errno():
+import errno
+return errno.errorcode[_errno()[0]]
 
 class SMBus(object):
 def __init__(self, path):
@@ -129,9 +135,10 @@
 args.size = size
 args.data = ctypes.pointer(data)
 err = self.__libc.ioctl(self.__fd, I2C_SMBUS, ctypes.byref(args))
+e = get_errno()
 if err != 0:
-self.__logger.error("Can't transfer data on I2C bus")
-raise RuntimeError("Can't transfer data on I2C bus")
+self.__logger.error("Can't transfer data on I2C bus 
[{}]".format(e))
+raise RuntimeError("Can't transfer data on I2C bus [{}]".format(e))
 
 def write_byte_data(self, device_cmd, value):
 self.__logger.info("Writing byte data on I2C bus: "

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

Title:
  [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after
  suspend/resume

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

Bug description:
  No sound in headphones jack after suspend/resume.
  But sound in headphones jack is OK after cold boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.15.0-031500rc2-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mik2139 F pulseaudio
   /dev/snd/controlC1:  mik2139 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 23:20:59 2014
  InstallationDate: Installed on 2014-04-26 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed

[Desktop-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor

2016-10-21 Thread Treviño
I've the impression this is due to nautilus not being properly resized
when display size changes (in a VM) or a new one is added...

nautilus -q

and starting the filemanager again should fix this.

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

Title:
  [yakkety] desktop is black and/or flickering after plugging in a
  second monitor

Status in compiz package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Using 16.04 daily image: 20160919(downloading date)
  With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable
  Graphic chips:
  00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06)
  01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] 
[10de:139b] (rev ff)

  Desktop wallpaper on extended display shows black background only, and
  the hdmi detection is very unstable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu7
  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: Fri Sep 23 05:30:30 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06e4]
  InstallationDate: Installed on 2016-09-20 (3 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed 
root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+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 1634263] Re: Touchpad movement doesn't work after suspend

2016-10-21 Thread svenmeier
After switching back into Gnome session touchpad movement works again.
Thus I suspect this to be a Gnome problem.

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

Title:
  Touchpad movement doesn't work after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Once or twice a week *after* resume from suspend I can no longer use
  the touchpad to movethe mouse pointer, mouse clicks are registered
  though.

  Reloading module psmouse works as a workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct 17 22:52:05 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-19-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  MachineType: LENOVO 20344
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=e61df794-2762-4b1b-bb74-3ad6415d4792 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN31WW(V1.17)
  dmi.board.asset.tag: 31900058Std
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: 31900058Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN31WW(V1.17):bd07/21/2015:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634263/+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 1634263] Re: Touchpad movement doesn't work after suspend

2016-10-21 Thread svenmeier
It seems all events are still correctly recognized by xorg.

** Summary changed:

- Touchpad movements doesn't work after suspend
+ Touchpad movement doesn't work after suspend

** Attachment added: "evtest output after touchpad went unresponsive"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634263/+attachment/4764856/+files/evtest.log

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

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

Title:
  Touchpad movement doesn't work after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Once or twice a week *after* resume from suspend I can no longer use
  the touchpad to movethe mouse pointer, mouse clicks are registered
  though.

  Reloading module psmouse works as a workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Oct 17 22:52:05 2016
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-19-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  MachineType: LENOVO 20344
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=e61df794-2762-4b1b-bb74-3ad6415d4792 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 96CN31WW(V1.17)
  dmi.board.asset.tag: 31900058Std
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058Std
  dmi.chassis.asset.tag: 31900058Std
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr96CN31WW(V1.17):bd07/21/2015:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoYoga213:
  dmi.product.name: 20344
  dmi.product.version: Lenovo Yoga 2 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634263/+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 850229] Re: Unread email count in thunderbird shown wrongly in messaging menu and launcher icon

2016-10-21 Thread Roelof Berkepeis
Bug still exists with Thunderbird v45.3.0 on 16.04 .. but recently i
discovered some solution : when clicking the envelop icon in the Ubuntu
notification bar (upper right, next to the clock) and then clicking the
inbox(es) in its menu, the little number at the Thunderbird launch icon
disappears ! So, i don't have to close and re-open Thunderbird anymore,
however, this is a workaround, not a real solution .. but maybe this
will lead to a real fix ..

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

Title:
  Unread email count in thunderbird shown wrongly in messaging menu and
  launcher icon

Status in Messaging Menu Thunderbird Extension:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Oneiric:
  Won't Fix

Bug description:
  The number of unread emails is shown incorrectly in the messaging menu
  and unity launcher icon of thunderbird though thunderbird application
  shows the correct count. See the attached screenshot for the
  illustration.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 7.0~b2+build2+nobinonly1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guruprasad   1650 F pulseaudio
  BuildID: 20110906005012
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf840 irq 47'
 Mixer name : 'Realtek ALC268'
 Components : 'HDA:10ec0268,103c30cc,0013 
HDA:10573055,10573055,00100700'
 Controls  : 21
 Simple ctrls  : 13
  Channel: default
  Date: Wed Sep 14 23:40:58 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.8
  Profiles: Profile0 (Default) - LastVersion=7.0/20110906005012 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.59
  dmi.board.name: 30CB
  dmi.board.vendor: Quanta
  dmi.board.version: 79.2E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv9700NotebookPC:pvrRev1:rvnQuanta:rn30CB:rvr79.2E:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv9700 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/messagingmenu-extension/+bug/850229/+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 1635624] [NEW] package account-plugin-owncloud (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui

2016-10-21 Thread p1pon
Public bug reported:

package account-plugin-owncloud (not installed) failed to
install/upgrade: tentative de remplacement de «
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi
au paquet owncloud-client:amd64 2.2.4-1.1

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: account-plugin-owncloud (not installed)
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 account-plugin-owncloud:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Oct 21 14:42:59 2016
ErrorMessage: tentative de remplacement de « 
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au 
paquet owncloud-client:amd64 2.2.4-1.1
InstallationDate: Installed on 2016-10-20 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: account-plugins
Title: package account-plugin-owncloud (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au 
paquet owncloud-client:amd64 2.2.4-1.1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package account-plugin-owncloud (not installed) failed to
  install/upgrade: tentative de remplacement de «
  /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient
  aussi au paquet owncloud-client:amd64 2.2.4-1.1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  package account-plugin-owncloud (not installed) failed to
  install/upgrade: tentative de remplacement de «
  /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient
  aussi au paquet owncloud-client:amd64 2.2.4-1.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: account-plugin-owncloud (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   account-plugin-owncloud:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Oct 21 14:42:59 2016
  ErrorMessage: tentative de remplacement de « 
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au 
paquet owncloud-client:amd64 2.2.4-1.1
  InstallationDate: Installed on 2016-10-20 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: account-plugins
  Title: package account-plugin-owncloud (not installed) failed to 
install/upgrade: tentative de remplacement de « 
/usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au 
paquet owncloud-client:amd64 2.2.4-1.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1635624/+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 1632027] Re: New Document feature missing from Nautilus 3.20+

2016-10-21 Thread Jeremy Bicha
Bronson, this bug is only about the "New Document" feature. I don't
think any of the other stuff you mentioned is directly related to this
issue. Please file a separate bug for each separate issue. That will
make it much easier to see the status of a specific issue.

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+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 1635375] Re: First letter doubled in Facebook posts.

2016-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: epiphany-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  First letter doubled in Facebook posts.

Status in elementary OS:
  New
Status in epiphany-browser package in Ubuntu:
  Confirmed

Bug description:
  I am running elementary OS Loki right now, and have been struggling
  with justifying using the Epiphany browser as my default, but with
  this bug it is simply impossible.

  When on Facebook, and typing the first word in a post, or in a
  sentence, the letter is always doubled, when using the shift key.

  It is nearly impossible to find any information on the internet about
  this, and while I would prefer to run Epiphany as default browser,
  this is a deal breaker for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1635375/+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 1062186] Re: 'Backup Failed' message when external backup drive first inserted

2016-10-21 Thread Robert Orzanna
*** This bug is a duplicate of bug 617012 ***
https://bugs.launchpad.net/bugs/617012

And in 16.04 as well.

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

Title:
  'Backup Failed' message when external backup drive first inserted

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed
Status in deja-dup package in Fedora:
  Unknown

Bug description:
  An error message entitled 'Backup Failed' with the text 'An operation
  is already pending' is displayed when I first plug in by external
  backup drive and Deja Dup attempts to perform a scheduled backup,
  although it succeeds on subsequent attempts (either scheduled or
  manual).

  The fstab entry for the drive is as follows:
  /dev/disk/by-uuid/1a1374a1-4bb9-4416-b21c-9350e57b70f1 
/media/thomas/Tom\040WD\040HD auto 
nosuid,nodev,nofail,noauto,compress=lzo,space_cache,uhelper=udisk 0 0

  I presume this is either due to both Gnome and Deja Dup attempting to
  mount the drive, or Deja Dup not waiting until the drive has been
  successfully mounted.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: deja-dup 24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Fri Oct  5 11:45:05 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120913)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1062186/+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 1634651] Re: Ubuntu software-center won't let login to ubuntu one account

2016-10-21 Thread Will Cooke
*** This bug is a duplicate of bug 1616943 ***
https://bugs.launchpad.net/bugs/1616943

** This bug has been marked a duplicate of bug 1616943
   Can't auth against U1 in g-s

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

Title:
  Ubuntu software-center won't let login to ubuntu one account

Status in gnome-software package in Ubuntu:
  New

Bug description:
  In order to install a proprietary snap package Software Center
  requires a Ubuntu One account in Ubuntu 16.10 however no matter how
  you enter your password and account's e-mail or choose "forgot
  password" option it won't let you log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-center (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 18 18:26:36 2016
  InstallationDate: Installed on 2016-10-18 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-center
  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/1634651/+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 1434986] Re: Not working network connection after boot

2016-10-21 Thread Ilya Bizyaev
Oh, sorry for a typo! That's Ubuntu 16.10!

** Tags added: yakkety

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

Title:
  Not working network connection after boot

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1434986] Re: Not working network connection after boot

2016-10-21 Thread Ilya Bizyaev
Seems to affect me on Ubuntu 16.04. Also I don't think that's a GNOME
problem as I use KDE.

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

Title:
  Not working network connection after boot

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1635598] [NEW] Paste into folder option missing on breadcrumb buttons

2016-10-21 Thread Silvio Bierman
Public bug reported:

Clicking the right mouse button on the breadcrumb-buttons that represent
the path to the current folder used to offer on option "Paste into
folder". This options is now gone.

This is extra annoying since the only alternative is right clicking an
EMPTY space in the window area itself. But in the list view mode if the
current folder content fills up the window there is no empty space
anywhere.

Luckily, CTRL+V still works so that is currently the only workaround.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Oct 21 12:44:29 2016
GsettingsChanges:
 
InstallationDate: Installed on 2016-10-13 (7 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Paste into folder option missing on breadcrumb buttons

Status in nautilus package in Ubuntu:
  New

Bug description:
  Clicking the right mouse button on the breadcrumb-buttons that
  represent the path to the current folder used to offer on option
  "Paste into folder". This options is now gone.

  This is extra annoying since the only alternative is right clicking an
  EMPTY space in the window area itself. But in the list view mode if
  the current folder content fills up the window there is no empty space
  anywhere.

  Luckily, CTRL+V still works so that is currently the only workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 21 12:44:29 2016
  GsettingsChanges:
   
  InstallationDate: Installed on 2016-10-13 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635598/+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 1634651] Re: Ubuntu software-center won't let login to ubuntu one account

2016-10-21 Thread Matthew Paul Thomas
That isn’t Ubuntu Software Center.

** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu)

** Changed in: gnome-software (Ubuntu)
   Status: Invalid => New

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

Title:
  Ubuntu software-center won't let login to ubuntu one account

Status in gnome-software package in Ubuntu:
  New

Bug description:
  In order to install a proprietary snap package Software Center
  requires a Ubuntu One account in Ubuntu 16.10 however no matter how
  you enter your password and account's e-mail or choose "forgot
  password" option it won't let you log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-center (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 18 18:26:36 2016
  InstallationDate: Installed on 2016-10-18 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-center
  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/1634651/+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 1635585] [NEW] Nautilus crashes after some time

2016-10-21 Thread Abhirav Kumar
Public bug reported:

I get this in my terminal. Normally when I start my system, nautilus
crashes after a few minutes. Ubuntu 16.04. System: Dell Inspiron 14 3000
Series

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:5481):gtk_icon_theme_lookup_by_gicon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gtk-WARNING **:
(/build/gtk+3.0-_oCaBb/gtk+3.0-3.20.6/./gtk/gtkicontheme.c:2226):gtk_icon_theme_choose_icon_for_scale:
runtime check failed: ((flags & GTK_ICON_LOOKUP_GENERIC_FALLBACK) == 0)

(nautilus:24185): Gdk-ERROR **: The program 'nautilus' received an X Window 
System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
  (Details: serial 37259 error_code 9 request_code 53 (core protocol) 
minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from 

[Desktop-packages] [Bug 1635579] [NEW] package udisks2 2.1.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-21 Thread Uellington Santos
Public bug reported:

Testing WSL on Windows 10 Insider Preview 14951

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
Uname: Linux 3.4.0+ x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
CustomUdevRuleFiles: 80-net-setup-link.rules
Date: Fri Oct 21 05:49:38 2016
Dmesg:
 
DuplicateSignature:
 package:udisks2:2.1.7-1ubuntu1
 Setting up udisks2 (2.1.7-1ubuntu1) ...
 udevadm trigger is not permitted while udev is unconfigured.
 dpkg: error processing package udisks2 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcInterrupts:
 
ProcKernelCmdLine: BOOT_IMAGE=/kernel ro
ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: 
sort: cannot read: /proc/modules: No such file or directory
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: udisks2
Title: package udisks2 2.1.7-1ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UDisksDump: Error: command ['udisksctl', 'dump'] failed with exit code 1: Error 
connecting to the udisks daemon: Could not connect: No such file or directory
UpgradeStatus: Upgraded to xenial on 2016-10-21 (0 days ago)

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


** Tags: amd64 apport-package need-duplicate-check uec-images xenial

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

Title:
  package udisks2 2.1.7-1ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in udisks2 package in Ubuntu:
  New

Bug description:
  Testing WSL on Windows 10 Insider Preview 14951

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  Uname: Linux 3.4.0+ x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Function not implemented
  CustomUdevRuleFiles: 80-net-setup-link.rules
  Date: Fri Oct 21 05:49:38 2016
  Dmesg:
   
  DuplicateSignature:
   package:udisks2:2.1.7-1ubuntu1
   Setting up udisks2 (2.1.7-1ubuntu1) ...
   udevadm trigger is not permitted while udev is unconfigured.
   dpkg: error processing package udisks2 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  ProcInterrupts:
   
  ProcKernelCmdLine: BOOT_IMAGE=/kernel ro
  ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 
2: sort: cannot read: /proc/modules: No such file or directory
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: udisks2
  Title: package udisks2 2.1.7-1ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UDisksDump: Error: command ['udisksctl', 'dump'] failed with exit code 1: 
Error connecting to the udisks daemon: Could not connect: No such file or 
directory
  UpgradeStatus: Upgraded to xenial on 2016-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1635579/+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 1589005] Re: After update DNS work unstable

2016-10-21 Thread Tamas Papp
I still have this problem with network-manager 1.2.4-0ubuntu1.

sudo service network-manager restart

provides a temporary workaround.

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

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   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/1589005/+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 1635456] Re: [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking station] No sound at all

2016-10-21 Thread Seth Arnold
This computer may have hardware problems; please install the mcelog
package and see what the /var/log/mcelog file reports:


[ 1800.75] mce: [Hardware Error]: Machine check events logged
[ 1840.847894] CPU0: Core temperature/speed normal
[ 1950.41] mce: [Hardware Error]: Machine check events logged
[ 2140.844426] CPU0: Core temperature/speed normal
[ 2175.62] mce: [Hardware Error]: Machine check events logged

Thanks

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

Title:
  [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking
  station] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  nao funciona caixas som usei alsamixer, usei pulseaudio, etc

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-73.81~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-73-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   marcelo1921 F...m pulseaudio
   /dev/snd/controlC0:  marcelo1921 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 20 21:40:40 2016
  InstallationDate: Installed on 2016-09-14 (35 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Áudio interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   marcelo1921 F...m pulseaudio
   /dev/snd/controlC0:  marcelo1921 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front, Docking station
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking 
station] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P17G
  dmi.board.vendor: PCCHIPS
  dmi.board.version: ECS
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: PCCHIPS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd02/13/2008:svnPCCHIPS:pnP17G:pvr1.0:rvnPCCHIPS:rnP17G:rvrECS:cvnPCCHIPS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: P17G
  dmi.product.version: 1.0
  dmi.sys.vendor: PCCHIPS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635456/+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 1635456] Re: [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking station] No sound at all

2016-10-21 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking
  station] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  nao funciona caixas som usei alsamixer, usei pulseaudio, etc

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-73.81~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-73-generic i686
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   marcelo1921 F...m pulseaudio
   /dev/snd/controlC0:  marcelo1921 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 20 21:40:40 2016
  InstallationDate: Installed on 2016-09-14 (35 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Áudio interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D1p:   marcelo1921 F...m pulseaudio
   /dev/snd/controlC0:  marcelo1921 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front, Docking station
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [P17G, SigmaTel STAC9221 A2, Green Headphone Out, Front, Docking 
station] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P17G
  dmi.board.vendor: PCCHIPS
  dmi.board.version: ECS
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: PCCHIPS
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd02/13/2008:svnPCCHIPS:pnP17G:pvr1.0:rvnPCCHIPS:rnP17G:rvrECS:cvnPCCHIPS:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: P17G
  dmi.product.version: 1.0
  dmi.sys.vendor: PCCHIPS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1635456/+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 203722] Re: Double clicking on Floppy Drive gives an error (Unable to mount location) despite it's mounted but not opened in Hardy RC

2016-10-21 Thread Bug Watch Updater
** Changed in: gvfs
   Status: New => Expired

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

Title:
  Double clicking on Floppy Drive gives an error (Unable to mount
  location) despite it's mounted but not opened in Hardy RC

Status in gvfs:
  Expired
Status in One Hundred Papercuts:
  Invalid
Status in gnome-mount package in Ubuntu:
  Invalid
Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Hardy RC.

  Step to reproduce it:
  The FIRST time I try to mount floppy double clicking its icon I get an error 
message: See attachment here 

  https://bugs.launchpad.net/ubuntu/+source/gnome-
  mount/+bug/203722/comments/7

  In English is:
  "Unable to mount location"
  "Can't mount file"

  but this doesn't prevent mounting itself because floppy is mounted correctly 
(just wait some seconds) although it doesn't open any folder.
  If I unmount and mount it again during the same gnome session no problem at 
all. (Apart from Bug #206860 and double folder opening bug)

  The error message come up every FIRST mounting time of every session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/203722/+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 1589005] Re: After update DNS work unstable

2016-10-21 Thread Aron Xu
Can't reproduce with current version, is it still affecting you?

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => 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/1589005

Title:
  After update DNS work unstable

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Today I have updated network-manager from update repo and chrome have
  started get err_name_resolution_failed apt started get network errors.

  W: Failed to fetch 
http://by.archive.ubuntu.com/ubuntu/pool/main/n/network-manager/network-manager_1.1.93-0ubuntu4_amd64.deb
    Temporary failure resolving 'by.archive.ubuntu.com'

  I got same error when  previously update network-manager from ubuntu-
  proposed, so I think this packet with regression moved to normal
  update.

  workaround: download old network-manager_1.1.93-0ubuntu4_amd64.deb and 
install it using
  sudo dpkg -i network-manager_1.1.93-0ubuntu4_amd64.deb
  and lock version 
  echo "network-manager hold" | sudo dpkg --set-selections

  "apt update" going to show network-manager as upgradable but "apt
  upgrage" going to ignore it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun  4 01:39:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-01 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.100.1 dev enp8s0  proto static  metric 100
   169.254.0.0/16 dev enp8s0  scope link  metric 1000
   192.168.100.0/24 dev enp8s0  proto kernel  scope link  src 192.168.100.9  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE   
  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  802-3-ethernet 
  1464993435  Sat 04 Jun 2016 01:37:15 MSK  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  yes enp8s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0
   HUAWEI-KpW2 1   8087b7e0-51dc-43c4-8928-4d03c85a5762  
802-11-wireless  1464546384  Sun 29 May 2016 21:26:24 MSK  yes  0   
  no/org/freedesktop/NetworkManager/Settings/1  no  --  
-- --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   enp8s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
Проводное соединение 1  34318290-4c71-4b1f-9154-d0f134b91440  
/org/freedesktop/NetworkManager/ActiveConnection/0
   wlp9s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----
   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/1589005/+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 1635376] Re: double-clicking on an executable created with gcc6 opens an error message

2016-10-21 Thread Khurshid Alam
Does a.out have execution permission? What is the expected result? Open
terminal and show output of a.out?

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

Title:
  double-clicking on an executable created with gcc6 opens an error
  message

Status in nautilus package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 x64 with Nautilus 3.20.3

  * Open a terminal
  * Install gcc: sudo apt install build-essential
  * Build an executable: printf "int main() { return 1; }" | gcc -x c -
  * Open a Nautilus window on the current directory: nautilus .
  * Double-click on the generated executable: a.out

  Expected result: Nautilus starts the executable
  Actual result: Nautilus displays an error message:

     Could not display "a.out".
     There is no application installed for shared library files.
     Do you want to search for an application to open this file?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635376/+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 1633845] Re: network-manager does not connect to wifi

2016-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  network-manager does not connect to wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to wifi network, network-manager remains
  blocked in waiting for authentification state then fails after cca
  1min. This started to happen after I updated to kubuntu 16.10.

  Stopping network manager from service and trying to manually connect
  with wpa_supplicant works fine.

  The only way to fix this for me was to stop network manager and/or
  networking and restart the services sometimes more than once.

  os: Kubuntu 16.10
  network-manager: 1.2.4
  hardware: dell xps 9550 
  network controller: BCM43602

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+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 1633845] Re: network-manager does not connect to wifi

2016-10-21 Thread Quentin
Same issue on ubuntu-gnome 16.10 after resuming from sleep.

Network controller: Broadcom Limited BCM43602 802.11ac Wireless LAN SoC (rev 01)
Hardware: Dell XPS 9550

It is required to restart the network manager.

There was the same issue in Ubuntu 16.04 6/7 months ago and it was fixed
in an update.

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

Title:
  network-manager does not connect to wifi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to wifi network, network-manager remains
  blocked in waiting for authentification state then fails after cca
  1min. This started to happen after I updated to kubuntu 16.10.

  Stopping network manager from service and trying to manually connect
  with wpa_supplicant works fine.

  The only way to fix this for me was to stop network manager and/or
  networking and restart the services sometimes more than once.

  os: Kubuntu 16.10
  network-manager: 1.2.4
  hardware: dell xps 9550 
  network controller: BCM43602

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+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 1635375] Re: First letter doubled in Facebook posts.

2016-10-21 Thread Callista Graves
Just Epiphany.  3.18.5

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

Title:
  First letter doubled in Facebook posts.

Status in elementary OS:
  New
Status in epiphany-browser package in Ubuntu:
  New

Bug description:
  I am running elementary OS Loki right now, and have been struggling
  with justifying using the Epiphany browser as my default, but with
  this bug it is simply impossible.

  When on Facebook, and typing the first word in a post, or in a
  sentence, the letter is always doubled, when using the shift key.

  It is nearly impossible to find any information on the internet about
  this, and while I would prefer to run Epiphany as default browser,
  this is a deal breaker for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1635375/+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 791717] Re: Display issues with multi-line input

2016-10-21 Thread Bug Watch Updater
** Changed in: gcalctool
   Status: New => Fix Released

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

Title:
  Display issues with multi-line input

Status in GCalctool:
  Fix Released
Status in gcalctool package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gcalctool

  When the input goes over 2 lines the calculator screen should adapt to
  display the extra text

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gcalctool 6.0.1~git20110421-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  Date: Thu Jun  2 10:07:37 2011
  ExecutablePath: /usr/bin/gcalctool
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=fr_FR.UTF-8
   LANGUAGE=fr_FR:en
  SourcePackage: gcalctool
  UpgradeStatus: Upgraded to natty on 2011-04-28 (34 days ago)
  XsessionErrors:
   (:6200): libindicator-WARNING **: Unable to find group ' Shortcut 
Group'
   (indicator-multiload:6240): Gdk-CRITICAL **: 
IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 
`private->update_and_descendants_freeze_count > 0' failed
   (gnome-power-manager:6213): libappindicator-WARNING **: Unable to connect to 
the Notification Watcher: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.101 was not 
provided by any .service files

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcalctool/+bug/791717/+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 1626605] Re: xorg error when waking up after suspend in YY

2016-10-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  xorg error when waking up after suspend in YY

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Enviroment: latest image of yy

  Distributor ID: Ubuntu
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Codename:   yakkety

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD

  Steps to reproduce:

  1º Boot or reboot your laptop
  2º Once you're in log in screen go to indicator-session and suspend it
  3º Once suspended, wake it up be pressing power button for example

  Current result: My mouse can move but clicking is not working on
  anything, then black screen and window error saying "The system is
  running on low graphics mode", finally it lets me choose how to start
  session again. Pics 1 and 2 attached

  Expected result: Laptop should wake up and let the user enter his
  session with out any issue.

  Add info: please find attached xorg logs, crash file saved in
  /sys/class/drm/card0/error and here is the dmesg output (line 938)
  https://pastebin.canonical.com/166279/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626605/+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 1632027] Re: New Document feature missing from Nautilus 3.20+

2016-10-21 Thread BronsonMathews
Ah one other frustrating feature is the way the new pop-ups in nautilus occur 
when a file transfer or action happens and finish. 
There needs to be a way to turn these off and disable them completely!

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+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 1635232] Re: If opening a second archive with file-roller, it doesn't open the new instance succesfully

2016-10-21 Thread Sebastien Bacher
Thanks

** Changed in: file-roller (Ubuntu)
   Status: New => Triaged

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

Title:
  If opening a second archive with file-roller, it doesn't open the new
  instance succesfully

Status in File Roller:
  Confirmed
Status in file-roller package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu Yakkety file-roller 3.22.0

  If opening a first archive (e.g. a zip-file) file-roller opens this correctly.
  This can be done using nautilus, xdg-open or directly passing the filename 
argument to file-roller.

  But if you already have one file-roller instance open, and try to open
  a second archive (either with nautilus, xdg-open or directly passing
  the filename argument), a new file-roller window is opened, but the
  archive is not opened at all.

  At that moment the user *can* however open via the toolbar
  "File->Open..." an archive, and that *does* work.

  This problem was not in Xenial, and started since the upgrade to
  Yakkety.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1635232/+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 1635411] Re: nvidia-361 361.45.11-0ubuntu3: nvidia-361 kernel module failed to build [error: redefinition of ‘radix_tree_empty’]

2016-10-21 Thread Daniel van Vugt
** Summary changed:

- nvidia-361 361.45.11-0ubuntu3: nvidia-361 kernel module failed to build
+ nvidia-361 361.45.11-0ubuntu3: nvidia-361 kernel module failed to build 
[error: redefinition of ‘radix_tree_empty’]

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

Title:
  nvidia-361 361.45.11-0ubuntu3: nvidia-361 kernel module failed to
  build [error: redefinition of ‘radix_tree_empty’]

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  Ubuntu 16.10 dev
  Nvidia 950m (hybrid)

  As of writing this, everything seem to work fine, there is just this
  warning saying that nvidia-361 driver as failed to install (I
  installed it few months ago). I will try to provide further info if I
  encounter other malfunctions.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: nvidia-361 361.45.11-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 4.8.0-26-generic
  Date: Thu Oct 20 22:11:23 2016
  DuplicateSignature: 
dkms:nvidia-361:361.45.11-0ubuntu3:/var/lib/dkms/nvidia-361/361.45.11/build/nvidia-uvm/uvm_linux.h:550:13:
 error: redefinition of ‘radix_tree_empty’
  InstallationDate: Installed on 2016-06-27 (115 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160627)
  PackageVersion: 361.45.11-0ubuntu3
  RelatedPackageVersions:
   dpkg 1.18.7ubuntu1
   apt  1.3~exp1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.45.11-0ubuntu3: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1635411/+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 1616943] Re: Can't auth against U1 in g-s

2016-10-21 Thread Robert Ancell
The verification failed because snapd-login-service was not installed -
this will be fixed in snapd-glib 1.2-0ubuntu1.1

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

Title:
  Can't auth against U1 in g-s

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Authentication using Ubuntu One credentials to install/remove snaps always  
fails. This is due to a behaviour change in snapd (no longer accepts login 
requests from non-root users). Existing credentials continue to work.

  [Test Case]
  1. Delete any existing credentials by deleting passwords marked 
"com.ubuntu.UbuntuOne.GnomeSoftware" using Seahorse.
  2. Start GNOME Software
  3. Search for a snap (e.g. "moon-buggy")
  4. Install Snap
  5. Enter Ubuntu One credentials when prompted

  Observed result:
  Dialog says "Incorrect email or password".

  Expected result:
  Authentication completes and the snap is installed.

  [Regression Potential]
  The solution is to use a new D-Bus service (snapd-login-service) and new 
library (snapd-glib) to get the Macaroon from snapd. This has some risk of 
introducing new bugs. The change is minimised (other snapd code paths 
unchanged) and the alternative is login to be impossible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616943/+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 1635541] [NEW] /usr/bin/gnome-software:11:gs_refine_item_pixbuf:gs_appstream_refine_app:gs_plugin_add_installed:gs_plugin_loader_run_results:gs_plugin_loader_get_installed_thre

2016-10-21 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.1+git20161003.0.7ac7d1b-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/a2c6112a5f99b4339fbcf556d3c6d186d48c55b6 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: xenial yakkety

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

Title:
  /usr/bin/gnome-
  
software:11:gs_refine_item_pixbuf:gs_appstream_refine_app:gs_plugin_add_installed:gs_plugin_loader_run_results:gs_plugin_loader_get_installed_thread_cb

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.1+git20161003.0.7ac7d1b-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/a2c6112a5f99b4339fbcf556d3c6d186d48c55b6 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1635541/+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 1632027] Re: New Document feature missing from Nautilus 3.20+

2016-10-21 Thread BronsonMathews
and the 16.10 version of the same view is unreadable

** Attachment added: "1610.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+attachment/4764708/+files/1610.png

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+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 1632027] Re: New Document feature missing from Nautilus 3.20+

2016-10-21 Thread BronsonMathews
ops these were supposed to be part of my other bug:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1634334

oh well, they're all related.

Ive tried to install nemo as a replacement in the meantime till this is
fixed...

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+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 1632027] Re: New Document feature missing from Nautilus 3.20+

2016-10-21 Thread BronsonMathews
also noticed other things seem weird such as
- shortcut keys are always showing in right click menu (no way to disable this 
either!)
- The dividers seem very visually awkward now in the right click menu, on 16.04 
is was very flat, now on 16.10 its very deep and gouging to look at.

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+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 1632027] Re: New Document feature missing from Nautilus 3.20+

2016-10-21 Thread BronsonMathews
ok ive added a screenshot showing the weird spacing issue thats
happening on nautilus 16.10. The icons have all get crushed up together
making this view useless

** Attachment added: "1604.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+attachment/4764707/+files/1604.png

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

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+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 1635375] Re: First letter doubled in Facebook posts.

2016-10-21 Thread wolf
Does this only occur in Epiphany or in other browsers too?

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

Title:
  First letter doubled in Facebook posts.

Status in elementary OS:
  New
Status in epiphany-browser package in Ubuntu:
  New

Bug description:
  I am running elementary OS Loki right now, and have been struggling
  with justifying using the Epiphany browser as my default, but with
  this bug it is simply impossible.

  When on Facebook, and typing the first word in a post, or in a
  sentence, the letter is always doubled, when using the shift key.

  It is nearly impossible to find any information on the internet about
  this, and while I would prefer to run Epiphany as default browser,
  this is a deal breaker for me.

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