date:20170223

** Summary changed:

- [gallium] EGL clients that saturate the GPU cause the Mir server to slow, 
freeze and stutter, showing very few frames
+ [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) 
that saturate the GPU cause the Mir server to slow, freeze and stutter, 
displaying very few frames

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

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

Title:
  [gallium] EGL clients using a gallium driver (radeon, nouveau,
  freedreno) that saturate the GPU cause the Mir server to slow, freeze
  and stutter, displaying very few frames

Status in Mir:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  GPU-heavy clients on Mesa gallium drivers (e.g. radeon, nouveau and
  freedreno) cause the Mir server to slow, sometimes to a halt. This is
  seen as a frozen screen, unable to move surfaces, or unable to switch
  VTs (for a while).

  For example:
     mir_demo_client_egltriangle -n
     mir_demo_client_eglplasma -n

  The -n flag (swapinterval = 0) seems to cause the client to overload
  the mir server to the point where it cannot render physical frames
  very often.

  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on AMD CEDAR
  ...
  $ es2_info
  EGL_VERSION = 1.4 (Gallium)
  EGL_VENDOR = Mesa Project
  EGL_EXTENSIONS = EGL_WL_bind_wayland_display EGL_KHR_image_base 
EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_reusable_sync EGL_KHR_fence_sync 
EGL_KHR_surfaceless_context EGL_NOK_swap_region EGL_NV_post_sub_buffer
  EGL_CLIENT_APIS = OpenGL OpenGL_ES OpenGL_ES2 OpenVG
  GL_VERSION: OpenGL ES 3.0 Mesa 9.2.0-devel
  GL_RENDERER: Gallium 0.4 on NVA8
  ...

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

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

[Desktop-packages] [Bug 1628153] Re: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most restarts

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

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

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

Title:
  [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all on most
  restarts

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On the vast majority of restarts of Ubuntu 16.04 I get no internal
  sound at all.

  There are no reported issues in system settings on the only sound card
  I have. The volume is not muted.

  On an estimated 1 in 10 restart, the sound works, and both the test
  sounds get played and other applications work fine.

  There is no reported errors or messages on the restarts when the sound
  has failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tony  16160 F...m pulseaudio
   /dev/snd/controlC1:  tony  16160 F pulseaudio
   /dev/snd/controlC0:  tony  16160 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Sep 27 15:56:02 2016
  InstallationDate: Installed on 2015-10-29 (334 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  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/pcmC1D0p:   tony  16160 F...m pulseaudio
   /dev/snd/controlC1:  tony  16160 F pulseaudio
   /dev/snd/controlC0:  tony  16160 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [W65_67SF, VIA VT1802, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2016-08-13 (45 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-23 Thread Simplehuman

#31, same problem also. As workaround for me - I just downgraded 
network-manager package to 1.4.4-1ubuntu1 . Downloaded it from here - 
https://launchpad.net/ubuntu/+source/network-manager/1.4.4-1ubuntu1/ and then 
sudo dpkg -i network-manager_1.4.4-1ubuntu1_amd64.deb . And blocked this 
version in Synaptic. Probably not the best solution, but the best that I could 
find for now and it works.
Bug is really critical for dayly use.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Desktop-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

2017-02-23 Thread ChristianEhrhardt

So while I understand to unify code paths by relying on accoutnsservice
lightdm needs to get back the feature of "hidden-shells=" IMHO.

So in some sense this is a regression in lightdm due to the change to
use accountsservice.

The solution clearly extceeds my Dbus-foo, but shouldn't lightdm be able
to get back "hidden-shells" by implementing a filter on the "Shell"
property of each user that accountsservice provides?

Maybe this was discussed in the lightdm/accountsservice communities -
I'm not part of them and search engines didn't find it for me - but
given how often the question how to hid users came up I'd think some
discussion on the shell filtering might already exist.

Waiting for the expertise of the triagers of lightdm/accountsservice on
that bug now.

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  New
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-23 Thread Martin Pitt

Yes, there, see "man resolved.conf". But I'd recommend a separate file
to avoid changing the package-provided conffile:

sudo mkdir -p /etc/systemd/resolved.conf.d
printf "[Resolve]\nDNSSEC=no\n" | sudo tee 
/etc/systemd/resolved.conf.d/no-dnssec.conf

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

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

2017-02-23 Thread monte

Please try network-manager-1.2.6 from xenial-proposed, if you have
16.04. For me it seems to fix this bug. But when you will test don't
forget to turn off all self-made scripts to see if it really does the
job.

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete

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

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

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

[Desktop-packages] [Bug 75850] Re: Pidgin should support OS keyrings

2017-02-23 Thread Alex Muntada

pidgin-gnome-keyring is available since xenial, shouldn't this bug
report be fix released already?

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

Title:
  Pidgin should support OS keyrings

Status in Gaim:
  Won't Fix
Status in Pidgin:
  New
Status in gaim package in Ubuntu:
  Invalid
Status in pidgin package in Ubuntu:
  Fix Committed

Bug description:
  Pidgin should support GNOME Keyring, KWallet, etc.

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

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

[Desktop-packages] [Bug 1667276] [NEW] Update HPLIP Xenial package to 3.6.11

2017-02-23 Thread Renne

Public bug reported:

We are using HP Pagewide 377dw printers which are not supported in the
current 3.16.3 package for Ubuntu 16.04 LTS. Please update HPLIP to
3.6.11 to support that printers in business environments.

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

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

Title:
  Update HPLIP Xenial package to 3.6.11

Status in hplip package in Ubuntu:
  New

Bug description:
  We are using HP Pagewide 377dw printers which are not supported in the
  current 3.16.3 package for Ubuntu 16.04 LTS. Please update HPLIP to
  3.6.11 to support that printers in business environments.

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

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

[Desktop-packages] [Bug 1653776] Re: remove imagemagick dependency

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

** Changed in: cups-filters (Ubuntu)
   Status: New => Confirmed

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

Title:
  remove imagemagick dependency

Status in cups-filters package in Ubuntu:
  Confirmed

Bug description:
  Please remove imagemagick dependency in cups-filters.
  Exploit after exploit, just because someone thinks printing to braille should 
be default for all ubuntu installation.

  
  /*
  Ubuntu tries supporting every obscure codecs, formats with programs/libs 
coded in thousands lines of crappy C code. If ubuntu had market share 
comparable to windows, ...
  */

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1653776/+subscriptions

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

[Desktop-packages] [Bug 1638778] Re: Wacom touch screen on lenovo X201t stopped working after upgrading from 14.04 to 16.04

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

** Changed in: xf86-input-wacom (Ubuntu)
   Status: New => Confirmed

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

Title:
  Wacom touch screen on lenovo X201t stopped working after upgrading
  from 14.04 to 16.04

Status in xf86-input-wacom package in Ubuntu:
  Confirmed

Bug description:
  I recently changed from Ubuntu 14.04 to 16.04. I re-installed from
  scratch as I was moving from 32bit to 64bit.

  My lenovo x201 tablet's touch screen and stylus did work fine with
  32bit 14.04.

  Now the touch screen is not even recognised.

  It does not show up in System Settings > Wacom Tablet

  Running:
  xsetwacom --list devices 

  returns nothing.

  sudo lshw | grep wacom

  returns nothing.

  xinput returns:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=11   [slave  pointer 
 (2)]
  ⎜   ↳ TPPS/2 IBM TrackPoint   id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated Camera   id=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=10   [slave  
keyboard (3)]
  ↳ ThinkPad Extra Buttons  id=12   [slave  
keyboard (3)]

  
  ...but no mention of the wacom touchscreen. 

  
  The following file is present on my system: 

  /lib/udev/rules.d/69-wacom.rules

  it contains the following:

  
  ACTION!="add|change", GOTO="wacom_end"

  # Match all serial wacom tablets with a serial ID starting with WACf
  # Notes: We assign NAME though we shouldn't, but currently the server 
requires it
  #We assign the lot to subsystem pnp too because server reads NAME from
  #the parent device. Once all that's fixed, as simple SUBSYSTEM="tty"
  #will do and the ENV{NAME} can be removed.
  SUBSYSTEM=="tty|pnp", SUBSYSTEMS=="pnp", ATTRS{id}=="WACf*", 
ENV{ID_MODEL}="Serial Wacom Tablet $attr{id}", ENV{ID_INPUT}="1", 
ENV{ID_INPUT_TABLET}="1", ENV{NAME}="Serial Wacom Tablet $attr{id}"
  SUBSYSTEM=="tty|pnp", SUBSYSTEMS=="pnp", ATTRS{id}=="FUJ*", 
ENV{ID_MODEL}="Serial Wacom Tablet $attr{id}", ENV{ID_INPUT}="1", 
ENV{ID_INPUT_TABLET}="1", ENV{NAME}="Serial Wacom Tablet $attr{id}"

  # comment out the next line if your distribution does not provide systemd
  # If a /dev/ttySx device with the WACf name is detected, start the
  # wacom-inputattach service with the kernel name as parameter
  SUBSYSTEM=="tty|pnp", KERNEL=="ttyS[0-9]*", ATTRS{id}=="WACf*", 
TAG+="systemd", ENV{SYSTEMD_WANTS}+="wacom-inputattach@%k.service"

  LABEL="wacom_end"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-input-wacom 1:0.32.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov  3 03:15:34 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  InstallationDate: Installed on 2016-10-23 (11 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 17ef:4816 Lenovo Integrated Webcam
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 2985EZG
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=462ac55e-9784-4072-898e-057558a90176 ro quiet splash vt.handoff=7
  SourcePackage: xf86-input-wacom
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET47WW (1.17 )
  dmi.board.name: 2985EZG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET47WW(1.17):bd07/14/2010:svnLENOVO:pn2985EZG:pvrThinkPadX201Tablet:

[Desktop-packages] [Bug 1589975] Re: Ubuntu 16.04 has Networking problems

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

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

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

Title:
  Ubuntu 16.04 has Networking problems

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 16.04 from Ubuntu 15.10, Ubuntu 16.04 does
  not properly "see" the home network (LAN). Additionally, my printer
  which is also attached to the LAN does not work correctly.

  These are erratic issues, meaning that they don't appear all the time.
  Further, no crash reports are generated either.

  To explain further. The computer running 16.04 will frequently NOT
  show up on the "network" screen. When I go over to the computer
  running Ubuntu 14.04 it also does not show the computer running 16.04
  as being on the LAN.

  In terms of printing, the printer queue shows the print job as "held".
  When you try to release the print job it asks if the printer is
  connected and then goes back to "holding" the print job.

  These actions seem to imply that networking is not working correctly
  with Ubuntu 16.04.

  Please see the comment by Jerrylamos here:
  
http://discourse.ubuntu.com/t/ubuntu-16-04-does-not-display-network-frequently/2768/2?u=ascolais

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.14
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Tue Jun  7 08:41:00 2016
  InstallationDate: Installed on 2016-04-13 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (44 days ago)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1617098] Re: Add support for option max-routes

2017-02-23 Thread Alberto Donato

Can this please be fixed in yakkety too?

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

Title:
  Add support for option max-routes

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-openvpn source package in Xenial:
  In Progress
Status in network-manager-openvpn source package in Zesty:
  Fix Released

Bug description:
  Hi,

  Currently in Ubuntu 16.04 network-manager-openvpn does not support the 
openvpn --max-routes switch.
  This means that per omission the VPN connection supports 100 routes that can 
be pushed by the openvpn server to the client. If the openvpn server pushes 
more 100 routes, which can happen in some cases, the VPN establishment fails.

  From OpenVPN manual:
  "--max-routes n
  Allow a maximum number of n --route options to be specified, either in the 
local configuration file, or pulled from an OpenVPN server. By default, n=100."

  Can you do one of the following?
  - Fully support max-routes in the GUI, with an option to choose the value of 
the max-routes
  or, simpler:
  - Do not implement the max-routes in the GUI but add '--max-routes 500' for 
example for all openvpn connection establishments. I mean increase the number 
of maximum routes for all openvpn connections with network-manager.

  There is also a gnome bugzilla related to this issue which was
  recently closed with a patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=720097

  When can we have the max-route implementation on network-manager-
  openvpn in ubuntu?

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

  mm:~$ apt-cache policy network-manager-openvpn
  network-manager-openvpn:
Installed: 1.1.93-1ubuntu1
Candidate: 1.1.93-1ubuntu1
Version table:
   *** 1.1.93-1ubuntu1 500
  500 http://pt.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/statusThanks,

  mm:~$ apt-cache policy network-manager-openvpn-gnome
  network-manager-openvpn-gnome:
Installed: 1.1.93-1ubuntu1
Candidate: 1.1.93-1ubuntu1
Version table:
   *** 1.1.93-1ubuntu1 500
  500 http://pt.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  mm:~$ apt-cache policy openvpn
  openvpn:
Installed: 2.3.10-1ubuntu2
Candidate: 2.3.10-1ubuntu2
Version table:
   *** 2.3.10-1ubuntu2 500
  500 http://pt.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Regards,

  Marco

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

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

[Desktop-packages] [Bug 1615602] Re: IRC message truncation

Unsubscribing ~ubuntu-sponsors for now, as there is nothing to sponsor
right now.

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

Title:
  IRC message truncation

Status in pidgin package in Ubuntu:
  Confirmed
Status in pidgin source package in Trusty:
  Confirmed
Status in pidgin source package in Xenial:
  Confirmed
Status in pidgin source package in Yakkety:
  Confirmed
Status in pidgin source package in Zesty:
  Confirmed

Bug description:
  This was upstream bug (https://developer.pidgin.im/ticket/4753) that
  recently has been fixed.

  I propose to add the patch to the offician ubuntu package so that
  users can get this fix before the new release, since the bug is quite
  irritating.

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

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

[Desktop-packages] [Bug 1615602] Re: IRC message truncation

Please resubscribe ~ubuntu-sponsors when you have something ready.

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

Title:
  IRC message truncation

Status in pidgin package in Ubuntu:
  Confirmed
Status in pidgin source package in Trusty:
  Confirmed
Status in pidgin source package in Xenial:
  Confirmed
Status in pidgin source package in Yakkety:
  Confirmed
Status in pidgin source package in Zesty:
  Confirmed

Bug description:
  This was upstream bug (https://developer.pidgin.im/ticket/4753) that
  recently has been fixed.

  I propose to add the patch to the offician ubuntu package so that
  users can get this fix before the new release, since the bug is quite
  irritating.

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

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

[Desktop-packages] [Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a

Is there any actual impact to Trusty users, please? Or is this just
tidying up some dangling symlinks for the sake of it?

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

Title:
  Invalid symlinks for libungif.so and libungif.a

Status in giflib package in Ubuntu:
  Fix Released
Status in giflib source package in Trusty:
  Triaged

Bug description:
  Impact
  ==
  libgif-dev in Ubuntu 14.04 LTS depends on libgif4 and has these symlinks:
  /usr/lib/libungif.a -> libgif.a
  /usr/lib/libungif.so -> libgif.so.4.1.6
  /usr/lib/x86_64-linux-gnu/libgif.so -> libgif.so.4.1.6
  /usr/lib/libungif.la -> libgif.la

  libgif4 has these files:
  /usr/lib/x86_64-linux-gnu/libgif.so.4.1.6
  /usr/lib/x86_64-linux-gnu/libgif.so.4 -> libgif.so.4.1.6

  Only the 3rd symlink (the multiarch one) in libgif-dev is correct. The
  others are dangling.

  This was caused by an obsolete debian/libgif-dev.links

  Test Case
  =
  Verify that libgif-dev only includes the one working symlink:
  /usr/lib/x86_64-linux-gnu/libgif.so -> libgif.so.4.1.6

  Regression Potential
  
  None, just removing some dangling symlinks that couldn't work any way.

  Original Bug Report
  ===
  In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in 
libgif-dev 4.1.6-11:

  Symbol links for libungif.a, libungif.la, and libungif.so are created
  in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6
  respectively. However, these files are not in /usr/lib but in
  /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid.

  I suggest fixing this by placing the symbol links in the same
  directory as the target files.

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

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

[Desktop-packages] [Bug 1337898] Re: Invalid symlinks for libungif.so and libungif.a

The "Impact" section in the bug whiteboard is supposed to contain this
information for an SRU, but right now it seems to contain a technical
description of what is wrong rather than describing any actual impact to
users.

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

Title:
  Invalid symlinks for libungif.so and libungif.a

Status in giflib package in Ubuntu:
  Fix Released
Status in giflib source package in Trusty:
  Triaged

Bug description:
  Impact
  ==
  libgif-dev in Ubuntu 14.04 LTS depends on libgif4 and has these symlinks:
  /usr/lib/libungif.a -> libgif.a
  /usr/lib/libungif.so -> libgif.so.4.1.6
  /usr/lib/x86_64-linux-gnu/libgif.so -> libgif.so.4.1.6
  /usr/lib/libungif.la -> libgif.la

  libgif4 has these files:
  /usr/lib/x86_64-linux-gnu/libgif.so.4.1.6
  /usr/lib/x86_64-linux-gnu/libgif.so.4 -> libgif.so.4.1.6

  Only the 3rd symlink (the multiarch one) in libgif-dev is correct. The
  others are dangling.

  This was caused by an obsolete debian/libgif-dev.links

  Test Case
  =
  Verify that libgif-dev only includes the one working symlink:
  /usr/lib/x86_64-linux-gnu/libgif.so -> libgif.so.4.1.6

  Regression Potential
  
  None, just removing some dangling symlinks that couldn't work any way.

  Original Bug Report
  ===
  In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in 
libgif-dev 4.1.6-11:

  Symbol links for libungif.a, libungif.la, and libungif.so are created
  in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6
  respectively. However, these files are not in /usr/lib but in
  /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid.

  I suggest fixing this by placing the symbol links in the same
  directory as the target files.

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

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

[Desktop-packages] [Bug 1576228] Re: Black borders around all windows

2017-02-23 Thread John Smith

As Dave pointed out, the problem is not consistent with black borders
but also with graphical glitch around windows, which I still think, has
something to do with, how shadows are rendered.

Adding an alternate attachment/image for graphic glitch.

** Attachment added: "Graphically glitched borders"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1576228/+attachment/4825203/+files/Graphics%20Glitch%20-%202017-02-23%2017-45-26.png

** Summary changed:

- Black borders around all windows
+ Black borders or graphic glitch around all windows

** Summary changed:

- Black borders or graphic glitch around all windows
+ Black borders or graphical glitch around all windows

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

Title:
  Black borders or graphical glitch around all windows

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

Bug description:
  While using the nvidia proprietary drivers in 14.04 - 16.04, my Dell
  XPS L501X resumes from suspend, but displays wide black borders around
  all windows with close/minimize/maximize buttons blacked out as per
  attached screenshot. It occurs inconsistently, as it doesn't happen
  every time the computer resumes.

  Also there seems to be certain amount of performance degradation as if
  the graphics driver was running at half-strength. The "nVidia X Server
  Settings" app suggests its in maximum performance mode.

  Adhoc WORKAROUND: switch display layout (I have an external monitor/TV
  attached to HDMI port) changing anything such as arrangement or
  resolution of the displays, etc. corrects the black border issue.

  See comment :https://bugs.launchpad.net/ubuntu/+source/nvidia-
  graphics-drivers-361/+bug/1576228/comments/4

  WORKAROUND: Use nouveau.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: [[0;32m  OK  [0m] Started LSB: Speech Dispatcher.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 28 18:43:37 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 435M] [10de:0df2] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell GF108M [GeForce GT 435M] [1028:046e]
  InstallationDate: Installed on 2016-04-23 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS L501X
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-21-generic 
root=UUID=f657e606-ac2a-49cd-9f3e-fca6a315338d ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J1VR3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn0J1VR3:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: XPS L501X
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A

[Desktop-packages] [Bug 790130] Re: no pressure sensitivity with wacom tablet in inkscape

2017-02-23 Thread peter.muster

This is a bug, that seems unmaintained, the comment of apienk says
pretty clearly, that he cannot save the configuration, otherwise it
works.

The only thing to do to get it to work under Linux is:
- open ~/.config/inkscape/preferences.xml in a Texteditor
- search for wacom 
- and enter mode="screen", in the appropriate section (see below)

This is just a GUI problem at the moment (apart from the overlay-
scrollbar thing that does not affect me).

The relevant section in the .xml that works for me now is:
  



  

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

Title:
  no pressure sensitivity with wacom tablet in inkscape

Status in Inkscape:
  Confirmed
Status in overlay-scrollbar:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: inkscape

  I am using inkscape 0.48 with a wacom pen & touch (CTH-460/k)

  I have been using this combination before and everything was working
  fine, but - probably - since the upgrade to natty pressure sensitivity
  does not work any more, whereas it is working fine, e.g. in the gimp.

  I have double- and triple-checked the settings. The tablet is
  recognised and everything is enabled and set to "screen". Yet, no joy.

  
  I'd like to work with this again, as this is a productive envrionment...

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: inkscape 0.48.1-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
  Uname: Linux 2.6.38-9-generic x86_64
  Architecture: amd64
  Date: Mon May 30 15:56:52 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to natty on 2011-03-18 (72 days ago)

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

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

[Desktop-packages] [Bug 1566513] Re: Complex numbers are exponentiated incorrectly

2017-02-23 Thread FanJun Kong - ( BH1SCW )

** Changed in: gnome-calculator (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: gnome-calculator (Ubuntu Xenial)
 Assignee: (unassigned) => FanJun Kong - ( BH1SCW ) (fjkong)

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

Title:
  Complex numbers are exponentiated incorrectly

Status in GNOME Calculator:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-calculator source package in Xenial:
  In Progress
Status in gnome-calculator source package in Yakkety:
  Fix Released

Bug description:
  The calculator incorrectly performs exponentiation if the base is
  complex and the exponent is a positive integer. Under these conditions
  the calculator exponentiates the real part of the base and leaves its
  imaginary part intact, that does not agree with the complex numbers
  operation rules. If the exponent is not a positive integer, the
  calculation is performed correctly.

  Steps to reproduce the bug:

  1. Start the program.
  2. Evaluate expression "i^2". The displayed result is "i".
  3. Evaluate expression "(1+i)^2". The displayed result is "1+i".
  4. Evaluate expression "(2+i)^2". The displayed result is "4+i".

  Please find a quick fix patch attached. I did not study its
  comprehensiveness and optimality, but it seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-calculator 1:3.16.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  5 22:59:29 2016
  InstallationDate: Installed on 2014-09-29 (554 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-calculator
  UpgradeStatus: Upgraded to wily on 2015-10-29 (159 days ago)

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

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

[Desktop-packages] [Bug 1667328] [NEW] Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps

2017-02-23 Thread Till Kamppeter

Public bug reported:

I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
#42-Ubuntu

In the last days the microphone stopped working when I am on the Google
Hangouts video conference in the Chromium browser. I checked the sound
settings of the System Settings and on the "input" tab the slider for
the microphone volume is grayed out and cannot be moved away from the
zero position. The microphone level monitor bar does not move when
talking or touching the microphone.

Then I found the following on the internet

http://askubuntu.com/questions/508221/sound-input-device-microphone-not-
working

and tried to solve the problem following the hints:

- Reboot does not solve the problem.

- I could not do any tests with gstreamer-properties as it seems to have
been removed from gstreamer (what is the successor?).

- pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices"
Tab that the microphone of the laptop is OK and that the kernel works
with it. The Level monitor bar is moving according to environment noise
and touching of the microphone.

- "sudo alsa force-reload" does not solve the problem.

- "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get
install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards does
not solve the problem.

- audacity is recording through the microphone correctly.

- Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d/alsa-
base.conf and rebooting does not solve the problem.

I hope that is a known problem. Please tell me if you need further
information.

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

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Summary changed:

- .
+ Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?) apps

** Description changed:

- .
+ I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
+ Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
+ #42-Ubuntu
+ 
+ In the last days the microphone stopped working when I am on the Google
+ Hangouts video conference in the Chromium browser. I checked the sound
+ settings of the System Settings and on the "input" tab the slider for
+ the microphone volume is grayed out and cannot be moved away from the
+ zero position. The microphone level monitor bar does not move when
+ talking or touching the microphone.
+ 
+ Then I found the following on the internet
+ 
+ http://askubuntu.com/questions/508221/sound-input-device-microphone-not-
+ working
+ 
+ and tried to solve the problem following the hints:
+ 
+ - Reboot does not solve the problem.
+ 
+ - I could not do any tests with gstreamer-properties as it seems to have
+ been removed from gstreamer (what is the successor?).
+ 
+ - pavucontrol (Pulse Audio Sound Control) shows on its "Input Devices"
+ Tab that the microphone of the laptop is OK and that the kernel works
+ with it. The Level monitor bar is moving according to environment noise
+ and touching of the microphone.
+ 
+ - "sudo alsa force-reload" does not solve the problem.
+ 
+ - "sudo apt-get remove --purge alsa-base pulseaudio; sudo apt-get
+ install alsa-base pulseaudio ubuntu-desktop" and reboot afterwards does
+ not solve the problem.
+ 
+ - audacity is recording through the microphone correctly.
+ 
+ - Adding "options snd-hda-intel position_fix=1" to /etc/modprobe.d/alsa-
+ base.conf and rebooting does not solve the problem.
+ 
+ I hope that is a known problem. Please tell me if you need further
+ information.

** Package changed: cups (Ubuntu) => gstreamer (Ubuntu)

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

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Lenovo X1 Carbon 2nd gen: Microphone not working in GTK (GStremer?)
  apps

Status in gstreamer package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a Lenovo Thinkpad X1 Carbon (2nd gen, 2014?) running Ubuntu
  Yakkety (16.10). Kernel is the most current one: 4.8.0-39-generic
  #42-Ubuntu

  In the last days the microphone stopped working when I am on the
  Google Hangouts video conference in the Chromium browser. I checked
  the sound settings of the System Settings and on the "input" tab the
  slider for the microphone volume is grayed out and cannot be moved
  away from the zero position. The microphone level monitor bar does not
  move when talking or touching the microphone.

  Then I found the following on the internet

  http://askubuntu.com/questions/508221/sound-input-device-microphone-
  not-working

  and trie

[Desktop-packages] [Bug 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-02-23 Thread FFab

Christopher M. Penalver, re backlight cycle.

Booting, grub config: no workaround, "quiet splash", reboot - I note
following cycle:

Grub menu - gray backlight (brightness same as grub menu background) -
then a flash (white), not covering the whole screen - black( 0%
brigthness, lasting 6 sec) - gray like before.

cold start:

grub-menu - gray - flash (white), not covering the whole screen -a cycle
of 16 times:   black  and  gray  - the last gray

note:
runnig Ubuntu, brightness cannot be changed
running Windows10, no brightness problem.

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1664147] Re: Chromium on trusty too outdated; not supported by gmail

2017-02-23 Thread Giacomo Nannicini

Considering the latest news about the vulnerability of SHA-1 (see
https://shattered.it/ ), any Chromium version < 56 is potentially
vulnerable.

** Information type changed from Public to Public Security

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

Title:
  Chromium on trusty too outdated; not supported by gmail

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  As of Feb 13 2017, the chromium version on trusty is 53.x which is at
  least a couple of versions behind chrome-stable. Gmail displays this
  message, "This version of Chrome is no longer supported. Please
  upgrade to asupported browser." Core functionality in gmail works
  fine, but I'm not sure of security ramifications of running an old
  browser, particularly when google advises against it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1664147/+subscriptions

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

[Desktop-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss

2017-02-23 Thread spike speigel

I would like to share that I found this post referring to a similar
issue where sound settings weren't maintained, maintained being a better
word than saved because I believe alsamixer might properly save the
settings.

According to the post it is pulseaudio which is actually modifying the
settings:

http://askubuntu.com/a/549939

I tested as suggested, by modifying the "Headphone Mic Boost" within
alsamixer and exiting. I then ran:

pulseaudio -k

And pulseaudio reset the "Headphone Mic Boost" to dB gain 0.00, 0.00.
The hissing reappeared.

If I could get pulseaudio to stop resetting the "Headphone Mic Boost" in
alsamixer, then that would be an acceptable workaround.

But, I think the real issue still needs to be resolved. One would
expect a dB gain 0.00, 0.00 to be absolutely silent. The user should
not need to kick it up a notch to dB gain 10.00, 10.00.

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

Title:
XPS 13 9360, Realtek ALC3246, Headphone audio hiss

Status in alsa-driver package in Ubuntu:
Confirmed

Bug description:
Pertaining to 16.04 on a dell XPS 13 9360

ii alsa-base 1.0.25+dfsg-0ubuntu5

Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

When headphones are plugged in, there is a clearly audible hiss (white
noise). This is present as soon as the headphones are plugged in, whether
'headphones' or 'headset' are selected from the pop-up box.

Using alsamixer to debug the issue reveals that it is related to
"Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
this is changed to:

10.00, 10.00 (one notch up) the hiss disappears.
20.00, 20.00 cause a louder hiss and
30.00, 30.00 causes an even louder hiss with high frequency audio artifacts.

When the headphones are removed and plugged back in the Headphone Mic
Boost setting returns to dB gain 0 and the problem also returns.

This (problem and workaround) has been reported in the wild:
https://news.ycombinator.com/item?id=13050843 and

https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
for example

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

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

[Desktop-packages] [Bug 994612] Re: gnome-screensaver-preferences missing

2017-02-23 Thread Pander

Can this bug still be reproduced with 16.04 and/or 16.10? If so, what
can be done upstream by GNOME and/or Ubuntu? What are urls to upstream
bugs in GNOME?

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

Title:
  gnome-screensaver-preferences missing

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  There is no user-friendly way to configure gnome-screensaver. And
  there was one, I know.

  P.S.
  Please don't tell me that one has to use xscreensaver instead. It does not 
have:
  * DBus  support
  * user-switching support
  * keyboard layout indicator

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

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

[Desktop-packages] [Bug 1667355] [NEW] Please merge gtk+2.0 2.24.31-2ubuntu1 (main) from Debian unstable (main)

2017-02-23 Thread FanJun Kong - ( BH1SCW )

Public bug reported:


Please upload merge gtk+2.0 2.24.31-2ubuntu1 (main) from Debian unstable
(main).

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Assignee: FanJun Kong - ( BH1SCW ) (fjkong)
 Status: In Progress

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => In Progress

** Changed in: gtk+2.0 (Ubuntu)
 Assignee: (unassigned) => FanJun Kong - ( BH1SCW ) (fjkong)

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

Title:
  Please merge gtk+2.0 2.24.31-2ubuntu1 (main) from Debian unstable
  (main)

Status in gtk+2.0 package in Ubuntu:
  In Progress

Bug description:

  Please upload merge gtk+2.0 2.24.31-2ubuntu1 (main) from Debian
  unstable (main).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1667355/+subscriptions

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

[Desktop-packages] [Bug 726480] Re: gnome-screensaver forces itself upon xscreensaver users

2017-02-23 Thread Pander

Can this bug still be reproduced with 16.04 and/or 16.10? If so, what
can be done upstream by GNOME and/or Ubuntu? What are urls to upstream
bugs in GNOME?

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

Title:
  gnome-screensaver forces itself upon xscreensaver users

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  gnome-screensaver installs the DBus file

  /usr/share/dbus-1/services/org.gnome.ScreenSaver.service

  which unconditionally starts gnome-screensaver whenever some other
  process (e.g. nm-applet, update-notifier) "pull the trigger". This is
  troubling for users of non-gnome desktop environments, e.g. LXDE.

  A workaround for me was to install the following
  /usr/local/share/dbus-1/services/org.gnome.ScreenSaver.service:

  
  [D-BUS Service]
  Name=org.gnome.ScreenSaver
  Exec=/bin/sh -c 'if xscreensaver-command -version >/dev/null 2>&1; then 
renice +10 $$ >/dev/null 2>&1; while sleep 60; do :; done else exec 
/usr/bin/gnome-screensaver; fi' gnome-screensaver-placeholder

  The dummy process remains active because if it exited immediately,
  dbus might try to restart gnome-screensaver. I don't know if this is
  really necessary.

  First of all, this needs to be fixed -- screensavers should not step
  on each others' toes. Secondly, is there a more elegant workaround?
  Note that because of bug #726471, a user can't override a misguided
  /usr/share/ service file in his home (~/.local/share) configuration:

  https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/726471

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.31-11.154-rt
  Uname: Linux 2.6.31-11-rt i686
  Architecture: i386
  Date: Mon Feb 28 12:44:49 2011
  GnomeSessionIdleInhibited: Unknown
  GnomeSessionInhibitors: Failed to acquire
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

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

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

[Desktop-packages] [Bug 1667350] Re: nautilus crashed with SIGABRT in g_assertion_message()

2017-02-23 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in nautilus package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.3-1ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7
  Date: Thu Feb 23 16:10:45 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2016-02-22 (367 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to zesty on 2017-01-13 (40 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  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/1667350/+subscriptions

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

[Desktop-packages] [Bug 1657037] Re: totem should not claim to be able to open pdfs

2017-02-23 Thread Sebastian Ramacher

** Package changed: vlc (Ubuntu) => thunderbird (Ubuntu)

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

Title:
  totem should not claim to be able to open pdfs

Status in thunderbird package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  For some dumb reason, thunderbird is opening pdfs with totem instead
  of a decent pdf reader.

  I'm aware I can override and configure all this in Thunderbid, but IMO
  the default should Just Work.

  I don't have the patience atm to weed through all the xdg-open and
  mime and .desktop-files spaghetti shit to figure out why the f*ck a
  mediaplayer would ever be the default to open a pdf when decent pdf
  readers are available on my system, but I'm pretty sure totem is at
  fault here for announcing to the system somewhere that it is able to
  handle pdfs.

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

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

[Desktop-packages] [Bug 528094] Re: lock screen fails with xscreensaver

2017-02-23 Thread vgeloven

Does https://www.jwz.org/xscreensaver/man1.html#8 help?

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

Title:
  lock screen fails with xscreensaver

Status in Session Menu:
  Confirmed
Status in xscreensaver package in Ubuntu:
  Confirmed

Bug description:
  The session menu "Lock Screen" option does not work. I managed to get
  Ctrl-Alt-L to lock the screen with Compiz, but the session menu item
  will not work.

  I tried:
  making symlinks from gnome-screensaver to xscreensaver and from 
gnome-screensaver-command to xscreensaver-command
  adding a .service file to /usr/share/dbus-1/services/ called 
org.gnome.ScreenSaver.service with the following content:
  [D-BUS Service]
  Name=org.gnome.ScreenSaver
  Exec=/usr/bin/xscreensaver

  I also tried that with
  Exec=/usr/bin/gnome-screensaver
  after creating the symlink.

  I'm not too familiar with dbus so I'm not sure what else I should do.
  Using gnome-screensaver is an option that follows dumping Gnome and
  choosing another distro in desirability. In other words, no chance. If
  gnome won't work with a real screensaver app that's additional
  activation energy to move me to another distro.

  Architecture: amd64
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: xscreensaver 5.08-0ubuntu5
  PackageArchitecture: amd64
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
  Uname: Linux 2.6.31-19-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev pulse pulse-access 
sambashare video

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-session/+bug/528094/+subscriptions

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

[Desktop-packages] [Bug 977993] Re: Can't lock screen

2017-02-23 Thread Pander

Have you tried https://www.jwz.org/xscreensaver/man1.html#8

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

Title:
  Can't lock screen

Status in xscreensaver package in Ubuntu:
  New

Bug description:
  Similar to bug #10228, I'm currently unable to lock the screen with
  xscreensaver. Ctrl-Alt-L does nothing, and `xscreensaver-command
  -lock` reports "xscreensaver-command: already locked."
  .

  I've tried the following to get it back up:
  $ killall xscreensaver # Returned with exit code 0
  $ xscreensaver-command -lock
  xscreensaver-command: no screensaver is running on display :0
  $ xscreensaver-command -restart
  xscreensaver-command: no screensaver is running on display :0
  $ xscreensaver
  xscreensaver: 14:22:19: "gnome-screensaver" is already running on display :0 
(window 0x3a1)
  $ xscreensaver-command -lock
  xscreensaver-command: no screensaver is running on display :0

  Looks like there might be some conflict between gnome-screensaver and
  xscreensaver. I've no idea why gnome-screensaver is running - I'm
  running LXDE and xscreensaver by default.

  Workaround: gnome-screensaver-command --exit && xscreensaver &

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xscreensaver 5.14-1ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 10 14:17:53 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64+mac 
(20101008)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LC_PAPER=en_GB.UTF-8
  SourcePackage: xscreensaver
  UpgradeStatus: Upgraded to oneiric on 2012-02-24 (45 days ago)

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

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

[Desktop-packages] [Bug 1667360] [NEW] sudo scanimage -L results in core dumped!

2017-02-23 Thread Alan

Public bug reported:

sudo scanimage -L
[sudo] password for hovgaard: 
Segmentation fault (core dumped)

I have installed Brother LDP2540DN printer/scanner via Brother .deb
files.

Tested on latest Kubuntu dev alpha Zesty relase 2.
System was fully updates as of 23 feb 2017.
Regards
Alan

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

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

Title:
  sudo scanimage -L results in core dumped!

Status in sane-backends package in Ubuntu:
  New

Bug description:
  sudo scanimage -L
  [sudo] password for hovgaard: 
  Segmentation fault (core dumped)

  I have installed Brother LDP2540DN printer/scanner via Brother .deb
  files.

  Tested on latest Kubuntu dev alpha Zesty relase 2.
  System was fully updates as of 23 feb 2017.
  Regards
  Alan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1667360/+subscriptions

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

[Desktop-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2017-02-23 Thread Ricardo Rodrigues

I'm also suffering from this issue.

New wireless headset with mic, can't use the mic...

But I'm using Ubuntu 16.10 (Yakkety Yak). What can I do to help debug
this issue?

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions

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

[Desktop-packages] [Bug 1514231] Re: Huawei Broadband stick not recognized

2017-02-23 Thread Norbert

I read http://forum.ubuntu-it.org/viewtopic.php?f=9&t=610274
Got modem working with:
sudo usb_modeswitch -v 12d1 -p 1446 -J

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

Title:
  Huawei Broadband stick not recognized

Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  USB Huawei broadband USB modem not recognized as modem but only as
  storage

  Nov  8 19:53:04 v5 usb_modeswitch_dispatcher[8223]: message repeated 3 times: 
[ Could not read attribute: No such file or directory]
  Nov  8 19:53:05 v5 usb_modeswitch[8223]: usb_modeswitch: use overriden config 
12d1:1446 from collection /etc/usb_modeswitch.d; make sure this is intended
  Nov  8 19:53:05 v5 usb_modeswitch[8223]: usb_modeswitch: please report any 
new or corrected settings; otherwise, check for outdated files
  Nov  8 19:53:05 v5 usb_modeswitch: switch device 12d1:1446 on 001/012
  Nov  8 19:53:06 v5 usb_modeswitch_dispatcher[8223]: Could not read attribute: 
No such file or directory
  Nov  8 19:53:06 v5 usb_modeswitch[8223]: usb_modeswitch: switched to 
12d1:1446 on 1/12
  Nov  8 19:53:07 v5 usb_modeswitch_dispatcher[8223]: Unable to open bind list 
file: No such file or directory
  Nov  8 19:53:07 v5 usb_modeswitch[8223]: usb_modeswitch: add device ID 
12d1:1446 to driver option
  Nov  8 19:53:07 v5 usb_modeswitch[8223]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Nov  8 19:53:14 v5 systemd[1]: Started USB_ModeSwitch_1-3:1.0.

  
  $ lsusb
  Bus 003 Device 002: ID 8087:8000 Intel Corp. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 04f2:b469 Chicony Electronics Co., Ltd 
  Bus 001 Device 002: ID 04ca:2004 Lite-On Technology Corp. Bluetooth 4.0 
[Broadcom BCM20702A0]
  Bus 001 Device 012: ID 12d1:1446 Huawei Technologies Co., Ltd. Broadband 
stick (modem on)
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: usb-modeswitch 2.2.5+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  8 19:53:21 2015
  InstallationDate: Installed on 2015-08-18 (82 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: usb-modeswitch
  UpgradeStatus: Upgraded to wily on 2015-11-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1514231/+subscriptions

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

[Desktop-packages] [Bug 1666100] Re: Use GNOME Software as default snap: URL handler

Hello Robert, or anyone else affected,

Accepted desktop-file-utils into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/desktop-file-utils/0.23-1ubuntu1.1 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 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!

** Description changed:

  [Impact]
  In the same way as apturl is set as the default apt: URL handler, we should 
do the same for GNOME Software with the snap: URL.
  
  The prime impact for users will be support for snap:// URLs in the
  browser.  This will allow web sites to provide a "click here to install
- this snap" type links which will take the user in to Ubuntu Software
- where the snap will be preselected. e.g.
- http://www.omgubuntu.co.uk/2017/02/snap-url-support-coming-ubuntu-
- software-app-plus-love-news  (link towards the bottom as an example of
- the sorts of things websites will be able to do).
- 
+ this snap" type links which will take the user directly to Ubuntu
+ Software (instead of having to choose a url handler) where the snap will
+ be preselected. e.g. http://www.omgubuntu.co.uk/2017/02/snap-url-
+ support-coming-ubuntu-software-app-plus-love-news  (link towards the
+ bottom as an example of the sorts of things websites will be able to
+ do).
  
  [Test Case]
  Run:
  $ xdg-open snap:moon-buggy
  
  Expected result:
  GNOME Software opens with information on the moon-buggy snap
  
  Observed result:
  Get error about "specified location not supported"
  
  [Regression Potential]
  Low, we set a default where there was previously none.

** Changed in: desktop-file-utils (Ubuntu Yakkety)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

** Changed in: desktop-file-utils (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

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

Title:
  Use GNOME Software as default snap: URL handler

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  Fix Committed
Status in desktop-file-utils source package in Yakkety:
  Fix Committed
Status in desktop-file-utils source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  In the same way as apturl is set as the default apt: URL handler, we should 
do the same for GNOME Software with the snap: URL.

  The prime impact for users will be support for snap:// URLs in the
  browser.  This will allow web sites to provide a "click here to
  install this snap" type links which will take the user directly to
  Ubuntu Software (instead of having to choose a url handler) where the
  snap will be preselected. e.g. http://www.omgubuntu.co.uk/2017/02
  /snap-url-support-coming-ubuntu-software-app-plus-love-news  (link
  towards the bottom as an example of the sorts of things websites will
  be able to do).

  [Test Case]
  Run:
  $ xdg-open snap:moon-buggy

  Expected result:
  GNOME Software opens with information on the moon-buggy snap

  Observed result:
  Get error about "specified location not supported"

  [Regression Potential]
  Low, we set a default where there was previously none.

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

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

[Desktop-packages] [Bug 1666100] Please test proposed package

Hello Robert, or anyone else affected,

Accepted desktop-file-utils into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/desktop-
file-utils/0.22-1ubuntu5.1 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 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!

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

Title:
  Use GNOME Software as default snap: URL handler

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  Fix Committed
Status in desktop-file-utils source package in Yakkety:
  Fix Committed
Status in desktop-file-utils source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  In the same way as apturl is set as the default apt: URL handler, we should 
do the same for GNOME Software with the snap: URL.

  The prime impact for users will be support for snap:// URLs in the
  browser.  This will allow web sites to provide a "click here to
  install this snap" type links which will take the user directly to
  Ubuntu Software (instead of having to choose a url handler) where the
  snap will be preselected. e.g. http://www.omgubuntu.co.uk/2017/02
  /snap-url-support-coming-ubuntu-software-app-plus-love-news  (link
  towards the bottom as an example of the sorts of things websites will
  be able to do).

  [Test Case]
  Run:
  $ xdg-open snap:moon-buggy

  Expected result:
  GNOME Software opens with information on the moon-buggy snap

  Observed result:
  Get error about "specified location not supported"

  [Regression Potential]
  Low, we set a default where there was previously none.

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

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

[Desktop-packages] [Bug 1663926] Re: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017

2017-02-23 Thread ptoharia

I upgraded my 17.04 to kernel 4.10 and gave a try to latest 378 drivers
(nvidia-378_378.09-0ubuntu0~gpu17.04.3_amd64) and got the same behaviour
as with kernel 4.9. Tried to roll back to previous working version of
the drivers (nvidia-378_378.09-0ubuntu0~gpu17.04.3_amd64.deb) but
couldn't find the package in the repositories. Anyone knows if its
possible to access this version?

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

Title:
  Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017

Status in Nvidia:
  New
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  There have been multiple reports that "nvidia-prime select intel" results in 
a black screen on the new Dell XPS 15 (9560, with Nvidia 1050)
  See the following threads:

  1. (initial report). 
  
https://www.reddit.com/r/Ubuntu/comments/5qjq4v/dell_xps_15_kaby_lake_w_nvidia_1050_review_2017/

  2. (lots of confirmations of the same thing)
   
https://www.reddit.com/r/Dell/comments/5rxb5x/any_dell_xps_15_9560_linux_users/ 

  3. (additional confirmation)
  
https://www.reddit.com/r/Dell/comments/5t2b5d/high_cpu_temp_and_fan_usage_for_ubuntu_on_9560/

  4. (reported on Nvidia forums)
  
https://devtalk.nvidia.com/default/topic/991853/complete-freeze-with-nvidia-prime/

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

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

[Desktop-packages] [Bug 1617098] Re: Add support for option max-routes

** Changed in: network-manager-openvpn (Ubuntu Xenial)
   Status: In Progress => Incomplete

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

Title:
  Add support for option max-routes

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-openvpn source package in Xenial:
  Incomplete
Status in network-manager-openvpn source package in Zesty:
  Fix Released

Bug description:
  Hi,

  Currently in Ubuntu 16.04 network-manager-openvpn does not support the 
openvpn --max-routes switch.
  This means that per omission the VPN connection supports 100 routes that can 
be pushed by the openvpn server to the client. If the openvpn server pushes 
more 100 routes, which can happen in some cases, the VPN establishment fails.

  From OpenVPN manual:
  "--max-routes n
  Allow a maximum number of n --route options to be specified, either in the 
local configuration file, or pulled from an OpenVPN server. By default, n=100."

  Can you do one of the following?
  - Fully support max-routes in the GUI, with an option to choose the value of 
the max-routes
  or, simpler:
  - Do not implement the max-routes in the GUI but add '--max-routes 500' for 
example for all openvpn connection establishments. I mean increase the number 
of maximum routes for all openvpn connections with network-manager.

  There is also a gnome bugzilla related to this issue which was
  recently closed with a patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=720097

  When can we have the max-route implementation on network-manager-
  openvpn in ubuntu?

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

  mm:~$ apt-cache policy network-manager-openvpn
  network-manager-openvpn:
Installed: 1.1.93-1ubuntu1
Candidate: 1.1.93-1ubuntu1
Version table:
   *** 1.1.93-1ubuntu1 500
  500 http://pt.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/statusThanks,

  mm:~$ apt-cache policy network-manager-openvpn-gnome
  network-manager-openvpn-gnome:
Installed: 1.1.93-1ubuntu1
Candidate: 1.1.93-1ubuntu1
Version table:
   *** 1.1.93-1ubuntu1 500
  500 http://pt.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

  mm:~$ apt-cache policy openvpn
  openvpn:
Installed: 2.3.10-1ubuntu2
Candidate: 2.3.10-1ubuntu2
Version table:
   *** 2.3.10-1ubuntu2 500
  500 http://pt.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Regards,

  Marco

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

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

[Desktop-packages] [Bug 947244] Re: deja-dup-monitor does not have branded icon in System Monitor

2017-02-23 Thread Diogo Gomes

Icon appears in system monitor in Ubuntu 16.04.

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: deja-dup
   Status: Triaged => Fix Released

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

Title:
  deja-dup-monitor does not have branded icon in System Monitor

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  deja-dup does not have unique icon in system monitor (as reported in
  LP: #92 which was closed because these should be individual bugs)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/947244/+subscriptions

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

[Desktop-packages] [Bug 1667425] [NEW] ModemManager crashed with SIGSEGV in g_closure_invoke()

2017-02-23 Thread siucdude

Public bug reported:

This is on 17.04 Beta, just started after today updates.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: modemmanager 1.6.4-1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Feb 22 21:43:41 2017
ExecutablePath: /usr/sbin/ModemManager
InstallationDate: Installed on 2015-12-17 (433 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: /usr/sbin/ModemManager
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x55bf1fab2ab7:  repz cmpsb %es:(%rdi),%ds:(%rsi)
 PC (0x55bf1fab2ab7) ok
 source "%es:(%rdi)" (0x55bf1fb453fa) ok
 destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: modemmanager
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to zesty on 2017-02-14 (8 days ago)
UserGroups:

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


** Tags: amd64 apport-crash need-amd64-retrace zesty

** Information type changed from Private to Public

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

Title:
  ModemManager crashed with SIGSEGV in g_closure_invoke()

Status in modemmanager package in Ubuntu:
  New

Bug description:
  This is on 17.04 Beta, just started after today updates.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: modemmanager 1.6.4-1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 22 21:43:41 2017
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2015-12-17 (433 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55bf1fab2ab7:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55bf1fab2ab7) ok
   source "%es:(%rdi)" (0x55bf1fb453fa) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to zesty on 2017-02-14 (8 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1666100] Re: Use GNOME Software as default snap: URL handler

2017-02-23 Thread Mateusz Stachowski

I checked the Yakkety package.

** 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 desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1666100

Title:
  Use GNOME Software as default snap: URL handler

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  Fix Committed
Status in desktop-file-utils source package in Yakkety:
  Fix Committed
Status in desktop-file-utils source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  In the same way as apturl is set as the default apt: URL handler, we should 
do the same for GNOME Software with the snap: URL.

  The prime impact for users will be support for snap:// URLs in the
  browser.  This will allow web sites to provide a "click here to
  install this snap" type links which will take the user directly to
  Ubuntu Software (instead of having to choose a url handler) where the
  snap will be preselected. e.g. http://www.omgubuntu.co.uk/2017/02
  /snap-url-support-coming-ubuntu-software-app-plus-love-news  (link
  towards the bottom as an example of the sorts of things websites will
  be able to do).

  [Test Case]
  Run:
  $ xdg-open snap:moon-buggy

  Expected result:
  GNOME Software opens with information on the moon-buggy snap

  Observed result:
  Get error about "specified location not supported"

  [Regression Potential]
  Low, we set a default where there was previously none.

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

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

[Desktop-packages] [Bug 1667425] Re: ModemManager crashed with SIGSEGV in g_closure_invoke()

2017-02-23 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

Title:
  ModemManager crashed with SIGSEGV in g_closure_invoke()

Status in modemmanager package in Ubuntu:
  New

Bug description:
  This is on 17.04 Beta, just started after today updates.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: modemmanager 1.6.4-1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Feb 22 21:43:41 2017
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2015-12-17 (433 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x55bf1fab2ab7:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x55bf1fab2ab7) ok
   source "%es:(%rdi)" (0x55bf1fb453fa) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to zesty on 2017-02-14 (8 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1621753] Re: Google Cast no longer finds Chromecast device

2017-02-23 Thread Chad Miller

Verified. Fixed in code. New version available soon.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => Fix Committed

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

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Chad Miller (cmiller)

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

Title:
  Google Cast no longer finds Chromecast device

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  After upgrading to latest chromium-browser version
  (52.0.2743.116-0ubuntu0.16.04.1.1250), the Google Cast extension no
  longer finds the Chromecast (v2) device. This used to work with the
  previous chromium version.

  Also, google-chrome-stable 53.0.2785.101-1 works fine on the same box,
  so the issue is with the chromium update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1621753/+subscriptions

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

[Desktop-packages] [Bug 1666100] Re: Use GNOME Software as default snap: URL handler

2017-02-23 Thread Will Cooke

I checked the Xenial package. Also good, so verification-done.

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

Title:
  Use GNOME Software as default snap: URL handler

Status in desktop-file-utils package in Ubuntu:
  Fix Released
Status in desktop-file-utils source package in Xenial:
  Fix Committed
Status in desktop-file-utils source package in Yakkety:
  Fix Committed
Status in desktop-file-utils source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  In the same way as apturl is set as the default apt: URL handler, we should 
do the same for GNOME Software with the snap: URL.

  The prime impact for users will be support for snap:// URLs in the
  browser.  This will allow web sites to provide a "click here to
  install this snap" type links which will take the user directly to
  Ubuntu Software (instead of having to choose a url handler) where the
  snap will be preselected. e.g. http://www.omgubuntu.co.uk/2017/02
  /snap-url-support-coming-ubuntu-software-app-plus-love-news  (link
  towards the bottom as an example of the sorts of things websites will
  be able to do).

  [Test Case]
  Run:
  $ xdg-open snap:moon-buggy

  Expected result:
  GNOME Software opens with information on the moon-buggy snap

  Observed result:
  Get error about "specified location not supported"

  [Regression Potential]
  Low, we set a default where there was previously none.

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

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

[Desktop-packages] [Bug 1165609] Re: There is no apparent way to stop Orca

2017-02-23 Thread Redfern-derek

Behavior still exists... `killall orca; apt remove gnome-orca` was my
approach. Would've kept it installed if there was some way to stop it
without resorting to killall.

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

Title:
  There is no apparent way to stop Orca

Status in OEM Priority Project:
  Invalid
Status in gnome-orca package in Ubuntu:
  Confirmed

Bug description:
  The "Orca Screen Reader" icon in the Dash is a trap. If a user
  accidentally opens it, the only apparent recourse for the incessant
  jabber is to either mute the volume system-wide or log out. This makes
  for a very poor user experience.

  Orca could avoid this situation by providing at least one of the
  following:

1) A notification of how to stop it, if there is a way to stop it.
2) A confirmation prompt prior to starting.
3) A quit option in a standard location such as the indicator menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-orca 3.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Apr  6 18:35:02 2013
  InstallationDate: Installed on 2013-04-06 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-orca
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1165609/+subscriptions

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

[Desktop-packages] [Bug 1666951] Re: time-admin window doesn't install ntp when prompted

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

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

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

Title:
  time-admin window doesn't install ntp when prompted

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

Bug description:
  I'm using Xubuntu 17.04 but I don't think this problem is specific to
  Xubuntu.

  By default, "Configuration" in "Time and Date Settings" is set to
  "Manual". If I change the option to "Keep synchronized with Internet
  servers" I am prompted to "Install NTP support" or to cancel the
  change. Obviously this is only when the ntp package isn't already
  installed.

  Clicking on "Install NTP support" displays a notification window to
  say that an application is requesting additional packages and that is
  can be found in "Software". Clicking on that window brings up gnome-
  software which says that the requested package cannot be found.

  I'm sure that in the past I was prompted for my administrator password
  as would be expected when installing software.

  Although I'm reporting this using a live environment I also saw this
  with my full disk based installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-system-tools 3.0.0-4ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: XFCE
  Date: Wed Feb 22 15:16:50 2017
  ExecutablePath: /usr/bin/time-admin
  LiveMediaBuild: Xubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170222)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-system-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1666882] Re: Setting radio frequency IT in wifi card

2017-02-23 Thread Massimo Cala'

** Information type changed from Public to Public Security

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

Title:
  Setting radio frequency IT in wifi card

Status in iw package in Ubuntu:
  New

Bug description:
  Hi,
  are in possession of the x201 notebook with the wireless card "Intel (R) 
Centrino (R) Advanced-N 6200 AGN, REV = 0x74" after upgrading to xubuntu 16.10 
I observed a slowdown in wireless connection. After several attempts and 
drivers checked:

  $ dmesg | grep firmware
  [3.040469] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [3.913823] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-6000-6.ucode failed with error -2
  [3.913880] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-6000-5.ucode failed with error -2
  [3.936700] iwlwifi :02:00.0: loaded firmware version 9.221.4.1 build 
25532 op_mode iwldvm

  $ dmesg | grep iwlwifi
  [3.894874] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [3.913823] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-6000-6.ucode failed with error -2
  [3.913880] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-6000-5.ucode failed with error -2
  [3.936700] iwlwifi :02:00.0: loaded firmware version 9.221.4.1 build 
25532 op_mode iwldvm
  [4.028640] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled
  [4.028643] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
  [4.028645] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
  [4.028647] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Advanced-N 
6200 AGN, REV=0x74
  [4.030910] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [4.416616] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
  [5.620886] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [5.621150] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [5.621242] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1
  [5.845019] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [5.845253] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [5.845344] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1

  and verified the /etc/modprobe.d/iwlwifi.conf configuration file:
  options iwlwifi swcrypto=1 11n_disable=8 bt_coex_active=0 led_mode=1

  without getting any improvement, reading on the internet I saw that the 
problem could be the frequencies of the wireless card, in fact across power of 
the NB I note:
  $ sudo iw reg get
  country DE: DFS-ETSI
     (2400 - 2483 @ 40), (N/A, 20), (N/A)
     (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
     (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
     (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
     (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  then run:
  $ sudo iw reg set IT

  $ sudo iw reg get
  country 98: DFS-ETSI
     (2402 - 2482 @ 40), (N/A, 20), (N/A)
     (5170 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
     (5250 - 5330 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
     (5490 - 5710 @ 160), (N/A, 26), (0 ms), DFS
     (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  after the command of "iw reg set IT" connect regains velocity having before 
upgrading to 16.10.
  At this point I changed the line "REGDOMAIN = IT" in /etc/default/cdra, but 
on reboot everything went back to the German frequencies DE. To solve I added 
temporarily in /etc/rc.local "iw reg set IT".

  Please could you fix it? Thank you

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

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

[Desktop-packages] [Bug 1462791] Re: Unity control center fails to rebind keys

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

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

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

Title:
  Unity control center fails to rebind keys

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

Bug description:
  A variety of predefined keys used by unity cannot be rebound.
  (Super+t, Super+w, pretty much anything used by Unity)

  If the user tries to rebind the keys using the unity-control-center ->
  keyboard -> shortcuts dialog, the keybindings will not function.

  The dialog should at least prevent the user from rebinding these keys.
  There is a workaround for binding the keys which involves digging
  around in compizconfig-settings-manager for the guilty keybinding. (
  http://askubuntu.com/questions/34145/can-i-define-keyboard-shortcuts-
  using-the-super-key )

  Ideally, the control center should interface with unity to allow
  binding the keys, there shouldn't be a separate configuration app.

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

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

[Desktop-packages] [Bug 1665402] Re: Own shortcut not working

2017-02-23 Thread Vej

I can reproduce this using xenial 16.04 with the german translation.

Reproduction steps:

* Execute "unity-control-center keyboard shortcuts" in a terminal.
* In the left menu select "own shortcuts" (or equivalent translation).
* Press the + to add a new shortcut. Name it "Test" and ad some valid command
like "unity-control-center"
* Select your new entry

What happens: The edit menu opens to edit the name and command

What should happen: The design changes indicating that the shortcut is
recorded.

Please note: This works fine with the predefined shortcuts in "unity-
control-center keyboard shortcuts".

Best Regards

Vej

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

** Tags added: xenial

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

Title:
Own shortcut not working

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

Bug description:
I do not know why the own-shortcuts not working. The only what i had
done in the system is removing the unity-webapps-common and a
autoremove after that.

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

[Desktop-packages] [Bug 1666882] Re: Setting radio frequency IT in wifi card

2017-02-23 Thread Massimo Cala'

** Information type changed from Public Security to Public

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

Title:
  Setting radio frequency IT in wifi card

Status in iw package in Ubuntu:
  New

Bug description:
  Hi,
  are in possession of the x201 notebook with the wireless card "Intel (R) 
Centrino (R) Advanced-N 6200 AGN, REV = 0x74" after upgrading to xubuntu 16.10 
I observed a slowdown in wireless connection. After several attempts and 
drivers checked:

  $ dmesg | grep firmware
  [3.040469] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [3.913823] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-6000-6.ucode failed with error -2
  [3.913880] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-6000-5.ucode failed with error -2
  [3.936700] iwlwifi :02:00.0: loaded firmware version 9.221.4.1 build 
25532 op_mode iwldvm

  $ dmesg | grep iwlwifi
  [3.894874] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
  [3.913823] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-6000-6.ucode failed with error -2
  [3.913880] iwlwifi :02:00.0: Direct firmware load for 
iwlwifi-6000-5.ucode failed with error -2
  [3.936700] iwlwifi :02:00.0: loaded firmware version 9.221.4.1 build 
25532 op_mode iwldvm
  [4.028640] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled
  [4.028643] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
  [4.028645] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
  [4.028647] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Advanced-N 
6200 AGN, REV=0x74
  [4.030910] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [4.416616] iwlwifi :02:00.0 wlp2s0: renamed from wlan0
  [5.620886] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [5.621150] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [5.621242] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1
  [5.845019] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [5.845253] iwlwifi :02:00.0: L1 Enabled - LTR Disabled
  [5.845344] iwlwifi :02:00.0: Radio type=0x1-0x3-0x1

  and verified the /etc/modprobe.d/iwlwifi.conf configuration file:
  options iwlwifi swcrypto=1 11n_disable=8 bt_coex_active=0 led_mode=1

  without getting any improvement, reading on the internet I saw that the 
problem could be the frequencies of the wireless card, in fact across power of 
the NB I note:
  $ sudo iw reg get
  country DE: DFS-ETSI
     (2400 - 2483 @ 40), (N/A, 20), (N/A)
     (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
     (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
     (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
     (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  then run:
  $ sudo iw reg set IT

  $ sudo iw reg get
  country 98: DFS-ETSI
     (2402 - 2482 @ 40), (N/A, 20), (N/A)
     (5170 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
     (5250 - 5330 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
     (5490 - 5710 @ 160), (N/A, 26), (0 ms), DFS
     (57000 - 66000 @ 2160), (N/A, 40), (N/A)

  after the command of "iw reg set IT" connect regains velocity having before 
upgrading to 16.10.
  At this point I changed the line "REGDOMAIN = IT" in /etc/default/cdra, but 
on reboot everything went back to the German frequencies DE. To solve I added 
temporarily in /etc/rc.local "iw reg set IT".

  Please could you fix it? Thank you

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

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

[Desktop-packages] [Bug 1662750] Re: Remove 3rd party / non-free license warnings and just show license as Unknown

Could you add some details about the steps you took to verify the fix
and for which release you verified?

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

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

Title:
  Remove 3rd party / non-free license warnings and just show license as
  Unknown

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

Bug description:
  [Impact]
  GNOME Software currently shows a large warning about software being 3rd party 
/ non-free when the license information is shown. This is occurring for all 
snaps due to bug 167. This is misleading and would be simpler to just state 
the license is "Unknown".

  [Test Case]
  1. Open GNOME Software and select a snap (e.g. moon-buggy)

  Expected result:
  moon-buggy is shown with an unknown license.

  Observed result:
  A large warning is shown about it being 3rd party / non-free.

  [Regression potential]
  Low. We now hide the warning and show the license field even when it is 
unkown.

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

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

[Desktop-packages] [Bug 1662749] Re: GNOME Software has entry in Startup Applications

Could add you details about what steps you took to verify the bug was
fixed and for which release you verified the fix?

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

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

Title:
  GNOME Software has entry in Startup Applications

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  GNOME Software shows in the startup applications list and can be disabled. 
This is a feature that should not be easily disabled by the user.

  [Test Case]
  1. Open Startup Applications

  Expected result:
  GNOME Software is not shown

  Observed result:
  GNOME Software is shown and can be disabled.

  [Regression Potential]
  Low - this just hides this entry.

  If a user had disabled the gnome-software service from automatically starting 
in the background, it will now be more difficult to re-enable it.
  rm ~/.config/autostart/gnome-software-service.desktop

  The gnome-software service is a bit heavy (LP: #1592678) so some users
  do disable it. The downside is that by disabling it, the Software app
  takes much longer to start.

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

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

[Desktop-packages] [Bug 1590462] Re: City search “Hospitalet” doesn’t find L'Hospitalet de Llobregat

This bug was fixed in the package geonames - 0.2+17.04.20170220-0ubuntu1

---
geonames (0.2+17.04.20170220-0ubuntu1) zesty; urgency=medium

  * Be less strict on city search (LP: #1590462)

 -- Albert Astals Cid   Mon, 20 Feb 2017
11:07:52 +

** Changed in: geonames (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  City search “Hospitalet” doesn’t find  L'Hospitalet de Llobregat

Status in Ubuntu UX:
  Fix Released
Status in geonames package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  The official name of my city is 
L'Hospitalet de Llobregat
  but it is often usually written as
Hospitalet de Llobregat

  On the wizard city/timezone selection window we only search from the 
beginning of the string so I could not find my city until i realized i may have 
to type the
L'
  at the beginning.

  : “As with any search
  field, any series of letters immediately followed by a space or
  punctuation character should match only complete words, while any
  series of letters at the end of the string should match both complete
  words and the beginnings of words. (In the terms being searched, a
  “word” is a series of letters that is immediately preceded by the
  start of the string or any non-letter character, and immediately
  followed by the end of the string or any non-letter character.)”

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

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

[Desktop-packages] [Bug 1667499] [NEW] the difference between 1.38 and 1.5 dpi in the displays settings is huge

2017-02-23 Thread graingert

Public bug reported:

1.38 is far too small, 1.5 is far too big.

I used to use 1.62 on ubuntu 16.10 and that was fine.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu Feb 23 22:25:26 2017
DistUpgraded: 2017-02-23 15:19:02,158 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
InstallationDate: Installed on 2017-02-13 (10 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
 Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-8-generic.efi.signed 
root=/dev/mapper/lvm-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to zesty on 2017-02-23 (0 days ago)
dmi.bios.date: 12/23/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0167.B21.1612230252
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B21.1612230252:bd12/23/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple 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.75-1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.4-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
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.8.0-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.13-1
xserver.bootTime: Thu Feb 23 22:23:05 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu9
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 reproducible single-occurrence ubuntu 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/1667499

Title:
  the difference between 1.38 and 1.5 dpi in the displays settings is
  huge

Status in xorg package in Ubuntu:
  New

Bug description:
  1.38 is far too small, 1.5 is far too big.

  I used to use 1.62 on ubuntu 16.10 and that was fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Thu Feb 23 22:25:26 2017
  DistUpgraded: 2017-02-23 15:19:02,158 DEBUG icon theme changed, re-reading
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
  InstallationDate: Installed on 2017-02-13 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:000

[Desktop-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-23 Thread Steve Langasek

As I recall resolved is also enabled by default in Ubuntu Server 16.10
(though not on Desktop), so this is a critical issue there as well.
Dimitri, could you please have a look at this backport?

Could someone who's seeing the DNSSEC problem please also file a
separate bug report, so we can track that problem separately?

** Also affects: network-manager (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

** Changed in: systemd (Ubuntu Yakkety)
Milestone: None => yakkety-updates

** Changed in: systemd (Ubuntu Yakkety)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  New
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Desktop-packages] [Bug 1667505] [NEW] Files and Trash hang

2017-02-23 Thread peterzay

Public bug reported:

Clicking on Files or Trash icons in launcher occasionally does nothing.

This is intermittent and not reproducible.  It has happened twice since
a recent fresh install of 16.04.2.  The system generally seems to have
to run all day before getting this bug.

This behaviour is new to 16.04.2 and was not present in 16.04.

The solution is to reboot.

If someone can give instructions on what to analyze prior to shutdown,
we may be able to solve this today.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 23 17:38:43 2017
EcryptfsInUse: Yes
GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+1030+502'"
InstallationDate: Installed on 2017-02-17 (6 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Files and Trash hang

Status in nautilus package in Ubuntu:
  New

Bug description:
  Clicking on Files or Trash icons in launcher occasionally does
  nothing.

  This is intermittent and not reproducible.  It has happened twice
  since a recent fresh install of 16.04.2.  The system generally seems
  to have to run all day before getting this bug.

  This behaviour is new to 16.04.2 and was not present in 16.04.

  The solution is to reboot.

  If someone can give instructions on what to analyze prior to shutdown,
  we may be able to solve this today.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-39.42~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 23 17:38:43 2017
  EcryptfsInUse: Yes
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+1030+502'"
  InstallationDate: Installed on 2017-02-17 (6 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever

2017-02-23 Thread Tobias Weis

Is there anything we can do to help fix this, do you need additional
info? Or what exactly is the case there has not even been a status
update in the last YEARS? Given that this is the most basic
functionality and affects _all_ users, I wonder why not even the
importance has been set?

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

Title:
  cut-n-paste move files got stuck forever

Status in nautilus package in Ubuntu:
  Confirmed
Status in pcmanfm package in Ubuntu:
  Confirmed

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in

2017-02-23 Thread Cruz Fernandez

@mikhaildd have you tried to select Settings->Sound->Headphones ?

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

Title:
  No sound via headphones (headset) when Ubuntu boots with them plugged
  in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The bug is twofold, first when computer boots if the headset
  (headphones with built-in mic, one audio jack) is plugged in, then
  there is no sound (via headphones or otherwise). If you plug
  headphones out and back in, then it usually works as expected.

  The second scenario is the same, except that plugging out and back in
  again doesn't help. In that case, I just restart the laptop, then plug
  them back in again and it works.

  In all cases, microphone works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 19 22:13:20 2016
  InstallationDate: Installed on 2016-05-07 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  crunch 3248 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-23 Thread Steve Langasek

I was reminded that libnss-resolve is in 'standard' now, which means
it's also installed by default on server and any bugs that affect only
the stub DNS resolver without affecting the dbus service - such as this
one - do not impact DNS resolution by default on server in 16.10.

(I was wondering why no one had reported it before now.)

So, I'm downgrading this from critical to high since it only hits users
of 16.10 server in a few corner cases (i.e. containers, chroots without
libnss-resolve installed).  It should still be SRUed.

** Changed in: systemd (Ubuntu Yakkety)
   Importance: Critical => High

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

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Desktop-packages] [Bug 1667129] Re: Python cannot create NMGtkWifiDialog

2017-02-23 Thread Jeremy Soller

Sure thing.

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

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

Title:
  Python cannot create NMGtkWifiDialog

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

Bug description:
  Python, using pygobject, is unable to spawn an NMGtkWifiDialog using
  the new function, due to the SSID setting not being settable
  (GArray is not supported by pygobject). If the SSID is not
  set, the dialog will not display correctly, and will not function.

  A potential fix is to copy the SSID from the AP information if
  present.

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

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

[Desktop-packages] [Bug 1667129] Re: Python cannot create NMGtkWifiDialog

2017-02-23 Thread Jeremy Soller

I created an upstream bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=779153

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

Title:
  Python cannot create NMGtkWifiDialog

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

Bug description:
  Python, using pygobject, is unable to spawn an NMGtkWifiDialog using
  the new function, due to the SSID setting not being settable
  (GArray is not supported by pygobject). If the SSID is not
  set, the dialog will not display correctly, and will not function.

  A potential fix is to copy the SSID from the AP information if
  present.

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

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

[Desktop-packages] [Bug 1586570] Re: openvpn chroot does not have a valid resolv.conf

2017-02-23 Thread Paul Crawford

I am seeing this with 64-bit 14.04.5 (even though 'grheard' did not have
this problem with 14.04) using OpenVPN via the network manager. Seems to
happen independently of DHCP renewals as several were logged before this
last bit:

Feb 23 19:31:03 paul-ubuntu dhclient: DHCPREQUEST of 192.168.1.100 on eth1 to 
192.168.1.1 port 67 (xid=0xacb31f1)
Feb 23 19:31:03 paul-ubuntu dhclient: DHCPACK of 192.168.1.100 from 192.168.1.1
Feb 23 19:31:03 paul-ubuntu dhclient: bound to 192.168.1.100 -- renewal in 1379 
seconds.
Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:  (eth1): DHCPv4 state 
changed renew -> renew
Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:address 192.168.1.100
Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:prefix 24 
(255.255.255.0)
Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:gateway 192.168.1.1
Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:hostname 'Desktop'
Feb 23 19:31:03 paul-ubuntu NetworkManager[1577]:nameserver 
'192.168.1.1'
Feb 23 19:31:03 paul-ubuntu dbus[1306]: [system] Activating service 
name='org.freedesktop.nm_dispatcher' (using servicehelper)
Feb 23 19:31:03 paul-ubuntu dbus[1306]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Feb 23 19:34:32 paul-ubuntu nm-openvpn[2357]: [server] Inactivity timeout 
(--ping-restart), restarting
Feb 23 19:34:32 paul-ubuntu nm-openvpn[2357]: SIGUSR1[soft,ping-restart] 
received, process restarting
Feb 23 19:34:34 paul-ubuntu nm-openvpn[2357]: NOTE: the current 
--script-security setting may allow this configuration to call user-defined 
scripts
Feb 23 19:34:54 paul-ubuntu nm-openvpn[2357]: RESOLVE: Cannot resolve host 
address: : Temporary failure in name resolution

This fault continued through several more DHCP renewals until I manually
reset the link:

Feb 23 23:04:11 paul-ubuntu nm-openvpn[2357]: message repeated 502 times: [ 
RESOLVE: Cannot resolve host address: : Temporary failure in name 
resolution]
Feb 23 23:04:26 paul-ubuntu nm-openvpn[2357]: RESOLVE: signal received during 
DNS resolution attempt
Feb 23 23:04:26 paul-ubuntu avahi-daemon[1439]: Withdrawing workstation service 
for tun0.
Feb 23 23:04:26 paul-ubuntu NetworkManager[1577]:SCPlugin-Ifupdown: devices 
removed (path: /sys/devices/virtual/net/tun0, iface: tun0)

So manually disconnecting and reconnecting the VPN works, but is
obviously not a satisfactory solution for machines that are normally
unattended or if you wish to maintain privacy!

System details:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename:   trusty

$ apt-cache policy openvpn
openvpn:
  Installed: 2.3.2-7ubuntu3.1
  Candidate: 2.3.2-7ubuntu3.1
  Version table:
 *** 2.3.2-7ubuntu3.1 0
500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2.3.2-7ubuntu3 0
500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

Title:
  openvpn chroot does not have a valid resolv.conf

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

Bug description:
  If you leave openvpn running for long enough it will eventually begin
  to fail with output like:

  May 27 19:16:54 wakko nm-openvpn[16480]: RESOLVE: Cannot resolve host
  address: : Temporary failure in name resolution

  Analysis shows this is because openvpn is sending DNS queries to
  127.0.0.1:

  socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 8
  connect(8, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  poll([{fd=8, events=POLLOUT}], 1, 0)= 1 ([{fd=8, revents=POLLOUT}])
  sendto(8, ..., 30, MSG_NOSIGNAL, NULL, 0) = 30

  However, this is not correct, dnsmasq listens on 127.0.1.1.

  It appears the a cause of this is the chroot, the chroot has no
  resolv.conf in it and the glibc default is to use  127.0.0.1

  openvpn does a DNS query before chroot'ing which used to be enough to
  cache resolv.conf forever. I wonder if something has changed in glibc
  recently to cause the resolv.conf to be reloaded (eg Debian apparently
  has a patch that does this)

  A work around would be to copy the system resolv.conf into
  /var/lib/openvpn/chroot before starting openvpn

  Seen on Xenial and a few prior versions.

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

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

[Desktop-packages] [Bug 75850] Re: Pidgin should support OS keyrings

2017-02-23 Thread Richard Laager

** Changed in: pidgin (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Pidgin should support OS keyrings

Status in Gaim:
  Won't Fix
Status in Pidgin:
  New
Status in gaim package in Ubuntu:
  Invalid
Status in pidgin package in Ubuntu:
  Fix Released

Bug description:
  Pidgin should support GNOME Keyring, KWallet, etc.

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

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

[Desktop-packages] [Bug 1667528] [NEW] /usr/bin/nm-applet:11:malloc_printerr:_int_free:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all

2017-02-23 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager-applet.  This problem was most recently seen with package 
version 1.2.0-0ubuntu0.16.04.4, the problem page at 
https://errors.ubuntu.com/problem/4dbb9121aa99599c4ed46ae754412f0dfee568e2 
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: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial

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

Title:
  /usr/bin/nm-
  
applet:11:malloc_printerr:_int_free:g_hash_table_remove_all_nodes:g_hash_table_remove_all_nodes:g_hash_table_remove_all

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
network-manager-applet.  This problem was most recently seen with package 
version 1.2.0-0ubuntu0.16.04.4, the problem page at 
https://errors.ubuntu.com/problem/4dbb9121aa99599c4ed46ae754412f0dfee568e2 
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/network-manager-applet/+bug/1667528/+subscriptions

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

[Desktop-packages] [Bug 1664060] Re: Can't see view message pane in Evolution after most recent apt-get upgrade

2017-02-23 Thread m...@papersolve.com

The latest batch of updates today (which included libwebkit2gtk updates)
fixed the Evolution message pane display problem for me, yay!

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

Title:
  Can't see view message pane in Evolution after most recent apt-get
  upgrade

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  someone on arch is describing the exact same issue whereby a package
  is updated, after the update evolution doesn't show any information in
  the message pane. Similar to what is reported on an arch forum here:
  https://bbs.archlinux.org/viewtopic.php?id=223046

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evolution 3.22.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Feb 12 15:43:07 2017
  InstallationDate: Installed on 2017-01-12 (31 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170111)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1661486] Re: nouveau write fault, CTXSW_TIMEOUT, hangs the display

2017-02-23 Thread Daniel Barrett

I switched from nouveau to the proprietary nvidia driver (nvidia-375),
and the crashes have stopped.

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

Title:
  nouveau write fault, CTXSW_TIMEOUT, hangs the display

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

Bug description:
  A few hours after upgrading to the latest kernel and plasma (using apt
  upgrade) in Xenial 16.04LTS, my computer display hung with:

  Feb  2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo: 
write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS] reason 02 [PTE] 
on channel 2 [007f9a3000 Xorg[1501]]
  Feb  2 20:36:16 snorkack kernel: [83600.290221] nouveau :01:00.0: fifo: 
gr engine fault on channel 2, recovering...
  Feb  2 20:33:42 snorkack colord[1394]: (colord:1394): Cd-WARNING **: failed 
to get session [pid 27934]: No such device or address
  Feb  2 20:36:19 snorkack vmnet-dhcpd: DHCPREQUEST for 192.168.50.128 from 
00:0c:29:d5:2d:15 via vmnet8
  Feb  2 20:36:19 snorkack vmnet-dhcpd: DHCPACK on 192.168.50.128 to 
00:0c:29:d5:2d:15 via vmnet8
  Feb  2 20:36:20 snorkack kernel: [83604.585547] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:20 snorkack kernel: [83604.585553] nouveau :01:00.0: fifo: 
sw engine fault on channel 8, recovering...
  Feb  2 20:36:22 snorkack kernel: [83606.583732] nouveau :01:00.0: fifo: 
runlist 0 update timeout
  Feb  2 20:36:24 snorkack kernel: [83608.880576] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:29 snorkack kernel: [83613.175601] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:33 snorkack kernel: [83617.470624] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:37 snorkack kernel: [83621.765648] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb  2 20:36:42 snorkack kernel: [83626.060672] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  ...repeats many times...

  I could still log in via SSH but could not unhang the system, so I
  rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  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
  CurrentDesktop: KDE
  Date: Thu Feb  2 23:20:22 2017
  InstallationDate: Installed on 2016-09-25 (131 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1661486/+subscriptions

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

[Desktop-packages] [Bug 997200] Re: [FFe] Add NetworkManager connectivity config package

2017-02-23 Thread Bryan Quigley

I agree, about splitting off other bugs that take advantage of this
feature.  There is already a whoopsie bug for instance -
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481.

Not everything needs to use this (immediately) for it to be useful.
(huge +1 to this change btw)

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

Title:
  [FFe] Add NetworkManager connectivity config package

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in update-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Precise:
  Won't Fix
Status in update-manager source package in Precise:
  Won't Fix
Status in network-manager source package in Quantal:
  Won't Fix
Status in update-manager source package in Quantal:
  Won't Fix
Status in network-manager source package in Raring:
  Won't Fix
Status in update-manager source package in Raring:
  Won't Fix

Bug description:
  Feature
  ===
  A separate network-manager-config-connectivity package that contains the 
3-line config snippet to enable NetworkManager's connectivity check. This is 
the same approach taken by Fedora since 2014 (their package is named 
config-connectivity-fedora).

  jbicha would like to have ubuntu-gnome-desktop recommend this package for 
zesty. With this config, GNOME Shell will popup a browser page when a captive 
portal is detected. The browser page is powered by webkit2gtk.
  https://help.gnome.org/misc/release-notes/3.14/#captive-portals

  By making it a separate package, it is very easy for Ubuntu flavors to
  opt in to installing it by default if they choose. And it's very easy
  for users to opt in or out without needing to mess around with system
  configuration files.

  This new feature (and how to opt out) will be mentioned in Ubuntu
  GNOME's Release Notes.

  Enabling the connectivity check by default for all of Ubuntu was discussed 
almost 5 years ago:
  https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html

  Link to new discussion:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html

  Git merge proposal attached.

  Original Bug Report
  ==
  When in a hotel there is a often a T&Cs page that is delivered when 
connecting to the network.  Some combination of network manager and update 
manager (or something else entirely) doesn't seem to be able to handle this, 
and update are left in a non-working state after not being able to read package 
headers file.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 17:27:02 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IpRoute:
   default via 10.155.32.1 dev wlan0  proto static
   10.155.32.0/19 dev wlan0  proto kernel  scope link  src 10.155.38.82  metric 
2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1635715] Re: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020

2017-02-23 Thread chris pollock

As you can see this is still happening

Feb 23 18:21:40 localhost gnome-settings-daemon.desktop[2991]: 
(gnome-settings-daemon:2991): color-plugin-WARNING **: failed to connect to 
device: Failed to connect to missing device 
/org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
Feb 23 18:21:40 localhost gnome-settings-daemon.desktop[2991]: 
(gnome-settings-daemon:2991): color-plugin-WARNING **: failed to connect to 
device: Failed to connect to missing device 
/org/freedesktop/ColorManager/devices/cups_PDF

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

2017-02-23 Thread Jeremy Bicha

The network-manager connectivity config bug is bug 997200 and I
restarted the ubuntu-devel discussion yesterday.

Therefore, I'm closing the network-manager task here.

** No longer affects: network-manager (Ubuntu)

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Whoopsie:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

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

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

[Desktop-packages] [Bug 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)

** Summary changed:

- [enhancement] Missing client API for relative surface movement
+ [enhancement] Missing client API for relative surface movement (e.g. dragging 
client-decorated windows)

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

Title:
  [enhancement] Missing client API for relative surface movement (e.g.
  dragging client-decorated windows)

Status in Mir:
  Incomplete
Status in MirAL:
  Incomplete
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Mir needs a client API to allow surfaces to move themselves
  relatively. This is required to support full client-side decorations
  (bug 1398849), and also other apps like Google Chrome and Gnome
  Nautilus which can be dragged using part of their client areas.

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

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

[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2017-02-23 Thread Czikus

The problem was solved for me by installing pulseaudio 8.0 from sources,
without Ubuntu patches. No need to re-connect the headphones or use the
workaround script anymore.

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

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Desktop-packages] [Bug 1636666] Re: [MIR] pcre2

2017-02-23 Thread Mathieu Trudel-Lapierre

I understand the concerns, and I share them, but I don't think we should
alone make the decision. Perhaps bring this up for wider discussion on
the ubuntu-devel mailing list?

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

Title:
  [MIR] pcre2

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in pcre2 package in Ubuntu:
  Incomplete
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Availability
  
  Synced with Debian. Built for all supported architectures.

  Rationale
  =
  Required by gnome-terminal 3.22+ and vte2.91 0.46+

  Security
  
  At least one open security issue, affecting Ubuntu 16.04 LTS
  https://people.canonical.com/~ubuntu-security/cve/pkg/pcre2.html
  https://security-tracker.debian.org/tracker/source-package/pcre2
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pcre

  Quality assurance
  =
  - Please subscribe Ubuntu Desktop Bugs or Ubuntu Foundation Bugs (like pcre3) 
to this package.
  https://bugs.launchpad.net/ubuntu/+source/pcre2
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pcre2

  Upstream tests are run during the build but there is no autopkgtest

  Does not have 3.0 (quilt) set

  Dependencies
  
  Only build-dependencies are dpkg and debhelper. No other added dependencies.

  Standards compliance
  
  3.9.6

  Maintenance
  ===
  - Actively developed upstream
  http://pcre.org/

  Background information
  ==
  As the package description states, the older version of this library is 
confusingly named pcre3 in Debian/Ubuntu. pcre3 is already in Ubuntu main.

  Other Info
  ==
  In the original release of pcre2 in Jan 2015, the author says this is not 
just a drastic update to the original pcre but a "new project". He felt free to 
change names and options.
  https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html

  pcre3 has gotten some bugfix releases since then (from 8.36 to 8.40
  released Jan 2017)

  Some discussion of how it's different:
  http://www.regular-expressions.info/pcre2.html

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

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

[Desktop-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-02-23 Thread Harm van Bakel

I also tested 1.2.6-0ubuntu0.16.04.1 and unfortunately it seems to break
suspend on my system. Instead of suspending, the system goes into a
forced reboot.

** Tags removed: verification-done xenial
** Tags added: verification-failed-xenial

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

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

[Desktop-packages] [Bug 1667180] Re: Image flickering with 50 Hz lighting

2017-02-23 Thread Bug Watch Updater

** Changed in: cheese
   Status: Confirmed => Incomplete

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

Title:
  Image flickering with 50 Hz lighting

Status in Cheese:
  Incomplete
Status in cheese package in Ubuntu:
  Triaged

Bug description:
  https://youtu.be/RJU-JmSPF2k

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cheese 3.18.1-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 23 02:44:20 2017
  InstallationDate: Installed on 2016-05-02 (296 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: MEDIONPC MS-7358
  RelatedPackageVersions:
   cheese3.18.1-2ubuntu3
   cheese-common 3.18.1-2ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

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

[Desktop-packages] [Bug 1636666] Re: [MIR] pcre2

2017-02-23 Thread Mathieu Trudel-Lapierre

To be clear, I share doko's feeling against having two versions of the
library in main if it can be avoided -- this is certainly not a
permanent situation, but most things don't appear to have switched to
pcre2 just yet (and I would expect they would in the near-ish term). In
that sense, I'd be more in favor of not upgrading vte/gnome-terminal for
the time being.

To make it simpler: how do we value the benefits of a new pcre2 in main
(meaning possibly some new features of gnome-terminal and vte) against
the (probably small, but still) maintenance burden of having two PCRE
libraries in main or the need to hold gnome-terminal and vte back for
this cycle?

To me wearing the MIR team hat, the benefits don't outweigh the
increased maintenance work (ie. you can do nothing to vte and gnome-
terminal, and we're good), especially when you consider that pcre is the
kind of thing that does tend to have CVEs every once in a while[1].

On the other hand, new features are shiny, but they look to me like they
might be cherry-pickable. I'm open to be convinced, and the security
team probably should have a say in it too (hence my suggestion of
bringing it up on the mailing list).

[1] http://www.cvedetails.com/product/5715/Pcre-Pcre.html?vendor_id=3265

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

Title:
  [MIR] pcre2

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in pcre2 package in Ubuntu:
  Incomplete
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  Availability
  
  Synced with Debian. Built for all supported architectures.

  Rationale
  =
  Required by gnome-terminal 3.22+ and vte2.91 0.46+

  Security
  
  At least one open security issue, affecting Ubuntu 16.04 LTS
  https://people.canonical.com/~ubuntu-security/cve/pkg/pcre2.html
  https://security-tracker.debian.org/tracker/source-package/pcre2
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=pcre

  Quality assurance
  =
  - Please subscribe Ubuntu Desktop Bugs or Ubuntu Foundation Bugs (like pcre3) 
to this package.
  https://bugs.launchpad.net/ubuntu/+source/pcre2
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pcre2

  Upstream tests are run during the build but there is no autopkgtest

  Does not have 3.0 (quilt) set

  Dependencies
  
  Only build-dependencies are dpkg and debhelper. No other added dependencies.

  Standards compliance
  
  3.9.6

  Maintenance
  ===
  - Actively developed upstream
  http://pcre.org/

  Background information
  ==
  As the package description states, the older version of this library is 
confusingly named pcre3 in Debian/Ubuntu. pcre3 is already in Ubuntu main.

  Other Info
  ==
  In the original release of pcre2 in Jan 2015, the author says this is not 
just a drastic update to the original pcre but a "new project". He felt free to 
change names and options.
  https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html

  pcre3 has gotten some bugfix releases since then (from 8.36 to 8.40
  released Jan 2017)

  Some discussion of how it's different:
  http://www.regular-expressions.info/pcre2.html

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

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

[Desktop-packages] [Bug 1667551] [NEW] can not install software

2017-02-23 Thread jeffrey morgan

Public bug reported:

ubuntu-software has stopped working, and i can not activate the chrome
download, or some other downloiads

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Feb 24 03:14:45 2017
DistUpgraded: Fresh install
DistroCodename: yakkety
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] 
(rev 04) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller 
[8086:4556]
InstallationDate: Installed on 2017-01-28 (26 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic 
root=UUID=e3ec930f-65d9-4c05-882b-afb1e148de81 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/29/2005
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
dmi.board.name: D915GEV
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC63667-503
dmi.chassis.type: 2
dmi.modalias: 
dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GEV:rvrAAC63667-503:cvn:ct2:cvr:
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Fri Feb 24 02:12:24 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputChicony HP Elite USB Keyboard KEYBOARD, id 8
 inputChicony HP Elite USB Keyboard KEYBOARD, id 9
 inputUSB Optical MouseMOUSE, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1

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


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

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

Title:
  can not install software

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu-software has stopped working, and i can not activate the chrome
  download, or some other downloiads

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb 24 03:14:45 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] 
(rev 04) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82915G/GV/910GL Integrated Graphics 
Controller [8086:4556]
  InstallationDate: Installed on 2017-01-28 (26 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic 
root=UUID=e3ec930f-65d9-4c05-882b-afb1e148de81 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2005
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
  dmi.board.name: D915GEV
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAC63667-503
  dmi.chassi

[Desktop-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-02-23 Thread Jeremy Bicha

Harm, can you find any logs that indicate that network-manager has
anything to do with that? Is that problem reliably reproducible with the
updated network-manager but not with the older network-manager?

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

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

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

And my verbose pulseaudio log when reproducing the error. Let me know if
there's anything else I can help with.

** Attachment added: "pulseverbose.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+attachment/4825565/+files/pulseverbose.log

-- 
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 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/ubuntu/+source/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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

I'm attaching my crash dump here. It looks very similar to Fabio's.

** Attachment added: "_usr_bin_pulseaudio.1001.crash"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+attachment/4825563/+files/_usr_bin_pulseaudio.1001.crash

-- 
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 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/ubuntu/+source/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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

It looks like my alsa_info is included in the crash dump, but here it is
anyway.

** Attachment added: "alsa-info.txt.iuKCT60EYU"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+attachment/4825564/+files/alsa-info.txt.iuKCT60EYU

-- 
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 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/ubuntu/+source/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 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-02-23 Thread Alex Tu

Hi Harm, could you please provide the detail information about the hardware 
which issue happened on? 
ex. 
* what's the platform brand and what's network devices?
* lspci -vvvnn, lsusb -vvv, and the /var/syslog

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in OEM Priority Project:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Yakkety:
  Fix Released

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  Also, as this is a general point release update, cases described in
  https://wiki.ubuntu.com/NetworkManager/DistroTesting should be used
  for smoke testing.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

  needed by:
  lp #1647283

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1645698/+subscriptions

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

[Desktop-packages] [Bug 1607681] Re: Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and Calculator

Fixed?

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: Confirmed => Incomplete

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

Title:
  Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot
  and Calculator

Status in Ubuntu:
  Incomplete

Bug description:
  Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot
  and Calculator

  Just run '/usr/games/sol' under Mir.

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

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

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

Ok, I've been playing around with it, and here's what I've been able to
interpret. The error only happens when, after connecting my headset
after a startup, I choose "headset" in the attached prompt. The error
*doesn't* happen if I choose "headphones" instead.

** Attachment added: "headphone-headset-microphone-prompt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+attachment/4825659/+files/Screenshot%20from%202017-02-23%2022-39-31.png

-- 
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 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/ubuntu/+source/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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

This is the log when I instead choose the "headphones" option, and I get
no error. Audio works great, but the microphone doesn't.

-- 
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 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/ubuntu/+source/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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()

This is the log when I instead choose the "headphones" option, and I get
no error. Audio works great, but the microphone doesn't.

** Attachment added: "pulseverbose.headphones.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1539209/+attachment/4825660/+files/pulseverbose.headphones.log

-- 
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 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/ubuntu/+source/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 1667585] [NEW] [unity8] dolphin visual noise while zooming in/out

You have been subscribed to a public bug:

Ubuntu 17.04 unity8
launch dolphin, zoom in/out (ctrl+/ctrl-)

you'll see some visual noise, see attached screenshot

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
[unity8] dolphin visual noise while zooming in/out
https://bugs.launchpad.net/bugs/1667585
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gtk+3.0 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 1667585] Re: [unity8] dolphin visual noise while zooming in/out

If not a bug in the app then that's likely to be a bug in the Mir code
path for GTK.

** Package changed: qtubuntu (Ubuntu) => gtk+3.0 (Ubuntu)

** Tags added: gtk-mir visual-quality

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

Title:
  [unity8] dolphin visual noise while zooming in/out

Status in Canonical System Image:
  New
Status in dolphin package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 unity8
  launch dolphin, zoom in/out (ctrl+/ctrl-)

  you'll see some visual noise, see attached screenshot

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

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

[Desktop-packages] [Bug 1662874] Re: gnome-calendar crashed with SIGSEGV in gcal_manager_refresh()

2017-02-23 Thread Khurshid Alam

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

If this is duplicate bug where is the original bug report?

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

Title:
  gnome-calendar crashed with SIGSEGV in gcal_manager_refresh()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Distributor ID:   Ubuntu Budgie
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04
  Codename: zesty

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-calendar 3.22.2-1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Wed Feb  8 12:20:44 2017
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-01-07 (31 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170107)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   LANG=pt_PT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x55f101ede4d8 :  mov
0x18(%rdi),%rdi
   PC (0x55f101ede4d8) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gcal_manager_refresh ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in gcal_manager_refresh()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1667585] Re: [unity8] dolphin visual noise while zooming in/out