[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-05 Thread Nicholas Stommel
Well, scratch that hope and consider me mistaken about Goth Queen's workaround. 
It appears that manually setting a fixed DNS server DOES allow for successful 
reconnect when the network manager is restarted (whereas before it wouldn't 
reconnect period), but just like this bug 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241 name 
resolution (not using the dnscrypt-proxy service, just a fixed DNS address) 
fails after waking up from suspend for some frustrating, arcane reason. I have 
downgraded the following packages:
(credit to Kostadin Stoilov)
sudo apt install network-manager=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm-glib-vpn1=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm-glib4=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm0=1.2.2-0ubuntu0.16.04.4
sudo apt install libnm-util2=1.2.2-0ubuntu0.16.04.4
sudo apt install resolvconf=1.78ubuntu2

and held them in place with 'sudo apt-mark hold' for the time being, as
there appears to be a critical flaw in the updated versions of network-
manager and possibly resolv-conf and dnsmasq. I suppose we just have to
wait until something is fixed.

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1677175] Re: network-manager 1.2.6 won't connect to vpn and displays false connected message

2017-04-05 Thread Nicholas Stommel
** No longer affects: linux (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/1677175

Title:
  network-manager 1.2.6 won't connect to vpn and displays false
  connected message

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have been having a rather serious and incredibly annoying problem on the 
updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to 
manually connect to my VPN provider using openvpn through the network manager 
fails literally any time except bootup. Every godforsaken time. Waking the 
computer from suspend results in the network manager 'reconnecting' but no 
actual internet connection. Restarting the network manager using 'sudo service 
network-manager restart' sometimes doesn't work at all and I actually have to 
reboot the computer for it to connect to the internet. Despite the icon showing 
that I'm connected, in actuality I have no internet connection and cannot load 
any web pages. 
  The critical thing is that this issue isn't present at all on v1.2.2, which I 
have downgraded to and used 'apt-mark hold' to keep it in place. I'm 
disappointed that the newer default version is so unstable. Any insight or 
confirmation of this issue would be appreciated.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-19 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: network-manager 1.2.2-0ubuntu0.16.04.4
  PackageArchitecture: amd64
  Tags:  xenial
  Uname: Linux 4.9.16 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-05 Thread Nicholas Stommel
Oops, Goth Queen actually provided a solution earlier, it was just difficult 
for me to understand at the time. Enter whatever fixed DNS server you want and
set 'Automatic (DHCP) addresses only' under IPv4 Settings in network-manager 
for the default network connection. So just manually entering in your VPN's DNS 
server (for PIA it's 209.222.18.222) or installing dnscrypt-proxy and choosing 
127.0.0.2 as the server both work. This seems an adequate workaround for now.

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1659316] Re: compiz

2017-04-05 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  compiz

Status in xorg package in Ubuntu:
  Expired

Bug description:
  i want start compiz but i have vesa driver installed

  Gathering information about your system...

   Distribution:  Ubuntu 15.10
   Desktop environment:   GNOME
   Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
   Driver in use: vesa
   Rendering method:  AIGLX

  Checking if it's possible to run Compiz on your system...  [SKIP]

  At least one check had to be skipped:
   Error: vesa driver in use

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jan 25 15:49:04 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  MachineType: Acer TravelMate 5730
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=dbf84782-3125-4254-83ec-9f0a4e9f125b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.19
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: TravelMate 5730
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Jan 25 15:07:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   32884 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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


[Desktop-packages] [Bug 1679622] Re: [unity8] aisleriot crashes with SIGABRT

2017-04-05 Thread dinamic
doesn't matter now.. mir is dead.. sorry for wasting your times guys

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

Title:
  [unity8] aisleriot crashes with SIGABRT

Status in aisleriot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  sol crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: aisleriot 1:3.22.1-1ubuntu1 [modified: 
usr/share/applications/sol.desktop]
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity8
  Date: Tue Apr  4 13:33:56 2017
  ExecutablePath: /usr/games/sol
  InstallationDate: Installed on 2016-12-12 (112 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: /usr/games/sol
  Signal: 6
  SourcePackage: aisleriot
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: sol crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-05 Thread Nicholas Stommel
Okay so since resolvconf and dmasq are not cooperating, I have resorted to 
using dnscrypt-proxy. Credit to QkiZ, the dnscrypt-proxy service works EVERY 
TIME and ignores the (completely broken) DNS resolution of dnsmasq and 
resolvconf. Even with the newest version of network-manager (1.2.6) on 16.04 
LTS and all its dependencies:
 network-manager
 libnm-glib-vpn1
 libnm-glib4
 libnm0
 libnm-util2
No more DNS resolution issues!
To apply this workaround (which actually also offers some security benefits 
against DNS leakage), use:
sudo apt install dnscrypt-proxy
In the network manager, select "Edit Connections", select the primary (non-VPN) 
network you use, click on the "IPv4 Settings" tab, change the "Method" tab to 
"Automatic (DHCP) addresses only", then add 127.0.0.2 to the "DNS servers:" 
box. Save your changes, then restart the connection by disabling and enabling 
networking. Now go to https://www.opendns.com/welcome/ and you should see a 
nice check mark.
Now, your network connection and VPN should work (meaning DNS resolution won't 
break on you) every single time you wake up from suspend or use 
sudo service network-manager restart
And if for some odd reason it's slow just restart the network manager 
repeatedly by aliasing that to something like 
alias nm-restart='sudo service network-manager restart' 
in your ~/.bash_aliases file. I know, annoying but at least DNS resolution 
actually works and the computer doesn't have to be literally restarted to 
connect to the internet. 
This isn't intended to be a fix, just a possible alternative for those of us 
who experience total DNS resolution failure using a vpn on 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/1671606

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1680301] [NEW] package thunderbird-locale-es-es 1:45.8.0+build1-0ubuntu0.16.10.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstal

2017-04-05 Thread Nico
Public bug reported:

Every time I boot my system I encounter this error. It popups every time
I boot my system

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: thunderbird-locale-es-es 1:45.8.0+build1-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nicosafull   1808 F pulseaudio
BuildID: 20170315131404
Channel: Unavailable
Date: Sat Apr  1 14:01:04 2017
DpkgTerminalLog:
 dpkg: error al procesar el paquete thunderbird-locale-es-es 
(--configure):
  El paquete está en un estado grave de inconsistencia - debe reinstalarlo
  antes de intentar su configuración.
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-06-09 (666 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
IpRoute:
 default via 192.168.0.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.13  metric 
600
NoProfiles: True
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird-locale-es-es 1:45.8.0+build1-0ubuntu0.16.10.1 failed 
to install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
UpgradeStatus: Upgraded to yakkety on 2017-02-28 (36 days ago)
dmi.bios.date: 08/10/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K53E.221
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K53E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53E.221:bd08/10/2012:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K53E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-package yakkety

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

Title:
  package thunderbird-locale-es-es 1:45.8.0+build1-0ubuntu0.16.10.1
  failed to install/upgrade: El paquete está en un estado grave de
  inconsistencia - debe reinstalarlo  antes de intentar su
  configuración.

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Every time I boot my system I encounter this error. It popups every
  time I boot my system

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: thunderbird-locale-es-es 1:45.8.0+build1-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicosafull   1808 F pulseaudio
  BuildID: 20170315131404
  Channel: Unavailable
  Date: Sat Apr  1 14:01:04 2017
  DpkgTerminalLog:
   dpkg: error al procesar el paquete thunderbird-locale-es-es 
(--configure):
El paquete está en un estado grave de inconsistencia - debe reinstalarlo
antes de intentar su configuración.
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-06-09 (666 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.13  metric 
600
  NoProfiles: True
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: 

[Desktop-packages] [Bug 1680295] Re: Xorg crashed with SIGABRT in OsAbort()

2017-04-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192

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 #1543192, 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/1680295/+attachment/4855874/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1543192
   Xorg crashed with SIGABRT in OsAbort()

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1680295

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xubuntu 17.04 beta 2 (Zesty Zapus) amd64

  Via PM800 chipset

  Video device:
  Trident ProVidia 9685 (Jaton TVGA9685PCI), PCI, 2MB?

  lspci:  00:09.0 VGA compatible controller: Trident Microsystems TGUI
  9660/938x/968x (rev d3)

  tty was an unreadable white screen with reversed corrupted text.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Apr  5 21:20:14 2017
  ExecutablePath: /usr/lib/xorg/Xorg
  InstallationDate: Installed on 2017-04-05 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x559be1d72590, argc=11, argv=0x7ffc08902b48, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc08902b38) at ../csu/libc-start.c:291
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1680288] [NEW] evince crashes on 'Type 3 font' error in PDF

2017-04-05 Thread Laura Derocher
Public bug reported:

I have a PDF that crashes Document Viewer repeatably at the same page.
Starting evince from console, I see these errors (at p.709, 719/958):

Syntax Error: Missing or invalid CharProcs dictionary in Type 3 font
Syntax Error: Weird page contents
evince: /build/buildd/cairo-1.13.0~20140204/src/cairo-scaled-font.c:459: 
_cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.
Aborted (core dumped)

MuPDF and Firefox also flag the font error, but don't crash. Firefox
says (at p.711, 721/958)

Warning: Error during font loading: Type3 font load error: TypeError:
this.stream.getByte is not a function  pdf.js:273:11

and MuPDF says (at p.712, 722/958)

error: syntaxerror: Type3 font missing CharProcs
error: cannot load type3 font (3207 0 R)
error: cannot set font
warning: Ignoring errors during rendering
warning: cannot draw text since font and size not set
error: syntaxerror: Type3 font missing CharProcs
error: cannot load type3 font (3207 0 R)
error: cannot set font
warning: cannot draw text since font and size not set
mupdf: warning: Errors found on page
warning: cannot render glyph

I attached a bit of a PDF that triggers this. Evince will crash when it
reaches p.708 (9/16 in the extract). MuPDF and Firefox will throw errors
at p.712 but won't crash. (idk why it's not the same.)

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

** Attachment added: "Silbey_710-725.pdf"
   
https://bugs.launchpad.net/bugs/1680288/+attachment/4855871/+files/Silbey_710-725.pdf

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

Title:
  evince crashes on 'Type 3 font' error in PDF

Status in evince package in Ubuntu:
  New

Bug description:
  I have a PDF that crashes Document Viewer repeatably at the same page.
  Starting evince from console, I see these errors (at p.709, 719/958):

  Syntax Error: Missing or invalid CharProcs dictionary in Type 3 font
  Syntax Error: Weird page contents
  evince: /build/buildd/cairo-1.13.0~20140204/src/cairo-scaled-font.c:459: 
_cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.
  Aborted (core dumped)

  MuPDF and Firefox also flag the font error, but don't crash. Firefox
  says (at p.711, 721/958)

  Warning: Error during font loading: Type3 font load error: TypeError:
  this.stream.getByte is not a function  pdf.js:273:11

  and MuPDF says (at p.712, 722/958)

  error: syntaxerror: Type3 font missing CharProcs
  error: cannot load type3 font (3207 0 R)
  error: cannot set font
  warning: Ignoring errors during rendering
  warning: cannot draw text since font and size not set
  error: syntaxerror: Type3 font missing CharProcs
  error: cannot load type3 font (3207 0 R)
  error: cannot set font
  warning: cannot draw text since font and size not set
  mupdf: warning: Errors found on page
  warning: cannot render glyph

  I attached a bit of a PDF that triggers this. Evince will crash when
  it reaches p.708 (9/16 in the extract). MuPDF and Firefox will throw
  errors at p.712 but won't crash. (idk why it's not the same.)

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

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


[Desktop-packages] [Bug 1676079] Re: fglrx-core 2:15.201.2-0ubuntu0.14.04.1: fglrx-core kernel module failed to build

2017-04-05 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1502978 ***
https://bugs.launchpad.net/bugs/1502978

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

** Changed in: fglrx-installer (Ubuntu)
   Status: New => Confirmed

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

Title:
  fglrx-core 2:15.201.2-0ubuntu0.14.04.1: fglrx-core kernel module
  failed to build

Status in fglrx-installer package in Ubuntu:
  Confirmed

Bug description:
  user@machine:~$ sudo apt-get install -y fglrx fglrx-core fglrx-amdcccle 
fglrx-dev
  ...
  Configurando fglrx-core (2:15.201.2-0ubuntu0.14.04.1) ...
  update-alternatives: a usar /usr/lib/fglrx-core/ld.so.conf para 
disponibilizar /etc/ld.so.conf.d/x86_64-linux-gnu_GFXCORE.conf 
(x86_64-linux-gnu_gfxcore_conf) em modo automático
  Loading new fglrx-core-15.201.2 DKMS files...
  First Installation: checking all kernels...
  Building only for 4.4.0-66-generic
  Building for architecture x86_64
  Building initial module for 4.4.0-66-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/fglrx-core.0.crash'
  Error! Bad return status for module build on kernel: 4.4.0-66-generic (x86_64)
  Consult /var/lib/dkms/fglrx-core/15.201.2/build/make.log for more information.
  update-initramfs: deferring update (trigger activated)
  A processar 'triggers' para initramfs-tools (0.103ubuntu4.6) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-66-generic
  A processar 'triggers' para libc-bin (2.19-0ubuntu6.11) ...
  A seleccionar pacote anteriormente não seleccionado fglrx.
  ...

  
  user@machine:~$ cat /var/lib/dkms/fglrx-core/15.201.2/build/make.log
  DKMS make.log for fglrx-core-15.201.2 for kernel 4.4.0-66-generic (x86_64)
  Sáb Mar 25 14:34:03 BRT 2017
  /usr/sbin/dkms: linha 73: cd: /var/lib/dkms/fglrx/15.201.2/build: Arquivo ou 
diretório não encontrado
  AMD kernel module generator version 2.1
  doing Makefile based build for kernel 2.6.x and higher
  rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
  make -C /lib/modules/4.4.0-66-generic/build 
SUBDIRS=/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x modules
  make[1]: Entrando no diretório `/usr/src/linux-headers-4.4.0-66-generic'
CC [M]  /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.o
  /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: In function 
‘firegl_major_proc_read’:
  /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:639:9: error: 
void value not ignored as it ought to be
   len = seq_printf(m, "%d\n", major);
   ^
  /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: In function 
‘KCL_fpu_save_init’:
  /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6508:49: error: 
‘XSTATE_FP’ undeclared (first use in this function)
 if (!(fpu->state.xsave.header.xfeatures & XSTATE_FP))
   ^
  /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6508:49: note: 
each undeclared identifier is reported only once for each function it appears in
  /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c: At top level:
  /var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.c:6498:12: 
warning: ‘KCL_fpu_save_init’ defined but not used [-Wunused-function]
   static int KCL_fpu_save_init(struct task_struct *tsk)
  ^
  make[2]: ** [/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x/firegl_public.o] 
Erro 1
  make[1]: ** [_module_/var/lib/dkms/fglrx-core/15.201.2/build/2.6.x] Erro 2
  make[1]: Saindo do diretório `/usr/src/linux-headers-4.4.0-66-generic'
  make: ** [kmod_build] Erro 2
  build failed with return value 2

  
  user@machine:~$ lsb_release -a
  LSB Version:  
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04
  Codename: trusty

  
  user@machine:~$ uname -a
  Linux machine 4.4.0-66-generic #87~14.04.1-Ubuntu SMP Fri Mar 3 17:32:36 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-core 2:15.201.2-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 4.4.0-66-generic
  Date: Sat Mar 25 12:46:41 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.201.2: added
   Error! Could not locate dkms.conf file.
   File:  does not exist.
  

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-04-05 Thread Steve Chadsey
I am having the same issue, not in a VM.  Ubuntu 16.04.1 LTS.  eth0 is a wired 
network controller.  I've attached a tar file containing:
- relevant syslog messages
- output of 'ethtool eht0'
- output of 'ethtool -i eth0'
- output of 'lspci -vvv'

I'm not sure what other information would be relevant but am happy to
provide it on request, either when the system is in the problem state or
otherwise.

I recover the situation by clicking the "Wired connection 1" in the
network indicator panel.

Clearly there are at least 3 problems here:
1. The network connection is lost
2. There is no reason given for the loss of connection
3. The connection is not automatically recovered


** Attachment added: "Output of various commands"
   
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+attachment/4855862/+files/command_output.tar

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

Title:
  Avahi-daemon withdraws address record

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

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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


[Desktop-packages] [Bug 1679622] Re: [unity8] aisleriot crashes with SIGABRT

2017-04-05 Thread Jeremy Bicha
My crash was because I was incorrectly trying to run aisleriot from a
terminal.

I was able to run aisleriot successfully by clicking its icon in the 
Applications list or by running it via ubuntu-terminal-app with either of these 
two ways:
ubuntu-app-launch sol
sol -- --desktop_file_hint=sol.desktop

I don't know what the original reporter's problem was. apport says that
/usr/share/applications/sol.desktop has been modified?

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

Title:
  [unity8] aisleriot crashes with SIGABRT

Status in aisleriot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  sol crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: aisleriot 1:3.22.1-1ubuntu1 [modified: 
usr/share/applications/sol.desktop]
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity8
  Date: Tue Apr  4 13:33:56 2017
  ExecutablePath: /usr/games/sol
  InstallationDate: Installed on 2016-12-12 (112 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: /usr/games/sol
  Signal: 6
  SourcePackage: aisleriot
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: sol crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1644393] Re: Menu button remains clicked even after clicking somewhere else

2017-04-05 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1562002 ***
https://bugs.launchpad.net/bugs/1562002

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

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

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

Title:
  Menu button remains clicked even after clicking somewhere else

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  If I click the menu button on the right and then somewhere else the
  menu button will not return to normal, instead it will look like it is
  already clicked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Nov 23 20:28:42 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+401+133'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2016-11-17 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  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/1644393/+subscriptions

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


[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

2017-04-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Avahi-daemon withdraws address record

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

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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


[Desktop-packages] [Bug 1642496] Re: loaders/libpixbufloader-ras.so missing in xenial

2017-04-05 Thread Bug Watch Updater
** Changed in: gdk-pixbuf
   Status: Unknown => Confirmed

** Changed in: gdk-pixbuf
   Importance: Unknown => Wishlist

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

Title:
  loaders/libpixbufloader-ras.so missing in xenial

Status in gdk-pixbuf:
  Confirmed
Status in gdk-pixbuf package in Ubuntu:
  Won't Fix

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  libgdk-pixbuf2.0-0:
Installed: 2.32.2-1ubuntu1.2
Candidate: 2.32.2-1ubuntu1.2
Version table:
   *** 2.32.2-1ubuntu1.2 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.32.2-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  eog is lacking support for sun raster files due to missing
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders
  /libpixbufloader-ras.so (see Bug
  https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1632359 #1632359
  reported by Melanie on 2016-10-11) and my question
  https://answers.launchpad.net/ubuntu/+source/gdk-
  pixbuf/+question/404136

  This seems also to be true for /usr/lib/i386-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders/libpixbufloader-ras.so

  This bug seems also to be present in other Ubuntu releases > 14.04

  Workaround is to copy libpixbufloader-ras.so from 14.04 and rebuild
  cache.

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

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


[Desktop-packages] [Bug 1673790] Re: bump LibreOffice to 5.3.1 on zesty and fix autpkgtest dependencies

2017-04-05 Thread Amr Ibrahim
** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  bump LibreOffice to 5.3.1 on zesty and fix autpkgtest dependencies

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Debian:
  Fix Released

Bug description:
  Please sponsor LibreOffice 1:5.3.1-0ubuntu1 and the corresponding
  -l10n package to zesty (use dget):

   
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice-l10n_5.3.1-0ubuntu1_source.changes
   
http://people.canonical.com/~bjoern/zesty/5.3.1/libreoffice_5.3.1-0ubuntu1_source.changes

  The few changes vs. version 1:5.3.0~rc3-0ubuntu2 are best viewed on
  git:

   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=f4b5ece6b1783202ed286e1f149ab60c3471f180
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=af8b1b6e9d4f00d1d6d31063e56bd4ca5d70b910
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=c525f97bab587d69ce56cf81f2edbfb7ae685cd7
   
https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/commit/?h=ubuntu-zesty-5.3=af39ca70101b069b214b01a197aa48ffc59820b8

  A zesty build with all but the the last change is available in the
  LibreOffice ppas at:

   https://launchpad.net/~libreoffice/+archive/ubuntu/ppa
   https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-5-3

  Note the last change is not substancial as LibreOffice 5.3.1 rc2 is
  equal to 5.3.1 final in everything but the version.

  NB: The LibreOffice package has some generated files in ./debian (e.g.
  control) so there might be more changes (in generated files) in the
  debdiff than the above.

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

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


[Desktop-packages] [Bug 1662227] Re: Error with command "apt-get update" when using versioned "Provides:" (apt is too old to support that case)

2017-04-05 Thread Amr Ibrahim
Me too. I can't upgrade to 5.3.2 in Trusty. The crash report of update-
manager is attached.

Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in 
_inline_callbacks
 result = gen.throw(excep)
   File 
"/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py",
 line 92, in commit
 _("Installing updates…"), True)
   File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in 
_inline_callbacks
 result = gen.throw(excep)
   File 
"/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py",
 line 159, in _show_transaction
 yield trans.run()
 aptdaemon.errors.TransactionFailed: Transaction failed: Package dependencies 
cannot be resolved
  The following packages have unmet dependencies:
 
 libreoffice-common: Depends: libreoffice-style but it is a virtual package

** Attachment added: "_usr_bin_update-manager.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1662227/+attachment/4855840/+files/_usr_bin_update-manager.1000.crash

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

Title:
  Error with command "apt-get update" when using versioned "Provides:"
  (apt is too old to support that case)

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I'm getting this error every time I do "apt-get update"

  Ign http://ni.archive.ubuntu.com trusty/multiverse Translation-en_US  
 
  Ign http://ni.archive.ubuntu.com trusty/restricted Translation-en_US  
 
  Ign http://ni.archive.ubuntu.com trusty/universe Translation-en_US
 
  Reading package lists... Done 
 
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  ...
  ...
  ...
  ...
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: Ignoring Provides line with DepCompareOp for package libreoffice-l10n
  W: You may want to run apt-get update to correct these problems

  This error started to show after I upgraded LibreOffice form 5.2 to
  5.3 with the LibreOffice PPA: ppa:libreoffice/ppa.

  The thing is that everything is working fine. I can update/upgrade the
  system, I can install packages, delete packages, etc. The problem is
  just with the error.

  I tried: "apt-get autoclean". "apt-get clean", "apt-get autoremove",
  apt-get install -f", and a lot of other things and nothing removes
  that ugly error.

  If I remove all PPA packages and remove the PPA itself the error goes
  away.

  This has been reported in askubuntu.com:

  
  
http://askubuntu.com/questions/880447/ubuntu-14-04-error-with-apt-get-update-w-ignoring-provides-line-with-depcom

  http://askubuntu.com/questions/879497/apt-spewing-warnings-after-
  libreoffice-update

  
  Help please. Thank you.

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

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


[Desktop-packages] [Bug 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install

2017-04-05 Thread Brian Murray
Hello Damien, or anyone else affected,

Accepted appstream into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/appstream/0.9.4-1ubuntu3 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: appstream (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Kubuntu 16.04.1 discover empty after fresh install

Status in appstream package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in plasma-discover package in Ubuntu:
  Invalid
Status in appstream source package in Xenial:
  Fix Committed
Status in packagekit source package in Xenial:
  Invalid
Status in plasma-discover source package in Xenial:
  Invalid

Bug description:
  [Impact]

   * A previous update made AppStream use modern-style component-ids, thereby 
breaking the Qt library if it is reading data from the cache and if that data 
happens to be a desktop-application.
   * This leads to KDE's Discover not displaying applications.
   * The issue was introduced by a patch to the Xenial version of AppStream, 
and is not present in any other version of the package in Ubuntu, affecting 
Xenial only.

  [Test Case 1]

   * Update the libappstream-qt package, run Discover: All apps should
  be loaded correctly.

  [Regression Potential]

   * Low, this change affects only the Qt bindings and nothing else. The
  change is also a simple string value change.

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

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


[Desktop-packages] [Bug 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install

2017-04-05 Thread Matthias Klumpp
I added an explanation (basically, a previous bugfix fixing GNOME
Software broke this for the Qt bindings).

** Description changed:

  [Impact]
  
-  * A previous update made AppStream use modern-style component-ids, thereby 
breaking the Qt library if it is reading data from the cache and if that data 
happens to be a desktop-application.
-  * This leads to KDE's Discover not displaying applications.
+  * A previous update made AppStream use modern-style component-ids, thereby 
breaking the Qt library if it is reading data from the cache and if that data 
happens to be a desktop-application.
+  * This leads to KDE's Discover not displaying applications.
+  * The issue was introduced by a patch to the Xenial version of AppStream, 
and is not present in any other version of the package in Ubuntu, affecting 
Xenial only.
  
  [Test Case 1]
  
-  * Update the libappstream-qt package, run Discover: All apps should be
+  * Update the libappstream-qt package, run Discover: All apps should be
  loaded correctly.
  
  [Regression Potential]
  
-  * Low, this change affects only the Qt bindings and nothing else. The
+  * Low, this change affects only the Qt bindings and nothing else. The
  change is also a simple string value change.

** Changed in: appstream (Ubuntu Xenial)
   Status: Incomplete => In Progress

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

Title:
  Kubuntu 16.04.1 discover empty after fresh install

Status in appstream package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in plasma-discover package in Ubuntu:
  Invalid
Status in appstream source package in Xenial:
  In Progress
Status in packagekit source package in Xenial:
  Invalid
Status in plasma-discover source package in Xenial:
  Invalid

Bug description:
  [Impact]

   * A previous update made AppStream use modern-style component-ids, thereby 
breaking the Qt library if it is reading data from the cache and if that data 
happens to be a desktop-application.
   * This leads to KDE's Discover not displaying applications.
   * The issue was introduced by a patch to the Xenial version of AppStream, 
and is not present in any other version of the package in Ubuntu, affecting 
Xenial only.

  [Test Case 1]

   * Update the libappstream-qt package, run Discover: All apps should
  be loaded correctly.

  [Regression Potential]

   * Low, this change affects only the Qt bindings and nothing else. The
  change is also a simple string value change.

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

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


[Desktop-packages] [Bug 1632359] Re: display of sun raster files with eog in ubuntu 16.04

2017-04-05 Thread Jeremy Bicha
*** This bug is a duplicate of bug 1642496 ***
https://bugs.launchpad.net/bugs/1642496

** This bug has been marked a duplicate of bug 1642496
   loaders/libpixbufloader-ras.so missing in xenial

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

Title:
  display of sun raster files with eog in ubuntu 16.04

Status in eog package in Ubuntu:
  Confirmed

Bug description:
  With former ubuntu distributions the image viewer eog could be used for 
opening sun raster files with file ending .ras. With the latest ubuntu release 
eog doesn't recognize the file format any more. I reinstalled eog, but it still 
hasn't worked out. However, opening of the .ras file works with other image 
viewers such as e.g. gimp or image magic.
  Any help is appreciated, thanks!

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

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


[Desktop-packages] [Bug 1642496] Re: loaders/libpixbufloader-ras.so missing in xenial

2017-04-05 Thread Jeremy Bicha
This ancient file format was intentionally dropped to reduce the chance
of security vulnerabilities and other bugs.

https://bugzilla.gnome.org/721372

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Won't Fix

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

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

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

Title:
  loaders/libpixbufloader-ras.so missing in xenial

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Won't Fix

Bug description:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  libgdk-pixbuf2.0-0:
Installed: 2.32.2-1ubuntu1.2
Candidate: 2.32.2-1ubuntu1.2
Version table:
   *** 2.32.2-1ubuntu1.2 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.32.2-1ubuntu1 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  eog is lacking support for sun raster files due to missing
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders
  /libpixbufloader-ras.so (see Bug
  https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1632359 #1632359
  reported by Melanie on 2016-10-11) and my question
  https://answers.launchpad.net/ubuntu/+source/gdk-
  pixbuf/+question/404136

  This seems also to be true for /usr/lib/i386-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders/libpixbufloader-ras.so

  This bug seems also to be present in other Ubuntu releases > 14.04

  Workaround is to copy libpixbufloader-ras.so from 14.04 and rebuild
  cache.

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

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


[Desktop-packages] [Bug 1680273] [NEW] /usr/bin/remmina:11:g_type_check_instance_cast:remmina_connection_holder_toolbar_autofit_restore:g_timeout_dispatch:g_main_dispatch:g_main_context_dispatch

2017-04-05 Thread errors.ubuntu.com bug bridge
Public bug reported:

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


** Tags: precise quantal raring saucy trusty utopic vivid wily xenial yakkety 
zesty

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

Title:
  
/usr/bin/remmina:11:g_type_check_instance_cast:remmina_connection_holder_toolbar_autofit_restore:g_timeout_dispatch:g_main_dispatch:g_main_context_dispatch

Status in remmina package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
remmina.  This problem was most recently seen with package version 
1.1.2-3ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/cb8d8108641b18fad9da69870c28fe6f6702b7cc 
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/remmina/+bug/1680273/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-04-05 Thread Oisín Mac Fhearaí
Actually I just checked and the same console output is emitted when the
media router flag is disabled, only without the segfault. I could try to
get a stacktrace in gdb if you'd like.

-- 
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 1621753] Re: Google Cast no longer finds Chromecast device

2017-04-05 Thread Oisín Mac Fhearaí
@Chad could you elaborate on whether the fix made it into a released
version? I just tested version 57.0.2987.98-0ubuntu0.16.04.1276,
released on 2017-03-15, and now I get the following behaviour:

With media-router flag disabled: "No Cast destinations found".

With media-router flag enabled: almost instant crash on start, with the
following console output:

[8913:8913:0405/235646.257452:ERROR:account_tracker.cc(356)] OnGetTokenFailure: 
Invalid credentials.
[8913:8913:0405/235646.257536:ERROR:account_tracker.cc(356)] OnGetTokenFailure: 
Invalid credentials.
[9227:9227:0405/235646.755599:ERROR:child_thread_impl.cc(762)] Request for 
unknown Channel-associated interface: ui::mojom::GpuMain
[1]8913 segmentation fault (core dumped)  chromium-browser

-- 
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 1663695] Re: Kubuntu 16.04.1 discover empty after fresh install

2017-04-05 Thread Brian Murray
Does this not need fixing in Zesty? If that is the case please explain
why not in the bug description.

** Changed in: appstream (Ubuntu Xenial)
   Status: In Progress => Incomplete

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

Title:
  Kubuntu 16.04.1 discover empty after fresh install

Status in appstream package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in plasma-discover package in Ubuntu:
  Invalid
Status in appstream source package in Xenial:
  Incomplete
Status in packagekit source package in Xenial:
  Invalid
Status in plasma-discover source package in Xenial:
  Invalid

Bug description:
  [Impact]

   * A previous update made AppStream use modern-style component-ids, thereby 
breaking the Qt library if it is reading data from the cache and if that data 
happens to be a desktop-application.
   * This leads to KDE's Discover not displaying applications.

  [Test Case 1]

   * Update the libappstream-qt package, run Discover: All apps should
  be loaded correctly.

  [Regression Potential]

   * Low, this change affects only the Qt bindings and nothing else. The
  change is also a simple string value change.

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

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


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

2017-04-05 Thread FFab
Upstream kernel test - kernel 4.11-rc5

boot-time >3 min.
no local login
only remote-login 

brigthness adjustment: not possible
HDMI not usable (not new)


** Tags removed: kernel-bug-exists-upstream-4.11-rc4
** Tags added: kernel-bug-exists-upstream-4.11-rc5

** Attachment added: "error and fail lines from dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639517/+attachment/4855820/+files/dmesg_error.txt

-- 
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:
  Confirmed

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 1676810] Re: Network Manager needs restarting from sleep

2017-04-05 Thread Alberto Salvia Novella
** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Network Manager needs restarting from sleep

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Each time my laptop is suspended and resumed, Network Manager seems
  unable to bring up Wifi.

  Calling...

  sudo service network-manager restart

  ...resolves the problem.

  I therefore placed the attached file at...

  /lib/systemd/system-sleep/network-manager

  ...which provides a workaround for the problem. However, there must be
  some kind of underlying bug in network-manager which requires it to be
  restarted after every suspend/resume cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Tue Mar 28 10:21:35 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp1s0  proto static  metric 600 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp1s0  proto kernel  scope link  src 192.168.1.203  
metric 600
  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.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 ac7e4d66-b979-41de-b4b2-6f7c5dffc232  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp1s0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
Kitchen 2   937ae07a-fb47-46ac-91a4-0fe200203a95  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/2  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1654044] Re: /usr/bin/evolution:11:webkit_editor_paste_clipboard_targets_cb:request_targets_received_func:selection_received:g_closure_invoke:signal_emit_unlocked_R

2017-04-05 Thread Brian Murray
Hello errors.ubuntu.com, or anyone else affected,

Accepted evolution into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/evolution/3.22.6-0ubuntu0.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 on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

** Changed in: evolution (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  
/usr/bin/evolution:11:webkit_editor_paste_clipboard_targets_cb:request_targets_received_func:selection_received:g_closure_invoke:signal_emit_unlocked_R

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution source package in Yakkety:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evolution.  This problem was most recently seen with package version 
3.22.3-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/d7254ed93e5e4954abf5ab6d0f2d68dba28f5cf7 
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/evolution/+bug/1654044/+subscriptions

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


[Desktop-packages] [Bug 1664222] Re: Update evolution-data-server to 3.22.7

2017-04-05 Thread Brian Murray
Hello Jeremy, or anyone else affected,

Accepted evolution-data-server into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/evolution-data-server/3.22.7-0ubuntu0.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 on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

** Changed in: evolution-data-server (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Update evolution-data-server to 3.22.7

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ==
  This is the third evolution SRU for yakkety. This update includes the new 
bugfix releases 3.22.4, 3.22.5, 3.22.6 and 3.22.7. Updating e-d-s is required 
to update evolution to 3.22.6 (LP: #1664226)

  https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
  https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

  Test Case
  =
  After installing the update, restart your computer.

  Run several eds-using apps like Evolution, GNOME Calendar and verify
  that they continue to run at least as well as before this update.

  Regression Potential
  
  Low. There are a fair number of changes in this update, but they are all 
targeted towards fixing bugs. This is the same release that other GNOME 3.22 
distros (like Debian stretch) ship. This may be the last official 3.22 release 
for the Evolution stack now that 3.24.0 has been released.

  3.22.6 introduced a regression in pop3 support that was fixed within a
  week by 3.22.7.

  Other Info
  ==
  Ubuntu 17.04 will stick with Evolution 3.22 (not 3.24).

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

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


[Desktop-packages] [Bug 1664226] Re: Update evolution to 3.22.6

2017-04-05 Thread Brian Murray
Hello Jeremy, or anyone else affected,

Accepted evolution into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/evolution/3.22.6-0ubuntu0.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 on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

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

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

** Changed in: evolution (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

** Tags added: verification-needed

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

Title:
  Update evolution to 3.22.6

Status in evolution package in Ubuntu:
  Fix Released
Status in evolution source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  ==
  This is the third SRU for Ubuntu 16.10 for evolution. This update includes 
the new bugfix releases 3.22.4, 3.22.5, and 3.22.6.

  https://git.gnome.org/browse/evolution/tree/NEWS/?h=gnome-3-22
  https://git.gnome.org/browse/evolution/log/?h=gnome-3-22

  Test Case
  =
  After installing this update, please restart your computer.

  Verify that evolution still works as well as it did before.

  Optionally, you can even go through some of the fixed bugs to verify
  the bug and the fix but there are a lot of fixed bugs!

  Regression Potential
  
  Low to Moderate. There are quite a few changes in this update but they should 
be bugfixes. This may be the last official 3.22 evolution release. This is the 
same version that is being shipped by other GNOME 3.22 distros.

  Other Info
  ==
  This update depends on evolution-data-server 3.22.6 (LP: #1664222)

  The previous evolution SRU for 16.10 got stuck in phased-updates. This
  update fixes at least one of those crash regressions (LP: #1654044)

  https://people.canonical.com/~ubuntu-archive/phased-updates.html

  Ubuntu 17.04 will stick with evolution 3.22 (not 3.24).

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

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


[Desktop-packages] [Bug 1680033] Re: Snap searches are often canceled

2017-04-05 Thread Robert Ancell
This is normally because you typed "ro" and g-s did a search on that and
when you type "cket" it cancels the "ro" search and does a "rocket"
search.

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

Title:
  Snap searches are often canceled

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Searching for specific snaps (e.g. rocket, wifi-ap or network-manager)
  through the UI is often canceled internally.

  Logs print:

  11:16:42:0596 Gs  failed to get search apps: Operation was cancelled
  11:16:42:0596 Gs  not handling error cancelled for action search: Operation 
was cancelled
  11:16:42:0596 GsPluginSnap begin snapd request: GET /v2/find?q=network-m 
HTTP/1.1
  Host:
  Authorization: Macaroon root="XXX"
  11:16:43:0679 Gs  failed to call gs_plugin_add_search on snap: Operation was 
cancelled

  Tested with latest gnome-software from https://git.gnome.org/browse
  /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6

  This blocks enablement of snap support in gnome-software on Fedora.

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

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


[Desktop-packages] [Bug 1680030] Re: Snap plugin for gnome-software misses self tests

2017-04-05 Thread Robert Ancell
You should also file these bugs upstream.

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

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

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

Title:
  Snap plugin for gnome-software misses self tests

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  The snap plugin implemented in gnome-software upstream does not have
  any self tests yet which were requested by upstream to get the plugin
  into a better shape.

  Tested with latest gnome-software from https://git.gnome.org/browse
  /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6

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

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


[Desktop-packages] [Bug 1680027] Re: gnome-software doesn't use snapd-glib exclusively

2017-04-05 Thread Robert Ancell
Why does this block enablement?

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

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

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

Title:
  gnome-software doesn't use snapd-glib exclusively

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  The code submitted to gnome-software upstream still doesn't use snapd-
  glib exclusively but has parts of the snapd REST API which are handled
  by its own. The HTTP REST API logic should be only implemented once
  and that in snapd-glib. See https://git.gnome.org/browse/gnome-
  software/tree/plugins/snap/gs-snapd.c

  Tested with latest gnome-software from https://git.gnome.org/browse
  /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6

  This blocks enablement of snap support in gnome-software on Fedora.

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

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


[Desktop-packages] [Bug 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

2017-04-05 Thread Robert Bruce Park
Given that python-gobject-2 is deprecated and only has a relatively
short list of rdeps I wonder if this is a candidate for removal?

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+subscriptions

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


[Desktop-packages] [Bug 1583821] Re: Applications shuffling around on desktops after screen lock

2017-04-05 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1295267 ***
https://bugs.launchpad.net/bugs/1295267

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

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

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

Title:
  Applications shuffling around on desktops after screen lock

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I use multiple desktops to organize open applications. Also, I am
  currently using multiple monitors. If I arrange my applications (e.g.
  Chrome on the laptop screen of desktop one, Geany on the attached
  monitor on desktop 1, another chrome on the laptop screen of desktop
  2, another app on the attached monitor on desktop 2) and then lock the
  screen, when I unlock all of the applications have moved around.
  Sometimes they all move to desktop 1, sometimes they are resized and
  half off the screen. But they are rarely on the same screen and
  desktop that I left them on.

  This is new behavior since the latest version upgrade. Previously,
  applications stayed on the screens where I left them.

  Some requested info:

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

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 19 17:17:20 2016
  DistUpgraded: 2016-04-29 20:29:44,172 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  InstallationDate: Installed on 2014-12-03 (532 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 80H1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (19 days ago)
  dmi.bios.date: 09/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B9CN12WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Edge 15
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Edge 15
  dmi.modalias: 
dmi:bvnLENOVO:bvrB9CN12WW:bd09/28/2014:svnLENOVO:pn80H1:pvrLenovoEdge15:rvnLENOVO:rnLenovoEdge15:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoEdge15:
  dmi.product.name: 80H1
  dmi.product.version: Lenovo Edge 15
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue May 17 10:15:01 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1103 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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


[Desktop-packages] [Bug 1629611] Re: dns server priority broken

2017-04-05 Thread gatopeich
Seems fixed in version 1.2.6

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

Title:
  dns server priority broken

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-vpnc:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager: 1.2.4-0ubuntu1

  
  Yakkety appears to have switched back from resolved to dnsmasq, but it seems 
server priority/order is broken.

  Example: In split DNS setups, connecting to VPN will not cause us to
  query the DNS provided by the VPN first (or only), which should be the
  proper way to resolve names in that case.

  Say server.example.com in the public DNS resolves to a.a.a.a and in
  the private DNS resolves to b.b.b.b.

  Stuff would work from my normal internet-connection, but connection to
  VPN would cause stuff to misbehave. I expect to hit the b.b.b.b
  address but since my normal LAN DNS is being used first, I'm really
  hitting a.a.a.a.

  Please let me know how to proceed - Hopefully this can be fixed in
  time for release.

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

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


[Desktop-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu

2017-04-05 Thread J. McDonald
#29 worked for me using 1.2.0+git20161018-3salbabix27xenial as long as I
did the following:

fusermount -u /media/iPhone

and then

ifuse /media/iPhone/

After that, I was able to access the entire filesystem on my iPhone
5c/iOS 10.2 and finally import my photos.  It's a bit clunky but it
works.  I will be glad when this is fixed and an update issued.

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

Title:
  iOS device contents not displayed in Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

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

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


[Desktop-packages] [Bug 1680226] [NEW] Broken SplitDNS resolution in networ-manager VPN after disconnect and reconnect

2017-04-05 Thread Giovanni Panozzo
Public bug reported:

Release: Ubuntu 16.04.2 LTS
network-manager package version: 1.2.6-0ubuntu0.16.04.1

I'm using Ubuntu Desktop 16.04 x64 and I have some VPN (OpenVPN and
Cisco vpnc) connections defined. In all these connections I use both
split tunnel and split dns.

When I connect to a remote VPN server, my Ubuntu client correctly resolves DNS 
names in zones pushed by the remode server using the remote DNS server.
For example: the remote VPN server pushes to the client "DNS resolver is 
192.168.10.1 for domain "vpndom.net"", then "host srv1.vpndom.net" is correctly 
resolved bu 192.168.10.1 and I get 192.168.10.7.

After disconnecting and reconnecting to the VPN server, my Ubuntu client
is no longer able to resolve DNS names in zones pushed by the VPN
servers: "host srv1.vpndom.net" returns host not found.

As a temporary solution, I downgraded netowrk manager to
1.2.2-0ubuntu0.16.04.4 and all is working fine. So I think the problem
is in network-manager 1.2.6-0ubuntu0.16.04.1

As a workaround, with the connected VPN tunnel, I just "sudo killall
dnsmasq": NetworkManager will then restart dnsmasq passing it all
correct DNSes. There is no need to disconnect from the vpn.

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

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

Title:
  Broken SplitDNS resolution in networ-manager VPN after disconnect and
  reconnect

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 16.04.2 LTS
  network-manager package version: 1.2.6-0ubuntu0.16.04.1

  I'm using Ubuntu Desktop 16.04 x64 and I have some VPN (OpenVPN and
  Cisco vpnc) connections defined. In all these connections I use both
  split tunnel and split dns.

  When I connect to a remote VPN server, my Ubuntu client correctly resolves 
DNS names in zones pushed by the remode server using the remote DNS server.
  For example: the remote VPN server pushes to the client "DNS resolver is 
192.168.10.1 for domain "vpndom.net"", then "host srv1.vpndom.net" is correctly 
resolved bu 192.168.10.1 and I get 192.168.10.7.

  After disconnecting and reconnecting to the VPN server, my Ubuntu
  client is no longer able to resolve DNS names in zones pushed by the
  VPN servers: "host srv1.vpndom.net" returns host not found.

  As a temporary solution, I downgraded netowrk manager to
  1.2.2-0ubuntu0.16.04.4 and all is working fine. So I think the problem
  is in network-manager 1.2.6-0ubuntu0.16.04.1

  As a workaround, with the connected VPN tunnel, I just "sudo killall
  dnsmasq": NetworkManager will then restart dnsmasq passing it all
  correct DNSes. There is no need to disconnect from the vpn.

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

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


[Desktop-packages] [Bug 1484932] Re: ipv6 dhcp client never started.

2017-04-05 Thread Marcelo Zacarias da Silva
After some testing, it seems that the problem is fixed in Debian 9
(stretch/testing). So I believe some future version of Ubuntu based on
Debian 9 (17.10?) will have the fix.

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

Title:
  ipv6 dhcp client never started.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm in a ipv6 network that sets ip number with dhcpv6 and not using
  the stateless protocol.

  but using ubuntu 15.04 there is never any dhclient started for ipv6
  and no way to change any configuration that I can find to start it.

  if I attach the cable and then manually start dhclient with "dhclient
  -6 -i eth3_109" I do get a ipv6 address and things works as intended.

  There has to be some way to star the dhclient software from network
  manager but I can't find it.

  There should be two dhclients started per network device one for ipv4
  and one for ipv6 only one is started for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  Uname: Linux 4.1.5-040105-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 14 14:32:06 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-04-09 (126 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  IpRoute:
   default via 10.10.1.254 dev eth3  proto static  metric 1024 
   10.10.1.0/24 dev eth3  proto kernel  scope link  src 10.10.1.156 
   10.10.6.0/24 dev eth3_109  proto kernel  scope link  src 10.10.6.14 
   169.254.0.0/16 dev eth3  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-05 Thread Ryan Harper
@Mercury

Hi, please note that the change I've made is *only* against the
resolvconf task; as you  say and document the issue (and potential fix)
is against dnsmasq; ergo there is no need for a resolvconf patch/change.

You mention:

"and resolvconf was not properly tracking how interfaces were added and
removed from the system."

I see no details or data in this bug, nor the RH bugzilla that indicates that 
resolvconf itself has an issue.  If you have
more information on this, then please do add that;

Specifically to the recent upgrade to resolvconf (I included the diff of
change); there is no runtime code change; only a systemd unit change on
when the service is started.  Even if there is some bug in resolvconf as
you say; it will occur in the previous version and the updated version
since the update did not modify any of the resolvconf runtime code.

If you believe that the *unit* change to resolvconf in 1.78ubuntu4 is
related to this issue, please add that specific information before
reopening the resolvconf task.

Finally, it does appear that there should be a dnsmasq task; I'll
nominate that.


** Changed in: resolvconf (Ubuntu)
   Status: Confirmed => 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/1671606

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1636486] Re: External screen flickers (esp. in terminals) with xorg modesetting driver on Intel Broadwell

2017-04-05 Thread Nicolas Ramoudt
Hi

Working for 2 days now on Ubuntu 17.04, updated to your proposed kernel 
4.11.0-994
Amazing... working dual 4K now via 2x displayport 1.2 without a glitch on both 
monitors for the first time.

Fantastic!  And indeed, I hope too, that these fixes will be included a.s.a.p.
I was almost desperate here...

Your solution-proposal really saved my day, so thanks a lot!

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

Title:
  External screen flickers (esp. in terminals) with xorg modesetting
  driver on Intel Broadwell

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I'm using a Dell XPS 13 (9343 // i7-5600U broadwell, 3200x1800 panel)
  laptop, directly attached to an external Dell P2715Q 4K (3840x2160
  @60Hz) via DP.

  The 4K external screen is flickering when doing light activity --
  easily reproduced when using an X terminal.

  Steps to reproduce:
  - open side by side Firefox (or Chrome) + a terminal and/or a gvim window on 
the external 4K screen
  - do some light web browsing
  - give focus to the X terminal or gvim
// at this point, display is still perfectly steady
  - press a key to enter a single character
// as soon as the key is pressed, external screen goes black for a few 
seconds. Laptop screen is not affected.
  - Wait for the screen to come back, then continue typing
// screen generally stays ON, but sometimes continues to flicker a few 
times in next minute.

  This happens almost every time I switch to the terminal window and
  start typing.

  OS specs:
  - Ubuntu 16.10 running Unity, modesetting Xorg driver
  - kernel 4.8.0. Issue is still present with 4.9.0rc1.

  The intel driver (cp /usr/share/doc/xserver-xorg-video-intel/xorg.conf
  /etc/X11) doesn't exhibit this issue.

  
  Also reported upstream: https://bugs.freedesktop.org/show_bug.cgi?id=97264

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

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


[Desktop-packages] [Bug 1680222] Re: gnome-calendar crashed with SIGSEGV in gcal_manager_refresh()

2017-04-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1505077 ***
https://bugs.launchpad.net/bugs/1505077

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 #1505077, 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/1680222/+attachment/4855680/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1680222

Title:
  gnome-calendar crashed with SIGSEGV in gcal_manager_refresh()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-calendar 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Apr  5 20:08:30 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-03-28 (7 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x5600dc3f7b08 :  mov
0x18(%rdi),%rdi
   PC (0x5600dc3f7b08) 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/1680222/+subscriptions

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


[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-05 Thread Mercury
Ryan,

The problem is not that a recent change in resolvconf caused a
regression.

The problem with resolvconf is that the upgrade to network-manager
exposed an existing bug in resolvconf.

This happens because the new version of network-manager now tells
resolvconf that it must only use a specific interface when talking to
the name server, and resolvconf was not properly tracking how interfaces
were added and removed from the system.

This is most obvious for VPN connections which use an interface for VPN
traffic, as that interface will be destroyed and recreated on every VPN
connection, triggering the bug in resolvconf. (Setting up the new DNS
for the new VPN interface is insufficient to make it happy.)

This can also be triggered on systems that remove and readd interfaces
for things like suspend or hibernate.

Redhat documented the bug fairly well when they found it, their bug
report on the matter is
https://bugzilla.redhat.com/show_bug.cgi?id=1373485

The actual patch that needs to be applied is git commit
2675f2061525bc954be14988d64384b74aa7bf8b, and the upstream gitweb URL
for viewing the diff is:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

There is a separate (but very related) issue, in that some existing VPNs
that involve ipsec have one interface for sending traffic and to hold an
IP, but the response traffic appears on the interface of the primary
internet connection.  This is completely broken in the middle of an LTS
by this change, and fixing the bug in resolvconf won't help.  I'm still
trying to sort out the right answer for some of my VPN use cases there.

** Changed in: resolvconf (Ubuntu)
   Status: Invalid => 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/1671606

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1677125] Re: zesty can't get to the login screen when a Geforce GT210 card (nouveau) is installed (GUI says "The system is running in low-graphics mode", log says "No devices d

2017-04-05 Thread e15
Asus Zenbook Prime ux32vd laptop. I've got "The system is running low
graphics mode" dialog on VT2, and usual lightdm greeting on VT7 after
upgrading from 16.10 to 17.04.

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677125/+attachment/4855670/+files/lspci.txt

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

Title:
  zesty can't get to the login screen when a Geforce GT210 card
  (nouveau) is installed (GUI says "The system is running in low-
  graphics mode", log says "No devices detected." "no screens found")

Status in xorg package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  zesty can't get to the login screen when a Geforce GT210 card is
  installed

  I just get an unclickable dialog "The system is running in low-
  graphics mode" and stuck.

  Although if I VT switch and log in by SSH I find mir-demos all run
  nicely. So this is just a problem with Xorg/lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Mar 29 14:08:04 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1313]
  InstallationDate: Installed on 2016-11-03 (146 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  MachineType: LENOVO 30AJS05700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=9a004175-205d-430e-bd14-8d796f0d18e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO
  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-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-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: Wed Mar 29 14:03:29 2017
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-1ubuntu9

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

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


[Desktop-packages] [Bug 1621962] Re: Regression: nm-applet menu fails to update connection list

2017-04-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Regression: nm-applet menu fails to update connection list

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

Bug description:
  Since using Ubuntu 16.04 instead of 14.04, I sometimes encounter an
  old list of WiFi networks in the nm-applet menu after wakeup from
  standby. The list is stuck then and not updated anymore.

  Using nmcli, I can see the correct list, so it is not a problem of
  NetworkManager or the WiFi stack, but of nm-applet it seems.

  I then have to use 'nmcli con up id ', to connect the
  network. If I do this, the nm-applet menu gets updated instantly, and
  resumes it's normal operation.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.2.0-0ubuntu0.16.04.4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Sep  9 20:21:29 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-23 (17 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.6  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
ALICE-WLAN44  3637f65f-54db-4b4e-b0f8-e4a559dbb7b7  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
------  
   
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
------
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1641889] Re: The network indicator shows the wrong status

2017-04-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  The network indicator shows the wrong status

Status in Network Manager Applet:
  Unknown
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager-applet package in Ubuntu:
  Triaged
Status in network-manager-applet source package in Xenial:
  Confirmed

Bug description:
  [Summary] The network indicator shows the wrong status

  [Reproduce Steps]
  1.Boot into Ubuntu OS , remove wireless connection
  Note : the issue can't be reproduced with wifi connection
  2.Enable/disable wifi function by hotkey the check wifi manager status

  [Results]
  Expected: "Enable Wi-Fi" option should be OFF
  Actual:"Enable Wi-Fi" option is ON

  [Additional Information]
  Product Name:Inspiron-7460
  BIOS Version:1.0.0

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

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


[Desktop-packages] [Bug 1679535] Re: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails)

2017-04-05 Thread Goodwin
I have the same problem with Tenda W311i adapter.

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

Title:
  ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup  fails)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I think this is a bug in the WIFI-driver or kernel.
  Ubuntu is connected to the WIFI (router) box, but it cannot find DNS server 
to get to the internet.

  I have periodically *serious* problems with WIFI in Ubuntu 17.04.
  The network icon shows "connected" to the router and internet, but browsers 
and other attempts to get data report DNS error / or not connected.

  This happens in all flavours of Ubuntu 17.04 (Ubuntu, Ubuntu GNOME
  etc.).

  Same laptop with Ubuntu 16.10 works flawlessly.

  The connection works fine after I reboot (power off/on) the router box.
  Then the bug may return (or may not return) after I turn on my laptop next 
time.

  This laptop is Toshiba Stellite P50 C.
  The laptop has Intel Corporation Wireless 3165 (rev 81).

  $ lspci -nnk | grep -iA2 net; uname -r; ls /lib/firmware/ | grep
  'iwlwifi-7265d'

  0d:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81)
  Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010]
  Kernel driver in use: iwlwifi
  --
  0e:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
  Subsystem: Toshiba America Info Systems RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1179:f840]
  Kernel driver in use: r8169
  Kernel modules: r8169
  4.11.0-041100rc4-generic

  Ref: https://wiki.debian.org/iwlwifi

  Restarting the network.manager does not help.
  $ sudo service network-manager restart
  Network manager connects (and sees) to the router, but cannot access internet.
  -

  Please see also:
  https://ubuntuforums.org/search.php?searchid=14761184
  and
  https://ubuntuforums.org/showthread.php?t=2356828

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.11.0-041100rc4-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  4 08:22:23 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-03-27 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  IpRoute:
   default via 192.168.1.1 dev wlp13s0 proto static metric 600
   169.254.0.0/16 dev wlp13s0 scope link metric 1000
   192.168.1.0/24 dev wlp13s0 proto kernel scope link src 192.168.1.34 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   wlp13s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Ubuntu-Linux-Network  dda6e4cf-5cd9-4e01-b638-418985262413  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp14s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
------
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
------
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1678622] Re: Libreoffice copy paste doesn't copy calculations

2017-04-05 Thread Cliff Carson
gnome-shell has nothing to do with this problem.  Replaced the Ubuntu
Gnome system with Ubuntu Unity and continue to have the problem in the
spreadsheet, in fact fails more consistently.  Could almost agree that
this is a hardware problem if there were not so many ways to do the
copy/paste using different keys/mouse/menu but they all fail the same
way.

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

Title:
  Libreoffice copy paste doesn't copy calculations

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When doing a copy/paste of rows only the text information is copied (a
  "Text Import" dialog box is displayed which normally wasn't before).
  If the copy/paste operation is repeated than the text and calculations
  are copied.  In fact if the copy (ctl-c) is hit twice and then the
  paste (ctl-v) the operation works correctly.  Using the Copy/Paste
  icons shows the same incorrect behavior.

  ii  libreoffice-calc1:5.3.1-0ubunt amd64  office
  productivity suite -- spreadsheet

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-calc 1:5.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr  2 10:05:34 2017
  InstallationDate: Installed on 2017-02-13 (47 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170211)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1673276] Re: Improvements to Debian rules file

2017-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package chromium-browser -
57.0.2987.98-0ubuntu0.16.10.1344

---
chromium-browser (57.0.2987.98-0ubuntu0.16.10.1344) yakkety-security; 
urgency=medium

  * Upstream release: 57.0.2987.98.
- CVE-2017-5030: Memory corruption in V8.
- CVE-2017-5031: Use after free in ANGLE.
- CVE-2017-5032: Out of bounds write in PDFium.
- CVE-2017-5029: Integer overflow in libxslt.
- CVE-2017-5034: Use after free in PDFium.
- CVE-2017-5035: Incorrect security UI in Omnibox.
- CVE-2017-5036: Use after free in PDFium.
- CVE-2017-5037: Multiple out of bounds writes in ChunkDemuxer.
- CVE-2017-5039: Use after free in PDFium.
- CVE-2017-5040: Information disclosure in V8.
- CVE-2017-5041: Address spoofing in Omnibox.
- CVE-2017-5033: Bypass of Content Security Policy in Blink.
- CVE-2017-5042: Incorrect handling of cookies in Cast.
- CVE-2017-5038: Use after free in GuestView.
- CVE-2017-5043: Use after free in GuestView.
- CVE-2017-5044: Heap overflow in Skia.
- CVE-2017-5045: Information disclosure in XSS Auditor.
- CVE-2017-5046: Information disclosure in Blink.
  * debian/patches/arm64-support no longer needed
  * debian/patches/stdatomic: Support gcc48.
  * debian/patches/snapshot-library-link: Add missing libsnapshot link
  * debian/patches/gtk-ui-stdmove: fix && pointer return with std::move
  * debian/control: Drop binary arch "any" and explicitly list four.
  * debian/patches/arm64-vpx-alignment: Avoid ARM64 alignment bug on some
compilers.
  * debian/rules: Fix armhf float ABI and remove unnecessary envvars.
(LP: #1673276)

 -- Chad MILLER   Wed, 15 Mar 2017 21:12:35
-0400

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5029

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5030

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5031

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5032

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5033

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5034

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5035

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5036

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5037

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5038

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5039

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5040

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5041

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5042

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5043

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5044

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5045

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-5046

** Changed in: chromium-browser (Ubuntu)
   Status: New => Fix Released

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

Title:
  Improvements to Debian rules file

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Hi, I help maintain the Chromium package in Endless OS, which is based
  on Ubuntu's package. We have two minor improvements to the Debian
  rules file that you probably want. These diffs are based on your
  Xenial v56 package. First, a simple typo:

  From b794c427fa8146e8f3eb38f593c0d6e0d42692c7 Mon Sep 17 00:00:00 2001
  From: Michael Catanzaro 
  Date: Mon, 2 Jan 2017 18:39:20 -0600
  Subject: [PATCH] Fix upstream typo in rules file

  So now we know armhf has not been tested
  ---
   debian/rules | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

  diff --git a/debian/rules b/debian/rules
  index 881dd1a..3baa6d2 100755
  --- a/debian/rules
  +++ b/debian/rules
  @@ -127,7 +127,7 @@ else ifeq (armhf,$(DEB_HOST_ARCH))
   common_defines += target_cpu="arm"
   #common_defines += arm_optionally_use_neon=false   # implies Android in 
2016-10
   common_defines += arm_use_neon=false
  -common_defined += arm_float_abi="hard" arm_use_thumb=true
  +common_defines += arm_float_abi="hard" arm_use_thumb=true
   else ifeq (arm64,$(DEB_HOST_ARCH))
   common_defines += target_cpu="arm64"
   else ifeq (i386,$(DEB_HOST_ARCH))

  
  Second we have a patch to remove some environment variables that are ignored 
by the new build system:

  From 3d7d37f64a31f4dad7e43bf78269a714bae1ed42 Mon Sep 17 00:00:00 2001
  From: Michael Catanzaro 
  Date: Sun, 8 Jan 2017 14:37:03 -0600
  

[Desktop-packages] [Bug 1673276] Re: Improvements to Debian rules file

2017-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package chromium-browser -
57.0.2987.98-0ubuntu0.16.04.1276

---
chromium-browser (57.0.2987.98-0ubuntu0.16.04.1276) xenial-security; 
urgency=medium

  * Upstream release: 57.0.2987.98.
- CVE-2017-5030: Memory corruption in V8.
- CVE-2017-5031: Use after free in ANGLE.
- CVE-2017-5032: Out of bounds write in PDFium.
- CVE-2017-5029: Integer overflow in libxslt.
- CVE-2017-5034: Use after free in PDFium.
- CVE-2017-5035: Incorrect security UI in Omnibox.
- CVE-2017-5036: Use after free in PDFium.
- CVE-2017-5037: Multiple out of bounds writes in ChunkDemuxer.
- CVE-2017-5039: Use after free in PDFium.
- CVE-2017-5040: Information disclosure in V8.
- CVE-2017-5041: Address spoofing in Omnibox.
- CVE-2017-5033: Bypass of Content Security Policy in Blink.
- CVE-2017-5042: Incorrect handling of cookies in Cast.
- CVE-2017-5038: Use after free in GuestView.
- CVE-2017-5043: Use after free in GuestView.
- CVE-2017-5044: Heap overflow in Skia.
- CVE-2017-5045: Information disclosure in XSS Auditor.
- CVE-2017-5046: Information disclosure in Blink.
  * debian/patches/arm64-support no longer needed
  * debian/patches/stdatomic: Support gcc48.
  * debian/patches/snapshot-library-link: Add missing libsnapshot link
  * debian/patches/gtk-ui-stdmove: fix && pointer return with std::move
  * debian/control: Drop binary arch "any" and explicitly list four.
  * debian/patches/arm64-vpx-alignment: Avoid ARM64 alignment bug on some
compilers.
  * debian/rules: Fix armhf float ABI and remove unnecessary envvars.
(LP: #1673276)

 -- Chad MILLER   Wed, 15 Mar 2017 21:12:35
-0400

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

Title:
  Improvements to Debian rules file

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Hi, I help maintain the Chromium package in Endless OS, which is based
  on Ubuntu's package. We have two minor improvements to the Debian
  rules file that you probably want. These diffs are based on your
  Xenial v56 package. First, a simple typo:

  From b794c427fa8146e8f3eb38f593c0d6e0d42692c7 Mon Sep 17 00:00:00 2001
  From: Michael Catanzaro 
  Date: Mon, 2 Jan 2017 18:39:20 -0600
  Subject: [PATCH] Fix upstream typo in rules file

  So now we know armhf has not been tested
  ---
   debian/rules | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)

  diff --git a/debian/rules b/debian/rules
  index 881dd1a..3baa6d2 100755
  --- a/debian/rules
  +++ b/debian/rules
  @@ -127,7 +127,7 @@ else ifeq (armhf,$(DEB_HOST_ARCH))
   common_defines += target_cpu="arm"
   #common_defines += arm_optionally_use_neon=false   # implies Android in 
2016-10
   common_defines += arm_use_neon=false
  -common_defined += arm_float_abi="hard" arm_use_thumb=true
  +common_defines += arm_float_abi="hard" arm_use_thumb=true
   else ifeq (arm64,$(DEB_HOST_ARCH))
   common_defines += target_cpu="arm64"
   else ifeq (i386,$(DEB_HOST_ARCH))

  
  Second we have a patch to remove some environment variables that are ignored 
by the new build system:

  From 3d7d37f64a31f4dad7e43bf78269a714bae1ed42 Mon Sep 17 00:00:00 2001
  From: Michael Catanzaro 
  Date: Sun, 8 Jan 2017 14:37:03 -0600
  Subject: [PATCH] Remove unused code from rules file

  All of these environment variables are ignored by the GN build, so it is
  misleading to keep them here.

  Also, remove the incorrect comment immediately below, since it prefaces
  a list of features that are both enabled and disabled.
  ---
   debian/rules | 11 ---
   1 file changed, 11 deletions(-)

  diff --git a/debian/rules b/debian/rules
  index 773b78e..33b7374 100755
  --- a/debian/rules
  +++ b/debian/rules
  @@ -62,17 +62,6 @@ DEB_DH_SCOUR_ARGS += -Xsvg
   DEB_DH_SHLIBDEPS_ARGS_chromium-codecs-ffmpeg := 
-ldebian/chromium-codecs-ffmpeg/$(LIB_DIR)
   DEB_DH_SHLIBDEPS_ARGS_chromium-codecs-ffmpeg-extra := 
-ldebian/chromium-codecs-ffmpeg-extra/$(LIB_DIR)
   
  -### linker flags to avoid memory allocation issues on 32-bit
  -export LDFLAGS+=-Wl,--no-keep-memory -Wl,--stats
  -
  -# See https://bugs.chromium.org/p/v8/issues/detail?id=3782
  -#export CFLAGS+=-fno-delete-null-pointer-checks
  -
  -export CC := $(shell which gcc-4 gcc-5 gcc cc |head -1)
  -export CXX := $(shell which g++-4 g+++5 g++ c++ |head -1)
  -export CPP := $(shell which g++-4 g+++5 g++ c++ |head -1)
  -
  -# disabled features
   common_defines+=\
enable_google_now=false \
enable_hangout_services_extension=true \

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

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

[Desktop-packages] [Bug 1679535] Re: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails)

2017-04-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup  fails)

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I think this is a bug in the WIFI-driver or kernel.
  Ubuntu is connected to the WIFI (router) box, but it cannot find DNS server 
to get to the internet.

  I have periodically *serious* problems with WIFI in Ubuntu 17.04.
  The network icon shows "connected" to the router and internet, but browsers 
and other attempts to get data report DNS error / or not connected.

  This happens in all flavours of Ubuntu 17.04 (Ubuntu, Ubuntu GNOME
  etc.).

  Same laptop with Ubuntu 16.10 works flawlessly.

  The connection works fine after I reboot (power off/on) the router box.
  Then the bug may return (or may not return) after I turn on my laptop next 
time.

  This laptop is Toshiba Stellite P50 C.
  The laptop has Intel Corporation Wireless 3165 (rev 81).

  $ lspci -nnk | grep -iA2 net; uname -r; ls /lib/firmware/ | grep
  'iwlwifi-7265d'

  0d:00.0 Network controller [0280]: Intel Corporation Wireless 3165 
[8086:3165] (rev 81)
  Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010]
  Kernel driver in use: iwlwifi
  --
  0e:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
  Subsystem: Toshiba America Info Systems RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1179:f840]
  Kernel driver in use: r8169
  Kernel modules: r8169
  4.11.0-041100rc4-generic

  Ref: https://wiki.debian.org/iwlwifi

  Restarting the network.manager does not help.
  $ sudo service network-manager restart
  Network manager connects (and sees) to the router, but cannot access internet.
  -

  Please see also:
  https://ubuntuforums.org/search.php?searchid=14761184
  and
  https://ubuntuforums.org/showthread.php?t=2356828

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  Uname: Linux 4.11.0-041100rc4-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr  4 08:22:23 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-03-27 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  IpRoute:
   default via 192.168.1.1 dev wlp13s0 proto static metric 600
   169.254.0.0/16 dev wlp13s0 scope link metric 1000
   192.168.1.0/24 dev wlp13s0 proto kernel scope link src 192.168.1.34 metric 
600
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile

   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   wlp13s0  wifi  connected/org/freedesktop/NetworkManager/Devices/2  
Ubuntu-Linux-Network  dda6e4cf-5cd9-4e01-b638-418985262413  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp14s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
------
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
------
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1680201] Re: nautilus crashes when searching for a file and then renaming it

2017-04-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1546141 ***
https://bugs.launchpad.net/bugs/1546141

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashes when searching for a file and then renaming it

Status in nautilus package in Ubuntu:
  New

Bug description:
  I searched for a file using the built-in search. I had only one
  result. I selected the file and pressed F2. I entered a new name and
  pressed enter. Then nautilus appeared to be frozen until it finally
  crashed maybe half a minute later.

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

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

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


[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2017-04-05 Thread Ryan Harper
The change introduced[1] in resolveconf-1.78ubuntu4 over 1.78ubuntu2
affects *when* resolvconf service starts; but does not affect the
runtime code and is not involved in any of the runtime action of the
resolvconf service.  I'm marking the resolvconf task as invalid.

If you feel that the resolvconf change to when resolvconf service starts during 
boot affects the runtime DNS settings, please do re-open against resolvconf and 
include:
a. systemctl status resolvconf
b. contents of /etc/resolv.conf  

1. diff -Nru resolvconf-1.78ubuntu2/debian/resolvconf.service 
resolvconf-1.78ubuntu4/debian/resolvconf.service
--- resolvconf-1.78ubuntu2/debian/resolvconf.service2015-06-03 
15:58:21.0 -0500
+++ resolvconf-1.78ubuntu4/debian/resolvconf.service2016-12-07 
03:03:18.0 -0600
@@ -2,7 +2,8 @@
 Description=Nameserver information manager
 Documentation=man:resolvconf(8)
 DefaultDependencies=no
-Before=networking.service
+Before=network-pre.target
+Wants=network-pre.target


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

** Changed in: resolvconf (Ubuntu)
 Assignee: Ryan Harper (raharper) => (unassigned)

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1678205] Re: Update epiphany to 3.22.7

2017-04-05 Thread Brian Murray
Hello Jeremy, or anyone else affected,

Accepted epiphany-browser into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/epiphany-
browser/3.22.7-0ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

** Changed in: epiphany-browser (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  Update epiphany to 3.22.7

Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in epiphany-browser source package in Yakkety:
  Fix Committed

Bug description:
  Impact
  --
  Another bugfix release in the stable 3.22 series. It fixes a crash, some 
issues with the snapshot service (takes a mini screenshot of the page for the 
New Tab page), and some issues with recording browser history.

  https://git.gnome.org/browse/epiphany/tree/NEWS/?h=gnome-3-22
  https://git.gnome.org/browse/epiphany/log/?h=gnome-3-22

  Test Case
  -
  Browse to some websites.

  Do a Google search to make sure that text entry works.

  To test one fix from this update, visit https://www.terveystalo.com/
  and click English. With 3.22.6, epiphany crashes. It shouldn't crash
  after the update.

  Regression Potential
  
  Low.

  The 3.18.10 update introduced a regression where it was impossible to
  enter text on websites. 3.18 releases are basically only done now for
  Ubuntu 16.04 LTS's benefit so those get less testing.

  To mitigate that regression potential, I have subscribed to epiphany-
  browser bugs in Launchpad to know about possible regressions sooner. I
  now specifically test for entering text on websites.

  This update is for 3.22 though which is still in use by many distros,
  such as Debian stretch and the latest Fedora. So it's less likely than
  3.18 to have that kind of major regression.

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

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


[Desktop-packages] [Bug 1680202] [NEW] can't reconfigure lightdm with dpkg. Please help

2017-04-05 Thread milius
Public bug reported:

I'm reverting a gdm3 configuration but this is what i get:

sudo dpkg-reconfigure lightdm  
insserv: warning: script is corrupt or invalid: /etc/init.d/../rc2.d/S01shm_load

Please, help me

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr  5 20:28:24 2017
InstallationDate: Installed on 2017-03-19 (17 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  can't reconfigure lightdm with dpkg. Please help

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm reverting a gdm3 configuration but this is what i get:

  sudo dpkg-reconfigure lightdm  
  insserv: warning: script is corrupt or invalid: 
/etc/init.d/../rc2.d/S01shm_load

  Please, help me

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  5 20:28:24 2017
  InstallationDate: Installed on 2017-03-19 (17 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu

2017-04-05 Thread J. McDonald
#29 worked for me using 1.2.0+git20161018-3salbabix27xenial as long as I
did the following:

fusermount -u /media/iPhone

and then

ifuse /media/iPhone/

After that, I was able to access the entire filesystem on my iPhone
5c/iOS 10.2 and finally import my photos.  It's a bit clunky but it
works.  I will be glad when this is fixed and an update issued.

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

Title:
  iOS device contents not displayed in Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

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

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


[Desktop-packages] [Bug 1680172] Re: signon-ui crashed with SIGABRT

2017-04-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1194732 ***
https://bugs.launchpad.net/bugs/1194732

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 #1194732, 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/1680172/+attachment/4855509/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1194732
   signon-ui crashed with SIGABRT in qt_message_fatal()

** 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 signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1680172

Title:
  signon-ui crashed with SIGABRT

Status in signon-ui package in Ubuntu:
  New

Bug description:
  signon-ui crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: signon-ui-x11 0.17+17.04.20170320-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Apr  5 19:31:07 2017
  ExecutablePath: /usr/bin/signon-ui
  ProcCmdline: /usr/bin/signon-ui
  ProcEnviron:
   LANGUAGE=hu_HU
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: signon-ui
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, 
char const*) () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () at 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   () at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: signon-ui crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1680172/+subscriptions

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


[Desktop-packages] [Bug 1680173] Re: bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()

2017-04-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1671316 ***
https://bugs.launchpad.net/bugs/1671316

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 #1671316, 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/1680173/+attachment/4855519/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1671316
   bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()

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

Title:
  bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()

Status in bamf package in Ubuntu:
  New

Bug description:
  bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: bamfdaemon 0.5.3+16.10.20160929-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Apr  5 19:32:04 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
  ProcCmdline: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
  ProcEnviron:
   LANG=hu_HU.UTF-8
   LANGUAGE=hu_HU
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f0d97f8de39 :   mov
0x8(%rax),%edx
   PC (0x7f0d97f8de39) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: bamf
  StacktraceTop:
   sn_xcb_display_new () at 
/usr/lib/x86_64-linux-gnu/libstartup-notification-1.so.0
   sn_display_new () at /usr/lib/x86_64-linux-gnu/libstartup-notification-1.so.0
   wnck_screen_get () at /usr/lib/x86_64-linux-gnu/libwnck-3.so.0
   bamf_legacy_screen_get_default ()
   ()
  Title: bamfdaemon crashed with SIGSEGV in sn_xcb_display_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1615732] Re: Execution of filter 'Junk check' fails with "Empty cache file"

2017-04-05 Thread Ben Holness
I also have this problem. I do not have a filter named "junk check" so I
presume it is something built in. I turned of junk handling options in
Evolution's preferences and now I get the same message but the filter is
the top one of my filters list. I have checked in the filesystem and the
file exists and is indeed 0 size.

I am using:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"

Evolution 3.18.5.2

This is a big issue if these are real messages that are being truncated!
If they are not real messages, or it's just the caching that failed and
the message is intact, it's not a big deal.

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

Title:
  Execution of filter 'Junk check' fails with "Empty cache file"

Status in Evolution:
  Unknown
Status in evolution package in Ubuntu:
  Confirmed
Status in evolution package in Debian:
  New

Bug description:
  I currently use an Evolution setup in which I retrieve email via IMAP
  from an unfiltered mailbox, and then use Evolution to automatically
  filter for spam/junk mail.

  This process works as expected upon starting Evolution: all email is
  retrieved from the mailbox (and thus resides in the Inbox folder,
  where it arrived), then it's filtered to identify spam, and then the
  spam is moved from the Inbox to a Junk folder.

  However, after Evolution has been running for some time (hard to
  estimate because it requires an email to be received, but likely 5-10
  minutes; it's possible that this is just "one email refresh interval"
  but also possible that something else is going on), newly received
  email stops being filtered for spam, and all the email remains in the
  Inbox. This happens at least in the case of receiving one email at a
  time, and most likely in the case where multiple emails are received
  in one send/receive cycle.

  When this failure to remove spam/junk happens, there's a yellow banner
  at the top of the screen saying, for example (the filename is not
  always the same),

  "Error while performing operation.

  Execution of filter 'Junk check' failed: Empty cache file:
  
/home/ais523/.cache/evolution/mail/1440221975.23984.44@tundra/folders/INBOX/cur/1f/23052"

  I checked the contents of the file in question; it appears to be a
  copy of the email that was just received, including all headers. (It's
  possible that there's a race condition here and that the file was
  empty when the filter looked at it, but became populated just after it
  errored out, but perhaps something else is going on.)

  This behaviour is a problem because it means that either I have to
  delete junk mail by hand, or else that I have to repeatedly close and
  reopen Evolution so that the automated system will work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution 3.18.5.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 22 17:19:59 2016
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-06-03 (811 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  SourcePackage: evolution
  UpgradeStatus: Upgraded to xenial on 2016-05-02 (112 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-04-05 Thread Alexander Gulyaev
looks like we have to wait for new kernel with ACPI calls fixed

one more related thread
https://bbs.archlinux.org/viewtopic.php?id=223056

-- 
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 1680166] Re: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-04-05 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  I wasn't actively using the machine: evince, chrome, and matlab were
  running.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr  5 11:52:53 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-03-21 (14 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: lightdm
  Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1680166] [NEW] package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-04-05 Thread Melissa Lemke
Public bug reported:

I wasn't actively using the machine: evince, chrome, and matlab were
running.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Apr  5 11:52:53 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-03-21 (14 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: lightdm
Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  I wasn't actively using the machine: evince, chrome, and matlab were
  running.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Apr  5 11:52:53 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-03-21 (14 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: lightdm
  Title: package lightdm 1.18.3-0ubuntu1.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-04-05 Thread Alexander Gulyaev
related thread
https://github.com/Bumblebee-Project/Bumblebee/issues/764


** Bug watch added: github.com/Bumblebee-Project/Bumblebee/issues #764
   https://github.com/Bumblebee-Project/Bumblebee/issues/764

-- 
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 1665602] Re: nautilus no thumbnails for .jpg and .png

2017-04-05 Thread Jeremy Bicha
Nick, please file a new bug. You can run

ubuntu-bug libgdk-pixbuf2.0-0

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

Title:
  nautilus no thumbnails for .jpg and .png

Status in gnome-desktop:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  thumbnail for .tif is ok
  corrado@corrado-z2:~$ inxi
  CPU~Dual core Intel Core i3-4130 (-HT-MCP-) speed/max~3366/3400 MHz 
Kernel~4.10.0-8-generic x86_64 Up~1:03 Mem~983.2/7861.2MB HDD~1000.2GB(16.0% 
used) Procs~231 Client~Shell inxi~2.3.8  
  corrado@corrado-z2:~$ uname -a
  Linux corrado-z2 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-z2:~$ 
  display was ok with kernel 4.9.0-15
  corrado@corrado-z2:~$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.20.3-1ubuntu4
Candidate: 1:3.20.3-1ubuntu4
Version table:
   *** 1:3.20.3-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-z2:~$

  ProblemType: Bug
  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
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Feb 17 11:22:50 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-view' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1329x774+49+24'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'"
  InstallationDate: Installed on 2017-01-23 (24 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170123)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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


[Desktop-packages] [Bug 1665602] Re: nautilus no thumbnails for .jpg and .png

2017-04-05 Thread Nick Dedekind
This is still not working for me with SVGs.

libgdk-pixbuf2.0-0: 



  Installed: 2.36.5-3   



  Candidate: 2.36.5-3   



  Version table:



 *** 2.36.5-3 500   



500 http://gb.archive.ubuntu.com/ubuntu zesty/main amd64 Packages   



100 /var/lib/dpkg/status

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

Title:
  nautilus no thumbnails for .jpg and .png

Status in gnome-desktop:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  thumbnail for .tif is ok
  corrado@corrado-z2:~$ inxi
  CPU~Dual core Intel Core i3-4130 (-HT-MCP-) speed/max~3366/3400 MHz 
Kernel~4.10.0-8-generic x86_64 Up~1:03 Mem~983.2/7861.2MB HDD~1000.2GB(16.0% 
used) Procs~231 Client~Shell inxi~2.3.8  
  corrado@corrado-z2:~$ uname -a
  Linux corrado-z2 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  corrado@corrado-z2:~$ 
  display was ok with kernel 4.9.0-15
  corrado@corrado-z2:~$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.20.3-1ubuntu4
Candidate: 1:3.20.3-1ubuntu4
Version table:
   *** 1:3.20.3-1ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-z2:~$

  ProblemType: Bug
  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
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Fri Feb 17 11:22:50 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.preferences' b'search-view' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'1329x774+49+24'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'larger'"
  InstallationDate: Installed on 2017-01-23 (24 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170123)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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


[Desktop-packages] [Bug 1679622] Re: [unity8] aisleriot crashes with SIGABRT

2017-04-05 Thread Jeremy Bicha
Yes, all you have to do is try to run Aisleriot in Unity8. Does it work
for you without crashing?

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

Title:
  [unity8] aisleriot crashes with SIGABRT

Status in aisleriot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  sol crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: aisleriot 1:3.22.1-1ubuntu1 [modified: 
usr/share/applications/sol.desktop]
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity8
  Date: Tue Apr  4 13:33:56 2017
  ExecutablePath: /usr/games/sol
  InstallationDate: Installed on 2016-12-12 (112 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: /usr/games/sol
  Signal: 6
  SourcePackage: aisleriot
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: sol crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1679622] Re: [unity8] aisleriot crashes with SIGABRT

2017-04-05 Thread William Hua
Hi, is there something specific you did to reproduce this? Would you
mind installing libgtk-3-0-dbgsym and libmirclient9-dbgsym and trying
again?

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

Title:
  [unity8] aisleriot crashes with SIGABRT

Status in aisleriot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  sol crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: aisleriot 1:3.22.1-1ubuntu1 [modified: 
usr/share/applications/sol.desktop]
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity8
  Date: Tue Apr  4 13:33:56 2017
  ExecutablePath: /usr/games/sol
  InstallationDate: Installed on 2016-12-12 (112 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: /usr/games/sol
  Signal: 6
  SourcePackage: aisleriot
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: sol crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1679822] Re: zeromq3 FTBFS with zesty test rebuild

2017-04-05 Thread Łukasz Zemczak
** Changed in: zeromq3 (Ubuntu)
 Assignee: (unassigned) => Łukasz Zemczak (sil2100)

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

Title:
  zeromq3 FTBFS with zesty test rebuild

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  zeromq3 version 4.2.1-2ubuntu1 failed to build from source on armhf
  during a recent test rebuild for zesty. The build log can be found
  here:

  https://launchpadlibrarian.net/312257088/buildlog_ubuntu-zesty-
  armhf.zeromq3_4.2.1-2ubuntu1_BUILDING.txt.gz

  There seems to have been 1 test failure:

  FAIL: tests/test_use_fd_tcp
  ===

  lt-test_use_fd_tcp: tests/test_use_fd_tcp.cpp:59: void 
pre_allocate_sock(void*, const char*, const char*): Assertion `rc == 0' failed.
  FAIL tests/test_use_fd_tcp (exit status: 134)

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

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


[Desktop-packages] [Bug 1679622] Re: [unity8] aisleriot crashes with SIGABRT

2017-04-05 Thread Jeremy Bicha
** Tags added: unity8 unity8-app

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

Title:
  [unity8] aisleriot crashes with SIGABRT

Status in aisleriot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  sol crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: aisleriot 1:3.22.1-1ubuntu1 [modified: 
usr/share/applications/sol.desktop]
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity8
  Date: Tue Apr  4 13:33:56 2017
  ExecutablePath: /usr/games/sol
  InstallationDate: Installed on 2016-12-12 (112 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: /usr/games/sol
  Signal: 6
  SourcePackage: aisleriot
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: sol crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1680111] Re: gnome-terminal does not start in unity8

2017-04-05 Thread Jeremy Bicha
** Tags added: apport-crash unity8 unity8-app

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

Title:
  gnome-terminal does not start in unity8

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  gnome-terminal does not start in unity8 in Ubuntu 17.04.

  gnome-terminal is an unusual app with a server and a client.

  It looks like errors.ubuntu.com is bundling the crash with some other
  issues.

  Here's one report:
  https://errors.ubuntu.com/oops/4645497a-19f9-11e7-88fb-fa163ef911dc

  As a workaround, for now I will probably set gnome-terminal to not
  show in the Unity 8 app launcher.

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

-- 
Mailing list: https://launchpad.net/~desktop-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-04-05 Thread Alexander Gulyaev
** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1663926/+attachment/4855445/+files/Xorg.0.log

-- 
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 1663926] Re: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017

2017-04-05 Thread Alexander Gulyaev
** Attachment added: "lightdm.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1663926/+attachment/4855444/+files/lightdm.log

-- 
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 1663926] Re: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017

2017-04-05 Thread Alexander Gulyaev
Ubuntu 16.10
nvidia 375 installed then switched to intel
freeze on lightdm login screen

Apr  5 20:56:21 xps kernel: [6.489405] bbswitch: disabling discrete graphics
Apr  5 20:56:21 xps kernel: [6.489411] ACPI Warning: 
\_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI 
requires [Package] (20160422/nsarguments-95)
Apr  5 20:56:21 xps kernel: [6.508439] pci_raw_set_power_state: 60 
callbacks suppressed
Apr  5 20:56:21 xps kernel: [6.508441] pci :01:00.0: Refused to change 
power state, currently in D0
Apr  5 20:56:21 xps lightdm[1303]: Seat type 'xlocal' is deprecated, use 
'type=local' instead
Apr  5 20:56:21 xps kernel: [6.749591] Non-volatile memory driver v1.3


** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1663926/+attachment/4855443/+files/syslog

-- 
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 1680143] [NEW] FTBFS in zesty-proposed

2017-04-05 Thread Balint Reczey
Public bug reported:

Due to dpkg's different interpretation of
DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie
 and
DEB_BUILD_MAINT_OPTIONS = hardening=+all
in Debian Stretch and Zesty 1.6.1-3 fails to build in Zesty.

IMO the delta between 1.6.1-2 and 1.6.1-3 is small enough to leave
1.6.1-2 in Zesty.

Changes:
 libvpx (1.6.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Mark libvpx-doc as Multi-Arch:foreign.
   * Do not forcefully disable PIE anymore as -pie changed meaning.
 (Closes: #859415)

Otherwise this patch would fix the issue:

--- a/debian/rules
+++ b/debian/rules
@@ -1,6 +1,6 @@
 #!/usr/bin/make -f
 
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie
 
 DEB_CFLAGS_MAINT_APPEND = -Wall
 DEB_CXXFLAGS_MAINT_APPEND = -Wall

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


** Tags: ftbfs zesty

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

Title:
  FTBFS in zesty-proposed

Status in libvpx package in Ubuntu:
  New

Bug description:
  Due to dpkg's different interpretation of
  DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie
   and
  DEB_BUILD_MAINT_OPTIONS = hardening=+all
  in Debian Stretch and Zesty 1.6.1-3 fails to build in Zesty.

  IMO the delta between 1.6.1-2 and 1.6.1-3 is small enough to leave
  1.6.1-2 in Zesty.

  Changes:
   libvpx (1.6.1-3) unstable; urgency=medium
   .
 * Team upload.
 * Mark libvpx-doc as Multi-Arch:foreign.
 * Do not forcefully disable PIE anymore as -pie changed meaning.
   (Closes: #859415)

  Otherwise this patch would fix the issue:

  --- a/debian/rules
  +++ b/debian/rules
  @@ -1,6 +1,6 @@
   #!/usr/bin/make -f
   
  -export DEB_BUILD_MAINT_OPTIONS = hardening=+all
  +export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie
   
   DEB_CFLAGS_MAINT_APPEND = -Wall
   DEB_CXXFLAGS_MAINT_APPEND = -Wall

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

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


[Desktop-packages] [Bug 1679822] Re: zeromq3 FTBFS with zesty test rebuild

2017-04-05 Thread Jeremy Bicha
** Changed in: zeromq3 (Ubuntu)
 Assignee: Jeremy Bicha (jbicha) => (unassigned)

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

Title:
  zeromq3 FTBFS with zesty test rebuild

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  zeromq3 version 4.2.1-2ubuntu1 failed to build from source on armhf
  during a recent test rebuild for zesty. The build log can be found
  here:

  https://launchpadlibrarian.net/312257088/buildlog_ubuntu-zesty-
  armhf.zeromq3_4.2.1-2ubuntu1_BUILDING.txt.gz

  There seems to have been 1 test failure:

  FAIL: tests/test_use_fd_tcp
  ===

  lt-test_use_fd_tcp: tests/test_use_fd_tcp.cpp:59: void 
pre_allocate_sock(void*, const char*, const char*): Assertion `rc == 0' failed.
  FAIL tests/test_use_fd_tcp (exit status: 134)

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

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


[Desktop-packages] [Bug 1679822] Re: zeromq3 FTBFS with zesty test rebuild

2017-04-05 Thread Łukasz Zemczak
Do we know it's a real failure, or maybe just a transient test failure?
I vaguely remember the test suite not being entirely stable.

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

Title:
  zeromq3 FTBFS with zesty test rebuild

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  zeromq3 version 4.2.1-2ubuntu1 failed to build from source on armhf
  during a recent test rebuild for zesty. The build log can be found
  here:

  https://launchpadlibrarian.net/312257088/buildlog_ubuntu-zesty-
  armhf.zeromq3_4.2.1-2ubuntu1_BUILDING.txt.gz

  There seems to have been 1 test failure:

  FAIL: tests/test_use_fd_tcp
  ===

  lt-test_use_fd_tcp: tests/test_use_fd_tcp.cpp:59: void 
pre_allocate_sock(void*, const char*, const char*): Assertion `rc == 0' failed.
  FAIL tests/test_use_fd_tcp (exit status: 134)

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

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


[Desktop-packages] [Bug 1679622] Re: [unity8] aisleriot crashes with SIGABRT

2017-04-05 Thread Jeremy Bicha
** Summary changed:

- sol crashed with SIGABRT
+ [unity8] aisleriot crashes with SIGABRT

** Information type changed from Private to Public

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

Title:
  [unity8] aisleriot crashes with SIGABRT

Status in aisleriot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  sol crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: aisleriot 1:3.22.1-1ubuntu1 [modified: 
usr/share/applications/sol.desktop]
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity8
  Date: Tue Apr  4 13:33:56 2017
  ExecutablePath: /usr/games/sol
  InstallationDate: Installed on 2016-12-12 (112 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: /usr/games/sol
  Signal: 6
  SourcePackage: aisleriot
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: sol crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1680118] Re: Login for network share is not storable as Anonymous

2017-04-05 Thread Thomas
** Attachment added: "screen-040.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1680118/+attachment/4855411/+files/screen-040.png

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

Title:
  Login for network share is not storable as Anonymous

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have some networks shares in our office which are not secured with
  passwords. Unfortunately nautilus is prompting every time I want to
  connect to these shares. When I enter a username and password I can
  store these credentials in my keyring, if I want to connect as
  Anonymous I can not do so and Nautilus prompts again for the login
  next time it wants to mount the share. Storing my choice also as
  Anonymous would be a nice feature. I add a screenshot for this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  NonfreeKernelModules: fxmc_usb gxsd prl_fs_freeze prl_fs prl_eth prl_tg
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  5 11:25:14 2017
  InstallationDate: Installed on 2016-10-23 (163 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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/1680118/+subscriptions

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


[Desktop-packages] [Bug 1680118] [NEW] Login for network share is not storable as Anonymous

2017-04-05 Thread Thomas
Public bug reported:

I have some networks shares in our office which are not secured with
passwords. Unfortunately nautilus is prompting every time I want to
connect to these shares. When I enter a username and password I can
store these credentials in my keyring, if I want to connect as Anonymous
I can not do so and Nautilus prompts again for the login next time it
wants to mount the share. Storing my choice also as Anonymous would be a
nice feature. I add a screenshot for this.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
Uname: Linux 4.4.0-71-generic x86_64
NonfreeKernelModules: fxmc_usb gxsd prl_fs_freeze prl_fs prl_eth prl_tg
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Apr  5 11:25:14 2017
InstallationDate: Installed on 2016-10-23 (163 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Login for network share is not storable as Anonymous

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have some networks shares in our office which are not secured with
  passwords. Unfortunately nautilus is prompting every time I want to
  connect to these shares. When I enter a username and password I can
  store these credentials in my keyring, if I want to connect as
  Anonymous I can not do so and Nautilus prompts again for the login
  next time it wants to mount the share. Storing my choice also as
  Anonymous would be a nice feature. I add a screenshot for this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  NonfreeKernelModules: fxmc_usb gxsd prl_fs_freeze prl_fs prl_eth prl_tg
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  5 11:25:14 2017
  InstallationDate: Installed on 2016-10-23 (163 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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/1680118/+subscriptions

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


[Desktop-packages] [Bug 1680104] Re: Package FTBFS

2017-04-05 Thread Łukasz Zemczak
The easiest way would be to simply disable the -Werror=deprecated-
declarations and see how this goes, but the *proper* fix would be to get
rid of the deprecated functions and use the new, proper ones instead. I
leave the decision how to proceed to the upstream developers.

Anyway, I propose a merge to fix the first part of the problem.

** Summary changed:

- Package FTBFS because of missing gnome-common dependency
+ Package FTBFS

** Branch linked: lp:~sil2100/bamf/fix_ftbfs_dep

** Description changed:

+ There are two issues that cause the package to FTBFS during rebuilds.
+ First one is the missing gnome-common build-dependency:
+ 
  make[1]: Entering directory '/<>/bamf-0.5.3+16.10.20160929'
  NOCONFIGURE=1 dh_autoreconf ./autogen.sh
  You need to install the gnome-common module and make
  sure the gnome-autogen.sh script is in your $PATH.
  dh_autoreconf: ./autogen.sh returned exit code 1
  debian/rules:11: recipe for target 'override_dh_autoreconf' failed
  make[1]: *** [override_dh_autoreconf] Error 2
  make[1]: Leaving directory '/<>/bamf-0.5.3+16.10.20160929'
  debian/rules:8: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
+ 
+ But even after this dependency is satisfied, the build seems to fail on
+ use of some deprecated functions in the code. One example:
+ 
+ bamf-legacy-window.c: In function 'top_window_action_menu':
+ bamf-legacy-window.c:548:3: error: 'gdk_screen_get_monitor_scale_factor' is 
deprecated: Use 'gdk_monitor_get_scale_factor' instead 
[-Werror=deprecated-declarations]
+scale = gdk_screen_get_monitor_scale_factor (gdk_screen_get_default (), 0);
+^
+ In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31:0,
+  from /usr/include/gtk-3.0/gdk/gdk.h:32,
+  from /usr/include/gtk-3.0/gtk/gtk.h:30,
+  from /usr/include/libwnck-3.0/libwnck/pager.h:29,
+  from /usr/include/libwnck-3.0/libwnck/libwnck.h:32,
+  from bamf-legacy-window.h:30,
+  from bamf-legacy-window.c:23:
+ /usr/include/gtk-3.0/gdk/gdkscreen.h:103:15: note: declared here
+  gint  gdk_screen_get_monitor_scale_factor (GdkScreen *screen,
+^~~
+ bamf-legacy-window.c: In function 'bamf_legacy_window_show_action_menu':
+ bamf-legacy-window.c:609:3: error: 'gtk_menu_popup' is deprecated: Use 
'(gtk_menu_popup_at_widget, gtk_menu_popup_at_pointer, gtk_menu_popup_at_rect)' 
instead [-Werror=deprecated-declarations]
+gtk_menu_popup (GTK_MENU (menu), NULL, NULL, position, self, button, time);
+^~
+ In file included from /usr/include/gtk-3.0/gtk/gtklabel.h:34:0,
+  from /usr/include/gtk-3.0/gtk/gtkaccellabel.h:35,
+  from /usr/include/gtk-3.0/gtk/gtk.h:33,
+  from /usr/include/libwnck-3.0/libwnck/pager.h:29,
+  from /usr/include/libwnck-3.0/libwnck/libwnck.h:32,
+  from bamf-legacy-window.h:30,
+  from bamf-legacy-window.c:23:
+ /usr/include/gtk-3.0/gtk/gtkmenu.h:138:9: note: declared here
+  voidgtk_menu_popup(GtkMenu*menu,
+  ^~
+ cc1: all warnings being treated as errors

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

Title:
  Package FTBFS

Status in bamf package in Ubuntu:
  In Progress

Bug description:
  There are two issues that cause the package to FTBFS during rebuilds.
  First one is the missing gnome-common build-dependency:

  make[1]: Entering directory '/<>/bamf-0.5.3+16.10.20160929'
  NOCONFIGURE=1 dh_autoreconf ./autogen.sh
  You need to install the gnome-common module and make
  sure the gnome-autogen.sh script is in your $PATH.
  dh_autoreconf: ./autogen.sh returned exit code 1
  debian/rules:11: recipe for target 'override_dh_autoreconf' failed
  make[1]: *** [override_dh_autoreconf] Error 2
  make[1]: Leaving directory '/<>/bamf-0.5.3+16.10.20160929'
  debian/rules:8: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

  But even after this dependency is satisfied, the build seems to fail
  on use of some deprecated functions in the code. One example:

  bamf-legacy-window.c: In function 'top_window_action_menu':
  bamf-legacy-window.c:548:3: error: 'gdk_screen_get_monitor_scale_factor' is 
deprecated: Use 'gdk_monitor_get_scale_factor' instead 
[-Werror=deprecated-declarations]
 scale = gdk_screen_get_monitor_scale_factor (gdk_screen_get_default (), 0);
 ^
  In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31:0,
   from /usr/include/gtk-3.0/gdk/gdk.h:32,
   from /usr/include/gtk-3.0/gtk/gtk.h:30,
   

[Desktop-packages] [Bug 1680104] Re: Package FTBFS

2017-04-05 Thread Łukasz Zemczak
Just a note - an experimental removal of -Werror from configure.ac makes
the trunk buildable again (with the dep-change branch applied). This
means that the only issues with the package right now are the
deprecation-warnings (or other warnings) - no other build issues.

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

Title:
  Package FTBFS

Status in bamf package in Ubuntu:
  In Progress

Bug description:
  There are two issues that cause the package to FTBFS during rebuilds.
  First one is the missing gnome-common build-dependency:

  make[1]: Entering directory '/<>/bamf-0.5.3+16.10.20160929'
  NOCONFIGURE=1 dh_autoreconf ./autogen.sh
  You need to install the gnome-common module and make
  sure the gnome-autogen.sh script is in your $PATH.
  dh_autoreconf: ./autogen.sh returned exit code 1
  debian/rules:11: recipe for target 'override_dh_autoreconf' failed
  make[1]: *** [override_dh_autoreconf] Error 2
  make[1]: Leaving directory '/<>/bamf-0.5.3+16.10.20160929'
  debian/rules:8: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

  But even after this dependency is satisfied, the build seems to fail
  on use of some deprecated functions in the code. One example:

  bamf-legacy-window.c: In function 'top_window_action_menu':
  bamf-legacy-window.c:548:3: error: 'gdk_screen_get_monitor_scale_factor' is 
deprecated: Use 'gdk_monitor_get_scale_factor' instead 
[-Werror=deprecated-declarations]
 scale = gdk_screen_get_monitor_scale_factor (gdk_screen_get_default (), 0);
 ^
  In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31:0,
   from /usr/include/gtk-3.0/gdk/gdk.h:32,
   from /usr/include/gtk-3.0/gtk/gtk.h:30,
   from /usr/include/libwnck-3.0/libwnck/pager.h:29,
   from /usr/include/libwnck-3.0/libwnck/libwnck.h:32,
   from bamf-legacy-window.h:30,
   from bamf-legacy-window.c:23:
  /usr/include/gtk-3.0/gdk/gdkscreen.h:103:15: note: declared here
   gint  gdk_screen_get_monitor_scale_factor (GdkScreen *screen,
 ^~~
  bamf-legacy-window.c: In function 'bamf_legacy_window_show_action_menu':
  bamf-legacy-window.c:609:3: error: 'gtk_menu_popup' is deprecated: Use 
'(gtk_menu_popup_at_widget, gtk_menu_popup_at_pointer, gtk_menu_popup_at_rect)' 
instead [-Werror=deprecated-declarations]
 gtk_menu_popup (GTK_MENU (menu), NULL, NULL, position, self, button, time);
 ^~
  In file included from /usr/include/gtk-3.0/gtk/gtklabel.h:34:0,
   from /usr/include/gtk-3.0/gtk/gtkaccellabel.h:35,
   from /usr/include/gtk-3.0/gtk/gtk.h:33,
   from /usr/include/libwnck-3.0/libwnck/pager.h:29,
   from /usr/include/libwnck-3.0/libwnck/libwnck.h:32,
   from bamf-legacy-window.h:30,
   from bamf-legacy-window.c:23:
  /usr/include/gtk-3.0/gtk/gtkmenu.h:138:9: note: declared here
   voidgtk_menu_popup(GtkMenu*menu,
   ^~
  cc1: all warnings being treated as errors

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

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


[Desktop-packages] [Bug 1264379] Re: ftbfs returning value in a void function (-Werror)

2017-04-05 Thread Łukasz Zemczak
** Changed in: bamf (Ubuntu)
   Status: Confirmed => Fix Released

** Tags removed: ftbfs

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

Title:
  ftbfs returning value in a void function (-Werror)

Status in bamf package in Ubuntu:
  Fix Released

Bug description:
  bamf-legacy-window-test.c: In function 'bamf_legacy_window_test_set_hint':
  bamf-legacy-window-test.c:430:3: error: 'return' with a value, in function 
returning void [-Werror]
 return g_hash_table_insert (self->hints, g_strdup (name), g_strdup 
(value));
 ^
  cc1: all warnings being treated as errors

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

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


[Desktop-packages] [Bug 1680111] [NEW] gnome-terminal does not start in unity8

2017-04-05 Thread Jeremy Bicha
Public bug reported:

gnome-terminal does not start in unity8 in Ubuntu 17.04.

gnome-terminal is an unusual app with a server and a client.

It looks like errors.ubuntu.com is bundling the crash with some other
issues.

Here's one report:
https://errors.ubuntu.com/oops/4645497a-19f9-11e7-88fb-fa163ef911dc

As a workaround, for now I will probably set gnome-terminal to not show
in the Unity 8 app launcher.

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

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

Title:
  gnome-terminal does not start in unity8

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  gnome-terminal does not start in unity8 in Ubuntu 17.04.

  gnome-terminal is an unusual app with a server and a client.

  It looks like errors.ubuntu.com is bundling the crash with some other
  issues.

  Here's one report:
  https://errors.ubuntu.com/oops/4645497a-19f9-11e7-88fb-fa163ef911dc

  As a workaround, for now I will probably set gnome-terminal to not
  show in the Unity 8 app launcher.

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

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


[Desktop-packages] [Bug 1680102] Re: sol crashed with SIGABRT

2017-04-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1679622 ***
https://bugs.launchpad.net/bugs/1679622

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 #1679622, 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/1680102/+attachment/4855379/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  sol crashed with SIGABRT

Status in aisleriot package in Ubuntu:
  New

Bug description:
  sol crashed with SIGABRT

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: aisleriot 1:3.22.1-1ubuntu1 [modified: 
usr/share/applications/sol.desktop]
  ProcVersionSignature: Ubuntu 4.10.0-17.19-generic 4.10.8
  Uname: Linux 4.10.0-17-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity8
  Date: Wed Apr  5 16:35:49 2017
  ExecutablePath: /usr/games/sol
  InstallationDate: Installed on 2016-12-12 (113 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: /usr/games/sol
  Signal: 6
  SourcePackage: aisleriot
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: sol crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1680104] [NEW] Package FTBFS because of missing gnome-common dependency

2017-04-05 Thread Łukasz Zemczak
Public bug reported:

make[1]: Entering directory '/<>/bamf-0.5.3+16.10.20160929'
NOCONFIGURE=1 dh_autoreconf ./autogen.sh
You need to install the gnome-common module and make
sure the gnome-autogen.sh script is in your $PATH.
dh_autoreconf: ./autogen.sh returned exit code 1
debian/rules:11: recipe for target 'override_dh_autoreconf' failed
make[1]: *** [override_dh_autoreconf] Error 2
make[1]: Leaving directory '/<>/bamf-0.5.3+16.10.20160929'
debian/rules:8: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

** Affects: bamf (Ubuntu)
 Importance: High
 Assignee: Łukasz Zemczak (sil2100)
 Status: In Progress


** Tags: ftbfs

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

Title:
  Package FTBFS because of missing gnome-common dependency

Status in bamf package in Ubuntu:
  In Progress

Bug description:
  make[1]: Entering directory '/<>/bamf-0.5.3+16.10.20160929'
  NOCONFIGURE=1 dh_autoreconf ./autogen.sh
  You need to install the gnome-common module and make
  sure the gnome-autogen.sh script is in your $PATH.
  dh_autoreconf: ./autogen.sh returned exit code 1
  debian/rules:11: recipe for target 'override_dh_autoreconf' failed
  make[1]: *** [override_dh_autoreconf] Error 2
  make[1]: Leaving directory '/<>/bamf-0.5.3+16.10.20160929'
  debian/rules:8: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

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

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


[Desktop-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions

2017-04-05 Thread Kai-Heng Feng
@aljosa,

Now the brightness save/restore is handled by systemd service now. Can
you check the status of the service?

On my system, I can find it via
Save Screen Backlight Brightness of backlight:intel_backlight


$ systemctl | grep backlight.service | awk '{print $1}'
systemd-backlight@backlight:intel_backlight.service
systemd-backlight@leds:dell::kbd_backlight.service

$ systemctl status systemd-backlight@backlight:intel_backlight.service

It should be 'Active: active (exited)'

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

Title:
  On laptops, screen brightness and keyboard backlight isn't memorized
  between sessions

Status in Dell Sputnik:
  New
Status in One Hundred Papercuts:
  Won't Fix
Status in Linux Mint:
  Confirmed
Status in upstart :
  Confirmed
Status in cinnamon-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Won't Fix
Status in mate-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Won't Fix

Bug description:
  HOW TO REPRODUCE:
    1. Boot a laptop.
    2. Set a different screen (or keyboard) backlight brightness level.
    3. Reboot.

  RESULT:
    Backlight is not memorized.

  FIX:
    A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA
  sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight
  sudo apt-get update
  sudo apt-get install sysvinit-backlight

  NOTES:
  1. If you have installed previous non-deb version, please remove it 
carefully manually
    sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness 
/etc/rc?.d/?25brightness
      2. If you have installed previous version from my PPA on Ubuntu 14.04 
LTS, please reinstall the package by:
    sudo apt-get purge sysvinit-backlight
    sudo apt-get install sysvinit-backlight
  3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too.

    B. Ubuntu 14.10 is at EOL (from July 2015), Ubuntu 15.04 is at EOL (from  
January 2016), Ubuntu 15.10 is near EOL (really at July 2016), so users should 
upgrade them to Ubuntu 16.04 (see C below).
   My script is incompatible with these Ubuntu versions - remove it with
    sudo apt-get purge sysvinit-backlight
    sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight

    C. Ubuntu 15.04, 15.10 and 16.04 LTS have systemd-backlight@.service. It 
saves and restores screen and keyboard backlight levels.
   My script is incompatible with these Ubuntu versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 19 17:20:26 2014
  InstallationDate: Installed on 2013-10-20 (91 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

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

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


[Desktop-packages] [Bug 1672931] Re: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar)

2017-04-05 Thread Christopher Townsend
Hey Daniel,

That xmir commit does not fix this issue:) It only fixes the crash.  I'm
still working on a proper solution for xmir, which I'm close to
committing.

** Changed in: xorg-server (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of
  native GTK/Qt (and so menus don't appear in the titlebar)

Status in Canonical System Image:
  Confirmed
Status in Libertine:
  In Progress
Status in Libertine devel series:
  In Progress
Status in Libertine trunk series:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in libertine package in Ubuntu:
  Triaged
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-app-launch package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  In Progress

Bug description:
  Qt & GTK apps on Unity8 are defaulting to Xmir instead of native
  GTK/Qt on Mir.

  I noticed a slight change in appearance and performance, but also:

  dan  25410  0.1  0.2 423316 38996 ?Sl   11:14   0:00 Xmir 
-rootless -displayfd 3 -mir org.gnome.Calculator
  dan  25456  1.8  0.5 606084 91736 ?Sl   11:14   0:03 Xmir 
-rootless -displayfd 3 -mir org.gnome.Nautilus
  dan  25611  1.7  0.2 345312 35520 ?Sl   11:18   0:00 Xmir 
-rootless -displayfd 3 -mir webbrowser-app_webbrowser-app_10

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

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


[Desktop-packages] [Bug 1680087] Re: package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other instances

2017-04-05 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite
  shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is
  different from other instances of package libogg0:i386

Status in libogg package in Ubuntu:
  New

Bug description:
  Since I updated ubuntu 14.04 to 16.04, I can not use "apt-get install'

  Vous pouvez lancer « apt-get -f install » pour corriger ces problèmes :
  Les paquets suivants contiennent des dépendances non satisfaites :
   aptitude : Dépend: libcwidget3v5 mais ne sera pas installé
   gstreamer1.0-plugins-base:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne 
sera pas installé
   libflac8:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne sera pas installé
   libtheora0:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé
   libvorbis0a:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé
  E: Dépendances non satisfaites. Essayez « apt-get -f install » sans paquet

  When I follow the instruction 'apt-get -f install' :

  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack) :
   tentative de remplacement de « /usr/share/doc/libogg0/changelog.Debian.gz », 
qui est différent d'autres instances du paquet libogg0:i386
  Des erreurs ont été rencontrées pendant l'exécution :
   /var/cache/apt/archives/libogg0_1.3.2-1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libogg0 1.3.2-1
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 04:03:24 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  DuplicateSignature:
   package:libogg0:1.3.2-1
   Unpacking libogg0:i386 (1.3.2-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', 
which is different from other instances of package libogg0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other 
instances of package libogg0:i386
  InstallationDate: Installed on 2014-11-03 (884 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libogg
  Title: package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from 
other instances of package libogg0:i386
  UpgradeStatus: Upgraded to xenial on 2017-04-03 (1 days ago)

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

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


[Desktop-packages] [Bug 1497166] Re: procps' 10-ipv6-privacy.conf stomps on the ifup/NetworkManager "privext"/"ipv6.ip6-privacy" settings

2017-04-05 Thread Mathieu Trudel-Lapierre
Ok, closing as Fix Released then if it's fixed.

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

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

** Changed in: ifupdown (Ubuntu)
   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/1497166

Title:
  procps' 10-ipv6-privacy.conf stomps on the ifup/NetworkManager
  "privext"/"ipv6.ip6-privacy" settings

Status in ifupdown package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  Invalid

Bug description:
  I have configured the following in /etc/network/interfaces:

  auto eth0
  iface eth0 inet6 auto
privext 0

  According to interfaces(5), this should disable IPv6 Privacy
  Extensions. However, after booting the machine,
  /proc/sys/net/ipv6/conf/eth0/use_tempaddr contains the value "2" -
  which means that Privacy Extensions are enabled. However running
  "ifdown eth0; ifup eth0" does fix the problem, so it is clear that
  ifup(8) does correctly set the use_tempaddr sysctl when bringing up
  the interface.

  What's going on is that sometime later in the bootup process, the
  procps package overrides the user-configured value and sets it
  unconditionally to "2" for every interface on the system. This happens
  because the file /etc/sysctl.d/10-ipv6-privacy.conf contains
  "net.ipv6.conf.all.use_tempaddr = 2". It should not, or this bug
  should be reassigned to the ifupdown package requesting for the
  removal of the defunct "privext" setting.

  On a related node, enabling IPv6 Privacy Extensions by default is
  counter to RFC 4941's recommendations. Quoting from section 3.6
  Deployment Considerations:

 The use of temporary addresses may cause unexpected difficulties with
 some applications.  As described below, some servers refuse to accept
 communications from clients for which they cannot map the IP address
 into a DNS name.  In addition, some applications may not behave
 robustly if temporary addresses are used and an address expires
 before the application has terminated, or if it opens multiple
 sessions, but expects them to all use the same addresses.
 Consequently, the use of temporary addresses SHOULD be disabled by
 default in order to minimize potential disruptions.  Individual
 applications, which have specific knowledge about the normal duration
 of connections, MAY override this as appropriate.

  As such, the most appropriate course of action is probably to stop
  shipping the 10-ipv6-privacy.conf file by default.

  The described behaviour is observed on Trusty LTS.

  Tore

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

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


[Desktop-packages] [Bug 1680087] [NEW] package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other instanc

2017-04-05 Thread ha
Public bug reported:

Since I updated ubuntu 14.04 to 16.04, I can not use "apt-get install'

Vous pouvez lancer « apt-get -f install » pour corriger ces problèmes :
Les paquets suivants contiennent des dépendances non satisfaites :
 aptitude : Dépend: libcwidget3v5 mais ne sera pas installé
 gstreamer1.0-plugins-base:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne sera 
pas installé
 libflac8:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne sera pas installé
 libtheora0:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé
 libvorbis0a:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé
E: Dépendances non satisfaites. Essayez « apt-get -f install » sans paquet

When I follow the instruction 'apt-get -f install' :

dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack) :
 tentative de remplacement de « /usr/share/doc/libogg0/changelog.Debian.gz », 
qui est différent d'autres instances du paquet libogg0:i386
Des erreurs ont été rencontrées pendant l'exécution :
 /var/cache/apt/archives/libogg0_1.3.2-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libogg0 1.3.2-1
ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
Uname: Linux 4.4.0-71-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue Apr  4 04:03:24 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu7
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu7
DuplicateSignature:
 package:libogg0:1.3.2-1
 Unpacking libogg0:i386 (1.3.2-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', 
which is different from other instances of package libogg0:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libogg0/changelog.Debian.gz', which is different from other 
instances of package libogg0:i386
InstallationDate: Installed on 2014-11-03 (884 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: libogg
Title: package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite 
shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is different from 
other instances of package libogg0:i386
UpgradeStatus: Upgraded to xenial on 2017-04-03 (1 days ago)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict xenial

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

Title:
  package libogg0 1.3.2-1 failed to install/upgrade: trying to overwrite
  shared '/usr/share/doc/libogg0/changelog.Debian.gz', which is
  different from other instances of package libogg0:i386

Status in libogg package in Ubuntu:
  New

Bug description:
  Since I updated ubuntu 14.04 to 16.04, I can not use "apt-get install'

  Vous pouvez lancer « apt-get -f install » pour corriger ces problèmes :
  Les paquets suivants contiennent des dépendances non satisfaites :
   aptitude : Dépend: libcwidget3v5 mais ne sera pas installé
   gstreamer1.0-plugins-base:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne 
sera pas installé
   libflac8:i386 : Dépend: libogg0:i386 (>= 1.0rc3) mais ne sera pas installé
   libtheora0:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé
   libvorbis0a:i386 : Dépend: libogg0:i386 (>= 1.1.0) mais ne sera pas installé
  E: Dépendances non satisfaites. Essayez « apt-get -f install » sans paquet

  When I follow the instruction 'apt-get -f install' :

  dpkg: erreur de traitement de l'archive 
/var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack) :
   tentative de remplacement de « /usr/share/doc/libogg0/changelog.Debian.gz », 
qui est différent d'autres instances du paquet libogg0:i386
  Des erreurs ont été rencontrées pendant l'exécution :
   /var/cache/apt/archives/libogg0_1.3.2-1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libogg0 1.3.2-1
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue Apr  4 04:03:24 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu7
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu7
  DuplicateSignature:
   package:libogg0:1.3.2-1
   Unpacking libogg0:i386 (1.3.2-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libogg0_1.3.2-1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libogg0/changelog.Debian.gz', 
which is different from other instances of package libogg0:i386
  ErrorMessage: trying to overwrite shared 

[Desktop-packages] [Bug 1677924] Re: Local privilege escalation via guest user login

2017-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package lightdm - 1.22.0-0ubuntu2

---
lightdm (1.22.0-0ubuntu2) zesty; urgency=medium

  * SECURITY UPDATE: Directory traversal allowing arbitrary directory
ownership and privilege escalation (LP: #1677924)
- debian/guest-account.sh: Detect existing malicious guest user home dirs
  before proceeding with guest user creation
- CVE-2017-7358

 -- Robert Ancell   Wed, 05 Apr 2017
10:34:32 +1200

** Changed in: lightdm (Ubuntu Zesty)
   Status: Triaged => Fix Released

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

Title:
  Local privilege escalation via guest user login

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in Light Display Manager 1.20 series:
  Fix Released
Status in Light Display Manager 1.22 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released

Bug description:
  It was discovered that a local attacker could watch for lightdm's
  guest-account script to create a /tmp/guest-XX file and then quickly 
create
  the lowercase representation of the guest user's home directory before lightdm
  could. This allowed the attacker to have control of the guest user's home
  directory and, subsequently, gain control of an arbitrary directory in the
  filesystem which could lead to privilege escalation.

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

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


[Desktop-packages] [Bug 1680045] Re: AbiWord opens 2 transparent windows on top

2017-04-05 Thread dinamic
** Also affects: abiword (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  AbiWord opens 2 transparent windows on top

Status in Canonical System Image:
  New
Status in abiword package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity8

  AbiWord opens 2 transparent windows on top (see screenshot) and if
  closed while the transparent windows are opened it will leave a
  process running 160% cpu forever

  run abiword (without Xmir), close

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

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


[Desktop-packages] [Bug 1618712] Re: Xmir -rootless: Fullscreen apps never go full screen

2017-04-05 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  Xmir -rootless: Fullscreen apps never go full screen

Status in Canonical System Image:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  Xmir -rootless: Fullscreen apps never go full screen.

  E.g. Press F11 in Gnome Terminal or in Chrome.

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

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


[Desktop-packages] [Bug 1674677] Re: eglGetDisplay(EGL_DEFAULT_DISPLAY) returns EGL_NO_DISPLAY

2017-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-375 -
375.39-0ubuntu3

---
nvidia-graphics-drivers-375 (375.39-0ubuntu3) zesty; urgency=medium

  [ Thomas Foster ]
  * debian/nvidia-375.install:
- install glvnd EGL vendor configuration file (LP: #1674677)

 -- Alberto Milone   Wed, 05 Apr 2017
10:14:48 +0200

** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  eglGetDisplay(EGL_DEFAULT_DISPLAY) returns EGL_NO_DISPLAY

Status in One Hundred Papercuts:
  Confirmed
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Fix Released

Bug description:
  I am using EGL to obtain offscreen rendering contexts, but upgrading
  this package today broke my application.  I have written a small test
  case, that I expect to print "PASS":

  ```
  #include   
 
  #include
 

 
  int main(int argc, char **argv) { 
 
  EGLDisplay eglDpy = eglGetDisplay(EGL_DEFAULT_DISPLAY);   
 
  std::cout << ((eglDpy == EGL_NO_DISPLAY) ? "FAIL" : "PASS") << std::endl; 
 
  }
  ```

  Build with e.g. `g++ egl_test.cpp -lEGL`.  Using nvidia-375
  (375.39-0ubuntu0.16.04.1), this test program will print "FAIL",
  because `eglGetDisplay(EGL_DEFAULT_DISPLAY)` returns `EGL_NO_DISPLAY`.
  If I install the 375.39 driver using Nvidia's installer, the test
  passes, so I think it is not an upstream issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-375 375.39-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 21 12:41:31 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-11 (160 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: nvidia-graphics-drivers-375
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1270579] Re: On laptops, screen brightness and keyboard backlight isn't memorized between sessions

2017-04-05 Thread aljosa
ASUS G752VS non-optimus laptop (Nvidia GTX1070)
Ubuntu 17.04
Linux 4.10.0-15-generic
Xorg-Server-1.19.3

Ubuntu 17.04 doesn't save my brightness settings. I can adjust the
screen brightness but after restarting the screen brightness of my
laptop resets to maximum. How can I ensure that my brightness preference
will persist after reboot?

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

Title:
  On laptops, screen brightness and keyboard backlight isn't memorized
  between sessions

Status in Dell Sputnik:
  New
Status in One Hundred Papercuts:
  Won't Fix
Status in Linux Mint:
  Confirmed
Status in upstart :
  Confirmed
Status in cinnamon-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Won't Fix
Status in mate-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Won't Fix

Bug description:
  HOW TO REPRODUCE:
    1. Boot a laptop.
    2. Set a different screen (or keyboard) backlight brightness level.
    3. Reboot.

  RESULT:
    Backlight is not memorized.

  FIX:
    A. For Ubuntu 12.04 LTS and 14.04 LTS install my package from PPA
  sudo add-apt-repository ppa:nrbrtx/sysvinit-backlight
  sudo apt-get update
  sudo apt-get install sysvinit-backlight

  NOTES:
  1. If you have installed previous non-deb version, please remove it 
carefully manually
    sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness 
/etc/rc?.d/?25brightness
      2. If you have installed previous version from my PPA on Ubuntu 14.04 
LTS, please reinstall the package by:
    sudo apt-get purge sysvinit-backlight
    sudo apt-get install sysvinit-backlight
  3. Version 0.1ubuntu1 supports save/restore of keyboard backlight too.

    B. Ubuntu 14.10 is at EOL (from July 2015), Ubuntu 15.04 is at EOL (from  
January 2016), Ubuntu 15.10 is near EOL (really at July 2016), so users should 
upgrade them to Ubuntu 16.04 (see C below).
   My script is incompatible with these Ubuntu versions - remove it with
    sudo apt-get purge sysvinit-backlight
    sudo add-apt-repository -r ppa:nrbrtx/sysvinit-backlight

    C. Ubuntu 15.04, 15.10 and 16.04 LTS have systemd-backlight@.service. It 
saves and restores screen and keyboard backlight levels.
   My script is incompatible with these Ubuntu versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 19 17:20:26 2014
  InstallationDate: Installed on 2013-10-20 (91 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

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

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


[Desktop-packages] [Bug 1680030] Re: Snap plugin for gnome-software misses self tests

2017-04-05 Thread Simon Fels
** Summary changed:

- Snap plug for gnome-software misses self tests
+ Snap plugin for gnome-software misses self tests

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

Title:
  Snap plugin for gnome-software misses self tests

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The snap plugin implemented in gnome-software upstream does not have
  any self tests yet which were requested by upstream to get the plugin
  into a better shape.

  Tested with latest gnome-software from https://git.gnome.org/browse
  /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6

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

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


[Desktop-packages] [Bug 1680045] [NEW] AbiWord opens 2 transparent windows on top

2017-04-05 Thread dinamic
Public bug reported:

Ubuntu 17.04 Unity8

AbiWord opens 2 transparent windows on top (see screenshot) and if
closed while the transparent windows are opened it will leave a process
running 160% cpu forever

run abiword (without Xmir), close

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

** Attachment added: "screenshot20170405_145810632.png"
   
https://bugs.launchpad.net/bugs/1680045/+attachment/4855279/+files/screenshot20170405_145810632.png

** 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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1680045

Title:
  AbiWord opens 2 transparent windows on top

Status in Canonical System Image:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity8

  AbiWord opens 2 transparent windows on top (see screenshot) and if
  closed while the transparent windows are opened it will leave a
  process running 160% cpu forever

  run abiword (without Xmir), close

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

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


[Desktop-packages] [Bug 1680041] Re: signon-ui crashed with SIGABRT

2017-04-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1194732 ***
https://bugs.launchpad.net/bugs/1194732

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 #1194732, 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/1680041/+attachment/4855270/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1194732
   signon-ui crashed with SIGABRT in qt_message_fatal()

** 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 signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1680041

Title:
  signon-ui crashed with SIGABRT

Status in signon-ui package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: signon-ui-x11 0.17+17.04.20170320-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7
  Date: Tue Apr  4 10:34:09 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/signon-ui
  ExecutableTimestamp: 1490022257
  InstallationDate: Installed on 2017-03-25 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/signon-ui
  ProcCwd: /home/anders
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: signon-ui
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, 
char const*) () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () at 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   () at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: signon-ui crashed with SIGABRT
  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/signon-ui/+bug/1680041/+subscriptions

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


[Desktop-packages] [Bug 1342031] Re: Rename QML modules to follow qml-module-foo naming

2017-04-05 Thread Timo Jyrinki
** Description changed:

- UPDATE: This would be a nice to have for Ubuntu 16.04 LTS, since
- otherwise we will need to keep the transitional packages until 2018.
- 
+ UPDATE: This would be a nice to have for Ubuntu 16.04 LTS, since otherwise we 
will need to keep the transitional packages until 2018.
+ UPDATE2: This would be a nice to have for Ubuntu 18.04 LTS, since otherwise 
we will need to keep the transitional packages until 2020.
  
  ===
  
  The package names of QML modules should be of the format qml-
  module-{$modulename}[version], a transition that was started during Qt
  5.3 preparation in Ubuntu. For example this could be qml-module-qtquick-
  localstorage or qml-module-qtsysteminfo for non versioned modules, and
  qml-module-ubuntu-webthing0.3 for versioned/co-installable modules.
  
  Further details in Debian e-mail:
  http://lists.alioth.debian.org/pipermail/pkg-kde-
  talk/2014-March/001889.html
  
  For Ubuntu, transitional packages should be put in place for smooth 
distribution upgrades, since we're shipping with the old names in previous 
Ubuntus. An example of that is at 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31
 - in other words:
  - Make the old package a transitional oldlibs package that depends on the new 
package
  - Add Breaks/Replaces to the new package for the old non-transitional 
packages (be careful about the version number specification)
  - Keep Multi-Arch: same and Architecture: any for the transitional package
  - Write "QML module" instead of "QML plugin"
  - Rename also the *.install files
  
  ---
  One more example on naming:
  
  For example, the "test" (qtdeclarative5-test-plugin) in the old
  qtdeclarative5-style package naming became "qttest" (qml-module-qttest)
  in the new naming since the path is actually under
  /usr/lib/*/qt5/qml/QtTest/
  
  qml-module-qtquick-xmllistmodel has path
  /usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have more
  than one subdir. /usr/lib/*/qt5/qml/Ubuntu/Connectivity/ would be qml-
  module-ubuntu-connectivity.

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

Title:
  Rename QML modules to follow qml-module-foo naming

Status in accounts-qml-module package in Ubuntu:
  Fix Released
Status in address-book-app package in Ubuntu:
  Fix Released
Status in bacon2d package in Ubuntu:
  Triaged
Status in clickmanager-plugin package in Ubuntu:
  New
Status in content-hub package in Ubuntu:
  New
Status in cordova-ubuntu package in Ubuntu:
  New
Status in dee-qt package in Ubuntu:
  New
Status in gsettings-qt package in Ubuntu:
  New
Status in history-service package in Ubuntu:
  New
Status in libhud-qt package in Ubuntu:
  Won't Fix
Status in libqofono package in Ubuntu:
  Fix Released
Status in libusermetrics package in Ubuntu:
  New
Status in mediascanner2 package in Ubuntu:
  Fix Released
Status in oxide-qt package in Ubuntu:
  New
Status in poppler-qml-plugin package in Ubuntu:
  New
Status in qml-box2d package in Ubuntu:
  New
Status in qml-friends package in Ubuntu:
  New
Status in qt3d-opensource-src package in Ubuntu:
  Fix Released
Status in qtconnectivity-opensource-src package in Ubuntu:
  Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
  Fix Released
Status in qtfeedback-opensource-src package in Ubuntu:
  Fix Released
Status in qtgrilo package in Ubuntu:
  New
Status in qtlocation-opensource-src package in Ubuntu:
  Fix Released
Status in qtmultimedia-opensource-src package in Ubuntu:
  Fix Released
Status in qtpim-opensource-src package in Ubuntu:
  Fix Released
Status in qtquickcontrols-opensource-src package in Ubuntu:
  Fix Released
Status in qtsensors-opensource-src package in Ubuntu:
  Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
  Fix Released
Status in reminders-app package in Ubuntu:
  New
Status in solid package in Ubuntu:
  New
Status in sync-monitor package in Ubuntu:
  New
Status in telephony-service package in Ubuntu:
  Triaged
Status in thumbnailer package in Ubuntu:
  Fix Released
Status in u1db-qt package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Triaged
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-settings-components package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released
Status in ubuntu-ui-extras package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntuone-credentials package in Ubuntu:
  Fix Released
Status in unity-action-api package in Ubuntu:
  Triaged
Status in unity-notifications package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  Fix Released

Bug description:
  UPDATE: This would be a nice to have for 

[Desktop-packages] [Bug 1680027] Re: gnome-software doesn't use snapd-glib exclusively

2017-04-05 Thread Simon Fels
** Description changed:

  The code submitted to gnome-software upstream still doesn't use snapd-
  glib exclusively but has parts of the snapd REST API which are handled
  by its own. The HTTP REST API logic should be only implemented once and
  that in snapd-glib. See https://git.gnome.org/browse/gnome-
  software/tree/plugins/snap/gs-snapd.c
  
+ Tested with latest gnome-software from https://git.gnome.org/browse
+ /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6
+ 
  This blocks enablement of snap support in gnome-software on Fedora.

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

Title:
  gnome-software doesn't use snapd-glib exclusively

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The code submitted to gnome-software upstream still doesn't use snapd-
  glib exclusively but has parts of the snapd REST API which are handled
  by its own. The HTTP REST API logic should be only implemented once
  and that in snapd-glib. See https://git.gnome.org/browse/gnome-
  software/tree/plugins/snap/gs-snapd.c

  Tested with latest gnome-software from https://git.gnome.org/browse
  /gnome-software/ on Ubuntu 17.04 against snapd 2.23.6

  This blocks enablement of snap support in gnome-software on Fedora.

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

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


  1   2   >