date:20170418

[Expired for Déjà Dup because there has been no activity for 60 days.]

** Changed in: deja-dup
   Status: Incomplete => Expired

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

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Expired
Status in duplicity package in Ubuntu:
  Expired

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+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 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

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

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

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

Title:
  'metadata' file not found when creating backup ("Could not restore
  ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Status in Déjà Dup:
  Expired
Status in duplicity package in Ubuntu:
  Expired

Bug description:
  Linux release: Ubuntu 13.04 64bit
  Kernel: 3.8.0-29-generic
  Python: 2.7.4
  Deja Dup: 26.0
  Duplicity: 0.6.21

  Hi. I've tried to do my monthly or so backup recently, but Deja Dup
  crashed after trying to backup a very large file (VM disk with Windows
  7, 50GB or so). I tried to do another one, this time excluding all my
  large VM's. However, now when trying to do a backup I'm getting the
  following error a few seconds after inputting my encryption password:

  Could not restore ‘/home/tom/.cache/deja-dup/metadata’: File not found
  in backup

  I've tried reinstalling both deja-dup and duplicity, purging
  duplicity, deleting deja-dup and duplicity from /home/tom/.cache,
  deleting the backup files on the external drive, deleting it's config
  as described here http://askubuntu.com/questions/53980/how-to-delete-
  all-the-settings-for-deja-dup. I know (well, I have some evidence
  supporting this) that the drive itself isn't faulty as I managed to
  backup my old laptop to the drive using duplicity and it worked fine
  (Fedora 19, deja dup 26.0 I think). I will upload the appropriate logs
  momentarily.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+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 1622575] Re: System hangs randomly (log shows 'EQ overflowing').

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

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

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

Title:
  System hangs randomly (log shows 'EQ overflowing').

Status in xorg package in Ubuntu:
  Expired

Bug description:
  X Server and then system freezes, ALT+CTRL+Fx doesn't work, sometimes even 
REISUB doesn't work.
  Memtest result is ok, no errors. HDD also is ok. Windows works perfectly on 
the machine.
  It's possible to login via SSH and reboot (but during reboot process it also 
often hangs completely).
  The problem occures randomly during every-day work (usually once or twice a 
day making me loose my work!), like with totally no adequate reasons.
  I'm using AMD Athlon 5350 (SocketAM1 APU) with radeon R3 integrated video.
  My operating system is Ubuntu 16.04.1 LTS with all the last available 
updates. Bug lasts throughout all the time. Tried to reinstall many times 
(MD5sum of the installation image was correct) - nothing changes.

  x-0.log in the attachment

  part of the log:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x562fc426a5ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x562fc424c083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x562fc4124662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f7320d91000+0x61f3) 
[0x7f7320d971f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f7320d91000+0x6a5d) 
[0x7f7320d97a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x562fc40b8000+0x94228) [0x562fc414c228]
  (EE) 6: /usr/lib/xorg/Xorg (0x562fc40b8000+0xb96f2) [0x562fc41716f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f732524e000+0x354a0) 
[0x7f73252834a0]
  (EE) 8: /lib/x86_64-linux-gnu/libpthread.so.0 (pthread_cond_wait+0xbe) 
[0x7f732503e39e]
  (EE) 9: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6b77fb) [0x7f731f3027fb]
  (EE) 10: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6b87c1) [0x7f731f3037c1]
  (EE) 11: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x61bf52) [0x7f731f266f52]
  (EE) 12: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x6d521e) [0x7f731f32021e]
  (EE) 13: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(0x7f731ec4b000+0x201de4) [0x7f731ee4cde4]
  (EE) 14: /usr/lib/xorg/modules/libglamoregl.so (glamor_block_handler+0x4b) 
[0x7f73204bcffb]
  (EE) 15: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f732133c000+0x471b2) 
[0x7f73213831b2]
  (EE) 16: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x562fc4111034]
  (EE) 17: /usr/lib/xorg/Xorg (WriteToClient+0x244) [0x562fc426e234]
  (EE) 18: /usr/lib/xorg/Xorg (WriteEventsToClient+0x1e2) [0x562fc4117022]
  (EE) 19: /usr/lib/xorg/Xorg (0x562fc40b8000+0x133b5f) [0x562fc41ebb5f]
  (EE) 20: /usr/lib/xorg/Xorg (DamageReportDamage+0x89) [0x562fc41f1359]
  (EE) 21: /usr/lib/xorg/Xorg (0x562fc40b8000+0x139c1a) [0x562fc41f1c1a]
  (EE) 22: /usr/lib/xorg/Xorg (0x562fc40b8000+0x13d140) [0x562fc41f5140]
  (EE) 23: /usr/lib/xorg/Xorg (0x562fc40b8000+0x4fb87) [0x562fc4107b87]
  (EE) 24: /usr/lib/xorg/Xorg (0x562fc40b8000+0x53bbf) [0x562fc410bbbf]
  (EE) 25: /usr/lib/xorg/Xorg (0x562fc40b8000+0x57c33) [0x562fc410fc33]
  (EE) 26: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f732526e830]
  (EE) 27: /usr/lib/xorg/Xorg (_start+0x29) [0x562fc40f9f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep 12 14:31:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] 
[1002:9830] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Kabini [Radeon HD 8400 
/ R3 Series] [1462:7865]
  InstallationDate: Installed on 2016-08-18 (25 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64

[Desktop-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones

2017-04-18 Thread Nate Meyers

This bug has been submitted to the linux kernel bug tracker as well

https://bugzilla.kernel.org/show_bug.cgi?id=195457

** Bug watch added: Linux Kernel Bug Tracker #195457
   http://bugzilla.kernel.org/195457

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1664065] Re: Canon mf4880 driver and cups install correctly. but no print

[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/1664065

Title:
  Canon mf4880 driver and cups install correctly. but no print

Status in cups package in Ubuntu:
  Expired

Bug description:
  Everything install correctly. printer was discovered in usb and
  network mode both. Print job with finish without error, but no print
  on the printer.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Feb 12 16:43:21 2017
  InstallationDate: Installed on 2015-12-29 (411 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Canon_MF4800_Series: cnusb:/dev/usb/lp0
  MachineType: Acer Aspire TC-605
  Papersize: letter
  PpdFiles: Canon_MF4800_Series: Canon MF4800 Series UFRII LT ver.3.0
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=daaeeb49-534f-4636-895e-a56cafb78c19 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to yakkety on 2017-02-12 (0 days ago)
  dmi.bios.date: 03/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A4
  dmi.board.name: Aspire TC-605
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A4:bd03/21/2014:svnAcer:pnAspireTC-605:pvr:rvnAcer:rnAspireTC-605:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire TC-605
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1664065/+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 1662645] Re: owncloud account does NOT support httpS

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

** Changed in: account-plugins (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  owncloud account does NOT support httpS

Status in account-plugins package in Ubuntu:
  Expired

Bug description:
  Ubuntu 15.04 OTA14
  Clean system
  in the account page there is Ubuntu One and owncloud.

  When I try to set the URL of my owncloud server httpS://owncloud/owncloud,
  I get an "invalid URL error"

  It works fine with http://owncloud but this is not very secure,
  and this disable access to my owncloud from outside home : firewall
  allows only httpS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1662645/+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 1683997] Re: Firefox scrollbars are too narrow and difficult to use in Zesty

2017-04-18 Thread Rocko

Attached is a screenshot showing the old-style and new-style scrollbars
in Firefox, which measure about 15 pixels and 5 pixels wide
respectively.

** Attachment added: "scrollbars.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1683997/+attachment/4864591/+files/scrollbars.png

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

Title:
  Firefox scrollbars are too narrow and difficult to use in Zesty

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox 52.0.1 in Ubuntu 17.04 has very narrow scrollbars that are
  difficult to click on using a mouse - they are about one-third of the
  width of the 'old-style' scrollbars used throughout most of Ubuntu
  until a few weeks ago. (ubuntu-gnome has the same problem, fwiw.)

  I notice that some applications, like gnome-terminal, still use the
  old-style scrollbars. Others, like Nautilus and Rhythmbox, have a
  half-width scrollbar like Firefox, but the scrollbar doubles in width
  when the mouse moves near to them, making them almost as usable as the
  old-style scrollbars.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 52.0.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rocko  1598 F pulseaudio
  BuildID: 20170321232041
  Channel: Unavailable
  Date: Wed Apr 19 11:51:57 2017
  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 2017-04-13 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  IpRoute:
   default via 10.0.2.2 dev enp0s3 proto static metric 100
   10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100
   169.254.0.0/16 dev enp0s3 scope link metric 1000
  IwConfig:
   lono wireless extensions.

   enp0s3no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=52.0.1/20170321232041
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RfKill:

  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1683997/+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 1683997] [NEW] Firefox scrollbars are too narrow and difficult to use in Zesty

2017-04-18 Thread Rocko

Public bug reported:

Firefox 52.0.1 in Ubuntu 17.04 has very narrow scrollbars that are
difficult to click on using a mouse - they are about one-third of the
width of the 'old-style' scrollbars used throughout most of Ubuntu until
a few weeks ago. (ubuntu-gnome has the same problem, fwiw.)

I notice that some applications, like gnome-terminal, still use the old-
style scrollbars. Others, like Nautilus and Rhythmbox, have a half-width
scrollbar like Firefox, but the scrollbar doubles in width when the
mouse moves near to them, making them almost as usable as the old-style
scrollbars.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: firefox 52.0.1+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rocko  1598 F pulseaudio
BuildID: 20170321232041
Channel: Unavailable
Date: Wed Apr 19 11:51:57 2017
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 2017-04-13 (5 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
IpRoute:
 default via 10.0.2.2 dev enp0s3 proto static metric 100
 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100
 169.254.0.0/16 dev enp0s3 scope link metric 1000
IwConfig:
 lono wireless extensions.

 enp0s3no wireless extensions.
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=52.0.1/20170321232041
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RfKill:

RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-bug zesty

** Description changed:

  Firefox 52.0.1 in Ubuntu 17.04 has very narrow scrollbars that are
- difficult to click on using a mouse - they are about half the width of
- the 'old-style' scrollbars used throughout most of Ubuntu until a few
- weeks ago. (ubuntu-gnome has the same problem, fwiw.)
+ difficult to click on using a mouse - they are about one-third of the
+ 'old-style' scrollbars used throughout most of Ubuntu until a few weeks
+ ago. (ubuntu-gnome has the same problem, fwiw.)
  
  I notice that some applications, like gnome-terminal, still use the old-
  style scrollbars. Others, like Nautilus and Rhythmbox, have a half-width
  scrollbar like Firefox, but the scrollbar doubles in width when the
  mouse moves near to them, making them almost as usable as the old-style
  scrollbars.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 52.0.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  rocko  1598 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  rocko  1598 F pulseaudio
  BuildID: 20170321232041
  Channel: Unavailable
  Date: Wed Apr 19 11:51:57 2017
  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
+  # 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 2017-04-13 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  IpRoute:
-  default via 10.0.2.2 dev enp0s3 proto static metric 100 
-  10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 me

[Desktop-packages] [Bug 1652282] Re: Wayland default policy prohibits root applications

It was announced today that the Ubuntu Desktop Team currently intends to
default to GNOME on Wayland for Ubuntu 18.04 LTS.

** Tags removed: gnome3-ppa third-party-packages yakkety
** Tags added: wayland

** Package changed: wayland (Ubuntu) => gparted (Ubuntu)

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

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

** Summary changed:

- Wayland default policy prohibits root applications
+ GParted does not work in GNOME on Wayland

** Changed in: ubuntu-gnome
   Status: New => Triaged

** Changed in: ubuntu-gnome
   Importance: Undecided => High

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

Title:
  GParted does not work in GNOME on Wayland

Status in GParted:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gparted package in Ubuntu:
  Triaged

Bug description:
  I have found that after switching from Xorg to Wayland on Ubuntu GNOME
  16.10 with GNOME 3.22 that GParted does not run when I try to run it
  as root. That is when I click the icon and enter my password nothing
  happens. I have found that when running what is run when the icon is
  clicked that the output in Terminal is (gparted-pkexec):

  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/boot.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:16832): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/boot.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/tmp.mount.

  So I am now unable to launch and use GParted as root which is really
  the only way I can run it in order to make changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gparted 0.25.0-1
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 23 11:13:13 2016
  InstallationDate: Installed on 2016-05-15 (221 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gparted
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gparted/+bug/1652282/+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 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-04-18 Thread Colan Schwartz

** Tags added: zesty

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-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:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  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-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
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+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 1683990] [NEW] [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all

2017-04-18 Thread Clare

Public bug reported:

I have had no sound since original (fairly recent) purchase. I purchased
online from Dell.

Sound preferences were originally showing in upper right hand corner of
the screen, but the sliders for changing volume were grayed out, and
choosing sound test had no audible or visual result.

Now sound preferences are not showing in upper right corner at all, and
system preferences --> sound no longer shows 'sound test' as an option.

I tried to fix original problem myself by killing then re-starting pulseaudio
No effect. Also I tried commands 

apt-get purge pulseaudio 
and then later 
apt-get install pulseaudio

it seemed to be after that when the sound preferences stopped showing in
upper right corner, but I also did a general ubuntu update at the same
time (and there is still a restart required for update for 'Latitude
E5X60 System Update' 68614)

Release: Ubuntu 16.04.2 LTS
Package: N: Unable to locate package pkgname

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  clare  2105 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 18 22:44:33 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
InstallationDate: Installed on 2017-01-05 (104 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  clare  2105 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to xenial on 2017-02-10 (67 days ago)
dmi.bios.date: 08/26/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.4
dmi.board.name: 0FFPFD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd08/26/2016:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0FFPFD:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 3510
dmi.sys.vendor: Dell Inc.

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

Title:
  [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have had no sound since original (fairly recent) purchase. I
  purchased online from Dell.

  Sound preferences were originally showing in upper right hand corner
  of the screen, but the sliders for changing volume were grayed out,
  and choosing sound test had no audible or visual result.

  Now sound preferences are not showing in upper right corner at all,
  and system preferences --> sound no longer shows 'sound test' as an
  option.

  I tried to fix original problem myself by killing then re-starting pulseaudio
  No effect. Also I tried commands 

  apt-get purge pulseaudio 
  and then later 
  apt-get install pulseaudio

  it seemed to be after that when the sound preferences stopped showing
  in upper right corner, but I also did a general ubuntu update at the
  same time (and there is still a restart required for update for
  'Latitude E5X60 System Update' 68614)

  Release: Ubuntu 16.04.2 LTS
  Package: N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 18 22:44:33 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2017-01-05 (104 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID

[Desktop-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-04-18 Thread T Martin

This bug began affecting me on April 16, 2017.  I'm using Chrome 57 and
when I move one window to my bottom 2x2 vertical desktop, the UI is
extremely laggy.  Moving it back to desktop 1 resolves the issue
immediately.

$ uname -a
Linux eldritch 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux


Does not seem to affect Firefox.

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-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:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  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-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
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+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 1648183] Re: Crackling and popping sound when using headphones

2017-04-18 Thread Nate Meyers

Same issue with asus zenbook 3, same audio card. In addition the built
in speaker output is broken, it can only be 0% or 100%, no in between.
Seemingly related.

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1588150] Re: Remove webkitgtk from archive

** Changed in: bijiben
   Status: In Progress => Fix Released

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

Title:
  Remove webkitgtk from archive

Status in Bijiben:
  Fix Released
Status in Empathy:
  Fix Released
Status in Evolution:
  Fix Released
Status in Geary:
  Fix Released
Status in Liferea:
  Fix Released
Status in LightDM Webkit Greeter:
  Fix Committed
Status in bijiben package in Ubuntu:
  Triaged
Status in birdfont package in Ubuntu:
  Fix Committed
Status in cairo-dock-plugins package in Ubuntu:
  Triaged
Status in empathy package in Ubuntu:
  Triaged
Status in evolution package in Ubuntu:
  Fix Released
Status in geary package in Ubuntu:
  Triaged
Status in gnome-web-photo package in Ubuntu:
  Triaged
Status in gtkpod package in Ubuntu:
  Triaged
Status in liferea package in Ubuntu:
  Fix Released
Status in lightdm-webkit-greeter package in Ubuntu:
  In Progress
Status in maildir-utils package in Ubuntu:
  Triaged
Status in surf package in Ubuntu:
  In Progress
Status in webkitgtk package in Ubuntu:
  Triaged
Status in xiphos package in Ubuntu:
  Triaged
Status in xombrero package in Ubuntu:
  Triaged

Bug description:
  webkitgtk is obsolete and has been replaced by webkit2gtk. This
  requires things to be ported to the new API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bijiben/+bug/1588150/+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 1683978] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-04-18 Thread Apport retracing service

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

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 #1681231, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1681231
   package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  I was set in up the new version 17.04 and window pop up and tell me
  what you all ready now, sorry i forgot to specify that was upgrade the
  version 16.04 on line, by the way the rest of the job was done well.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 18 18:30:32 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-01-05 (469 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1683978/+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 1683978] [NEW] package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-04-18 Thread jl allard

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

Public bug reported:

I was set in up the new version 17.04 and window pop up and tell me what
you all ready now, sorry i forgot to specify that was upgrade the
version 16.04 on line, by the way the rest of the job was done well.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: cracklib-runtime 2.9.2-3
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue Apr 18 18:30:32 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-01-05 (469 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: cracklib2
Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  I was set in up the new version 17.04 and window pop up and tell me
  what you all ready now, sorry i forgot to specify that was upgrade the
  version 16.04 on line, by the way the rest of the job was done well.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 18 18:30:32 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-01-05 (469 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1683978/+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 1681038] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

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

** Changed in: cups (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/1681038

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Apr  8 12:26:01 2017
  DpkgHistoryLog:
   Start-Date: 2017-04-08  12:25:53
   Commandline: apt-get -f install
   Requested-By: abdul (1000)
   Remove: printer-driver-splix:amd64 (2.0.0+svn315-4fakesync1), 
bluez-cups:amd64 (5.37-0ubuntu5), printer-driver-hpcups:amd64 
(3.16.3+repack0-1), printer-driver-postscript-hp:amd64 (3.16.3+repack0-1), 
hplip:amd64 (3.16.3+repack0-1), printer-driver-gutenprint:amd64 (5.2.11-1), 
cups-core-drivers:amd64 (2.1.3-4ubuntu0.2), cups-daemon:amd64 (2.1.3-4), 
cups:amd64 (2.1.3-4ubuntu0.2), indicator-printers:amd64 
(0.1.7+15.04.20150220-0ubuntu2)
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-02-14 (52 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: LENOVO 20351
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=f95918d9-59c9-4fc3-91a3-c5236d029fec ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=f95918d9-59c9-4fc3-91a3-c5236d029fec ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/23/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1681038/+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 1683483] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2017-04-18 Thread Apport retracing service

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

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 #1681038, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1681038
   package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed 
pre-removal script returned error exit status 1

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Impossible to actualize, many errors!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon Apr 17 21:27:32 2017
  DpkgTerminalLog:
   Removing cups-daemon (2.1.3-4) ...
   Job for cups.service canceled.
   invoke-rc.d: initscript cups, action "stop" failed.
   dpkg: error processing package cups-daemon (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-06-28 (293 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer AOA150
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c0b8ad0e-eb56-45e6-91c3-bba6b84af2c2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c0b8ad0e-eb56-45e6-91c3-bba6b84af2c2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3310
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AOA150
  dmi.product.version: 1
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1683483/+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 1683483] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

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

** 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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1683483

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Impossible to actualize, many errors!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon Apr 17 21:27:32 2017
  DpkgTerminalLog:
   Removing cups-daemon (2.1.3-4) ...
   Job for cups.service canceled.
   invoke-rc.d: initscript cups, action "stop" failed.
   dpkg: error processing package cups-daemon (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-06-28 (293 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer AOA150
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c0b8ad0e-eb56-45e6-91c3-bba6b84af2c2 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c0b8ad0e-eb56-45e6-91c3-bba6b84af2c2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3310
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3310:bd10/06/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: AOA150
  dmi.product.version: 1
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1683483/+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 1683898] Re: Compose key can't be set in Settings>Keyboard with GNOME 3.24

** Changed in: gnome-control-center
   Status: Unknown => Confirmed

** Changed in: gnome-control-center
   Importance: Unknown => Medium

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

Title:
  Compose key can't be set in Settings>Keyboard with GNOME 3.24

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  The changes implemented with https://bugs.launchpad.net/ubuntu/+source
  /ubuntu-docs/+bug/1624778 in https://help.gnome.org/users/gnome-
  help/stable/tips-specialchars.html.en#compose do not reflect the
  current settings dialog for Ubuntu-Gnome 17.04.

  Going from "All Settings" to "Keyboard" switches to "Keyboard Shortcuts" 
immediately.
  The new "Keyboard Shortcuts" dialog does not seem to contain settings for 
'compose key' (the group "Typing" only contains "Switch to {next,previous} 
input source").

  PS: In the meantime, where do I find the settings for 'compose key' in
  Ubuntu-Gnome 17.04? :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1683898/+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 1683178] Re: Youtube video tab name always starts with a (11)

My firefox configuration is far from standard but I don't see this
behaviour on 52.0.2+build1-0ubuntu0.16.04.1.

Thanks

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

Title:
  Youtube video tab name always starts with a (11)

Status in firefox package in Ubuntu:
  New

Bug description:
  Any youtube video tab name will have a (11) prefix.
  For example https://www.youtube.com/watch?v=JGwWNGJdvx8 link will have a tab 
name
  (11)Ed Sheeran - Shape of You [Official Video]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 52.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alien  2837 F pulseaudio
   /dev/snd/pcmC1D0p:   alien  2837 F...m pulseaudio
   /dev/snd/controlC1:  alien  2837 F pulseaudio
  BuildID: 20170329150444
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Sun Apr 16 14:46:13 2017
  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-05-13 (337 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-31a01c83-f379-435d-a34c-493582170107
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{a95d8332-e4b4-6e7f-98ac-20b733364387}/defaults/preferences/leechblock.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=52.0.2/20170329150444 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20170214.1-0ubuntu0.16.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-31a01c83-f379-435d-a34c-493582170107
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A00
  dmi.board.name: 02C3X1
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A00
  dmi.modalias: 
dmi:bvnAlienware:bvrA00:bd10/21/2014:svnAlienware:pnAlienware13:pvrA00:rvnAlienware:rn02C3X1:rvrA00:cvnAlienware:ct8:cvrA00:
  dmi.product.name: Alienware 13
  dmi.product.version: A00
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1683178/+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 1683268] Re: Evince/Okular displays incorrect characters (Regression?)

2017-04-18 Thread mogliii

Update: Tried opening the test file with different programs. Here is a
summary.

Bad: Gimp, Inkscape, Okular, Evince, Libreoffice, pdf2svg (open svg file in 
Inkscape)
Good: Firefox, Imagemagick, pdf2gs (open ps file in evince)

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

Title:
  Evince/Okular displays incorrect characters (Regression?)

Status in poppler package in Ubuntu:
  New

Bug description:
  See https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/518236

  There seems to be a regression bug exactly as described in the linked
  bug report, in the currently fully patched ubuntu 16.04.

  I found this problem recently with a pdf prepared by origin on
  windows. The file contains mu characters. I came accross this bug
  report, and the datasheet posted by the OP, on page 6, lower right,
  shows missing characters in Okular 0.24.2 with PDF Backend 0.6.5. (I
  am attaching two images, one by okular and one by Firefox). Evince
  also renders wrongly.

  libpoppler is 0.41.0-0ubuntu1.1.

  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1683268/+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 1683898] Re: Compose key section needs to be updated

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Triaged

** Summary changed:

- Compose key section needs to be updated
+ Compose key can't be set in Settings>Keyboard with GNOME 3.24

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=781478
   Importance: Unknown
   Status: Unknown

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

Title:
  Compose key can't be set in Settings>Keyboard with GNOME 3.24

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  The changes implemented with https://bugs.launchpad.net/ubuntu/+source
  /ubuntu-docs/+bug/1624778 in https://help.gnome.org/users/gnome-
  help/stable/tips-specialchars.html.en#compose do not reflect the
  current settings dialog for Ubuntu-Gnome 17.04.

  Going from "All Settings" to "Keyboard" switches to "Keyboard Shortcuts" 
immediately.
  The new "Keyboard Shortcuts" dialog does not seem to contain settings for 
'compose key' (the group "Typing" only contains "Switch to {next,previous} 
input source").

  PS: In the meantime, where do I find the settings for 'compose key' in
  Ubuntu-Gnome 17.04? :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1683898/+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 1664007] Re: package gnome-keyring 3.20.0-2ubuntu4 failed to install/upgrade: intentando sobreescribir `/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', que está tamb

2017-04-18 Thread HECTOR DAVID

** Branch linked: lp:~cjwatson/launchpad/fix-mp-js-buglink

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

Title:
  package gnome-keyring 3.20.0-2ubuntu4 failed to install/upgrade:
  intentando sobreescribir `/usr/lib/x86_64-linux-gnu/pkcs11/gnome-
  keyring-pkcs11.so', que está también en el paquete libp11-kit-gnome-
  keyring:amd64 3.20.0-2ubuntu4

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  i only update mys system and install many tools from kali linux

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gnome-keyring 3.20.0-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Fri Feb 10 13:13:05 2017
  ErrorMessage: intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', que está también en 
el paquete libp11-kit-gnome-keyring:amd64 3.20.0-2ubuntu4
  InstallationDate: Installed on 2017-02-10 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.21kali1
   apt  1.3.4
  SourcePackage: gnome-keyring
  Title: package gnome-keyring 3.20.0-2ubuntu4 failed to install/upgrade: 
intentando sobreescribir 
`/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', que está también en 
el paquete libp11-kit-gnome-keyring:amd64 3.20.0-2ubuntu4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1664007/+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 1680736] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

2017-04-18 Thread HECTOR DAVID

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

** Branch linked: lp:~cjwatson/launchpad/fix-mp-js-buglink

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

Title:
  gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  happen during start up

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-keyring 3.20.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Fri Apr  7 15:45:26 2017
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  InstallationDate: Installed on 2016-12-09 (118 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  Signal: 6
  SourcePackage: gnome-keyring
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
   ()
  Title: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip fax floppy lpadmin plugdev sambashare sudo 
tape video
  mtime.conffile..etc.xdg.autostart.gnome-keyring-pkcs11.desktop: 
2016-12-16T15:22:07.050785
  mtime.conffile..etc.xdg.autostart.gnome-keyring-secrets.desktop: 
2016-12-16T15:22:07.050785

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1680736/+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 1683048] Re: package gnome-user-guide 3.18.1-1 failed to install/upgrade: no se puede leer el enlace `./usr/share/help/ta/gnome-help/accounts-which-application.page': Error de

Note the following lines, among others, from your logs:

[  401.452821] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[  401.452839] ata3.00: irq_stat 0x4001
[  401.452852] ata3.00: failed command: READ DMA EXT
[  401.452869] ata3.00: cmd 25/00:08:f0:03:fc/00:00:19:00:00/e0 tag 29 dma 4096 
in
res 51/40:08:f0:03:fc/00:00:19:00:00/e0 Emask 0x9 
(media error)
[  401.452876] ata3.00: status: { DRDY ERR }
[  401.452881] ata3.00: error: { UNC }
[  401.662161] ata3.00: configured for UDMA/133
[  401.662216] sd 2:0:0:0: [sda] tag#29 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[  401.662226] sd 2:0:0:0: [sda] tag#29 Sense Key : Medium Error [current] 
[  401.662235] sd 2:0:0:0: [sda] tag#29 Add. Sense: Unrecovered read error - 
auto reallocate failed
[  401.662247] sd 2:0:0:0: [sda] tag#29 CDB: Read(10) 28 00 19 fc 03 f0 00 00 
08 00
[  401.662253] blk_update_request: I/O error, dev sda, sector 435946480

Thanks

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

Title:
  package gnome-user-guide 3.18.1-1 failed to install/upgrade: no se
  puede leer el enlace `./usr/share/help/ta/gnome-help/accounts-which-
  application.page': Error de entrada/salida

Status in gnome-user-docs package in Ubuntu:
  Invalid

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gnome-user-guide 3.18.1-1
  ProcVersionSignature: Ubuntu 4.8.0-47.50-lowlatency 4.8.17
  Uname: Linux 4.8.0-47-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   gnome-user-guide:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Apr 15 18:49:45 2017
  DpkgTerminalLog:
   Preparando para desempaquetar .../gnome-user-guide_3.22.0-1_all.deb ...
   Desempaquetando gnome-user-guide (3.22.0-1) sobre (3.18.1-1) ...
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/gnome-user-guide_3.22.0-1_all.deb (--unpack):
no se puede leer el enlace 
`./usr/share/help/ta/gnome-help/accounts-which-application.page': Error de 
entrada/salida
  ErrorMessage: no se puede leer el enlace 
`./usr/share/help/ta/gnome-help/accounts-which-application.page': Error de 
entrada/salida
  InstallationDate: Installed on 2016-11-17 (149 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gnome-user-docs
  Title: package gnome-user-guide 3.18.1-1 failed to install/upgrade: no se 
puede leer el enlace 
`./usr/share/help/ta/gnome-help/accounts-which-application.page': Error de 
entrada/salida
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1683048/+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 1683048] Re: package gnome-user-guide 3.18.1-1 failed to install/upgrade: no se puede leer el enlace `./usr/share/help/ta/gnome-help/accounts-which-application.page': Error de

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment to this bug report it
seems that there may be a problem with your hardware.  I'd recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Changed in: gnome-user-docs (Ubuntu)
   Importance: Undecided => Low

** Tags added: hardware-error

** 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 gnome-user-docs in Ubuntu.
https://bugs.launchpad.net/bugs/1683048

Title:
  package gnome-user-guide 3.18.1-1 failed to install/upgrade: no se
  puede leer el enlace `./usr/share/help/ta/gnome-help/accounts-which-
  application.page': Error de entrada/salida

Status in gnome-user-docs package in Ubuntu:
  Invalid

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gnome-user-guide 3.18.1-1
  ProcVersionSignature: Ubuntu 4.8.0-47.50-lowlatency 4.8.17
  Uname: Linux 4.8.0-47-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   gnome-user-guide:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Apr 15 18:49:45 2017
  DpkgTerminalLog:
   Preparando para desempaquetar .../gnome-user-guide_3.22.0-1_all.deb ...
   Desempaquetando gnome-user-guide (3.22.0-1) sobre (3.18.1-1) ...
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/gnome-user-guide_3.22.0-1_all.deb (--unpack):
no se puede leer el enlace 
`./usr/share/help/ta/gnome-help/accounts-which-application.page': Error de 
entrada/salida
  ErrorMessage: no se puede leer el enlace 
`./usr/share/help/ta/gnome-help/accounts-which-application.page': Error de 
entrada/salida
  InstallationDate: Installed on 2016-11-17 (149 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gnome-user-docs
  Title: package gnome-user-guide 3.18.1-1 failed to install/upgrade: no se 
puede leer el enlace 
`./usr/share/help/ta/gnome-help/accounts-which-application.page': Error de 
entrada/salida
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1683048/+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 1683898] Re: Compose key section needs to be updated

2017-04-18 Thread Armin Grodon

Thank's a lot for the answers :)

Bug is reported as https://bugzilla.gnome.org/show_bug.cgi?id=781478
(against 'gnome-control-center' since I hope that it's getting changed
back, will report it against 'gnome-user-docs' otherwise)

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

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

Title:
  Compose key section needs to be updated

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  The changes implemented with https://bugs.launchpad.net/ubuntu/+source
  /ubuntu-docs/+bug/1624778 in https://help.gnome.org/users/gnome-
  help/stable/tips-specialchars.html.en#compose do not reflect the
  current settings dialog for Ubuntu-Gnome 17.04.

  Going from "All Settings" to "Keyboard" switches to "Keyboard Shortcuts" 
immediately.
  The new "Keyboard Shortcuts" dialog does not seem to contain settings for 
'compose key' (the group "Typing" only contains "Switch to {next,previous} 
input source").

  PS: In the meantime, where do I find the settings for 'compose key' in
  Ubuntu-Gnome 17.04? :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1683898/+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 1683268] Re: Evince/Okular displays incorrect characters (Regression?)

2017-04-18 Thread mogliii

This is a small pdf (2x1 cm^2) with 1 um (u = greek symbol) created in
Origin on Windows.

** Attachment added: "Graph1.pdf"

https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1683268/+attachment/4864500/+files/Graph1.pdf

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

Title:
Evince/Okular displays incorrect characters (Regression?)

Status in poppler package in Ubuntu:
New

Bug description:
See https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/518236

There seems to be a regression bug exactly as described in the linked
bug report, in the currently fully patched ubuntu 16.04.

I found this problem recently with a pdf prepared by origin on
windows. The file contains mu characters. I came accross this bug
report, and the datasheet posted by the OP, on page 6, lower right,
shows missing characters in Okular 0.24.2 with PDF Backend 0.6.5. (I
am attaching two images, one by okular and one by Firefox). Evince
also renders wrongly.

libpoppler is 0.41.0-0ubuntu1.1.

Description: Ubuntu 16.04.2 LTS
Release: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1683268/+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 and 16.10 yakkety

2017-04-18 Thread Lev Popov

I've installed 1:8.0-0ubuntu3.3~xenial1 from testing PPA and it partly
fixed the issue.

My headphones are Plantronics BackBeat PRO.

A2DP works perfectly fine when connection is initiated by linux machine,
but when it's initiated by headphones, when they turn on, there is no
sound. In syslog:

Apr 19 02:14:07 xps pulseaudio[11005]: [pulseaudio] module-bluez5-device.c: 
Default profile not connected, selecting off profile
Apr 19 02:14:10 xps bluetoothd[12649]: 
/org/bluez/hci0/dev_0C_E0_E4_45_40_F2/fd7: fd(25) ready
Apr 19 02:14:10 xps pulseaudio[11005]: [pulseaudio] bluez5-util.c: Transport 
TryAcquire() failed for transport /org/bluez/hci0/dev_0C_E0_E4_45_40_F2/fd7 
(Operation Not Authorized)
Apr 19 02:14:20 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:20 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:20 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:21 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:21 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.
Apr 19 02:14:21 xps pulseaudio[11005]: [pulseaudio] sink-input.c: Failed to 
create sink input: sink is suspended.

-- 
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
  and 16.10 yakkety

Status in PulseAudio:
  Confirmed
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 and 16.10.

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 1683898] Re: Compose key section needs to be updated

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

You can report against gnome-control-center asking them to move the
Compose key settings back.

And you can report against gnome-user-docs to document the current way
to set the Compose key. (Open Tweak Tool. Switch to the Typing panel.
Click Position of Compose key.)

https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-control-center
https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-user-docs

** Changed in: gnome-user-docs (Ubuntu)
Status: New => Confirmed

** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed

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

Title:
Compose key section needs to be updated

Status in gnome-control-center package in Ubuntu:
Confirmed
Status in gnome-user-docs package in Ubuntu:
Confirmed

Bug description:
The changes implemented with https://bugs.launchpad.net/ubuntu/+source
/ubuntu-docs/+bug/1624778 in https://help.gnome.org/users/gnome-
help/stable/tips-specialchars.html.en#compose do not reflect the
current settings dialog for Ubuntu-Gnome 17.04.

Going from "All Settings" to "Keyboard" switches to "Keyboard Shortcuts"
immediately.
The new "Keyboard Shortcuts" dialog does not seem to contain settings for
'compose key' (the group "Typing" only contains "Switch to {next,previous}
input source").

PS: In the meantime, where do I find the settings for 'compose key' in
Ubuntu-Gnome 17.04? :(

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

[Desktop-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

2017-04-18 Thread Török Edwin

FWIW this crash has jut occured for me on Zesty while running the audio
tests from checkbox-ng. It is not easily reproducible though (it
happened the first time I run the tests, but didn't the second time).

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1676431] Re: Calculator key doesn't launch the calculator

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
   Calculator key doesn't launch the calculator

Status in unity-settings-daemon package in Ubuntu:
  Fix Committed
Status in unity-settings-daemon source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  Calculator key doesn't launch the calculator in Zesty

  This is because gnome-calculator 3.24 renamed its .desktop.

  Test Case
  -
  Run Unity.
  Install the update.
  If you have a keyboard with a Calculator key, press that key.

  Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab.
  Click the row that says Launch calculator. Type something else (How about 
Super+C). Once it's set, press that key combination.

  In either case, the Calculator should start.

  Regression Potential
  
  This is the same fix applied in gnome-settings-daemon.

  https://launchpadlibrarian.net/312312021/gnome-settings-
  daemon_3.24.0-0ubuntu1_3.24.0-0ubuntu2.diff.gz

  https://git.gnome.org/browse/gnome-settings-
  daemon/commit/?id=ace15f5dc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1676431/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-18 Thread Brian Murray

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

** Tags removed: regression-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/1671606

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1682913] Re: Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

2017-04-18 Thread Timo Aaltonen

GLESv1 support will be removed upstream soon, so it's not coming back

** Changed in: mesa (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games

Status in mesa package in Ubuntu:
  Won't Fix

Bug description:
  I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed 
graphical issues in some games, that render partially black. E.g.:
  - menu of Payday 2: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/
  - menu of Faeria: 
https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/

  I've traced the issue to a missing lib, libgles1, which for some
  reason has been removed from the 17.04 repos, as using Oibaf's PPA and
  manually installing the lib from it fixes the issues on these games.

  So, please build a version for Mesa 17.0.3 and put it in the repos,
  it's needed by some games.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1682913/+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 1683898] Re: Compose key section needs to be updated

2017-04-18 Thread Gunnar Hjalmarsson

Please note that the Ubuntu Desktop Guide, i.e.

https://help.ubuntu.com/stable/ubuntu-help/tips-
specialchars.html#compose

is not intended to reflect Ubuntu GNOME 17.04, but only Ubuntu 17.04
(with Unity). OTOH, neither GNOME Help seems to accurately reflect
Ubuntu GNOME 17.04 in this respect; changing the affected packages of
this bug.

As you say, the GUI option to set a compose key seems to be gone in
Ubuntu GNOME 17.04. Can't tell if it's a bad design decision or if there
is some other GUI way which is not (yet) documented. Anyway, you can set
it with a terminal command.

To make the compose key, run:

gsettings set org.gnome.desktop.input-sources xkb-options
"['compose:rctrl']"

To see which other keys are possible to use, enter the terminal command:

man xkeyboard-config

and scroll down to the section "Position of Compose key".

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New

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

Title:
Compose key section needs to be updated

Status in gnome-control-center package in Ubuntu:
New
Status in gnome-user-docs package in Ubuntu:
New

PS: In the meantime, where do I find the settings for 'compose key' in
Ubuntu-Gnome 17.04? :(

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

[Desktop-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-04-18 Thread Colan Schwartz

I removed the duplicate marker as I don't believe this to be a duplicate
of bug #1615871 (Poor performance with WebKit on yakkety with Intel
modesetting enabled).

The upstream bug is really
https://bugs.chromium.org/p/chromium/issues/detail?id=683486 , but I
can't find any way to add the remote watch.  Can someone help?

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-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:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  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-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
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+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 1683898] [NEW] Compose key section needs to be updated

You have been subscribed to a public bug:

The changes implemented with https://bugs.launchpad.net/ubuntu/+source
/ubuntu-docs/+bug/1624778 in https://help.gnome.org/users/gnome-
help/stable/tips-specialchars.html.en#compose do not reflect the current
settings dialog for Ubuntu-Gnome 17.04.

Going from "All Settings" to "Keyboard" switches to "Keyboard Shortcuts" 
immediately.
The new "Keyboard Shortcuts" dialog does not seem to contain settings for 
'compose key' (the group "Typing" only contains "Switch to {next,previous} 
input source").

PS: In the meantime, where do I find the settings for 'compose key' in
Ubuntu-Gnome 17.04? :(

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

-- 
Compose key section needs to be updated
https://bugs.launchpad.net/bugs/1683898
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs 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 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

2017-04-18 Thread Colan Schwartz

** This bug is no longer a duplicate of bug 1615871
   Poor performance with WebKit on yakkety with Intel modesetting enabled

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

Title:
  After upgrading to 16.10, Chrome has become unusable because of
  extremely slow update

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Both Chrome and Firefox actually were extremely slow regarding visual
  update (1 second after clicking a tab, lagging when entering text).
  Examining this old report: https://bugs.launchpad.net/ubuntu-
  gnome/+bug/1386721, I tried disbling bootloader graphics and VESA
  framebuffer, which suddenly made firefox behave as it used to, but
  chrome shows no improvement.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-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:Unity7
  Date: Thu Sep 29 12:19:56 2016
  DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2016-04-28 (153 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BTS26N00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago)
  dmi.bios.date: 03/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET28W (1.06 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS26N00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTS26N00
  dmi.product.version: ThinkPad X1 Carbon 3rd
  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-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
  xserver.bootTime: Thu Sep 29 12:15:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1628866/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-04-18 Thread Marco Venturini

@Andrei

Yes it does, thanks a lot.

Still there is some strange behavior that may be due to this driver.

For instance if follow those steps the audio stops playing until the system is 
rebooted
1) Open a flac or mp3 with vlc 
2) ... audio plays nicely
3) Open PulseAudio volume control 
4) wait 10-20 s
5) ... audio stops playing

To me the current behavior it's not a big deal, but if it can be useful
to debug the driver i can provide additional information.

Thanks Again,
Marco

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

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

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1683917] [NEW] General Input/Output error with Google Drive

2017-04-18 Thread Guillermo

Public bug reported:

This is a problem with Libreoffice Writer, but for some reason it didn't
allow me to set that as package (libreoffice-writer)

When adding a Google Drive service, before it can show the remote files it 
fails, I get the message "General Input/Output error with Google Drive". 
The authentication  trough though, because I get an email from Google letting 
me know there was  sign-in from a new device. 
Weirdly,the flatpack from Libre Office is being able to connect correctly. 

Using Ubuntu 17.04, Libreoffice 1:5.3.1

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

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

Title:
  General Input/Output error with Google Drive

Status in libreoffice package in Ubuntu:
  New

Bug description:
  This is a problem with Libreoffice Writer, but for some reason it
  didn't allow me to set that as package (libreoffice-writer)

  When adding a Google Drive service, before it can show the remote files it 
fails, I get the message "General Input/Output error with Google Drive". 
  The authentication  trough though, because I get an email from Google letting 
me know there was  sign-in from a new device. 
  Weirdly,the flatpack from Libre Office is being able to connect correctly. 

  Using Ubuntu 17.04, Libreoffice 1:5.3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1683917/+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 1677198] Re: OpenVPN not Working in 17.04 via "Import a saved VPN configuration"

2017-04-18 Thread Lonnie Lee Best

** Summary changed:

- OpenVPN not Working in 17.04
+ OpenVPN not Working in 17.04 via "Import a saved VPN configuration"

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

Title:
  OpenVPN not Working in 17.04 via "Import a saved VPN configuration"

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

Bug description:
  I can definitely confirm that Network Manager's OpenVPN is not working
  yet in Ubuntu 17.04.

  I set up my configuration via import:
  http://neartalk.com/ss/2017-03-29_001_633x332.png

  On all earlier versions of Ubuntu, after importing the configuration,
  I'm able to connect to the VPN. However, in 17.04, connection attempts
  always give this error immediately:

  "The VPN Connection disconnected because the VPN Service has stopped"

  Clearly the VPN Service has NOT stopped. I've confirmed that this
  error is false by taking the exact same import-file and I imported it
  into an Ubuntu 16.04 computer and then the VPN connected without
  issue. Also, with this same import-file I've had no issues in Ubuntu
  16.10.

  So I've thoroughly confirmed that there is no issue with the VPN
  service. The issue is with the client in Ubuntu 17.04.

  I cannot upgrade to 17.04 until this is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 29 05:25:14 2017
  InstallationDate: Installed on 2017-01-30 (58 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1677198/+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 670178] Re: SVG file rendered incorrectly

** Changed in: librsvg
   Status: Confirmed => Fix Released

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

Title:
  SVG file rendered incorrectly

Status in librsvg:
  Fix Released
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  The attached stars.svg is rendered incorrectly in Eye of Gnome,
  Nautilus preview, Gimp import, Evince etc. The top left star does not
  have its shadow.

  Works correctly in inkscape, Firefox, Chrome.

  Created in inkscape.

To manage notifications about this bug go to:
https://bugs.launchpad.net/librsvg/+bug/670178/+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 1676431] Re: Calculator key doesn't launch the calculator

2017-04-18 Thread Fr-coord

Hello,

Just installed unity-settings-daemon 15.04.1+17.04.20170418-0ubuntu1
from proposed, and the calculator key now invokes the calculator, again.

Thank you.

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

Title:
   Calculator key doesn't launch the calculator

Status in unity-settings-daemon package in Ubuntu:
  Fix Committed
Status in unity-settings-daemon source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  Calculator key doesn't launch the calculator in Zesty

  This is because gnome-calculator 3.24 renamed its .desktop.

  Test Case
  -
  Run Unity.
  Install the update.
  If you have a keyboard with a Calculator key, press that key.

  Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab.
  Click the row that says Launch calculator. Type something else (How about 
Super+C). Once it's set, press that key combination.

  In either case, the Calculator should start.

  Regression Potential
  
  This is the same fix applied in gnome-settings-daemon.

  https://launchpadlibrarian.net/312312021/gnome-settings-
  daemon_3.24.0-0ubuntu1_3.24.0-0ubuntu2.diff.gz

  https://git.gnome.org/browse/gnome-settings-
  daemon/commit/?id=ace15f5dc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1676431/+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 1676431] Re: Calculator key doesn't launch the calculator

2017-04-18 Thread Adam Conrad

Hello Fr-coord, or anyone else affected,

Accepted unity-settings-daemon into zesty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unity-settings-daemon/15.04.1+17.04.20170418-0ubuntu1 in a few hours,
and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: unity-settings-daemon (Ubuntu Zesty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
   Calculator key doesn't launch the calculator

Status in unity-settings-daemon package in Ubuntu:
  Fix Committed
Status in unity-settings-daemon source package in Zesty:
  Fix Committed

Bug description:
  Impact
  --
  Calculator key doesn't launch the calculator in Zesty

  This is because gnome-calculator 3.24 renamed its .desktop.

  Test Case
  -
  Run Unity.
  Install the update.
  If you have a keyboard with a Calculator key, press that key.

  Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab.
  Click the row that says Launch calculator. Type something else (How about 
Super+C). Once it's set, press that key combination.

  In either case, the Calculator should start.

  Regression Potential
  
  This is the same fix applied in gnome-settings-daemon.

  https://launchpadlibrarian.net/312312021/gnome-settings-
  daemon_3.24.0-0ubuntu1_3.24.0-0ubuntu2.diff.gz

  https://git.gnome.org/browse/gnome-settings-
  daemon/commit/?id=ace15f5dc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1676431/+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 1683887] [NEW] Tap-to-click and two finger scrolling not working after upgrading to zesty

2017-04-18 Thread Thibaut Robert

Public bug reported:

It seems that syndaemon is not working properly and never reactivates the 
tap-to-click functionality.
The problem occurs only when I use the enter key to validate my password on the 
login screen. If I validate with the mouse, the touchpad is working correctly. 
(It took me hours of investigation to figure out why it was always working with 
guest account: because I do not use the keyboard to log in)

When broken, I make it work again with synclient TouchpadOff=0. In that
case tap-to-click is not disabled when I use the keyboard. Syndaemon is
running but seems to be stuck.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue Apr 18 19:37:07 2017
DistUpgraded: 2017-04-15 12:31:17,011 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (No such file or directory) (8))
DistroCodename: zesty
DistroVariant: ubuntu
MachineType: Dell Inc. Latitude E5440
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=a1748360-88e9-482a-a704-a8608e20b6f3 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: Upgraded to zesty on 2017-04-15 (3 days ago)
dmi.bios.date: 05/01/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 08RCYC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn08RCYC:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Tap-to-click and two finger scrolling not working after upgrading to
  zesty

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  It seems that syndaemon is not working properly and never reactivates the 
tap-to-click functionality.
  The problem occurs only when I use the enter key to validate my password on 
the login screen. If I validate with the mouse, the touchpad is working 
correctly. (It took me hours of investigation to figure out why it was always 
working with guest account: because I do not use the keyboard to log in)

  When broken, I make it work again with synclient TouchpadOff=0. In
  that case tap-to-click is not disabled when I use the keyboard.
  Syndaemon is running but seems to be stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr 18 19:37:07 2017
  DistUpgraded: 2017-04-15 12:31:17,011 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (No such file or directory) (8))
  DistroCodename: zesty
  DistroVariant: ubuntu
  MachineType: Dell Inc. Latitude E5440
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=a1748360-88e9-482a-a704-a8608e20b6f3 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (3 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 08RCYC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn08RCYC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  versi

[Desktop-packages] [Bug 670178] Re: SVG file rendered incorrectly

2017-04-18 Thread madbiologist

Oops, I meant to say that the fix will be in the next release in the
2.41 series (2.41.x).

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

Title:
  SVG file rendered incorrectly

Status in librsvg:
  Confirmed
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  The attached stars.svg is rendered incorrectly in Eye of Gnome,
  Nautilus preview, Gimp import, Evince etc. The top left star does not
  have its shadow.

  Works correctly in inkscape, Firefox, Chrome.

  Created in inkscape.

To manage notifications about this bug go to:
https://bugs.launchpad.net/librsvg/+bug/670178/+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 670178] Re: SVG file rendered incorrectly

2017-04-18 Thread madbiologist

Fixed upstream.  Will be in librsvg 2.41.

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

Title:
  SVG file rendered incorrectly

Status in librsvg:
  Confirmed
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  The attached stars.svg is rendered incorrectly in Eye of Gnome,
  Nautilus preview, Gimp import, Evince etc. The top left star does not
  have its shadow.

  Works correctly in inkscape, Firefox, Chrome.

  Created in inkscape.

To manage notifications about this bug go to:
https://bugs.launchpad.net/librsvg/+bug/670178/+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 1683875] [NEW] package python-tdb 1.3.8-2 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1

2017-04-18 Thread Артём

Public bug reported:

python-samba

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-tdb 1.3.8-2
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Apr 17 19:41:06 2017
ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
InstallationDate: Installed on 2017-03-14 (35 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: tdb
Title: package python-tdb 1.3.8-2 failed to install/upgrade: подпроцесс 
установлен сценарий pre-removal возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package python-tdb 1.3.8-2 failed to install/upgrade: подпроцесс
  установлен сценарий pre-removal возвратил код ошибки 1

Status in tdb package in Ubuntu:
  New

Bug description:
  python-samba

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-tdb 1.3.8-2
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Apr 17 19:41:06 2017
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2017-03-14 (35 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: tdb
  Title: package python-tdb 1.3.8-2 failed to install/upgrade: подпроцесс 
установлен сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tdb/+bug/1683875/+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 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)

2017-04-18 Thread Lastique

> And if you had a look at the upstream bug you'd see that the patch
doesn't work.

I can see that someone reported it to not work for one-key combinations
(e.g. Ctrl). I believe, the previous patch that was removed had the same
limitation, and it was "good enough".

We need to see if it works for two-key combinations (e.g. Ctrl+Alt or
Alt+Shift).

> It needs to get upstream first anyway.

It's unlikely to be accepted into XKb for the same reasons as the
previous patch. This ticket is a request to add the patch to Ubuntu
packages because this is a real problem that affects people.

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1683383/+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 1683840] Re: /usr/bin/gnome-calendar:11:get_start_of_week:gcal_week_header_add_event:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscrib

** Changed in: gnome-calendar
   Status: Unknown => Confirmed

** Changed in: gnome-calendar
   Importance: Unknown => High

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:gcal_week_header_add_event:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscribe

Status in GNOME Calendar:
  Confirmed
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0e9b28c8f82887d3c43f2034c47eb57b25df8d3b 
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/gnome-calendar/+bug/1683840/+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 1677198] Re: OpenVPN not Working in 17.04

2017-04-18 Thread pureblood

Okay, nevermind, in my case it was enough to delete the VPN connections
and then add them again with the "Edit Connection..." option in the nm-
applet menu (somehow "VPN Connections -> Configure VPN..." is grayed out
and cannot be called). Once created again, the VPN connection work just
fine as they used to. Maybe mine is a completely different problem.

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

Title:
  OpenVPN not Working in 17.04

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

Bug description:
  I can definitely confirm that Network Manager's OpenVPN is not working
  yet in Ubuntu 17.04.

  I set up my configuration via import:
  http://neartalk.com/ss/2017-03-29_001_633x332.png

  On all earlier versions of Ubuntu, after importing the configuration,
  I'm able to connect to the VPN. However, in 17.04, connection attempts
  always give this error immediately:

  "The VPN Connection disconnected because the VPN Service has stopped"

  Clearly the VPN Service has NOT stopped. I've confirmed that this
  error is false by taking the exact same import-file and I imported it
  into an Ubuntu 16.04 computer and then the VPN connected without
  issue. Also, with this same import-file I've had no issues in Ubuntu
  16.10.

  So I've thoroughly confirmed that there is no issue with the VPN
  service. The issue is with the client in Ubuntu 17.04.

  I cannot upgrade to 17.04 until this is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 29 05:25:14 2017
  InstallationDate: Installed on 2017-01-30 (58 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1677198/+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 1683162] Re: Nautilus: Double click on folder is not working in list view with touchscreen

2017-04-18 Thread Marian Krause

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

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

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

Title:
  Nautilus: Double click on folder is not working in list view with
  touchscreen

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have a similar problem to one with touchpad.
  https://bugzilla.gnome.org/show_bug.cgi?id=748501

  I have mouse, touchpad and touchscreen.
  I can always do double click on folder to enter it with mouse and with 
touchpad.
  But I can't enter into folder with double click with touchscreen whem 
nautilus is in list view.
  I can do it in icon view.

  My laptop is Dell Latitude 7350, and when I'm detaching screen,
  touchscreen is my only pointing device. It is annoying because I like
  list view, and I don't like icons view.

  Please, help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr 16 18:21:54 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-28 (170 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   XDG_RUNTIME_DIR=
  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/1683162/+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 1683862] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: package libreoffice-common is already installed and configured

2017-04-18 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to
  install/upgrade: package libreoffice-common is already installed and
  configured

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I leave the computer alone for a few minutes and when I return there
  is a crash.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Apr 17 19:56:14 2017
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libnss3-nssdb (--configure):
package libnss3-nssdb is already installed and configured
  ErrorMessage: package libreoffice-common is already installed and configured
  InstallationDate: Installed on 2017-04-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to 
install/upgrade: package libreoffice-common is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1683862/+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 1683860] [NEW] Search domains are not considered for split-tunnelling connections

2017-04-18 Thread Lastique

Public bug reported:

For split-tunnelling VPN connections (i.e. when the "Use only for
resources on this connection" checkbox is set in the IPv4 -> Routes
menu), the IPv4 -> Search Domains field has no effect.

For example, my VPN connection has the following parameters:

[ipv4]
dns=xxx.xxx.xxx.xxx;
dns-search=mydomain.net;
ignore-auto-dns=true
method=auto
never-default=true

After connecting, `systemd-resolve --status` shows for this connection:

Link 5 (tun0)
  Current Scopes: DNS
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: allow-downgrade
DNSSEC supported: yes
 DNS Servers: xxx.xxx.xxx.xxx
  DNS Domain: ~mydomain.net

Note that there is a ~ character before the domain name, which has a
special semantics in systemd-resolved (as I understand, such entries are
not used as search names).

As a result, the search name is not used to complete simple names:

systemd-resolve foo
foo: resolve call failed: All attempts to contact name servers or networks 
failed
ping foo
ping: foo: Name or service not known
ping foo.mydomain.net
64 bytes from xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): icmp_seq=1 ttl=62 time=5.33 ms


Note that the search domains work if the VPN connection is configured as 
non-split-tunnelling connection. In this case `systemd-resolve --status` shows 
"DNS Domain: mydomain.net" (without ~) and `systemd-resolve foo` and `ping foo` 
work as expected.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Apr 18 18:46:53 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-05-01 (717 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-18T18:41:39.752743
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Search domains are not considered for split-tunnelling connections

Status in network-manager package in Ubuntu:
  New

Bug description:
  For split-tunnelling VPN connections (i.e. when the "Use only for
  resources on this connection" checkbox is set in the IPv4 -> Routes
  menu), the IPv4 -> Search Domains field has no effect.

  For example, my VPN connection has the following parameters:

  [ipv4]
  dns=xxx.xxx.xxx.xxx;
  dns-search=mydomain.net;
  ignore-auto-dns=true
  method=auto
  never-default=true

  After connecting, `systemd-resolve --status` shows for this
  connection:

  Link 5 (tun0)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes
   DNS Servers: xxx.xxx.xxx.xxx
DNS Domain: ~mydomain.net

  Note that there is a ~ character before the domain name, which has a
  special semantics in systemd-resolved (as I understand, such entries
  are not used as search names).

  As a result, the search name is not used to complete simple names:

  systemd-resolve foo
  foo: resolve call failed: All attempts to contact name servers or networks 
failed
  ping foo
  ping: foo: Name or service not known
  ping foo.mydomain.net
  64 bytes from xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx): icmp_seq=1 ttl=62 time=5.33 
ms

  
  Note that the search domains work if the VPN connection is configured as 
non-split-tunnelling connection. In this case `systemd-resolve --status` shows 
"DNS Domain: mydomain.net" (without ~) and `systemd-resolve foo` and `ping foo` 
work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Apr 18 18:46:53 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-01 (717 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release

[Desktop-packages] [Bug 1683862] [NEW] package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: package libreoffice-common is already installed and configured

2017-04-18 Thread Codne01

Public bug reported:

I leave the computer alone for a few minutes and when I return there is
a crash.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Mon Apr 17 19:56:14 2017
DuplicateSignature:
 package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial1
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package libnss3-nssdb (--configure):
  package libnss3-nssdb is already installed and configured
ErrorMessage: package libreoffice-common is already installed and configured
InstallationDate: Installed on 2017-04-17 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: libreoffice
Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to 
install/upgrade: package libreoffice-common is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to
  install/upgrade: package libreoffice-common is already installed and
  configured

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I leave the computer alone for a few minutes and when I return there
  is a crash.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Apr 17 19:56:14 2017
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libnss3-nssdb (--configure):
package libnss3-nssdb is already installed and configured
  ErrorMessage: package libreoffice-common is already installed and configured
  InstallationDate: Installed on 2017-04-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to 
install/upgrade: package libreoffice-common is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1683862/+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 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)

2017-04-18 Thread tlk

Timo Aaltonen (tjaalton) wrote 10 hours ago:#3

And if you had a look at the upstream bug you'd see that the patch doesn't 
work. It needs to get upstream first anyway.
---
1) It's just one (incomplete) report that it doesn't. I'll try the patch myself 
soon.
2) The previous patch wasn't in upstream either, yet Ubuntu maintainers did 
absolutely right to accept it IMO.
3) AFAIK Xorg people rejected this change outright (that is? after some 
prolonged explanaitons what the actual problem was - shows that they just don't 
have the issue thus don't care too much).
3) Yet people shouldn't be held hostage because the proposed behavior breaks 
the XKB spec - without (? AFAIK) a single confirmed case of it breaking any 
real world X client.

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1683383/+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 1683840] Re: /usr/bin/gnome-calendar:11:get_start_of_week:gcal_week_header_add_event:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscrib

** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => High

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

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

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

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:gcal_week_header_add_event:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscribe

Status in GNOME Calendar:
  Unknown
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0e9b28c8f82887d3c43f2034c47eb57b25df8d3b 
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/gnome-calendar/+bug/1683840/+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 1683848] [NEW] /usr/bin/gnome-calendar:11:gcal_manager_source_enabled:make_row_from_source:add_source:ffi_call_unix64:ffi_call

2017-04-18 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/c0a03b08533661e8af125723d955e200566ff060 
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-calendar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial yakkety zesty

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

Title:
  /usr/bin/gnome-
  
calendar:11:gcal_manager_source_enabled:make_row_from_source:add_source:ffi_call_unix64:ffi_call

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/c0a03b08533661e8af125723d955e200566ff060 
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-calendar/+bug/1683848/+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 1683847] [NEW] /usr/bin/gnome-calendar:11:update_selected_dates_from_button_data:gcal_year_view_component_added:cal_data_model_add_to_subscriber:cal_data_model_foreach_componen

2017-04-18 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3c79f891e7177b6fee3ff3a1bea2aecc81af8997 
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-calendar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: zesty

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

Title:
  /usr/bin/gnome-
  
calendar:11:update_selected_dates_from_button_data:gcal_year_view_component_added:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscribe

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/3c79f891e7177b6fee3ff3a1bea2aecc81af8997 
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-calendar/+bug/1683847/+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 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

2017-04-18 Thread Alexey

Unchecking "Auto power-on" in Blueman PowerManager plugin configuration
solved this issue for me.

Additionally (or alternatively) consider unchecking "Blueman Applet" in
"Startup Applications Preferences".

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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 1604851] Re: Missing arm64 xmir binaries

2017-04-18 Thread Łukasz Zemczak

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

Title:
  Missing arm64 xmir binaries

Status in Canonical System Image:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Currently we are not building xmir packages for arm64 as there was no
  consumer for such binaries. With the current xenial plans and a
  potential switch to arm64, we now need to provide arm64 binaries for
  testing our Ubuntu Touch arm64 images (which currently cannot be built
  without xmir on arm64). This is critical and crucial for our Ubuntu
  Touch switch to xenial.

  [Test Case]

  Making sure that xmir builds on arm64. Currently no other testing
  means are easily available, we need to have xmir building at all to
  build our first arm64 rootfs and then dive into testing.

  [Regression Potential]

  No risk potential on existing platforms as it only involves packaging
  changes enabling the new architecture for xmir. No source changes
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604851/+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 1683840] [NEW] /usr/bin/gnome-calendar:11:get_start_of_week:gcal_week_header_add_event:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscr

2017-04-18 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0e9b28c8f82887d3c43f2034c47eb57b25df8d3b 
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-calendar
 Importance: Unknown
 Status: Unknown

** Affects: gnome-calendar (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: zesty

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:gcal_week_header_add_event:cal_data_model_add_to_subscriber:cal_data_model_foreach_component:e_cal_data_model_subscribe

Status in GNOME Calendar:
  Unknown
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/0e9b28c8f82887d3c43f2034c47eb57b25df8d3b 
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/gnome-calendar/+bug/1683840/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

2017-04-18 Thread Andrei Aldea

You're welcome guys, glad to be of help.

@Venkat How exactly did you get microsd to work? Is this on the Asus
E200HA? I don't believe mine works as of now.

@Marco  Indeed 17.04 requires you to remove the default kernel after the
install. Does the line you added fix your sound issue?

Cheers,
Andrei

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

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

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

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

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1632772] Re: GNOME on Wayland does not start from LightDM

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

** Changed in: ubuntu-gnome
   Status: New => Confirmed

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

Title:
  GNOME on Wayland does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  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
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1632772] Re: GNOME on Wayland does not start from LightDM

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

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

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

Title:
  GNOME on Wayland does not start from LightDM

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  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
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

2017-04-18 Thread James Gross

Ah, so this code:

if dpkg --compare-versions "$2" le-nl "1.2.2-0ubuntu4"; then
mkdir -p /etc/NetworkManager/conf.d || true
# for old versions, override the global config with a null 
config
touch 
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf

Should have ge-nl rather than le-nl?  Seems like it's backwards and that
all new installs need the override, rather than old installs.

Also, why the decision to only do a netplan on install?

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:
   
  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1680496] Re: black screen when using 'GNOME Wayland' with lightdm on zesty

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

** This bug has been marked a duplicate of bug 1632772
   GNOME on Wayland does not start from LightDM

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

Title:
  black screen when using 'GNOME Wayland' with lightdm on zesty

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  In an up to date Ubuntu 17.04 amd64 vm, if I:

  1. install ubuntu-gnome-desktop
  2. select lightdm as the default
  3. sudo service lightdm stop ; sudo service lightdm start
  4. login choosing 'GNOME Wayland'

  the screen goes black with a flashing cursor in the upper left. If I
  'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop lightdm
  and start gdm3, then I can login to a wayland gnome3 desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1680496/+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 1683836] [NEW] WIFI stoped working when updating 16.10 -> 17.04

2017-04-18 Thread jkn

Public bug reported:

Network manager detects 'Bus 001 Device 004: ID 148f:5370 Ralink
Technology, Corp. RT5370 Wireless Adapter'. It detects WIFI network, but
fails to connect. I booted with older kernel vmlinuz-4.8.0-46-generic:
same result.  I installed ubuntu 16.10 to same computer and WIFI does
work.  Password is OK.

Authentication seems to fail in Ubuntu 17.04:
Apr 18 17:13:01 k10 NetworkManager[727]: 
[1492524781.2784] policy: auto-activating connection 'ZyXELbb3a'
[1492524781.2798] device (wlxc83a35cde1eb): Activation: starting connection 
'ZyXELbb3a' (5362ba4d-c40e-40a3-8e17-4e3deaab48ae)
[1492524781.2801] device (wlxc83a35cde1eb): state change: disconnected -> 
prepare (reason 'none') [30 40 0]
[1492524781.6699] device (wlxc83a35cde1eb): set-hw-addr: set-cloned MAC address 
to C8:3A:35:CD:E1:EB (permanent)
[1492524781.9391] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
[1492524781.9394] device (wlxc83a35cde1eb): Activation: (wifi) access point 
'ZyXELbb3a' has security, but secrets are required.
[1492524781.9395] device (wlxc83a35cde1eb): state change: config -> need-auth 
(reason 'none') [50 60 0]
[1492524781.9748] device (wlxc83a35cde1eb): state change: need-auth -> prepare 
(reason 'none') [60 40 0]
[1492524781.9782] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
[1492524781.9792] device (wlxc83a35cde1eb): Activation: (wifi) connection 
'ZyXELbb3a' has security, and secrets exist.  No new secrets needed.
[1492524781.9796] Config: added 'ssid' value 'ZyXELbb3a'
[1492524781.9800] Config: added 'scan_ssid' value '1'
[1492524781.9803] Config: added 'key_mgmt' value 'WPA-PSK'
[1492524781.9806] Config: added 'auth_alg' value 'OPEN'
[1492524781.9808] Config: added 'psk' value ''
[1492524781.9821] sup-iface[0x55d34390d2d0,wlxc83a35cde1eb]: config: set 
interface ap_scan to 1
[1492524782.0010] device (wlxc83a35cde1eb): supplicant interface state: 
inactive -> scanning
[1492524783.3941] device (wlxc83a35cde1eb): supplicant interface state: 
scanning -> authenticating
[1492524783.5787] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> disconnected
[1492524793.5868] device (wlxc83a35cde1eb): supplicant interface state: 
disconnected -> scanning
[1492524794.9891] device (wlxc83a35cde1eb): supplicant interface state: 
scanning -> authenticating
[1492524795.1145] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> disconnected


Ubuntu 16.10 is same to authentication:
Apr 18 13:46:10 k15 NetworkManager[714]: 
[1492512370.3874] policy: auto-activating connection 'ZyXELbb3a'
[1492512370.3884] device (wlxc83a35cde1eb): Activation: starting connection 
'ZyXELbb3a' (fd199068-2375-4268-bb74-d60484d1fadb)
[1492512370.3886] device (wlxc83a35cde1eb): state change: disconnected -> 
prepare (reason 'none') [30 40 0]
[1492512370.3887] manager: NetworkManager state is now CONNECTING
[1492512370.3895] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
[1492512370.3897] device (wlxc83a35cde1eb): Activation: (wifi) access point 
'ZyXELbb3a' has security, but secrets are required.
[1492512370.3898] device (wlxc83a35cde1eb): state change: config -> need-auth 
(reason 'none') [50 60 0]
[1492512370.3936] device (wlxc83a35cde1eb): state change: need-auth -> prepare 
(reason 'none') [60 40 0]
[1492512370.3940] device (wlxc83a35cde1eb): state change: prepare -> config 
(reason 'none') [40 50 0]
[1492512370.3943] device (wlxc83a35cde1eb): Activation: (wifi) connection 
'ZyXELbb3a' has security, and secrets exist.  No new secrets needed.
[1492512370.3943] Config: added 'ssid' value 'ZyXELbb3a'
[1492512370.3944] Config: added 'scan_ssid' value '1'
[1492512370.3944] Config: added 'key_mgmt' value 'WPA-PSK'
[1492512370.3944] Config: added 'auth_alg' value 'OPEN'
[1492512370.3944] Config: added 'psk' value ''
[1492512370.3949] sup-iface[0x55da7c3f2210,wlxc83a35cde1eb]: config: set 
interface ap_scan to 1
[1492512371.8005] device (wlxc83a35cde1eb): supplicant interface state: 
inactive -> authenticating
[1492512371.8071] device (wlxc83a35cde1eb): supplicant interface state: 
authenticating -> associating
[1492512371.8216] device (wlxc83a35cde1eb): supplicant interface state: 
associating -> 4-way handshake
[1492512371.8482] device (wlxc83a35cde1eb): supplicant interface state: 4-way 
handshake -> completed
[1492512371.8482] device (wlxc83a35cde1eb): Activation: (wifi) Stage 2 of 5 
(Device Configure) successful.  Connected to wireless network 'ZyXELbb3a'.
[1492512371.8483] device (wlxc83a35cde1eb): state change: config -> ip-config 
(reason 'none') [50 70 0]
[1492512371.8623] dhcp4 (wlxc83a35cde1eb): activation: beginning transaction 
(timeout in 45 seconds)
Apr 18 13:46:11 k15 NetworkManager[714]:   [1492512371.9292] dhcp4 
(wlxc83a35cde1eb): dhclient started with pid 1027

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu3
ProcVersionSignature: Ubun

[Desktop-packages] [Bug 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

2017-04-18 Thread spike speigel

@aapo-rantalainen

This might be the solution.  Worked for me:

https://github.com/blueman-project/blueman/issues/682

** Bug watch added: github.com/blueman-project/blueman/issues #682
   https://github.com/blueman-project/blueman/issues/682

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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 1296114] Re: [desktop] Bluetooth is always enabled after reboot even if it was disabled

2017-04-18 Thread spike speigel

@cibersheep

This might be the solution.  Worked for me:

https://github.com/blueman-project/blueman/issues/682

** Bug watch added: github.com/blueman-project/blueman/issues #682
   https://github.com/blueman-project/blueman/issues/682

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

Title:
  [desktop] Bluetooth is always enabled after reboot even if it was
  disabled

Status in Bluetooth Menu:
  Invalid
Status in indicator-bluetooth package in Ubuntu:
  Invalid
Status in rfkill package in Ubuntu:
  Incomplete
Status in urfkill package in Ubuntu:
  Triaged

Bug description:
  If bluetooth was disabled using the switcher in the bluetooth
  indicator, after reboot it becomes enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 22 22:34:52 2014
  InstallationDate: Installed on 2014-01-27 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: 
Connecting to session manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+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 1683162] Re: Nautilus: Double click on folder is not working in list view with touchscreen

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  Nautilus: Double click on folder is not working in list view with
  touchscreen

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have a similar problem to one with touchpad.
  https://bugzilla.gnome.org/show_bug.cgi?id=748501

  I have mouse, touchpad and touchscreen.
  I can always do double click on folder to enter it with mouse and with 
touchpad.
  But I can't enter into folder with double click with touchscreen whem 
nautilus is in list view.
  I can do it in icon view.

  My laptop is Dell Latitude 7350, and when I'm detaching screen,
  touchscreen is my only pointing device. It is annoying because I like
  list view, and I don't like icons view.

  Please, help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr 16 18:21:54 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-28 (170 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   XDG_RUNTIME_DIR=
  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/1683162/+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 1021375] Re: Nautilus says the USB stick is read only when it is not

2017-04-18 Thread LukeL99

Had this problem happen to me on 16.04.2. killall nautilus worked for
me, and doesn't come back across multiple unplugs and restarts of
nautilus.

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

Title:
  Nautilus says the USB stick is read only when it is not

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is not.

  I tested it with two different USB sticks in two different computers
  running Ubuntu 12.04 and the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1021375/+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 1680496] Re: black screen when using 'GNOME Wayland' with lightdm on zesty

duplicate bug #1632772?

@Jeremy, that gdm commit suggests it's not a technical reason but that
they assume that if wayland is not using in gdm that's because it's not
working on the configuration so there is no point listing a session
which is not going to work

https://git.gnome.org/browse/gdm/commit/?id=246d9a23

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

Title:
  black screen when using 'GNOME Wayland' with lightdm on zesty

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  In an up to date Ubuntu 17.04 amd64 vm, if I:

  1. install ubuntu-gnome-desktop
  2. select lightdm as the default
  3. sudo service lightdm stop ; sudo service lightdm start
  4. login choosing 'GNOME Wayland'

  the screen goes black with a flashing cursor in the upper left. If I
  'dpkg-reconfigure -plow lightdm' and choose 'gdm3', then stop lightdm
  and start gdm3, then I can login to a wayland gnome3 desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1680496/+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 1683160] Re: virus foud

2017-04-18 Thread Adolfo Jayme

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

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

Title:
  virus foud

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  bug found

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   [[0m[0;31m* [0m] (1 of 11) A start job is running for 
dev-disk-by\x2dpath-pci\x2d:00:1d.0\x2dusb\x2d0:1.3:1.0\x2dscsi\x2d0:0:0:0.device
 (29s / 1min 30s)
[K[[0;32m  OK  [0m] Started Modem Manager.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 16 21:47:28 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 2nd Generation Core Processor 
Family Integrated Graphics Controller [1179:fb20]
  InstallationDate: Installed on 2016-07-07 (282 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite C850
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=0b46d6d7-62a9-4dc4-b79e-d3885d2434df ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.30
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.30:bd09/21/2012:svnTOSHIBA:pnSatelliteC850:pvrPSC74G-01S001:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C850
  dmi.product.version: PSC74G-01S001
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 16 20:47:57 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 826 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1683160/+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 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi adapters from working (mac address randomization)

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some USB
  WiFi adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1683285] Re: New version freeglut 3.0.0

2017-04-18 Thread Adolfo Jayme

** Changed in: freeglut (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  New version freeglut 3.0.0

Status in freeglut package in Ubuntu:
  Incomplete
Status in freeglut package in Debian:
  New

Bug description:
  Hello!

  New version of freeglut has been released two years ago (!). I
  prepared a patch to update the package. Could you review it and upload
  the new version?

  I'm attaching patch to debian folder. You have to download and unpack
  the new upstream version via uscan or from official web-site. I did it
  to reduce file size.

  I already sent my patch to Debian, but there is no reaction on it.
  Debian Maintainer told that there were some problems with
  dependencies[1], but unfortunately he didn't indicate what
  dependencies were.

  But in spite of that, I hope it's possible to upload the new package
  to Ubuntu 17.10.

  [1]: https://bugs.debian.org/859687

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeglut/+bug/1683285/+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 1683268] Re: Evince/Okular displays incorrect characters (Regression?)

Thank you for your bug report, could you maybe attach an example pdf to
the bug?

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

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

Title:
  Evince/Okular displays incorrect characters (Regression?)

Status in poppler package in Ubuntu:
  New

Bug description:
  See https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/518236

  There seems to be a regression bug exactly as described in the linked
  bug report, in the currently fully patched ubuntu 16.04.

  I found this problem recently with a pdf prepared by origin on
  windows. The file contains mu characters. I came accross this bug
  report, and the datasheet posted by the OP, on page 6, lower right,
  shows missing characters in Okular 0.24.2 with PDF Backend 0.6.5. (I
  am attaching two images, one by okular and one by Firefox). Evince
  also renders wrongly.

  libpoppler is 0.41.0-0ubuntu1.1.

  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1683268/+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 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

2017-04-18 Thread spike speigel

** Tags added: xenial

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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 1677198] Re: OpenVPN not Working in 17.04

2017-04-18 Thread pureblood

I confirm the issue. I cannot login through VPN anymore since I updated
from 16.10 to 17.04. I will also add to that it is impossible now to
configure the VPN connections. The "Configure VPN..." option in the menu
is grayed out and cannot be selected anymore from the NetworkManager.

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

Title:
  OpenVPN not Working in 17.04

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

Bug description:
  I can definitely confirm that Network Manager's OpenVPN is not working
  yet in Ubuntu 17.04.

  I set up my configuration via import:
  http://neartalk.com/ss/2017-03-29_001_633x332.png

  On all earlier versions of Ubuntu, after importing the configuration,
  I'm able to connect to the VPN. However, in 17.04, connection attempts
  always give this error immediately:

  "The VPN Connection disconnected because the VPN Service has stopped"

  Clearly the VPN Service has NOT stopped. I've confirmed that this
  error is false by taking the exact same import-file and I imported it
  into an Ubuntu 16.04 computer and then the VPN connected without
  issue. Also, with this same import-file I've had no issues in Ubuntu
  16.10.

  So I've thoroughly confirmed that there is no issue with the VPN
  service. The issue is with the client in Ubuntu 17.04.

  I cannot upgrade to 17.04 until this is fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Mar 29 05:25:14 2017
  InstallationDate: Installed on 2017-01-30 (58 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: Upgraded to zesty on 2017-03-27 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1677198/+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 1640741] Re: ubuntu 17.04 gnome-software install button not working

Stanislav, that is a different bug. See
https://launchpad.net/bugs/1672424

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

Title:
  ubuntu 17.04 gnome-software install button not working

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  on ubuntu 17.04 gnome-software install button does nothing.
  try with different applications: UFRaw, Shutter, Entangle ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.2+git20161108.0.a58dfc7-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
  CurrentDesktop: Unity
  Date: Thu Nov 10 11:08:48 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-11-06 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1640741/+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 1676431] Re: Calculator key doesn't launch the calculator

** Description changed:

+ Impact
+ --
Calculator key doesn't launch the calculator in Zesty
+
+ This is because gnome-calculator 3.24 renamed its .desktop.
+
+ Test Case
+ -
+ Run Unity.
+ Install the update.
+ If you have a keyboard with a Calculator key, press that key.
+
+ Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab.
+ Click the row that says Launch calculator. Type something else (How about
Super+C). Once it's set, press that key combination.
+
+ In either case, the Calculator should start.
+
+ Regression Potential
+
+ This is the same fix applied in gnome-settings-daemon.

** Changed in: unity-settings-daemon (Ubuntu)
Status: Triaged => In Progress

** Changed in: unity-settings-daemon (Ubuntu)
Assignee: Jeremy Bicha (jbicha) => (unassigned)

** Description changed:

Impact
--
Calculator key doesn't launch the calculator in Zesty

This is because gnome-calculator 3.24 renamed its .desktop.

Test Case
-
Run Unity.
Install the update.
If you have a keyboard with a Calculator key, press that key.

Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab.
Click the row that says Launch calculator. Type something else (How about
Super+C). Once it's set, press that key combination.

In either case, the Calculator should start.

Regression Potential

This is the same fix applied in gnome-settings-daemon.
+
+ https://launchpadlibrarian.net/312312021/gnome-settings-
+ daemon_3.24.0-0ubuntu1_3.24.0-0ubuntu2.diff.gz
+
+ https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=ace15f5dc

** Tags added: zesty

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

Title:
Calculator key doesn't launch the calculator

Status in unity-settings-daemon package in Ubuntu:
In Progress

Bug description:
Impact
--
Calculator key doesn't launch the calculator in Zesty

This is because gnome-calculator 3.24 renamed its .desktop.

Test Case
-
Run Unity.
Install the update.
If you have a keyboard with a Calculator key, press that key.

Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab.
Click the row that says Launch calculator. Type something else (How about
Super+C). Once it's set, press that key combination.

In either case, the Calculator should start.

Regression Potential

This is the same fix applied in gnome-settings-daemon.

https://launchpadlibrarian.net/312312021/gnome-settings-
daemon_3.24.0-0ubuntu1_3.24.0-0ubuntu2.diff.gz

https://git.gnome.org/browse/gnome-settings-
daemon/commit/?id=ace15f5dc

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

2017-04-18 Thread Mathieu Trudel-Lapierre

That's indeed what seems to be the case, and this has already been
debugged. The issue is that the code that does the override on upgrade
looks for the wrong version of NetworkManager, since it has been updated
in Xenial.

This change has been in the process of being tested; I'll upload to the
release proper as soon as I know that it really does work.

The netplan code itself should be created only on new installs; for an
upgrade, it's not there, and thus we need to explicitly write an
override for NM via NM postinst.

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:
   
  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi adapters from working (mac address randomization)

2017-04-18 Thread Simos Xenitellis 

Jesse, I do not have 17.04 so I cannot test these myself. You guys could
help:

At https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
networkmanager-1-4-0/ it mentions that:

Update-2017-01-25: with 1.6 release and newer, the default value changed
from “permanent” to “preserve” [commit],[bug].

The "preserve" default value means that NM will not attempt to change the MAC 
address upon activation. 
I just checked the source of "network-manager" on 17.04 (using LXD with 17.04 
container) and it goes not have this update.

Could you please check in NetworkManager to see what is the default value for
“ethernet.cloned-mac-address” and “wifi.cloned-mac-address”, on a Ubuntu 17.04 
installation?

I think that "nmcli device show" might show it. If not, try somehow to
figure out the default.

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

Title:
  Ubuntu 17.04: New privacy feature in NetworkManager stops some USB
  WiFi adapters from working (mac address randomization)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1030022] Re: Port from legacy Xlib to modern XCB

2017-04-18 Thread Lenin

** Changed in: amiwm (Ubuntu)
 Assignee: (unassigned) => Lenin (gagarin)

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

Title:
  Port from legacy Xlib to modern XCB

Status in Compiz:
  Triaged
Status in 9wm package in Ubuntu:
  New
Status in aewm package in Ubuntu:
  New
Status in aewm++ package in Ubuntu:
  New
Status in afterstep package in Ubuntu:
  New
Status in amiwm package in Ubuntu:
  New
Status in blackbox package in Ubuntu:
  New
Status in cairo package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Triaged
Status in ctwm package in Ubuntu:
  New
Status in dwm package in Ubuntu:
  Opinion
Status in enlightenment package in Ubuntu:
  New
Status in fvwm package in Ubuntu:
  New
Status in fvwm1 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in icewm package in Ubuntu:
  New
Status in jwm package in Ubuntu:
  Invalid
Status in larswm package in Ubuntu:
  New
Status in lwm package in Ubuntu:
  New
Status in matchbox-window-manager package in Ubuntu:
  New
Status in metacity package in Ubuntu:
  Invalid
Status in miwm package in Ubuntu:
  New
Status in muffin package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in pekwm package in Ubuntu:
  New
Status in ratpoison package in Ubuntu:
  New
Status in sapphire package in Ubuntu:
  New
Status in sawfish package in Ubuntu:
  New
Status in spectrwm package in Ubuntu:
  Fix Released
Status in tinywm package in Ubuntu:
  New
Status in tritium package in Ubuntu:
  New
Status in twm package in Ubuntu:
  New
Status in vtwm package in Ubuntu:
  New
Status in w9wm package in Ubuntu:
  New
Status in windowlab package in Ubuntu:
  New
Status in wm2 package in Ubuntu:
  New
Status in wmaker package in Ubuntu:
  Opinion
Status in xmonad package in Ubuntu:
  New

Bug description:
  Port/rewrite the window manager to use the modern XCB (X C Binding)
  library instead of the old legacy Xlib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1030022/+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 1440570] Re: VNC'ing into gnome-session-flashback (Metacity) in non-shared desktop mode causes Super+KEY pressed behavior

2017-04-18 Thread Alberts Muktupāvels

** Changed in: metacity (Ubuntu Utopic)
   Status: Confirmed => Invalid

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

Title:
  VNC'ing into gnome-session-flashback (Metacity) in non-shared desktop
  mode causes Super+KEY pressed behavior

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Trusty:
  Fix Released
Status in metacity source package in Utopic:
  Invalid
Status in metacity source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  When VNC'ing into gnome-session-flashback (Metacity) with either 
tightvncserver or vnc4server configured for non-shared desktop mode, when one 
opens a terminal for example, and types the "s" key, it acts as if the Super 
key is also pressed along with it. Hence, this appears to be a gnome-* issue.

  [Test Case]
  Vivid new install setup for tightvncserver:
  sudo apt-get update && sudo apt-get -y dist-upgrade && sudo apt-get -y 
install xrdp gnome-session-flashback && sudo apt-get -y remove vino && nano 
.xsession
  #START
  export XDG_CURRENT_DESKTOP='GNOME-Flashback:Unity'
  exec gnome-session --session=gnome-flashback-metacity 
--disable-acceleration-check
  #END

  sudo nano /etc/xrdp/xrdp.ini

  change to:
  #START
  [globals]
  bitmap_cache=yes
  bitmap_compression=yes
  port=3389
  crypt_level=high
  channel_code=1
  max_bpp=24
  #black=00
  #grey=d6d3ce
  #dark_grey=808080
  #blue=08246b
  #dark_blue=08246b
  #white=ff
  #red=ff
  #green=00ff00
  #background=626c72

  [xrdp1]
  name=sesman-Xvnc
  lib=libvnc.so
  username=ask
  password=ask
  ip=127.0.0.1
  port=-1
  #END

  Log out, log back in, and RDP in via either Windows Remote Desktop
  Connection or Remmina.

  
  [Regression Potential]
  This patch adds an additional check for modmask. It is already in upstream 
metacity.

  
  WORKAROUND: Applications > System Tools > System Settings > Keyboard > 
Shortcuts > Disable all shortcuts containing the Super key.

  WORKAROUND: Don't use the .xsession file with tightvncserver, but this
  then creates a shared desktop experience, instead of ones own, not
  seen by the user at the local console.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: vnc4server 4.1.1+xorg4.3.0-37.3ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Apr  5 13:10:40 2015
  InstallationDate: Installed on 2014-12-14 (112 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141213)
  SourcePackage: vnc4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1440570/+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 885989] Re: white screen on second monitor when using two xsessions

2017-04-18 Thread Alberts Muktupāvels

Setting to invalid (won't fix):
- precise will be end of life in 10 days.
- trusty already have gtk+ 3.10 were multi screen support has been removed.

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Invalid

** Changed in: nautilus (Ubuntu Precise)
   Status: Triaged => Invalid

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

Title:
  white screen on second monitor when using two xsessions

Status in Nautilus:
  Won't Fix
Status in nautilus package in Ubuntu:
  Invalid
Status in nautilus source package in Precise:
  Invalid

Bug description:
  If enable dual head mode (two X screens), the second monitor went
  white after login with unity or unity-2d. After tracking the gnome-
  session, it is caused by running "nautilus -n" for this configuration.
  And if kill the nautilus process, the desktop showed up normally on
  second screen.

  lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  apt-cache policy nautilus
  nautilus:
Installed: 1:3.2.1-0ubuntu2
Candidate: 1:3.2.1-0ubuntu2
Version table:
   *** 1:3.2.1-0ubuntu2 0
  500 http://cn.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.2.0-0ubuntu5 0
  500 http://cn.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/885989/+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 976124] Re: lightdm multiseat: no login possible

2017-04-18 Thread Alberts Muktupāvels

** Changed in: lightdm (Ubuntu Precise)
   Status: Confirmed => Invalid

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

Title:
  lightdm multiseat: no login possible

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Invalid

Bug description:
  I am testing a multiseat setup with precise:

  One XServer is running on intel graphics card, a second one is running
  on a DisplayLink (usb video) device.

  The two greeters are displayed, but without password fields shown so
  it is not possible to login. If auto-login is enabled in lightdm.conf
  multiseat works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sat Apr  7 20:35:52 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/976124/+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 1640741] Re: ubuntu 17.04 gnome-software install button not working

2017-04-18 Thread Stanislav Khotinok

Hi,
Hi,
Hi, is it really fixed?

I've installed clean Ubuntu GNOME 17.04 (Zesty Zapus) and have the same
issue. When you download any .deb file like Chrome, Virtualbox and etc
and double click on it - it opens Software Center. But clicking on
Install button does nothing. But if you select any app from Software
Center, for example Caffeine - Install button works just fine. So the
issue is only with downloaded .deb files. If you try to use Gdebi for
the same files - everything works fine.

I've tried reinstalling it by doing:

$ sudo apt-get --purge remove gnome-software
$ sudo apt-get install gnome-software

But the problem remains.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty

$ dpkg -s gnome-software
Package: gnome-software
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 1371
Maintainer: Ubuntu Developers 
Architecture: amd64
Version: 3.22.7-0ubuntu3
Replaces: gnome-packagekit-session (<< 3.16.0-2~)
Depends: appstream, aptdaemon, gnome-software-common (= 3.22.7-0ubuntu3), 
gnome-software-plugin-snap, gsettings-desktop-schemas (>= 3.18), packagekit (>= 
1.1.4), software-properties-gtk, dconf-gsettings-backend | gsettings-backend, 
libappstream-glib8 (>= 0.6.9), libapt-pkg5.0 (>= 1.2), libatk1.0-0 (>= 1.12.4), 
libc6 (>= 2.14), libcairo2 (>= 1.2.4), libfwupd1 (>= 0.7.3), libgcc1 (>= 
1:3.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.46), 
libgnome-desktop-3-12 (>= 3.18), libgtk-3-0 (>= 3.22.4), libgtkspell3-3-0, 
libgudev-1.0-0 (>= 146), libjson-glib-1.0-0 (>= 0.13.2), liboauth0 (>= 0.9.1), 
libpango-1.0-0 (>= 1.14.0), libpolkit-gobject-1-0 (>= 0.99), libsecret-1-0 (>= 
0.7), libsoup2.4-1 (>= 2.52), libsqlite3-0 (>= 3.5.9), libstdc++6 (>= 5.2)
Recommends: libgtk2-perl
Suggests: fwupd, gnome-software-plugin-flatpak, gnome-software-plugin-limba
Breaks: gnome-packagekit-session (<< 3.16.0-2~)
Conffiles:
 /etc/apt/apt.conf.d/60gnome-software 5674c7f56873f7747749e9691c6f322e
 /etc/xdg/autostart/gnome-software-service.desktop 
a96b13d13b4342bb9b0a23ae40d936ca
Description: Software Center for GNOME
 Software lets you install and update applications and system extensions.
 .
 Software uses a plugin architecture to separate the frontend from the
 technologies that are used underneath. Currently, a PackageKit plugin provides
 data from a number of traditional packaging systems, such as rpm or apt. An
 appdata plugin provides additional metadata from locally installed data in the
 appdata format.
Homepage: https://wiki.gnome.org/Apps/Software
Original-Maintainer: Debian GNOME Maintainers 


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

Title:
  ubuntu 17.04 gnome-software install button not working

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  on ubuntu 17.04 gnome-software install button does nothing.
  try with different applications: UFRaw, Shutter, Entangle ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.2+git20161108.0.a58dfc7-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
  CurrentDesktop: Unity
  Date: Thu Nov 10 11:08:48 2016
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-11-06 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161106)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1640741/+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 1682701] Re: Fails To Connect To WPA2 WiFi

2017-04-18 Thread Skaarj Warrior

I have the same problem with Debian 9 [XFCE]. Wired connections are OK,
but I can't connect to Wi-Fi networks. WICD (network-manager
alternative) doesn't have the same problem!

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

Title:
  Fails To Connect To WPA2 WiFi

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

Bug description:
  The task-bar applet showing network connection will not connect to the
  DSL modem wireless, as it used to do in prior releases.

  I tried three different wireless dongles, all with the same result.

  I'm running the live 17.04 system, and I tried it on three different
  machines as well.

  Other than the machine I submitted the bug report on (which also has
  ethernet connectivity), all of my other machines depend on wireless,
  so 17.04 is not usable.

  I tried both Lubuntu 17.04 and Xubuntu 17.04, and both live-systems
  have the same problem.

  1) lubuntu@lubuntu:~$ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  2) lubuntu@lubuntu:~$ sudo apt-cache policy network-manager-applet
  N: Unable to locate package network-manager-applet

  3) I expected the wireless to connect, as it has always done in prior
  releases.

  4) It tried connecting for a period of time, then gave up.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager-gnome 1.4.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CasperVersion: 1.380
  CurrentDesktop: LXDE
  Date: Fri Apr 14 02:52:32 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev enp3s0 proto static metric 100 
   192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.2 metric 100
  LiveMediaBuild: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   Wired connection 1  d5e527dc-f755-3a8e-978a-a4233102a518  802-3-ethernet   
1492138159  Fri 14 Apr 2017 02:49:19 AM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes enp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/0 
   TEMAIRANET  19205db9-bf9d-4768-9851-5e7a2941266a  802-11-wireless  0 
  neveryes  0 
no/org/freedesktop/NetworkManager/Settings/1  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH   
   CONNECTION  CON-UUID  CON-PATH   

   enp3s0   ethernet  connected 
/org/freedesktop/NetworkManager/Devices/1  Wired connection 1  
d5e527dc-f755-3a8e-978a-a4233102a518  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlx0025223f6edb  wifi  disconnected  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1682701/+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 1676431] Re: Calculator key doesn't launch the calculator

** Changed in: unity-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
   Calculator key doesn't launch the calculator

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

Bug description:
  Calculator key doesn't launch the calculator in Zesty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1676431/+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 1676431] Re: Calculator key doesn't launch the calculator