[Desktop-packages] [Bug 1745105] Re: Make "Revert (Display) settings" the default option

2018-01-23 Thread Daniel van Vugt
When done, please let us know the ID of your newly created bug.

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

Title:
  Make "Revert (Display) settings" the default option

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  In Display settings, the default option when changes the configuration is 
"keep changes".
  If there is a problem and you can NOT see the message, if you press "Intro" 
(accidently or because you don't know what to do) is going to keep the change 
so you are going to be in troubles.

  Should not be "Revert settings" the default option?

  System:
  Ubuntu 17.10
  GNOME Shell 3.26.2

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

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


[Desktop-packages] [Bug 1745105] Re: Display setting default option

2018-01-23 Thread Daniel van Vugt
Interesting idea. Since this would be a design change, please submit it
to the upstream developers here:

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

** Summary changed:

- Display setting default option
+ Make "Revert (Display) settings" the default option

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Make "Revert (Display) settings" the default option

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  In Display settings, the default option when changes the configuration is 
"keep changes".
  If there is a problem and you can NOT see the message, if you press "Intro" 
(accidently or because you don't know what to do) is going to keep the change 
so you are going to be in troubles.

  Should not be "Revert settings" the default option?

  System:
  Ubuntu 17.10
  GNOME Shell 3.26.2

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

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


[Desktop-packages] [Bug 1745105] [NEW] Display setting default option

2018-01-23 Thread Angel Cervera Claudio
Public bug reported:

In Display settings, the default option when changes the configuration is "keep 
changes".
If there is a problem and you can NOT see the message, if you press "Intro" 
(accidently or because you don't know what to do) is going to keep the change 
so you are going to be in troubles.

Should not be "Revert settings" the default option?

System:
Ubuntu 17.10
GNOME Shell 3.26.2

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


** Tags: ux

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

Title:
  Display setting default option

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In Display settings, the default option when changes the configuration is 
"keep changes".
  If there is a problem and you can NOT see the message, if you press "Intro" 
(accidently or because you don't know what to do) is going to keep the change 
so you are going to be in troubles.

  Should not be "Revert settings" the default option?

  System:
  Ubuntu 17.10
  GNOME Shell 3.26.2

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

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


[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with Chromium

2018-01-23 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1652110 ***
https://bugs.launchpad.net/bugs/1652110

No need for Saikrishna's PPA for that, the patches to have external
widevine libs located have been integrated in the official Ubuntu
packages, starting at version 63.0.3239.84.

A wild guess is that maybe the version of the widevine libs you have is
too old and thus incompatible with that version of chromium?

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

Title:
  Unable to use the widevine plugin with Chromium

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium is unable to use the widevine component from google chrome :
  libwidevinecdmadapter.so and libwidevinecdm.so

  How to reproduce :

  - copy the 2 files the chrome archive in /usr/lib/chromium-browser
  - check chrome://components/
  - Widevine does not appear

  Solution :

  With the help from several people (hogliux for patch and saiarcot895
  for PPA) , a PPA is available with this feature :

  - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  - You need the binary widevine plugin plugin (2 files) :

  https://bugs.launchpad.net/ubuntu/+source/chromium-
  
browser/+bug/1371274/+attachment/4397708/+files/WidevineLinuxForChromium44.tar.gz

  To be copied in /usr/lib/chromium

  - Launch netflix.com and see if it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep 18 21:11:17 2014
  InstallationDate: Installed on 2013-10-02 (350 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'system-image-cli'
  UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932

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

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


[Desktop-packages] [Bug 1745094] [NEW] package ubuntu-software 3.20.5-0ubuntu0.16.04.6 failed to install/upgrade: paketet ubuntu-software är inte redo för att konfigureras kan inte konfigurera (aktue

2018-01-23 Thread Peter de Laval
Public bug reported:

This happened while the system was booting.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ubuntu-software 3.20.5-0ubuntu0.16.04.6
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 tzdata: Install
 ubuntu-software: Configure
 tzdata: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Jan 24 07:34:37 2018
DpkgTerminalLog:
 Förbereder att packa upp .../tzdata_2017c-0ubuntu0.16.04_all.deb ...
 Packar upp tzdata (2017c-0ubuntu0.16.04) över (2016j-0ubuntu0.16.04) ...
 dpkg: fel vid hantering av paketet ubuntu-software (--configure):
  paketet ubuntu-software är inte redo för att konfigureras
  kan inte konfigurera (aktuell status är "half-installed")
ErrorMessage: paketet ubuntu-software är inte redo för att konfigureras  kan 
inte konfigurera (aktuell status är "half-installed")
InstallationDate: Installed on 2016-08-09 (532 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: gnome-software
Title: package ubuntu-software 3.20.5-0ubuntu0.16.04.6 failed to 
install/upgrade: paketet ubuntu-software är inte redo för att konfigureras  kan 
inte konfigurera (aktuell status är "half-installed")
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package ubuntu-software 3.20.5-0ubuntu0.16.04.6 failed to
  install/upgrade: paketet ubuntu-software är inte redo för att
  konfigureras  kan inte konfigurera (aktuell status är "half-
  installed")

Status in gnome-software package in Ubuntu:
  New

Bug description:
  This happened while the system was booting.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-software 3.20.5-0ubuntu0.16.04.6
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   tzdata: Install
   ubuntu-software: Configure
   tzdata: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Jan 24 07:34:37 2018
  DpkgTerminalLog:
   Förbereder att packa upp .../tzdata_2017c-0ubuntu0.16.04_all.deb ...
   Packar upp tzdata (2017c-0ubuntu0.16.04) över (2016j-0ubuntu0.16.04) ...
   dpkg: fel vid hantering av paketet ubuntu-software (--configure):
paketet ubuntu-software är inte redo för att konfigureras
kan inte konfigurera (aktuell status är "half-installed")
  ErrorMessage: paketet ubuntu-software är inte redo för att konfigureras  kan 
inte konfigurera (aktuell status är "half-installed")
  InstallationDate: Installed on 2016-08-09 (532 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gnome-software
  Title: package ubuntu-software 3.20.5-0ubuntu0.16.04.6 failed to 
install/upgrade: paketet ubuntu-software är inte redo för att konfigureras  kan 
inte konfigurera (aktuell status är "half-installed")
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

2018-01-23 Thread Václav Haisman
So, I have been experimenting. I have removed ulimit -v 100...0 out of
the command line because I have unlimited limit by default. What I have
added though is ulimit -s 16384 which doubles stack limit and I have
also ulimit -n 2048 to double file limit. Todays backup passed without
the usual exception.

I suggest others do the same. Find out file handle limits and stack size
limits and try again with doubled values. And remove the VM limit if it
actually sets a limit from unlimited.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1745093] [NEW] package firefox (not installed) failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/firefox/browser/features/activity-str...@mozilla.org.x

2018-01-23 Thread carlos pereira da silva
Public bug reported:

uso lubuntu o firefox sempre funcionou corretamente e sempre que ligo o
pc  digito sudo apt-get update  e sudo apt-get upgrade e o uso do
navegador firefox não funcionou não abre.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: firefox (not installed)
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic i686
ApportVersion: 2.20.7-0ubuntu3.7
AptOrdering:
 firefox:i386: Install
 NULL: ConfigurePending
Architecture: i386
Date: Wed Jan 24 03:25:49 2018
ErrorMessage: não pode copiar dados extráidos para 
'./usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi' para 
'/usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi.dpkg-new': 
fim de ficheiro ou stream inesperado
InstallationDate: Installed on 2018-01-04 (19 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: firefox
Title: package firefox (not installed) failed to install/upgrade: não pode 
copiar dados extráidos para 
'./usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi' para 
'/usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi.dpkg-new': 
fim de ficheiro ou stream inesperado
UpgradeStatus: Upgraded to artful on 2018-01-05 (19 days ago)

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


** Tags: apport-package artful i386

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

Title:
  package firefox (not installed) failed to install/upgrade: não pode
  copiar dados extráidos para './usr/lib/firefox/browser/features
  /activity-str...@mozilla.org.xpi' para
  '/usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi
  .dpkg-new': fim de ficheiro ou stream inesperado

Status in firefox package in Ubuntu:
  New

Bug description:
  uso lubuntu o firefox sempre funcionou corretamente e sempre que ligo
  o pc  digito sudo apt-get update  e sudo apt-get upgrade e o uso do
  navegador firefox não funcionou não abre.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: firefox (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic i686
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   firefox:i386: Install
   NULL: ConfigurePending
  Architecture: i386
  Date: Wed Jan 24 03:25:49 2018
  ErrorMessage: não pode copiar dados extráidos para 
'./usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi' para 
'/usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi.dpkg-new': 
fim de ficheiro ou stream inesperado
  InstallationDate: Installed on 2018-01-04 (19 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: firefox
  Title: package firefox (not installed) failed to install/upgrade: não pode 
copiar dados extráidos para 
'./usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi' para 
'/usr/lib/firefox/browser/features/activity-str...@mozilla.org.xpi.dpkg-new': 
fim de ficheiro ou stream inesperado
  UpgradeStatus: Upgraded to artful on 2018-01-05 (19 days ago)

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

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


[Desktop-packages] [Bug 1745080] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-01-23 Thread dino99
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  New to Linux.  Trying to install Wine from
  https://wiki.winehq.org/Ubuntu.  Followed all the instructions.  All
  went fine until the end when I got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Jan 23 22:13:38 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QOF7eR/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-22 (1 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1734196] Re: gnome-control-center: Ubuntu dock settings is blank

2018-01-23 Thread Launchpad Bug Tracker
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  gnome-control-center: Ubuntu dock settings is blank

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

Bug description:
  Upon opening the Dock settings in gnome-control-center, I find that it
  is blank and devoid from any information or settings. the only thing
  that is there is a separator line at the very top. Also, I know this
  should be another bug report, but I want to say that the new gnome-
  shell for Ubuntu is not showing up for me and instead shows the
  default gnome-shell.

  1.
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  2.
  gnome-control-center:
    Installed: 1:3.26.2-0ubuntu1
    Candidate: 1:3.26.2-0ubuntu1
    Version table:
   *** 1:3.26.2-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  3. I expected there to be settings and information to show up in the dock 
settings.
  4. I got a blank canvas and a separator line in the dock settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 11:40:49 2017
  InstallationDate: Installed on 2017-07-20 (126 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2017-11-23 (0 days ago)

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

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


[Desktop-packages] [Bug 1737979] Re: Wayland freezes with matplotlib

2018-01-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Wayland freezes with matplotlib

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce problem:
  _ Using python and matplotlib to plot something
  _ When the plot appears, move the mouse to save icon
  _ Boom, it's freezed
  Wait several minutes for it to start moving again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 20:45:02 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:13dd]
  InstallationDate: Installed on 2017-11-03 (39 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. X451CAP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X451CAP.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X451CAP
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX451CAP.203:bd02/18/2014:svnASUSTeKCOMPUTERINC.:pnX451CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX451CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X451CAP
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with Chromium

2018-01-23 Thread Saikrishna Arcot
*** This bug is a duplicate of bug 1652110 ***
https://bugs.launchpad.net/bugs/1652110

armhf is not building in my PPAs, so I can't test whether it's working
in my setup on that version.

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

Title:
  Unable to use the widevine plugin with Chromium

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium is unable to use the widevine component from google chrome :
  libwidevinecdmadapter.so and libwidevinecdm.so

  How to reproduce :

  - copy the 2 files the chrome archive in /usr/lib/chromium-browser
  - check chrome://components/
  - Widevine does not appear

  Solution :

  With the help from several people (hogliux for patch and saiarcot895
  for PPA) , a PPA is available with this feature :

  - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  - You need the binary widevine plugin plugin (2 files) :

  https://bugs.launchpad.net/ubuntu/+source/chromium-
  
browser/+bug/1371274/+attachment/4397708/+files/WidevineLinuxForChromium44.tar.gz

  To be copied in /usr/lib/chromium

  - Launch netflix.com and see if it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep 18 21:11:17 2014
  InstallationDate: Installed on 2013-10-02 (350 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'system-image-cli'
  UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932

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

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


[Desktop-packages] [Bug 1745080] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-01-23 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 sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1745080

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  New to Linux.  Trying to install Wine from
  https://wiki.winehq.org/Ubuntu.  Followed all the instructions.  All
  went fine until the end when I got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Jan 23 22:13:38 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QOF7eR/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-22 (1 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1745080] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2018-01-23 Thread Joe Ferrari
Public bug reported:

New to Linux.  Trying to install Wine from
https://wiki.winehq.org/Ubuntu.  Followed all the instructions.  All
went fine until the end when I got this error.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Jan 23 22:13:38 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-QOF7eR/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-01-22 (1 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  New to Linux.  Trying to install Wine from
  https://wiki.winehq.org/Ubuntu.  Followed all the instructions.  All
  went fine until the end when I got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Jan 23 22:13:38 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-QOF7eR/13-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-22 (1 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1744584] Re: Exclude Snap .cache from Dejadup backups

2018-01-23 Thread Michael Terry
OK, I've committed a patch in upstream master that excludes
~/snap/*/*/.cache and uploaded a cherry-picked patch to bionic.

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

Title:
  Exclude Snap .cache from Dejadup backups

Status in Déjà Dup:
  Fix Committed
Status in Snappy:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  The official Backup solution offered by Ubuntu does not support
  advanced whitelisting/blacklisting of directories. With the
  introduction of snaps, the cache of the snap apps is stored in ~/snaps
  /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't
  be configured to exclude these directories from backups.

  Since 2009, there have been several requests from the community to add
  support of advanced include/exclude support in Dejadup but there is no
  progress. Do you have any plans to provide minimum support for
  excluding specific snap folders such as .cache?

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

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


[Desktop-packages] [Bug 1744584] Re: Exclude Snap .cache from Dejadup backups

2018-01-23 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/deja-dup/ubuntu

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

Title:
  Exclude Snap .cache from Dejadup backups

Status in Déjà Dup:
  Fix Committed
Status in Snappy:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  The official Backup solution offered by Ubuntu does not support
  advanced whitelisting/blacklisting of directories. With the
  introduction of snaps, the cache of the snap apps is stored in ~/snaps
  /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't
  be configured to exclude these directories from backups.

  Since 2009, there have been several requests from the community to add
  support of advanced include/exclude support in Dejadup but there is no
  progress. Do you have any plans to provide minimum support for
  excluding specific snap folders such as .cache?

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

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


[Desktop-packages] [Bug 1744584] Re: Exclude Snap .cache from Dejadup backups

2018-01-23 Thread Michael Terry
** Changed in: deja-dup
   Status: Triaged => Fix Committed

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

Title:
  Exclude Snap .cache from Dejadup backups

Status in Déjà Dup:
  Fix Committed
Status in Snappy:
  New
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  The official Backup solution offered by Ubuntu does not support
  advanced whitelisting/blacklisting of directories. With the
  introduction of snaps, the cache of the snap apps is stored in ~/snaps
  /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't
  be configured to exclude these directories from backups.

  Since 2009, there have been several requests from the community to add
  support of advanced include/exclude support in Dejadup but there is no
  progress. Do you have any plans to provide minimum support for
  excluding specific snap folders such as .cache?

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

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


[Desktop-packages] [Bug 1745070] Re: Decorations/headerbars are broken in bionic: double bar in Xorg logins and missing in Wayland logins

2018-01-23 Thread Daniel van Vugt
** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

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

Title:
  Decorations/headerbars are broken in bionic: double bar in Xorg logins
  and missing in Wayland logins

Status in Ubuntu theme:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Decorations/headerbars are broken in bionic: double bar in Xorg logins
  and missing window buttons + rounding in Wayland logins. Screenshots
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Wed Jan 24 10:15:01 2018
  InstallationDate: Installed on 2017-12-12 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

2018-01-23 Thread fermulator
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  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/gnome-shell/+bug/1714989/+subscriptions

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


[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server

2018-01-23 Thread Ads20000
That will take work that Ubuntu developers might not have the time to do. The 
process is here for anyone who does have time and wants to get this into 17.10, 
it's thorough because updates into existing releases is risky...it might be 
that the fix from 37 needs to be backported to 36...
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

Title:
  "Operation not supported by backend" when backing up to smb server

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

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with Chromium

2018-01-23 Thread Richard Audette
*** This bug is a duplicate of bug 1652110 ***
https://bugs.launchpad.net/bugs/1652110

https://github.com/kusti8/chromium-build/releases/download/netflix-1.0.0
/chromium-browser_56.0.2924.84-0ubuntu0.14.04.1.1011.deb is a not-
official build, which works with Raspbian, where someone has bundled the
widevine libraries, presumably pulled from a Chromebook.  On the Pi, it
will run Netflix.  This is where I have found the armhf widevine
libraries.

On another system (the Odroid XU4, armhf) I am running Ubuntu, with
Chromium 63.0.3239.84-0ubuntu0.16.04.1, from this PPA:
https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev , as the
top of this thread suggested the Widevine libraries would be supported
if copied to the appropriate folder.

Using the armhf widevine libraries that I have taken from the Pi which
is working with Netflix, and copied into /usr/lib/chromium-browser of
63.0.3239.84-0ubuntu0.16.04.1 , I have been not been able to get Netflix
to work.

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

Title:
  Unable to use the widevine plugin with Chromium

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium is unable to use the widevine component from google chrome :
  libwidevinecdmadapter.so and libwidevinecdm.so

  How to reproduce :

  - copy the 2 files the chrome archive in /usr/lib/chromium-browser
  - check chrome://components/
  - Widevine does not appear

  Solution :

  With the help from several people (hogliux for patch and saiarcot895
  for PPA) , a PPA is available with this feature :

  - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  - You need the binary widevine plugin plugin (2 files) :

  https://bugs.launchpad.net/ubuntu/+source/chromium-
  
browser/+bug/1371274/+attachment/4397708/+files/WidevineLinuxForChromium44.tar.gz

  To be copied in /usr/lib/chromium

  - Launch netflix.com and see if it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep 18 21:11:17 2014
  InstallationDate: Installed on 2013-10-02 (350 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'system-image-cli'
  UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932

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

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


[Desktop-packages] [Bug 1744970] Re: Lowering some windows causes other, unrelated windows to also be lowered.

2018-01-23 Thread Daniel van Vugt
Bug confirmed. But to lower a window with middle click you need to be
logged into a Xorg session. It doesn't work in Wayland sessions (bug
1698083).

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

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

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

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

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

Title:
  Lowering some windows causes other, unrelated windows to also be
  lowered.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

    1. Open four windows, each using half of the screen:

  ┌──C──╥──D──┐
    ┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

    2. Lower window A.

  Expected behavior:

    Window A is lowered:

  ┌──A──╥──D──┐
    ┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

  Actual behavior:

    Window A and window B are lowered:

  ┌──A──╥──B──┐
    ┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 07:50:21 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-15 (495 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-21 (2 days ago)

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

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


[Desktop-packages] [Bug 1744970] Re: Lowering some windows causes other, unrelated windows to also be lowered.

2018-01-23 Thread Daniel van Vugt
Very nice. I fixed the whitespace by editing the description externally
and replacing them with non-breaking spaces.

** Description changed:

- Steps to reproduce:
+ Steps to reproduce:
  
-   1. Open four windows, each using half of the screen:
+   1. Open four windows, each using half of the screen:
  
- ┌──C──╥──D──┐
-   ┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐
-   │ ║ │ ││ ║ │
-   │ ║ │ └┤ ║ │
-   └─╨─┘  └─╨─┘
-  2D view3D view
+ ┌──C──╥──D──┐
+   ┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐
+   │ ║ │ ││ ║ │
+   │ ║ │ └┤ ║ │
+   └─╨─┘  └─╨─┘
+  2D view3D view
  
-   2. Lower window A.
+   2. Lower window A.
  
- Expected behavior:
+ Expected behavior:
  
-   Window A is lowered:
+   Window A is lowered:
  
- ┌──A──╥──D──┐
-   ┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐
-   │ ║ │ ││ ║ │
-   │ ║ │ └┤ ║ │
-   └─╨─┘  └─╨─┘
-  2D view3D view
+ ┌──A──╥──D──┐
+   ┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐
+   │ ║ │ ││ ║ │
+   │ ║ │ └┤ ║ │
+   └─╨─┘  └─╨─┘
+  2D view3D view
  
- Actual behavior:
+ Actual behavior:
  
-   Window A and window B are lowered:
+   Window A and window B are lowered:
  
- ┌──A──╥──B──┐
-   ┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐
-   │ ║ │ ││ ║ │
-   │ ║ │ └┤ ║ │
-   └─╨─┘  └─╨─┘
-  2D view3D view
+ ┌──A──╥──B──┐
+   ┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐
+   │ ║ │ ││ ║ │
+   │ ║ │ └┤ ║ │
+   └─╨─┘  └─╨─┘
+  2D view3D view
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 07:50:21 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-15 (495 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-21 (2 days ago)

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

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

Title:
  Lowering some windows causes other, unrelated windows to also be
  lowered.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

    1. Open four windows, each using half of the screen:

  ┌──C──╥──D──┐
    ┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

    2. Lower window A.

  Expected behavior:

    Window A is lowered:

  ┌──A──╥──D──┐
    ┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

  Actual behavior:

    Window A and window B are lowered:

  ┌──A──╥──B──┐
    ┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 07:50:21 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-15 (495 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-21 (2 days ago)

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

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


[Desktop-packages] [Bug 1744970] Re: Lowering some windows causes other, unrelated windows to also be lowered.

2018-01-23 Thread Daniel van Vugt
I am reminded of bug 1729461, although different. I also think there are
similar bug reports elsewhere but can't find them.

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

Title:
  Lowering some windows causes other, unrelated windows to also be
  lowered.

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

    1. Open four windows, each using half of the screen:

  ┌──C──╥──D──┐
    ┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

    2. Lower window A.

  Expected behavior:

    Window A is lowered:

  ┌──A──╥──D──┐
    ┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

  Actual behavior:

    Window A and window B are lowered:

  ┌──A──╥──B──┐
    ┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐
    │ ║ │ ││ ║ │
    │ ║ │ └┤ ║ │
    └─╨─┘  └─╨─┘
   2D view3D view

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 07:50:21 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-15 (495 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-21 (2 days ago)

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

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


[Desktop-packages] [Bug 857651] Re: Unable to hide users from login screen / user switcher

2018-01-23 Thread spike speigel
** Tags added: artful

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

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

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

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


[Desktop-packages] [Bug 1729461] Re: Clicking notification raises a slew of unrelated windows

2018-01-23 Thread Daniel van Vugt
** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Clicking notification raises a slew of unrelated windows

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Running GNOME Shell. When (for example) I click on a Signal
  notification, Shell will raise the Signal window, and then raises my
  password manager window, and two different(!) Telegram windows over
  the top.

  This is not the ideal behaviour :).

  This is not limited to Signal; Geary notifications suffer the same
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:26:18 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-20 (42 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170919)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1718654] Re: Touchpad input doesn't work after longer suspend.

2018-01-23 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  Touchpad input doesn't work after longer suspend.

Status in gnome-shell package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  When I resume my laptop from a longer (not sure what the threshold is
  yet) suspend, I don't get input from the touchpad, a short suspend
  cycle fixes it.

  Touchscreen works all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 21 14:20:56 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1712660] Re: application menu icon in title bar has wrong size

2018-01-23 Thread Egmont Koblinger
Please see lp:1724250 for some further investigation.

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

Title:
  application menu icon in title bar has wrong size

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in humanity-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  gnome-terminal application menu icon in the title bar has the wrong size. 
Porbably only affects humanity-icon-theme, works fine with a Ubuntu Gnome and 
the adwaita icon theme.
  See screenshot

  Ubuntu 17.10, gnome-temrinal 3.24.2-0ubuntu4

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

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


[Desktop-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

2018-01-23 Thread Egmont Koblinger
Yet another report of this bug, with further precious details and a
screenshot revealing that the misdrawn icon is bigger than 128, maybe
140 or 144 or so pixels large:

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

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

Title:
  gnome-terminal graphic artifact

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

2018-01-23 Thread Egmont Koblinger
The same bug is also reported at lp:1712660.

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

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

Title:
  gnome-terminal graphic artifact

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

2018-01-23 Thread Egmont Koblinger
Let's make it clear that it's absolutely most definitely not a bug in
gnome-terminal. Gnome-terminal uses old-fashioned server-side
decorations, that is, the window border is drawn by the window manager.
There is no way gnome-terminal could legally ask it to draw something
else there.

The picture there looks like part of a terminal icon, the one that's
shown e.g. in gnome-terminal's About dialog in 128x128. The misdrawn one
also seems to be of this size, however, scaled up from a lower
resolution.

The only way I can reasonably think of where the window manager takes
this icon from is the _NET_WM_ICON window property, as shown e.g. by the
xprop command. After you click on the desired window, by default it
prints a low-res variant of the picture to the terminal.

The output of "xprop -notype 32c _NET_WM_ICON" consists of two numbers:
the dimension, followed by that many numbers in the natural order, each
number encoding one pixel. E.g. for me the first two numbers are 32, 32,
and then the next 32^2 = 1024 numbers encode the icon in its smallest
size. Then it's followed by the same at size 48x48 (so far this
corresponds to the parameterless xprop command showing these two sizes).
and then it even starts printing at size 256x256 but the output stops
prematurely.

Look at e.g. https://unix.stackexchange.com/questions/48860/how-to-dump-
the-icon-of-a-running-x-program for how to convert these numbers to .pam
format. Then forget pamrgbatopng mentioned on that site, use
imagemagic's "convert" to convert to let's say .png.

gnome-terminal's source has a "gtk_window_set_default_icon_name
(GNOME_TERMINAL_ICON_NAME)", the latter constant being defined as
"utilities-terminal". A bit of strace'ing reveals that the About dialog
takes the picture from the Humanity theme.

Putting together the pieces we have so far: gnome-terminal installs
_NET_WM_ICON via the gtk_window_set_default_icon_name call, taking the
files /usr/share/icons/Humanity/apps/[size]/utilities-terminal.svg, at
sizes 32, 48, maybe 128, maybe 256; not sure if 256 fails now or when
querying, not sure whose fault that chopped output is, not sure if it's
relevant to our bug.

The picture incorrectly shown indeed suspiciously looks like Humanity's
utilities-terminal icon scaled up from 48 to 128.

The question is... Why does the window manager decide to even try to
show the icon, and why does it fail to properly do so...???

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

Title:
  gnome-terminal graphic artifact

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1745065] Re: gnome-control-center crashed with SIGSEGV in __GI_____strtoul_l_internal()

2018-01-23 Thread Apport retracing service
*** This bug is a duplicate of bug 1712961 ***
https://bugs.launchpad.net/bugs/1712961

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 #1712961, 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/1745065/+attachment/5042052/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1745065

Title:
  gnome-control-center crashed with SIGSEGV in
  __GI_strtoul_l_internal()

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

Bug description:
  The control center cannot be opened.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jan 24 01:46:23 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-11 (134 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7fcbef5880f5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fcbef5880f5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff8940d7a8, base=10, 
group=, loc=0x7fcbef923800 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:292
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: gnome-control-center crashed with SIGSEGV in 
__GI_strtoul_l_internal()
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1745057] [NEW] package firefox 58.0+build6-0ubuntu0.16.04.1 failed to install/upgrade: el paquet firefox no està llest per a configurar-se no es pot configurar (estat actual «

2018-01-23 Thread Josep Pujadas-Jubany
Public bug reported:

Crash

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: firefox 58.0+build6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 firefox: Configure
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  usuari 1057 F pulseaudio
BuildID: 2018015619
Channel: Unavailable
Date: Wed Jan 24 00:44:51 2018
DpkgTerminalLog:
 dpkg: s'ha produït un error en processar el paquet firefox (--configure):
  el paquet firefox no està llest per a configurar-se
  no es pot configurar (estat actual «half-installed»)
ErrorMessage: el paquet firefox no està llest per a configurar-se  no es pot 
configurar (estat actual «half-installed»)
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-05-25 (243 days ago)
InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
IpRoute:
 default via 192.168.1.1 dev wlp2s0  proto static  metric 600 
 192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.81  metric 
600
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 58.0+build6-0ubuntu0.16.04.1 failed to install/upgrade: 
el paquet firefox no està llest per a configurar-se  no es pot configurar 
(estat actual «half-installed»)
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.15
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Lepus_BA
dmi.board.vendor: Acer
dmi.board.version: V1.15
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.15:bd03/16/2017:svnAcer:pnTravelMateB117-M:pvrV1.15:rvnAcer:rnLepus_BA:rvrV1.15:cvnAcer:ct10:cvrChassisVersion:
dmi.product.family: BSW
dmi.product.name: TravelMate B117-M
dmi.product.version: V1.15
dmi.sys.vendor: Acer

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

Title:
  package firefox 58.0+build6-0ubuntu0.16.04.1 failed to
  install/upgrade: el paquet firefox no està llest per a configurar-se
  no es pot configurar (estat actual «half-installed»)

Status in firefox package in Ubuntu:
  New

Bug description:
  Crash

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: firefox 58.0+build6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   firefox: Configure
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuari 1057 F pulseaudio
  BuildID: 2018015619
  Channel: Unavailable
  Date: Wed Jan 24 00:44:51 2018
  DpkgTerminalLog:
   dpkg: s'ha produït un error en processar el paquet firefox (--configure):
el paquet firefox no està llest per a configurar-se
no es pot configurar (estat actual «half-installed»)
  ErrorMessage: el paquet firefox no està llest per a configurar-se  no es pot 
configurar (estat actual «half-installed»)
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-05-25 (243 days ago)
  InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600 
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.81  
metric 600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 58.0+build6-0ubuntu0.16.04.1 failed to 
install/upgrade: el paquet firefox no està llest per a configurar-se  no es pot 
configurar (estat actual «half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Lepus_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.15
  dmi.chassis.type: 10

[Desktop-packages] [Bug 1744855] Re: Upgrade to 2.84-3ubuntu3.1 breaks remote access (webui)

2018-01-23 Thread B. Bogart
Thanks for the hint. I'm not sure why my config worked before at all! I
changed:

"rpc-host-whitelist-enabled": true,

to

"rpc-host-whitelist-enabled": false,

And also:

"rpc-whitelist-enabled": false,

to

"rpc-whitelist-enabled": true,

And its working fine now... This seems to imply my whitelist was not
being used before or upgrading messed up the config file?

Marking as invalid, since it simply exposed a previous config error.

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

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

Title:
  Upgrade to 2.84-3ubuntu3.1 breaks remote access (webui)

Status in transmission package in Ubuntu:
  Invalid

Bug description:
  I just upgraded to transmission-daemon 2.84-3ubuntu3.1 and I can no
  longer use the webui (nor android clients) to access transmission.
  This is the webui URL I've been using:

  http://cine:9091/transmission/web/

  This is the error I'm getting:

  Connection Failed
  Could not connect to the server. You may need to reload the page to reconnect.

  transmission-remote on the machine works fine. The server running
  transmission-daemon is on a local network on the same subnet as the
  android and webui clients. Nothing has changed beyond installing a few
  updates, including 2.84-3.

  Here is my settings.json:

  {
  "alt-speed-down": 15,
  "alt-speed-enabled": false,
  "alt-speed-time-begin": 540,
  "alt-speed-time-day": 127,
  "alt-speed-time-enabled": false,
  "alt-speed-time-end": 1020,
  "alt-speed-up": 15,
  "bind-address-ipv4": "0.0.0.0",
  "bind-address-ipv6": "::",
  "blocklist-date": 1308104247,
  "blocklist-enabled": true,
  "blocklist-updates-enabled": true,
  "blocklist-url": "http://john.bitsurge.net/public/biglist.p2p.gz;,
  "cache-size-mb": 4,
  "compact-view": false,
  "dht-enabled": true,
  "download-dir": "/home/bbogart/Downloads",
  "download-queue-enabled": true,
  "download-queue-size": 5,
  "encryption": 1,
  "filter-mode": "show-all",
  "idle-seeding-limit": 30,
  "idle-seeding-limit-enabled": false,
  "incomplete-dir": "/home/bbogart/Downloads",
  "incomplete-dir-enabled": false,
  "inhibit-desktop-hibernation": true,
  "lazy-bitfield-enabled": true,
  "lpd-enabled": false,
  "main-window-height": 975,
  "main-window-is-maximized": 0,
  "main-window-layout-order": "menu,toolbar,filter,list,statusbar",
  "main-window-width": 968,
  "main-window-x": 285,
  "main-window-y": 0,
  "message-level": 1,
  "minimal-view": false,
  "open-dialog-dir": "/home/bbogart",
  "open-file-limit": 32,
  "peer-congestion-algorithm": "",
  "peer-id-ttl-hours": 6,
  "peer-limit-global": 240,
  "peer-limit-per-torrent": 60,
  "peer-port": 60639,
  "peer-port-random-high": 65535,
  "peer-port-random-low": 49152,
  "peer-port-random-on-start": true,
  "peer-socket-tos": "default",
  "pex-enabled": true,
  "play-download-complete-sound": false,
  "port-forwarding-enabled": true,
  "preallocation": 1,
  "prefetch-enabled": 1,
  "prompt-before-exit": true,
  "proxy": "",
  "proxy-auth-enabled": false,
  "proxy-auth-password": "",
  "proxy-auth-username": "",
  "proxy-enabled": false,
  "proxy-port": 80,
  "proxy-type": 0,
  "queue-stalled-enabled": true,
  "queue-stalled-minutes": 30,
  "ratio-limit": 1.2496,
  "ratio-limit-enabled": true,
  "recent-download-dir-1": "/home/bbogart/Downloads",
  "rename-partial-files": false,
  "rpc-authentication-required": false,
  "rpc-bind-address": "0.0.0.0",
  "rpc-enabled": true,
  "rpc-host-whitelist": "",
  "rpc-host-whitelist-enabled": true,
  "rpc-password": "{e607e2c7c28eab2770c82c1d0574c0e731c050d5TdP8HGP6",
  "rpc-port": 9091,
  "rpc-url": "/transmission/",
  "rpc-username": "",
  "rpc-whitelist": "192.168.0.*",
  "rpc-whitelist-enabled": false,
  "scrape-paused-torrents-enabled": true,
  "script-torrent-done-enabled": false,
  "script-torrent-done-filename": "/home/bbogart",
  "seed-queue-enabled": false,
  "seed-queue-size": 10,
  "show-backup-trackers": false,
  "show-desktop-notification": true,
  "show-extra-peer-details": false,
  "show-filterbar": true,
  "show-notification-area-icon": true,
  "show-options-window": true,
  "show-statusbar": true,
  "show-toolbar": true,
  "show-tracker-scrapes": false,
  "sort-mode": "sort-by-ratio",
  "sort-reversed": false,
  "speed-limit-down": 100,
  "speed-limit-down-enabled": false,
  "speed-limit-up": 100,
  "speed-limit-up-enabled": false,
  "start-added-torrents": true,
  "statusbar-stats": "total-ratio",
  

[Desktop-packages] [Bug 1677198] Re: OpenVPN not Working in 17.04 via "Import a saved VPN configuration"

2018-01-23 Thread Jan-Åke Larsson
Removing deprecated items from the ovpn configuration file does not help
in my case. I still need the patched packages.

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

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

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

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

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

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

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

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

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

  I cannot upgrade to 17.04 until this is fixed.

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

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

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


[Desktop-packages] [Bug 1745044] [NEW] [Ubuntu 18.04] Screen not recorded by Chrome recording extensions

2018-01-23 Thread Daniele Besana
Public bug reported:

Not sure I report this correctly.
Since updating to 18.04, all chrome extensions capturing the desktop (es. 
Awesome Screenshot and Screencastify) don't work anymore.
They capture just a black screen.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
Uname: Linux 4.14.0-15-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 23:27:50 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: webcamstudio, 0.73, 4.14.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 520 [17aa:5053]
InstallationDate: Installed on 2015-12-07 (778 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
 Bus 001 Device 005: ID 04ca:7058 Lite-On Technology Corp. 
 Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FMS1G400
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.14.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/20/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET42W (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS1G400
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET42W(1.16):bd09/20/2016:svnLENOVO:pn20FMS1G400:pvrThinkPadT460:rvnLENOVO:rn20FMS1G400:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS1G400
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
version.libdrm2: libdrm2 2.4.89-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Jan 11 19:43:07 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2

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


** Tags: amd64 apport-bug bionic ubuntu wayland-session

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

Title:
  [Ubuntu 18.04] Screen not recorded by Chrome recording extensions

Status in xorg package in Ubuntu:
  New

Bug description:
  Not sure I report this correctly.
  Since updating to 18.04, all chrome extensions capturing the desktop (es. 
Awesome Screenshot and Screencastify) don't work anymore.
  They capture just a black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 23:27:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: webcamstudio, 0.73, 4.14.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 520 [17aa:5053]
  InstallationDate: Installed on 2015-12-07 (778 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint 

[Desktop-packages] [Bug 1644021] Re: Firefox doesn't include EmojiOne font

2018-01-23 Thread Launchpad Bug Tracker
This bug was fixed in the package firefox - 58.0+build6-0ubuntu0.16.04.1

---
firefox (58.0+build6-0ubuntu0.16.04.1) xenial-security; urgency=medium

  * New upstream stable release (58.0build6)

  [ Rico Tzschichholz ]
  * Bump build-dep on rustc >= 1.21.0 and cargo >= 0.22
  * Update patches
- debian/patches/ppc-no-static-sizes.patch
- debian/patches/unity-menubar.patch
- debian/patches/allow-lockPref-everywhere.patch
- debian/patches/revert-upstream-search-engine-changes.patch
- debian/patches/warn-only-on-duplicates.patch
  * Drop upstreamed/obsolete patches
- debian/patches/build-ppc64-s390x-nss.patch
- debian/patches/build-ppc64-s390x-rust.patch
  * Update make-langpack-xpis target
- debian/build/rules.mk
  * Build language packs based on web extensions
- debian/build/xpi-id.py
  * Bump debhelper compat level to 9
  * Drop 12.04/Precise specific changes
  * Update copyright and license files
  * Install watermark.svg from the onbording extension as symbolic icon
- debian/build/rules.mk
- debian/firefox.dirs.in
  * mozbuild/shellutil.py: Don't treat '~' character as special
- debian/patches/dont-treat-tilde-as-special.patch
  * Add Nepali language pack
- update debian/config/locales.all
- update debian/config/locales.shipped
- update debian/control
  * Adapt to upstream and use ./mach
- debian/build/rules.mk
  * Install EmojiOneMozilla.ttf (LP: #1644021)
- debian/firefox.install.in
  * Update patches
- debian/patches/allow-lockPref-everywhere.patch
- debian/patches/revert-upstream-search-engine-changes.patch
  * Fix build on ppc64
- debian/patches/ppc64_moz1416170.patch
  * Update patches
- debian/patches/normalize-distribution-searchplugins.patch

  [ Jeremy Bicha ]
  * Avoid direct dependency on libgtk2.0-0 which is required by Flash only
  * Drop obsolete Build-Depends on quilt, libgconf2-dev and libgnomeui-dev
  * Depend on libdbusmenu-gtk3-4 instead of the GTK+ 2 version

  [ Chris Coulson ]
  * Backport some skia fixes to fix a build failure on aarch64 against
kernel headers that don't define HWCAP_CRC32
- add debian/patches/skia-fix-aarch64-build-on-older-linux.patch
- update debian/patches/series
  * Refresh debian/patches/unity-menubar.patch
  * Compile rust code with "debuginfo=1" on 32-bit hosts to reduce code size
and hopefully prevent the builds from running out of address space
- add debian/patches/reduce-rust-debuginfo-on-32bit-architectures.patch
- update debian/patches/series

 -- Chris Coulson   Mon, 22 Jan 2018
22:17:34 +

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1644021

Title:
  Firefox doesn't include EmojiOne font

Status in firefox package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged
Status in thunderbird package in Debian:
  Fix Released

Bug description:
  Firefox has shipped with an emoji font since version 50.0, but Ubuntu
  doesn't include it in their Firefox packages.

  Therefore, when opening a page in Firefox containing emoji characters,
  the black and white glyphs from DejaVu are displayed instead of the
  glyphs from the EmojiOneMozilla font.

  According to http://packages.ubuntu.com/xenial-
  updates/amd64/firefox/filelist, EmojiOneMozilla.ttf is not included in
  the Firefox package in Ubuntu's repositories.

  Manual installing this font and verifying that it works:
  1) Download Firefox tarball from Firefox website
  2) Extract EmojiOneMozilla.ttf from /firefox/fonts/
  3) Copy EmojiOneMozilla.ttf to /usr/lib/firefox/fonts/
  4) Quit Ubuntu session and launch a new one
  5) Launch Firefox and go to a page containing emoji characters, such as 
http://getemoji.com/ or 
https://eosrei.github.io/emojione-color-font/full-demo.html
  6) Now, instead of using glyphs from DejaVu, the majority of emoji on the 
page are taken from EmojiOneMozilla.ttf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 50.0+build2-0ubuntu0.12.04.2
  ProcVersionSignature: Ubuntu 3.13.0-101.148~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-101-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gris   2087 F pulseaudio
  BuildID: 20161114145344
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xf880 irq 42'
     Mixer name : 'Intel IbexPeak HDMI'
     Components : 

[Desktop-packages] [Bug 1644021] Re: Firefox doesn't include EmojiOne font

2018-01-23 Thread Launchpad Bug Tracker
This bug was fixed in the package firefox - 58.0+build6-0ubuntu0.14.04.1

---
firefox (58.0+build6-0ubuntu0.14.04.1) trusty-security; urgency=medium

  * New upstream stable release (58.0build6)

  [ Rico Tzschichholz ]
  * Bump build-dep on rustc >= 1.21.0 and cargo >= 0.22
  * Update patches
- debian/patches/ppc-no-static-sizes.patch
- debian/patches/unity-menubar.patch
- debian/patches/allow-lockPref-everywhere.patch
- debian/patches/revert-upstream-search-engine-changes.patch
- debian/patches/warn-only-on-duplicates.patch
  * Drop upstreamed/obsolete patches
- debian/patches/build-ppc64-s390x-nss.patch
- debian/patches/build-ppc64-s390x-rust.patch
  * Update make-langpack-xpis target
- debian/build/rules.mk
  * Build language packs based on web extensions
- debian/build/xpi-id.py
  * Bump debhelper compat level to 9
  * Drop 12.04/Precise specific changes
  * Update copyright and license files
  * Install watermark.svg from the onbording extension as symbolic icon
- debian/build/rules.mk
- debian/firefox.dirs.in
  * mozbuild/shellutil.py: Don't treat '~' character as special
- debian/patches/dont-treat-tilde-as-special.patch
  * Add Nepali language pack
- update debian/config/locales.all
- update debian/config/locales.shipped
- update debian/control
  * Adapt to upstream and use ./mach
- debian/build/rules.mk
  * Install EmojiOneMozilla.ttf (LP: #1644021)
- debian/firefox.install.in
  * Update patches
- debian/patches/allow-lockPref-everywhere.patch
- debian/patches/revert-upstream-search-engine-changes.patch
  * Fix build on ppc64
- debian/patches/ppc64_moz1416170.patch
  * Update patches
- debian/patches/normalize-distribution-searchplugins.patch

  [ Jeremy Bicha ]
  * Avoid direct dependency on libgtk2.0-0 which is required by Flash only
  * Drop obsolete Build-Depends on quilt, libgconf2-dev and libgnomeui-dev
  * Depend on libdbusmenu-gtk3-4 instead of the GTK+ 2 version

  [ Chris Coulson ]
  * Backport some skia fixes to fix a build failure on aarch64 against
kernel headers that don't define HWCAP_CRC32
- add debian/patches/skia-fix-aarch64-build-on-older-linux.patch
- update debian/patches/series
  * Refresh debian/patches/unity-menubar.patch
  * Compile rust code with "debuginfo=1" on 32-bit hosts to reduce code size
and hopefully prevent the builds from running out of address space
- add debian/patches/reduce-rust-debuginfo-on-32bit-architectures.patch
- update debian/patches/series

 -- Chris Coulson   Mon, 22 Jan 2018
22:37:02 +

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1644021

Title:
  Firefox doesn't include EmojiOne font

Status in firefox package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged
Status in thunderbird package in Debian:
  Fix Released

Bug description:
  Firefox has shipped with an emoji font since version 50.0, but Ubuntu
  doesn't include it in their Firefox packages.

  Therefore, when opening a page in Firefox containing emoji characters,
  the black and white glyphs from DejaVu are displayed instead of the
  glyphs from the EmojiOneMozilla font.

  According to http://packages.ubuntu.com/xenial-
  updates/amd64/firefox/filelist, EmojiOneMozilla.ttf is not included in
  the Firefox package in Ubuntu's repositories.

  Manual installing this font and verifying that it works:
  1) Download Firefox tarball from Firefox website
  2) Extract EmojiOneMozilla.ttf from /firefox/fonts/
  3) Copy EmojiOneMozilla.ttf to /usr/lib/firefox/fonts/
  4) Quit Ubuntu session and launch a new one
  5) Launch Firefox and go to a page containing emoji characters, such as 
http://getemoji.com/ or 
https://eosrei.github.io/emojione-color-font/full-demo.html
  6) Now, instead of using glyphs from DejaVu, the majority of emoji on the 
page are taken from EmojiOneMozilla.ttf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 50.0+build2-0ubuntu0.12.04.2
  ProcVersionSignature: Ubuntu 3.13.0-101.148~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-101-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gris   2087 F pulseaudio
  BuildID: 20161114145344
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  

[Desktop-packages] [Bug 1644021] Re: Firefox doesn't include EmojiOne font

2018-01-23 Thread Launchpad Bug Tracker
This bug was fixed in the package firefox - 58.0+build6-0ubuntu0.17.10.1

---
firefox (58.0+build6-0ubuntu0.17.10.1) artful-security; urgency=medium

  * New upstream stable release (58.0build6)

  [ Rico Tzschichholz ]
  * Bump build-dep on rustc >= 1.21.0 and cargo >= 0.22
  * Update patches
- debian/patches/ppc-no-static-sizes.patch
- debian/patches/unity-menubar.patch
- debian/patches/allow-lockPref-everywhere.patch
- debian/patches/revert-upstream-search-engine-changes.patch
- debian/patches/warn-only-on-duplicates.patch
  * Drop upstreamed/obsolete patches
- debian/patches/build-ppc64-s390x-nss.patch
- debian/patches/build-ppc64-s390x-rust.patch
  * Update make-langpack-xpis target
- debian/build/rules.mk
  * Build language packs based on web extensions
- debian/build/xpi-id.py
  * Bump debhelper compat level to 9
  * Drop 12.04/Precise specific changes
  * Update copyright and license files
  * Install watermark.svg from the onbording extension as symbolic icon
- debian/build/rules.mk
- debian/firefox.dirs.in
  * mozbuild/shellutil.py: Don't treat '~' character as special
- debian/patches/dont-treat-tilde-as-special.patch
  * Add Nepali language pack
- update debian/config/locales.all
- update debian/config/locales.shipped
- update debian/control
  * Adapt to upstream and use ./mach
- debian/build/rules.mk
  * Install EmojiOneMozilla.ttf (LP: #1644021)
- debian/firefox.install.in
  * Update patches
- debian/patches/allow-lockPref-everywhere.patch
- debian/patches/revert-upstream-search-engine-changes.patch
  * Fix build on ppc64
- debian/patches/ppc64_moz1416170.patch
  * Update patches
- debian/patches/normalize-distribution-searchplugins.patch

  [ Jeremy Bicha ]
  * Avoid direct dependency on libgtk2.0-0 which is required by Flash only
  * Drop obsolete Build-Depends on quilt, libgconf2-dev and libgnomeui-dev
  * Depend on libdbusmenu-gtk3-4 instead of the GTK+ 2 version

  [ Chris Coulson ]
  * Backport some skia fixes to fix a build failure on aarch64 against
kernel headers that don't define HWCAP_CRC32
- add debian/patches/skia-fix-aarch64-build-on-older-linux.patch
- update debian/patches/series
  * Refresh debian/patches/unity-menubar.patch
  * Compile rust code with "debuginfo=1" on 32-bit hosts to reduce code size
and hopefully prevent the builds from running out of address space
- add debian/patches/reduce-rust-debuginfo-on-32bit-architectures.patch
- update debian/patches/series

 -- Chris Coulson   Mon, 22 Jan 2018
20:59:26 +

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1644021

Title:
  Firefox doesn't include EmojiOne font

Status in firefox package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Triaged
Status in thunderbird package in Debian:
  Fix Released

Bug description:
  Firefox has shipped with an emoji font since version 50.0, but Ubuntu
  doesn't include it in their Firefox packages.

  Therefore, when opening a page in Firefox containing emoji characters,
  the black and white glyphs from DejaVu are displayed instead of the
  glyphs from the EmojiOneMozilla font.

  According to http://packages.ubuntu.com/xenial-
  updates/amd64/firefox/filelist, EmojiOneMozilla.ttf is not included in
  the Firefox package in Ubuntu's repositories.

  Manual installing this font and verifying that it works:
  1) Download Firefox tarball from Firefox website
  2) Extract EmojiOneMozilla.ttf from /firefox/fonts/
  3) Copy EmojiOneMozilla.ttf to /usr/lib/firefox/fonts/
  4) Quit Ubuntu session and launch a new one
  5) Launch Firefox and go to a page containing emoji characters, such as 
http://getemoji.com/ or 
https://eosrei.github.io/emojione-color-font/full-demo.html
  6) Now, instead of using glyphs from DejaVu, the majority of emoji on the 
page are taken from EmojiOneMozilla.ttf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 50.0+build2-0ubuntu0.12.04.2
  ProcVersionSignature: Ubuntu 3.13.0-101.148~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-101-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-101-generic.
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: ALC272 Analog [ALC272 Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gris   2087 F pulseaudio
  BuildID: 20161114145344
  CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xf880 irq 42'
     

[Desktop-packages] [Bug 1745029] Re: plasma-workspace FTBFS with appstream 0.11.8-1

2018-01-23 Thread Bug Watch Updater
** Changed in: appstream
   Status: Unknown => New

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

Title:
  plasma-workspace FTBFS with appstream 0.11.8-1

Status in AppStream:
  New
Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  plasma-workspace fails to build from source with with appstream
  0.11.8-1 synced from debian

  https://launchpad.net/ubuntu/+source/plasma-
  workspace/4:5.11.5-0ubuntu2

  [ 49%] Linking CXX shared module appstreamrunner.so
  cd /<>/obj-x86_64-linux-gnu/runners/appstream && /usr/bin/cmake 
-E cmake_link_script CMakeFiles/appstreamrunner.dir/link.txt --verbose=1
  /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x 
-fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align 
-Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time 
-Wl,--no-undefined -Wl,--fatal-warnings -Wl,--enable-new-dtags 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
-shared  -o appstreamrunner.so 
CMakeFiles/appstreamrunner.dir/appstreamrunner.cpp.o 
CMakeFiles/appstreamrunner.dir/appstreamrunner_autogen/mocs_compilation.cpp.o 
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5.41.0 AppStreamQt-NOTFOUND 
/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Package.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5I18n.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.9.3 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.3 
  c++: error: AppStreamQt-NOTFOUND: No such file or directory

  
  (initially failed on just s390x, as that build did not get unblocked for 
meltdown fixes until after 0.11.8-1 was synced. Above rebuild confirmed failure 
then on all architectures)

  Seems other packages are also likely to fail if/when there are new
  builds

  e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888144 for
  frameworkintegration

  I would note that doing test builds on Kubuntu CI, both upstream 5.12
  beta and master branches of plasma-workspace also fail to build in the
  same manner.

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

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


[Desktop-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

2018-01-23 Thread Egmont Koblinger
Does this also happen on other windows of gnome-terminal (e.g.
Search->Find, Edit->Preferences, Edit->Profile Preferences,
Help->About)?

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

Title:
  gnome-terminal graphic artifact

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

2018-01-23 Thread David Biró
Same in here, it is an annoying feature. How can I contribute and fix
this if no one does?

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

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

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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


[Desktop-packages] [Bug 1296409] Re: Update confusing clear button

2018-01-23 Thread Bug Watch Updater
** Changed in: gnome-calculator
   Status: Unknown => Confirmed

** Changed in: gnome-calculator
   Importance: Unknown => Medium

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

Title:
  Update confusing clear button

Status in GNOME Calculator:
  Confirmed
Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  The clear button can confuse users into thinking its backspace, to fix
  we use window-close instead of edit-clear-symbolic

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

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


[Desktop-packages] [Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

2018-01-23 Thread Bug Watch Updater
** Changed in: gedit
   Status: Unknown => New

** Changed in: gedit
   Importance: Unknown => Low

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

Status in gedit:
  New
Status in gedit package in Ubuntu:
  New

Bug description:
  If I paste a special character - say from the Character Map - into
  Gedit or medit in Ubuntu 16.04 into the middle of a line, then the
  space characters directly after the special character display with a
  "compressed" character spacing until the behaviour is "interrupted" by
  a standard text character.

  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines
  with the special character problem.

  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .

  https://askubuntu.com/questions/986258/why-do-special-characters-
  change-spacing-following-space-character-in-gedit-or-m

  Please see that post for full details, worked example, and
  screenshots.

  Additional comments:

  * As stated above:
  - running Ubuntu 16.04

  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0

  I am aware that it is thus not strictly a gedit issue, and probably
  affects multiple Gnome editors under multiple Linux variants - but
  Gedit is my favourite text editor and Ubuntu is my favourite Linux so
  I thought I would start here.

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

  $ apt-cache policy gedit
  gedit:
    Installed: 3.18.3-0ubuntu4
    Candidate: 3.18.3-0ubuntu4
    Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy medit
  medit:
    Installed: 1.2.0-2
    Candidate: 1.2.0-2
    Version table:
   *** 1.2.0-2 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1663648] Re: Scrollbar of history panel doesn't work

2018-01-23 Thread Bug Watch Updater
** Changed in: gnome-calculator
   Status: Unknown => Fix Released

** Changed in: gnome-calculator
   Importance: Unknown => Medium

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

Title:
  Scrollbar of history panel doesn't work

Status in GNOME Calculator:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety
  gnome-calculator 1:3.22.0-1ubuntu1 amd64

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

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


[Desktop-packages] [Bug 1717678] Re: Crash when opening TTF font

2018-01-23 Thread Bug Watch Updater
** Changed in: gnome-font-viewer
   Status: Unknown => Fix Released

** Changed in: gnome-font-viewer
   Importance: Unknown => Medium

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

Title:
  Crash when opening TTF font

Status in GNOME Font Viewer:
  Fix Released
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
  3a. Try to install this Symbol font 
(https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf)

  $ gnome-font-viewer symbol.ttf

  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).

  $ gnome-font-viewer
  /usr/share/fonts/truetype/msttcorefonts/webdings.ttf

  Expected results:
  * GNOME Font Viewer opened window for font preview and installation

  Actual results:
  * GNOME Font Viewer crashed with the following output:

  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)

  Note: I attached the font file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1717678/+subscriptions

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


[Desktop-packages] [Bug 1745029] [NEW] plasma-workspace FTBFS with appstream 0.11.8-1

2018-01-23 Thread Rik Mills
Public bug reported:

plasma-workspace fails to build from source with with appstream 0.11.8-1
synced from debian

https://launchpad.net/ubuntu/+source/plasma-workspace/4:5.11.5-0ubuntu2

[ 49%] Linking CXX shared module appstreamrunner.so
cd /<>/obj-x86_64-linux-gnu/runners/appstream && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/appstreamrunner.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x 
-fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align 
-Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time 
-Wl,--no-undefined -Wl,--fatal-warnings -Wl,--enable-new-dtags 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
-shared  -o appstreamrunner.so 
CMakeFiles/appstreamrunner.dir/appstreamrunner.cpp.o 
CMakeFiles/appstreamrunner.dir/appstreamrunner_autogen/mocs_compilation.cpp.o 
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5.41.0 AppStreamQt-NOTFOUND 
/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Package.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5I18n.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.9.3 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.3 
c++: error: AppStreamQt-NOTFOUND: No such file or directory


(initially failed on just s390x, as that build did not get unblocked for 
meltdown fixes until after 0.11.8-1 was synced. Above rebuild confirmed failure 
then on all architectures)

Seems other packages are also likely to fail if/when there are new
builds

e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888144 for
frameworkintegration

I would note that doing test builds on Kubuntu CI, both upstream 5.12
beta and master branches of plasma-workspace also fail to build in the
same manner.

** Affects: appstream
 Importance: Unknown
 Status: Unknown

** Affects: appstream (Ubuntu)
 Importance: High
 Status: Confirmed

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

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

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

** Also affects: appstream via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888144
   Importance: Unknown
   Status: Unknown

** Description changed:

  plasma-workspace fails to build from source with with appstream 0.11.8-1
  synced from debian
  
  https://launchpad.net/ubuntu/+source/plasma-workspace/4:5.11.5-0ubuntu2
  
- (initially failed on just s390x, as that build did not get unblocked for
- meltdown fixes until after 0.11.8-1 was synced. Above rebuild confirmed
- failure then on all architectures)
+ [ 49%] Linking CXX shared module appstreamrunner.so
+ cd /<>/obj-x86_64-linux-gnu/runners/appstream && /usr/bin/cmake 
-E cmake_link_script CMakeFiles/appstreamrunner.dir/link.txt --verbose=1
+ /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x 
-fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align 
-Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time 
-Wl,--no-undefined -Wl,--fatal-warnings -Wl,--enable-new-dtags 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
-shared  -o appstreamrunner.so 
CMakeFiles/appstreamrunner.dir/appstreamrunner.cpp.o 
CMakeFiles/appstreamrunner.dir/appstreamrunner_autogen/mocs_compilation.cpp.o 
/usr/lib/x86_64-linux-gnu/libKF5Runner.so.5.41.0 AppStreamQt-NOTFOUND 
/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Package.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5I18n.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5.41.0 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.9.3 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.9.3 
+ c++: error: AppStreamQt-NOTFOUND: No such file or directory
+ 
+ 
+ (initially failed on just s390x, as that build did not get unblocked for 
meltdown fixes until after 0.11.8-1 was synced. Above rebuild confirmed failure 
then on all architectures)
  
  Seems other packages are also likely to fail if/when there are new
  builds
  
  e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888144 for
  frameworkintegration
  
  I would note that doing test builds on Kubuntu CI, both upstream 5.12
  beta and master branches of plasma-workspace also fail to build in the
  

[Desktop-packages] [Bug 1663648] Re: Scrollbar of history panel doesn't work

2018-01-23 Thread Robert Roth
Thank you for your bug report. This bug has been reported to the
developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=770791

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

Title:
  Scrollbar of history panel doesn't work

Status in GNOME Calculator:
  Unknown
Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety
  gnome-calculator 1:3.22.0-1ubuntu1 amd64

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

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


[Desktop-packages] [Bug 1724250] Re: gnome-terminal graphic artifact

2018-01-23 Thread Egmont Koblinger
Another report of the same issue: https://askubuntu.com/questions/983629
/terminal-window-stuck-with-the-corner-of-another-window-drawn-on-it

It's interesting that you have 4 buttons instead of 3 (and it's the same
at that other report).

Did you somehow add a 4th button? What and how exactly? Or does it only
appear in gnome-terminal? What do those buttons do if you click on them?

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

Title:
  gnome-terminal graphic artifact

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Opening gnome-terminal in Ubuntu 17.10 shows the terminal window with
  a graphic artifact on the right of the title bar, where the window
  buttons to minimize, maximize and close are.

  The window buttons are working so this is just a visual glitch and
  does not otherwise affect gnome-terminal functionalities.

  It does not matter whether the gnome-terminal window is maximized or
  not, the graphic artifact is always present and does not disappear
  hovering on it with the mouse.

  Other applications do not appear to be affected, only gnome-terminal.

  I'm using NVIDIA Corporation GM204M [GeForce GTX 970M] with the NVIDIA
  binary driver 384.90.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 15:37:42 2017
  InstallationDate: Installed on 2017-10-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1296409] Re: Update confusing clear button

2018-01-23 Thread Robert Roth
Thank you for your bug report. This bug has been reported to the
developers of the software. You can track it and make comments at:
https://bugzilla.gnome.org/show_bug.cgi?id=792844

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

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

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

Title:
  Update confusing clear button

Status in GNOME Calculator:
  Unknown
Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  The clear button can confuse users into thinking its backspace, to fix
  we use window-close instead of edit-clear-symbolic

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

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


[Desktop-packages] [Bug 1371274] Re: Unable to use the widevine plugin with Chromium

2018-01-23 Thread Olivier Tilloy
*** This bug is a duplicate of bug 1652110 ***
https://bugs.launchpad.net/bugs/1652110

Which PPA is that exactly? Can't you use the regular ubuntu packages
from the archive?

It puzzles me that this should work at all. Chromium packages (as
opposed to Chrome) never ship widevine binaries, they can't for legal
reasons. So I don't see how that script that generates a package from
chromium (not *chrome*) might possibly include working widevine
binaries.

I guess you would need to get your hands on an actual chromebook to
extract the binaries from there, but that's pure speculation as I don't
have such hardware.

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

Title:
  Unable to use the widevine plugin with Chromium

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  Chromium is unable to use the widevine component from google chrome :
  libwidevinecdmadapter.so and libwidevinecdm.so

  How to reproduce :

  - copy the 2 files the chrome archive in /usr/lib/chromium-browser
  - check chrome://components/
  - Widevine does not appear

  Solution :

  With the help from several people (hogliux for patch and saiarcot895
  for PPA) , a PPA is available with this feature :

  - https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev

  - You need the binary widevine plugin plugin (2 files) :

  https://bugs.launchpad.net/ubuntu/+source/chromium-
  
browser/+bug/1371274/+attachment/4397708/+files/WidevineLinuxForChromium44.tar.gz

  To be copied in /usr/lib/chromium

  - Launch netflix.com and see if it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.94-0ubuntu0.14.04.1~pkg1042
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep 18 21:11:17 2014
  InstallationDate: Installed on 2013-10-02 (350 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  SystemImageInfo: Error: [Errno 2] Aucun fichier ou dossier de ce type: 
'system-image-cli'
  UpgradeStatus: Upgraded to trusty on 2014-05-31 (109 days ago)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-06-01T14:14:23.245932

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

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


[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server

2018-01-23 Thread Szymon Lipiński
Is it possible to add this to Ubuntu 17.10? Current version 36.2 is
totally unusable, and I don't want to jump into 18.04 yet.

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

Title:
  "Operation not supported by backend" when backing up to smb server

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

Bug description:
  OS: Ubuntu 17.10 beta
  setting up deja-dup to backup to smb/ssh server fails

  With ssh: Permission denied
  syslog:
  Sep  7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from 
uid 1000 finished with success after 414ms

  
  with smb: Backup failed
  InvalidBackendURL: missing // - relative paths not supported for scheme 
gio+invalid: gio+invalid://
  syslog:
  Sep  7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 
0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How 
does the code know the size to allocate?
  Sep  7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from 
uid 1000 finished with success after 402ms

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 10:30:37 2017
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1744871] Re: Watch directory feature produces 'torrent file contains invalid data' error

2018-01-23 Thread Leonidas S. Barbosa
Hi,

Can you try a do this again and verify the status with: sudo systemctl status 
transmission-daemon.service ?
It may be related to permissions, just a guess.

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

Title:
  Watch directory feature produces 'torrent file contains invalid data'
  error

Status in transmission package in Ubuntu:
  New

Bug description:
  To reproduce:
  1: Download a torrent file (i used the file from https://xubuntu.org/download 
to test)
  2: Add it manually to Transmission
  3: Everything works fine
  4: In preferences set up a directory in the 'Automatically add .torrent files 
from:' setting
  5: Place that very same file in the directory you have selected
  6: Note the error message

  What i expect to happen:
  The torrent file should be added to the download and start downloading 
normally. No difference between adding manually and automatically should be 
there.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: transmission-gtk 2.92-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 23 10:02:18 2018
  InstallationDate: Installed on 2017-12-14 (39 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: transmission
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2018-01-23 Thread Nikita Yerenkov-Scott
I hadn't noticed this bug in a while. And then suddenly yesterday (on
Arch Linux) it appeared!

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Committed
Status in gnome-shell package in Debian:
  Confirmed
Status in gnome-shell package in Fedora:
  In Progress

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-23 Thread Launchpad Bug Tracker
This bug was fixed in the package libjogl2-java - 2.3.2+dfsg-7

---
libjogl2-java (2.3.2+dfsg-7) unstable; urgency=medium

  * Reupload using correct .changes.

 -- Timo Aaltonen   Sat, 13 Jan 2018 09:17:50 +0200

** Changed in: libjogl2-java (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

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

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


[Desktop-packages] [Bug 1663648] Re: Scrollbar of history panel doesn't work

2018-01-23 Thread Robert Roth
** Bug watch added: GNOME Bug Tracker #770791
   https://bugzilla.gnome.org/show_bug.cgi?id=770791

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

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

Title:
  Scrollbar of history panel doesn't work

Status in GNOME Calculator:
  Unknown
Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety
  gnome-calculator 1:3.22.0-1ubuntu1 amd64

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

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


[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)

2018-01-23 Thread Florian Boucault
Found this patch: https://github.com/manjaro/packages-
community/tree/master/nautilus-typeahead

Not sure if it works

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

Title:
  Restore interactive_search.patch (type-ahead search)

Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  Nautilus dropped the popular type-ahead search feature years ago.
  Ubuntu has been carrying a patch to revert that change. See bug
  1164016 for the original LP bug and patch proposal.

  Nautilus is now under very active development. During the 3.22 cycle,
  that patch needed to be rebased. I tried to do it and what I came up
  with caused a crash (it didn't really crash for me, but ricotz and
  some others experienced it) and the first letter typed activated type-
  ahead search but the first letter was dropped. In other words, you
  would need to type "ddow" to activate the Downloads folder instead of
  just "dow" like in previous releases. (LP: #1635988)

  I did that rebase in October 2016 and no one has stepped up then to
  improve the patch.

  The Nautilus maintainer csoriano has said that the slots and views
  changed significantly during 3.22 and will likely be refactored more
  in the future.

  If there's no one available to maintain the patch, unfortunately,
  we'll eventually have to drop the patch to not be stuck on an ancient
  version of Nautilus.

  I am proposing that we do this at the start of the 17.10 development
  cycle. This gives 6 months for a developer to step up and try to fix
  the patch and 12 months before 18.04 LTS.

  Other Items
  ===
  - For better performance with the built-in search, we need to reconsider 
avoiding tracker in Unity (LP: #176)

  - There is an option in Preferences for users to disable searching in
  subfolders. I don't think we want to do that by default but maybe it
  can help some people.

  The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with
  this patch now disabled.

  
https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

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


[Desktop-packages] [Bug 1710382] Re: Wireless network frequently drops in 17.10

2018-01-23 Thread Pete
I am also having the same problem w/ 17.10.

Maybe be a duplicate of bug 1726187 and 1736690.

I am also having issues with my WiFi connection dropping out, freezing,
etc.

I see other bugs reported as well for 17.10 / 18.04 Ubunutu.

I am using latest 17.10 build, clean install.
Laptop: Yoga 11e
Kernel: 4.13.0-21-generic
WiFi: Network controller: Intel Corporation Wireless 7265 (rev 61)

Occasionally it works when connecting, then stops.

What I find most peculiar is that I discovered the DNS appears to
intermittently stop 'while' I am using the computer online.

If I manually edit "/etc/resolv.conf" (which you shouldn't have to do),
and change "nameserver 127.0.0.53" to "nameserver 8.8.8.8".

Then save, everything works fine and is stable until the next reboot!

I don't think this is a driver/kernel issue, its almost like resolv.conf
is broken.

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

Title:
  Wireless network frequently drops in 17.10

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  On a fairly clean 17.10 install, on a Thinkpad T450, the wireless
  connection keeps dropping. Other devices nearby do not suffer the same
  way.

  I can turn the wifi off and on again to get reconnected. It happens
  multiple times over a short period of an hour or so. So quite
  irritating.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 12 15:52:20 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-02 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto static metric 600 
   10.124.121.0/24 dev lxdbr0 proto kernel scope link src 10.124.121.1 
   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.95 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   
CONNECTION  CON-UUID  CON-PATH  
  
   lxdbr0   bridgeconnected/org/freedesktop/NetworkManager/Devices/27  
lxdbr0  9e57f30a-21b5-4f87-aa76-06a328c24462  
/org/freedesktop/NetworkManager/ActiveConnection/10 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3   
popey   b83cf629-38b9-47dc-8916-3aaa2868e90a  
/org/freedesktop/NetworkManager/ActiveConnection/6  
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2   
--  ----
  
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1   
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1726187] Re: After 17.04 -> 17.10 upgrade, wifi often freezes

2018-01-23 Thread Pete
I am also having issues with my WiFi connection dropping out, freezing,
etc.

I see other bugs reported as well for 17.10 / 18.04 Ubunutu.

I am using latest 17.10 build, clean install.
Laptop: Yoga 11e
Kernel: 4.13.0-21-generic
WiFi:  Network controller: Intel Corporation Wireless 7265 (rev 61)

Occasionally it works when connecting, then stops.

What I find most peculiar is that I discovered the DNS appears to
intermittently stop while I am using the computer.

If I manually edit "/etc/resolv.conf" (which you shouldn't have to do),
and change "nameserver 127.0.0.53" to "nameserver 8.8.8.8".

Once saved everything works fine and is stable until the next reboot.

I don't think this is a driver/kernel issue, its almost like resolv.conf
is broken.

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

Title:
  After 17.04 -> 17.10 upgrade, wifi often freezes

Status in network-manager package in Ubuntu:
  New

Bug description:
  (might be incorrect package)

  About once every few hours, my wifi locks up until I use "turn off +
  turn on" in the network control - upper right corner drop down.  This
  has started happening after the upgrade from 17.04 to 17.10. The
  wireless signal is very strong, and it remains strong even after lock
  up.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 20:41:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-04-13 (192 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.2.1 dev wlp58s0 proto static metric 600 
   169.254.0.0/16 dev wlp58s0 scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.2.0/24 dev wlp58s0 proto kernel scope link src 192.168.2.131 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to artful on 2017-10-19 (3 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/3  
docker0 c1be4834-7fc1-4167-8509-90e5d1946c14  
/org/freedesktop/NetworkManager/ActiveConnection/2  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
pups4bf35394-3e64-4dbe-b1b2-5d1953df7058  
/org/freedesktop/NetworkManager/ActiveConnection/14 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.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/1726187/+subscriptions

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


[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir

2018-01-23 Thread Vlad Orlov
Not sure if the upstream entry should be wontfix or not, it seems
unmaintained.

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

Title:
  intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Committed
Status in intltool source package in Xenial:
  New
Status in intltool source package in Artful:
  New

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

  systemd uses 'intltool-update -m' from intltoolize in its 'make check'.
  $(top_srcdir)/po/POTFILES.skip contains the name of a generated file 
(src/core/org.freedesktop.systemd1.policy.in), which will be generated as 
$(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If 
$(builddir)==$(srcdir) than everything works fine. When they are different, 
there's no way to instruct intltool-update to skip the file. Since the name of 
the build directory is not known and can be arbitrary, there should be a way to 
instruct intltool-update to ignore files relative to the $(top_builddir), or 
something like that. One option would be to turn the file list into a list of 
globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in 
our case).

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

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


[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir

2018-01-23 Thread Vlad Orlov
Thanks :)

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

Title:
  intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Committed
Status in intltool source package in Xenial:
  New
Status in intltool source package in Artful:
  New

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

  systemd uses 'intltool-update -m' from intltoolize in its 'make check'.
  $(top_srcdir)/po/POTFILES.skip contains the name of a generated file 
(src/core/org.freedesktop.systemd1.policy.in), which will be generated as 
$(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If 
$(builddir)==$(srcdir) than everything works fine. When they are different, 
there's no way to instruct intltool-update to skip the file. Since the name of 
the build directory is not known and can be arbitrary, there should be a way to 
instruct intltool-update to ignore files relative to the $(top_builddir), or 
something like that. One option would be to turn the file list into a list of 
globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in 
our case).

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

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


[Desktop-packages] [Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

2018-01-23 Thread Launchpad Bug Tracker
This bug was fixed in the package session-migration - 0.3.3

---
session-migration (0.3.3) bionic; urgency=medium

  * src/session-migration.c:
fix default permission when creating unexisting parent directories
to be 700. (LP: #1735929)

 -- Didier Roche   Tue, 23 Jan 2018 10:31:30 +0100

** Changed in: session-migration (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Triaged
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Triaged
Status in session-migration package in Ubuntu:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

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

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


[Desktop-packages] [Bug 1743096] Re: Simple Scan not sending mail

2018-01-23 Thread Launchpad Bug Tracker
This bug was fixed in the package simple-scan - 3.26.3-0ubuntu1

---
simple-scan (3.26.3-0ubuntu1) bionic; urgency=medium

  * New upstream stable release:
- Fix email sending failing with PDF attachments (LP: #1743096)

 -- Robert Ancell   Mon, 22 Jan 2018
15:42:39 +1300

** Changed in: simple-scan (Ubuntu Bionic)
   Status: Triaged => Fix Released

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

Title:
  Simple Scan not sending mail

Status in simple-scan package in Ubuntu:
  Fix Released
Status in simple-scan source package in Artful:
  Triaged
Status in simple-scan source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Simple scan is unable to send email with PDF attachments.

  [Test Case]
  1. Open Simple Scan
  2. Scan a document in text mode (the default)
  3. Email the document

  Expected result:
  Email client opens with attached .pdf file

  Observed result:
  Nothing occurs. Running 'simple-scan -d' from the command line shows an error 
about trying to run the invalid command 'xdg-email--attach'.

  [Regression Potential]
  Low. Adds back in a missing space character that got dropped in some 
refactoring.

  Original description:

  This is my first bug report so I hope I'm making sense:

  Simple scan doesn't send mail when trying to send a scanned document.
  Using simple-scan -d I get this error:

  [+9.63s] WARNING: app-window.vala:1208: Unable to email document:
  Failed to execute child process “xdg-email--attach” (No such file or
  directory)

  Looking through the code within app-window.vala on lines 1194 - 1196 I
  see:

  var command_line = "xdg-email";
  if (type == "pdf")
  command_line += "--attach %s".printf (file.get_path ());

  I'm thinking there should be a space " " prior to --attach on line
  1196.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1743096/+subscriptions

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


[Desktop-packages] [Bug 1744696] Re: web interface fails on load

2018-01-23 Thread Leonidas S. Barbosa
Hi,

I couldn't reproduce your issue in xenial using the same settings.json
from git url. I can access the web ui with no  msg or error and also
upload a torrent file normally.

RPC page gives me this:

409: Conflict
Your request had an invalid session-id header.

To fix this, follow these steps:

When reading a response, get its X-Transmission-Session-Id header and remember 
it
Add the updated header to your outgoing requests
When you get this 409 error message, resend your request with the updated header
This requirement has been added to help prevent CSRF attacks.

X-Transmission-Session-Id:
T1lMgv8HPeGmqojuDnzC9sC2ujyxUssUDIUF8FuicbVP4Ahj


Can you provide more details about your settings/environment.
Here are the steps I followed to try to reproduce:

1) I upgrade my transmission and transmission-daemon to  2.84-3ubuntu3.1
2) sudo systemctl stop transmission-daemon.service
3) copy and paste settings.json from git url into 
/etc/transmission/settings.json
4) sudo systemctl start transmission-daemon.service
5) Open a url for transmission webui in another host.

Let me know if I miss something.

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

Title:
  web interface fails on load

Status in transmission package in Ubuntu:
  New

Bug description:
  Upstream issue report (fixed in upstream version 2.92)
  https://github.com/transmission/transmission/issues/476

  I am unable to connect to the remote web UI, or use any other remote
  control application. Transmission itself works, but I can't control it
  except by ssh-ing into the machine its running on with transmission-
  remote.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: transmission 2.84-3ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Jan 22 21:57:36 2018
  Dependencies: transmission-common 2.84-3ubuntu3.1
  InstallationDate: Installed on 2013-06-24 (1673 days ago)
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: transmission
  UpgradeStatus: Upgraded to xenial on 2017-02-05 (351 days ago)

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

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


[Desktop-packages] [Bug 1744922] Re: GNOME Font VIewer does not show TTF font

2018-01-23 Thread Bug Watch Updater
** Changed in: gnome-font-viewer
   Status: Unknown => Confirmed

** Changed in: gnome-font-viewer
   Importance: Unknown => Medium

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

Title:
  GNOME Font VIewer does not show TTF font

Status in GNOME Font Viewer:
  Confirmed
Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font (for example Symbol from 
https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf )
  3. Try to open downloaded font with `gnome-font-viewer symbol.ttf`

  Actual results:
  GNOME Font Viewer shows blank white window (see screenshot). Terminal output 
is empty, .xsession-errors is clean.

  Expected results:
  GNOME Font Viewer shows font preview.

  Note: the font file is not damaged, it opens normally with `mate-font-
  viewer`.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-font-viewer 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jan 23 14:14:09 2018
  InstallationDate: Installed on 2017-12-23 (30 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1744922/+subscriptions

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


[Desktop-packages] [Bug 1744619] Re: Transitioning GNOME away from libnm-glib

2018-01-23 Thread Jeremy Bicha
** Also affects: unity-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Transitioning GNOME away from libnm-glib

Status in gnome-shell package in Ubuntu:
  New
Status in network-manager-iodine package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New

Bug description:
  Debian has dropped libnm-glib support from most of its VPN plugins.

  We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome-
  shell to properly interact with VPNs.

  unity-control-center will need to be ported away from libnm-glib for
  it to display VPNs.

  The only other known affected desktop is Cinnamon which has fixes
  "pending"

  Here's the Debian transition bug:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm

  At first look, KDE Plasma did not seem to be hurt by the libnm-glib
  support removal, but Kubuntu should probably check more closely.

  I am filing this bug to coordinate this transition and keep the VPN
  plugins in -proposed until we at least update gnome-shell.

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

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


[Desktop-packages] [Bug 1570921] Re: suspend not working

2018-01-23 Thread Jean-Max Reymond
Now, It works for me with 17.10 (HP Pavilion dv6)

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

Title:
  suspend not working

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  My computer cannot go to suspend state.  The monitor switch off but the 
cpu/cpu fan keeps running and the hard drive is active.
  It doesn't respond, I need to switch off manually to reboot the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 15 18:42:49 2016
  InstallationDate: Installed on 2016-04-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1717678] Re: Crash when opening TTF font

2018-01-23 Thread Norbert
** Bug watch added: GNOME Bug Tracker #757680
   https://bugzilla.gnome.org/show_bug.cgi?id=757680

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

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

Title:
  Crash when opening TTF font

Status in GNOME Font Viewer:
  Unknown
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
  3a. Try to install this Symbol font 
(https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf)

  $ gnome-font-viewer symbol.ttf

  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).

  $ gnome-font-viewer
  /usr/share/fonts/truetype/msttcorefonts/webdings.ttf

  Expected results:
  * GNOME Font Viewer opened window for font preview and installation

  Actual results:
  * GNOME Font Viewer crashed with the following output:

  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)

  Note: I attached the font file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1717678/+subscriptions

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


[Desktop-packages] [Bug 1717678] JournalErrors.txt

2018-01-23 Thread Norbert
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1717678/+attachment/5041821/+files/JournalErrors.txt

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

Title:
  Crash when opening TTF font

Status in GNOME Font Viewer:
  Unknown
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
  3a. Try to install this Symbol font 
(https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf)

  $ gnome-font-viewer symbol.ttf

  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).

  $ gnome-font-viewer
  /usr/share/fonts/truetype/msttcorefonts/webdings.ttf

  Expected results:
  * GNOME Font Viewer opened window for font preview and installation

  Actual results:
  * GNOME Font Viewer crashed with the following output:

  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)

  Note: I attached the font file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1717678/+subscriptions

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


[Desktop-packages] [Bug 1717678] ProcCpuinfoMinimal.txt

2018-01-23 Thread Norbert
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1717678/+attachment/5041822/+files/ProcCpuinfoMinimal.txt

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

Title:
  Crash when opening TTF font

Status in GNOME Font Viewer:
  Unknown
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
  3a. Try to install this Symbol font 
(https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf)

  $ gnome-font-viewer symbol.ttf

  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).

  $ gnome-font-viewer
  /usr/share/fonts/truetype/msttcorefonts/webdings.ttf

  Expected results:
  * GNOME Font Viewer opened window for font preview and installation

  Actual results:
  * GNOME Font Viewer crashed with the following output:

  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)

  Note: I attached the font file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1717678/+subscriptions

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


[Desktop-packages] [Bug 1717678] Dependencies.txt

2018-01-23 Thread Norbert
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1717678/+attachment/5041820/+files/Dependencies.txt

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

Title:
  Crash when opening TTF font

Status in GNOME Font Viewer:
  Unknown
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
  3a. Try to install this Symbol font 
(https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf)

  $ gnome-font-viewer symbol.ttf

  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).

  $ gnome-font-viewer
  /usr/share/fonts/truetype/msttcorefonts/webdings.ttf

  Expected results:
  * GNOME Font Viewer opened window for font preview and installation

  Actual results:
  * GNOME Font Viewer crashed with the following output:

  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)

  Note: I attached the font file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1717678/+subscriptions

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


[Desktop-packages] [Bug 1717678] ProcEnviron.txt

2018-01-23 Thread Norbert
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1717678/+attachment/5041823/+files/ProcEnviron.txt

** Description changed:

  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
  3a. Try to install this font
  
- $ gnome-font-viewer wingding_0.ttf
+ $ gnome-font-viewer symbol.ttf (https://raw.githubusercontent.com/IamDH4
+ /ttf-wps-fonts/master/symbol.ttf)
  
  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).
  
  $ gnome-font-viewer /usr/share/fonts/truetype/msttcorefonts/webdings.ttf
  
  Expected results:
  * GNOME Font Viewer opened window for font preview and installation
  
  Actual results:
  * GNOME Font Viewer crashed with the following output:
  
  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)
  
  Note: I attached the font file.

** Description changed:

  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
- 3a. Try to install this font
+ 3a. Try to install this Symbol font 
(https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf)
  
- $ gnome-font-viewer symbol.ttf (https://raw.githubusercontent.com/IamDH4
- /ttf-wps-fonts/master/symbol.ttf)
+ $ gnome-font-viewer symbol.ttf
  
  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).
  
  $ gnome-font-viewer /usr/share/fonts/truetype/msttcorefonts/webdings.ttf
  
  Expected results:
  * GNOME Font Viewer opened window for font preview and installation
  
  Actual results:
  * GNOME Font Viewer crashed with the following output:
  
  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)
  
  Note: I attached the font file.

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

Title:
  Crash when opening TTF font

Status in GNOME Font Viewer:
  Unknown
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
  3a. Try to install this Symbol font 
(https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf)

  $ gnome-font-viewer symbol.ttf

  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).

  $ gnome-font-viewer
  /usr/share/fonts/truetype/msttcorefonts/webdings.ttf

  Expected results:
  * GNOME Font Viewer opened window for font preview and installation

  Actual results:
  * GNOME Font Viewer crashed with the following output:

  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)

  Note: I attached the font file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1717678/+subscriptions

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


[Desktop-packages] [Bug 1717678] Re: Crash when opening TTF font

2018-01-23 Thread Norbert
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: MATE
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2014-02-07 (1445 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
Package: gnome-font-viewer 3.16.2-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Tags:  xenial
Uname: Linux 4.4.0-104-generic x86_64
UpgradeStatus: Upgraded to xenial on 2017-04-15 (282 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev 
plugdev sambashare scanner sudo tape vboxusers video wireshark
_MarkForUpload: True


** Tags added: apport-collected

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

Title:
  Crash when opening TTF font

Status in GNOME Font Viewer:
  Unknown
Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font
  3a. Try to install this Symbol font 
(https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf)

  $ gnome-font-viewer symbol.ttf

  3b. Try to open webdings.ttf font from `ttf-mscorefonts-installer`
  package (see bug 1647906 for details).

  $ gnome-font-viewer
  /usr/share/fonts/truetype/msttcorefonts/webdings.ttf

  Expected results:
  * GNOME Font Viewer opened window for font preview and installation

  Actual results:
  * GNOME Font Viewer crashed with the following output:

  (gnome-font-viewer:14847): Pango-CRITICAL **: pango_find_base_dir: assertion 
'text != NULL || length == 0' failed
  Violación de segmento (`core' generado)

  Note: I attached the font file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1717678/+subscriptions

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


[Desktop-packages] [Bug 1744922] Re: GNOME Font VIewer does not show TTF font

2018-01-23 Thread Norbert
** Bug watch added: GNOME Bug Tracker #792835
   https://bugzilla.gnome.org/show_bug.cgi?id=792835

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

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

Title:
  GNOME Font VIewer does not show TTF font

Status in GNOME Font Viewer:
  Unknown
Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font (for example Symbol from 
https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf )
  3. Try to open downloaded font with `gnome-font-viewer symbol.ttf`

  Actual results:
  GNOME Font Viewer shows blank white window (see screenshot). Terminal output 
is empty, .xsession-errors is clean.

  Expected results:
  GNOME Font Viewer shows font preview.

  Note: the font file is not damaged, it opens normally with `mate-font-
  viewer`.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-font-viewer 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jan 23 14:14:09 2018
  InstallationDate: Installed on 2017-12-23 (30 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1744922/+subscriptions

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


[Desktop-packages] [Bug 1744970] Re: Lowering some windows causes other, unrelated windows to also be lowered.

2018-01-23 Thread Andrew
See also Launchpad bug #2627, "Non-leading whitespace mangled in bug
description and comments".

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

Title:
  Lowering some windows causes other, unrelated windows to also be
  lowered.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

1. Open four windows, each using half of the screen:

  ┌──C──╥──D──┐
┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐
│ ║ │ ││ ║ │
│ ║ │ └┤ ║ │
└─╨─┘  └─╨─┘
   2D view3D view

2. Lower window A.

  Expected behavior:

Window A is lowered:

  ┌──A──╥──D──┐
┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐
│ ║ │ ││ ║ │
│ ║ │ └┤ ║ │
└─╨─┘  └─╨─┘
   2D view3D view

  Actual behavior:

Window A and window B are lowered:

  ┌──A──╥──B──┐
┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐
│ ║ │ ││ ║ │
│ ║ │ └┤ ║ │
└─╨─┘  └─╨─┘
   2D view3D view

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 07:50:21 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-15 (495 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-21 (2 days ago)

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

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


[Desktop-packages] [Bug 1533267] Re: gcr-prompter is logging too much

2018-01-23 Thread Bug Watch Updater
** Changed in: gcr
   Status: Unknown => Confirmed

** Changed in: gcr
   Importance: Unknown => Medium

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

Title:
  gcr-prompter is logging too much

Status in GCR:
  Confirmed
Status in gcr package in Ubuntu:
  Triaged

Bug description:
  When prompted to unlock a SSH private key, gcr-prompter logs no less
  than 29 messages in auth.log:

Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: received 
BeginPrompting call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: preparing a prompt 
for callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: creating new 
GcrPromptDialog prompt
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: automatically 
selecting secret exchange protocol
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: generating public key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: beginning the secret 
exchange: [sx-aes-1]\npublic=pub-base64\n
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: returned from the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: received 
PerformPrompt call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: receiving secret 
exchange: [sx-aes-1]\npublic=pub-base64\n
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: deriving shared 
transport key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: deriving transport key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: starting password 
prompt for callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gtk: GtkDialog mapped 
without a transient parent. This is discouraged.
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: completed password 
prompt for callback :1.2@/org/gnome/keyring/Prompt/p4
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: encrypting data
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: sending the secret 
exchange: [sx-aes-1]\npublic=pub-base64\nsecret=secret-base64==\n
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: returned from the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: received 
PerformPrompt call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: closing the prompt
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptDone method on /org/gnome/keyring/Prompt/p4@:1.2, and ignoring reply

  
  This looks like debug logging to me. Also, it's probably best to avoid 
logging the secret exchange (obfuscated above).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gcr 3.18.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 12 10:54:14 2016
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

2018-01-23 Thread Tao Rich
I filed a bug report with GNOME:

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

I added the link to:

Also affects project.

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

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

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

Status in gedit:
  Unknown
Status in gedit package in Ubuntu:
  New

Bug description:
  If I paste a special character - say from the Character Map - into
  Gedit or medit in Ubuntu 16.04 into the middle of a line, then the
  space characters directly after the special character display with a
  "compressed" character spacing until the behaviour is "interrupted" by
  a standard text character.

  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines
  with the special character problem.

  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .

  https://askubuntu.com/questions/986258/why-do-special-characters-
  change-spacing-following-space-character-in-gedit-or-m

  Please see that post for full details, worked example, and
  screenshots.

  Additional comments:

  * As stated above:
  - running Ubuntu 16.04

  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0

  I am aware that it is thus not strictly a gedit issue, and probably
  affects multiple Gnome editors under multiple Linux variants - but
  Gedit is my favourite text editor and Ubuntu is my favourite Linux so
  I thought I would start here.

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

  $ apt-cache policy gedit
  gedit:
    Installed: 3.18.3-0ubuntu4
    Candidate: 3.18.3-0ubuntu4
    Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy medit
  medit:
    Installed: 1.2.0-2
    Candidate: 1.2.0-2
    Version table:
   *** 1.2.0-2 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1744970] [NEW] Lowering some windows causes other, unrelated windows to also be lowered.

2018-01-23 Thread Andrew
Public bug reported:

Steps to reproduce:

  1. Open four windows, each using half of the screen:

┌──C──╥──D──┐
  ┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐
  │ ║ │ ││ ║ │
  │ ║ │ └┤ ║ │
  └─╨─┘  └─╨─┘
 2D view3D view

  2. Lower window A.

Expected behavior:

  Window A is lowered:

┌──A──╥──D──┐
  ┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐
  │ ║ │ ││ ║ │
  │ ║ │ └┤ ║ │
  └─╨─┘  └─╨─┘
 2D view3D view

Actual behavior:

  Window A and window B are lowered:

┌──A──╥──B──┐
  ┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐
  │ ║ │ ││ ║ │
  │ ║ │ └┤ ║ │
  └─╨─┘  └─╨─┘
 2D view3D view

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 07:50:21 2018
DisplayManager: gdm3
InstallationDate: Installed on 2016-09-15 (495 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2018-01-21 (2 days ago)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Lowering some windows causes other, unrelated windows to also be
  lowered.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

1. Open four windows, each using half of the screen:

  ┌──C──╥──D──┐
┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐
│ ║ │ ││ ║ │
│ ║ │ └┤ ║ │
└─╨─┘  └─╨─┘
   2D view3D view

2. Lower window A.

  Expected behavior:

Window A is lowered:

  ┌──A──╥──D──┐
┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐
│ ║ │ ││ ║ │
│ ║ │ └┤ ║ │
└─╨─┘  └─╨─┘
   2D view3D view

  Actual behavior:

Window A and window B are lowered:

  ┌──A──╥──B──┐
┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐
│ ║ │ ││ ║ │
│ ║ │ └┤ ║ │
└─╨─┘  └─╨─┘
   2D view3D view

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 07:50:21 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-15 (495 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-21 (2 days ago)

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

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


[Desktop-packages] [Bug 1744855] Re: Upgrade to 2.84-3ubuntu3.1 breaks remote access (webui)

2018-01-23 Thread Leonidas S. Barbosa
Hi,

It seems the patch touched new settings the may causing this issue.
Are your clients using authentication?
Seems you either needs the clients to be configured to use password auth or set 
a host whitelist with this new configuration.

Can you try that and see if it fix?

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

Title:
  Upgrade to 2.84-3ubuntu3.1 breaks remote access (webui)

Status in transmission package in Ubuntu:
  New

Bug description:
  I just upgraded to transmission-daemon 2.84-3ubuntu3.1 and I can no
  longer use the webui (nor android clients) to access transmission.
  This is the webui URL I've been using:

  http://cine:9091/transmission/web/

  This is the error I'm getting:

  Connection Failed
  Could not connect to the server. You may need to reload the page to reconnect.

  transmission-remote on the machine works fine. The server running
  transmission-daemon is on a local network on the same subnet as the
  android and webui clients. Nothing has changed beyond installing a few
  updates, including 2.84-3.

  Here is my settings.json:

  {
  "alt-speed-down": 15,
  "alt-speed-enabled": false,
  "alt-speed-time-begin": 540,
  "alt-speed-time-day": 127,
  "alt-speed-time-enabled": false,
  "alt-speed-time-end": 1020,
  "alt-speed-up": 15,
  "bind-address-ipv4": "0.0.0.0",
  "bind-address-ipv6": "::",
  "blocklist-date": 1308104247,
  "blocklist-enabled": true,
  "blocklist-updates-enabled": true,
  "blocklist-url": "http://john.bitsurge.net/public/biglist.p2p.gz;,
  "cache-size-mb": 4,
  "compact-view": false,
  "dht-enabled": true,
  "download-dir": "/home/bbogart/Downloads",
  "download-queue-enabled": true,
  "download-queue-size": 5,
  "encryption": 1,
  "filter-mode": "show-all",
  "idle-seeding-limit": 30,
  "idle-seeding-limit-enabled": false,
  "incomplete-dir": "/home/bbogart/Downloads",
  "incomplete-dir-enabled": false,
  "inhibit-desktop-hibernation": true,
  "lazy-bitfield-enabled": true,
  "lpd-enabled": false,
  "main-window-height": 975,
  "main-window-is-maximized": 0,
  "main-window-layout-order": "menu,toolbar,filter,list,statusbar",
  "main-window-width": 968,
  "main-window-x": 285,
  "main-window-y": 0,
  "message-level": 1,
  "minimal-view": false,
  "open-dialog-dir": "/home/bbogart",
  "open-file-limit": 32,
  "peer-congestion-algorithm": "",
  "peer-id-ttl-hours": 6,
  "peer-limit-global": 240,
  "peer-limit-per-torrent": 60,
  "peer-port": 60639,
  "peer-port-random-high": 65535,
  "peer-port-random-low": 49152,
  "peer-port-random-on-start": true,
  "peer-socket-tos": "default",
  "pex-enabled": true,
  "play-download-complete-sound": false,
  "port-forwarding-enabled": true,
  "preallocation": 1,
  "prefetch-enabled": 1,
  "prompt-before-exit": true,
  "proxy": "",
  "proxy-auth-enabled": false,
  "proxy-auth-password": "",
  "proxy-auth-username": "",
  "proxy-enabled": false,
  "proxy-port": 80,
  "proxy-type": 0,
  "queue-stalled-enabled": true,
  "queue-stalled-minutes": 30,
  "ratio-limit": 1.2496,
  "ratio-limit-enabled": true,
  "recent-download-dir-1": "/home/bbogart/Downloads",
  "rename-partial-files": false,
  "rpc-authentication-required": false,
  "rpc-bind-address": "0.0.0.0",
  "rpc-enabled": true,
  "rpc-host-whitelist": "",
  "rpc-host-whitelist-enabled": true,
  "rpc-password": "{e607e2c7c28eab2770c82c1d0574c0e731c050d5TdP8HGP6",
  "rpc-port": 9091,
  "rpc-url": "/transmission/",
  "rpc-username": "",
  "rpc-whitelist": "192.168.0.*",
  "rpc-whitelist-enabled": false,
  "scrape-paused-torrents-enabled": true,
  "script-torrent-done-enabled": false,
  "script-torrent-done-filename": "/home/bbogart",
  "seed-queue-enabled": false,
  "seed-queue-size": 10,
  "show-backup-trackers": false,
  "show-desktop-notification": true,
  "show-extra-peer-details": false,
  "show-filterbar": true,
  "show-notification-area-icon": true,
  "show-options-window": true,
  "show-statusbar": true,
  "show-toolbar": true,
  "show-tracker-scrapes": false,
  "sort-mode": "sort-by-ratio",
  "sort-reversed": false,
  "speed-limit-down": 100,
  "speed-limit-down-enabled": false,
  "speed-limit-up": 100,
  "speed-limit-up-enabled": false,
  "start-added-torrents": true,
  "statusbar-stats": "total-ratio",
  "torrent-added-notification-enabled": false,
  "torrent-complete-notification-enabled": true,
  "torrent-complete-sound-command": "canberra-gtk-play -i complete-download 
-d 'transmission torrent downloaded'",
  

[Desktop-packages] [Bug 1744941] Re: gnome-software crashes in as_app_parse_desktop_file

2018-01-23 Thread Ubuntu Foundations Team Bug Bot
The attachment "Debdiff for xenial package" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  gnome-software crashes in as_app_parse_desktop_file

Status in appstream package in Ubuntu:
  In Progress

Bug description:
  See more at upstream bug: https://github.com/hughsie/appstream-
  glib/pull/221

  This affects all the releases since xenial.

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

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


[Desktop-packages] [Bug 1744825] Re: trashcan shows full, but will not empty

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

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

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

Title:
  trashcan shows full, but will not empty

Status in nautilus package in Ubuntu:
  New

Bug description:
  status:
  internal disk used as backup filled up.
  system reports zero space left.
  --
  action:
  Right clicked Trash icon.
  clicked 
  system asks "empty all items from trash?"
  clicked 
  panel pops up "file operations" showing a progress bar and says "preparing"
  progress bar remains empty
  panel disappears after a while
  trash can icon remains "full"
  --
  can be repeated with same results

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 23 10:39:28 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1235x472+45+24'"
   b'org.gnome.nautilus.icon-view' b'captions' b"['date_modified', 'where', 
'none']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2017-12-13 (40 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1744825/+subscriptions

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


[Desktop-packages] [Bug 1570921] Re: suspend not working

2018-01-23 Thread Michael Hathaway
This just started happening on my Lenovo Yoga. All worked fine
previously. Something is causing the computer to turn back on a few
seconds after going into suspend

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

Title:
  suspend not working

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  My computer cannot go to suspend state.  The monitor switch off but the 
cpu/cpu fan keeps running and the hard drive is active.
  It doesn't respond, I need to switch off manually to reboot the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 15 18:42:49 2016
  InstallationDate: Installed on 2016-04-15 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1723591] Re: Nautilus locks up every time I press Ctrl+C

2018-01-23 Thread Sebastien Bacher
It still feels weird that it's blocking if there is no plugin, could you
install it back and check if there are really no python extension (and
maybe with a new user)

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

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

Title:
  Nautilus locks up every time I press Ctrl+C

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Every time I press Ctrl+C to copy a file, Nautilus locks up for 5s or
  so.

  Steps:
  * open a folder in Nautilus
  * select a file
  * press Ctrl+C

  Expected:
  * nothing, really

  Current:
  * Nautilus locks up for a number of seconds

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 14 11:42:37 2017
  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/1723591/+subscriptions

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


[Desktop-packages] [Bug 1744922] Re: GNOME Font VIewer does not show TTF font

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

** Changed in: gnome-font-viewer (Ubuntu)
   Importance: Undecided => Low

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

Title:
  GNOME Font VIewer does not show TTF font

Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install `gnome-font-viewer`
  2. Download TTF font (for example Symbol from 
https://raw.githubusercontent.com/IamDH4/ttf-wps-fonts/master/symbol.ttf )
  3. Try to open downloaded font with `gnome-font-viewer symbol.ttf`

  Actual results:
  GNOME Font Viewer shows blank white window (see screenshot). Terminal output 
is empty, .xsession-errors is clean.

  Expected results:
  GNOME Font Viewer shows font preview.

  Note: the font file is not damaged, it opens normally with `mate-font-
  viewer`.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-font-viewer 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Jan 23 14:14:09 2018
  InstallationDate: Installed on 2017-12-23 (30 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1744619] Re: Transitioning GNOME away from libnm-glib

2018-01-23 Thread Sebastien Bacher
Changing the title to reflect what I think the changeset is about, let
me know if you think it's not an accurate summary

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

Title:
  Transitioning GNOME away from libnm-glib

Status in network-manager-iodine package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New

Bug description:
  Debian has dropped libnm-glib support from most of its VPN plugins.

  We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome-
  shell to properly interact with VPNs.

  unity-control-center will need to be ported away from libnm-glib for
  it to display VPNs.

  The only other known affected desktop is Cinnamon which has fixes
  "pending"

  Here's the Debian transition bug:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm

  At first look, KDE Plasma did not seem to be hurt by the libnm-glib
  support removal, but Kubuntu should probably check more closely.

  I am filing this bug to coordinate this transition and keep the VPN
  plugins in -proposed until we at least update gnome-shell.

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

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


[Desktop-packages] [Bug 1744619] Re: libnm-glib removal transition

2018-01-23 Thread Sebastien Bacher
That was discussed on IRC and there are some details in the upstream
report (https://bugzilla.gnome.org/show_bug.cgi?id=779776)

The main issue on the GNOME side seems to be that libnm and libnm-glib
bindings can't be loaded at the same time, which means that gnome-shell
and its plugins need to be using the same library, which means they need
to be updated in sync to avoid issue.

There doesn't seem to be a need to remove libnm-glib from Ubuntu yet
though (if it's still needed/used), upstream hasn't removed it either
but building the nm plugins without it might lead to issues for unity-
control-center which is using the old library still

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

** Summary changed:

- libnm-glib removal transition
+ Transitioning GNOME away from libnm-glib

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

Title:
  Transitioning GNOME away from libnm-glib

Status in network-manager-iodine package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New

Bug description:
  Debian has dropped libnm-glib support from most of its VPN plugins.

  We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome-
  shell to properly interact with VPNs.

  unity-control-center will need to be ported away from libnm-glib for
  it to display VPNs.

  The only other known affected desktop is Cinnamon which has fixes
  "pending"

  Here's the Debian transition bug:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm

  At first look, KDE Plasma did not seem to be hurt by the libnm-glib
  support removal, but Kubuntu should probably check more closely.

  I am filing this bug to coordinate this transition and keep the VPN
  plugins in -proposed until we at least update gnome-shell.

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

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


[Desktop-packages] [Bug 1744963] [NEW] printing a PDF generated by LibreOffice sometimes fail with lpr but is printed correctly with evince

2018-01-23 Thread J-K
Public bug reported:

Sometimes a PDF generated by LibreOffice is not printed correctly with lpr but 
is printed correctly with evince.
For an example see attached PDF: Using lpr only the first line is printed, 
nothing more.

I'm using Ubuntu 16.04.2 LTS with cups-filters 1.8.3-2ubuntu3.1 . The
printer is HP LaserJet 3055, connected via network - DeviceURI
hp:/net/HP_LaserJet_3055?ip=192.168.XXX.XXX using hplip 3.16.3+repack0-1
.

Maybe this bug is related to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=613987 ?

Do you need additional information?

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "example document which is not printed correctly using lpr"
   
https://bugs.launchpad.net/bugs/1744963/+attachment/5041809/+files/Hol+Pack.pdf

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

Title:
  printing a PDF generated by LibreOffice sometimes fail with lpr but is
  printed correctly with evince

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Sometimes a PDF generated by LibreOffice is not printed correctly with lpr 
but is printed correctly with evince.
  For an example see attached PDF: Using lpr only the first line is printed, 
nothing more.

  I'm using Ubuntu 16.04.2 LTS with cups-filters 1.8.3-2ubuntu3.1 . The
  printer is HP LaserJet 3055, connected via network - DeviceURI
  hp:/net/HP_LaserJet_3055?ip=192.168.XXX.XXX using hplip
  3.16.3+repack0-1 .

  Maybe this bug is related to https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=613987 ?

  Do you need additional information?

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

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


[Desktop-packages] [Bug 1533267] Re: gcr-prompter is logging too much

2018-01-23 Thread Sebastien Bacher
** Changed in: gcr (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  gcr-prompter is logging too much

Status in GCR:
  Unknown
Status in gcr package in Ubuntu:
  Triaged

Bug description:
  When prompted to unlock a SSH private key, gcr-prompter logs no less
  than 29 messages in auth.log:

Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: received 
BeginPrompting call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: preparing a prompt 
for callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: creating new 
GcrPromptDialog prompt
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: automatically 
selecting secret exchange protocol
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: generating public key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: beginning the secret 
exchange: [sx-aes-1]\npublic=pub-base64\n
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: returned from the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: received 
PerformPrompt call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: receiving secret 
exchange: [sx-aes-1]\npublic=pub-base64\n
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: deriving shared 
transport key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: deriving transport key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: starting password 
prompt for callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gtk: GtkDialog mapped 
without a transient parent. This is discouraged.
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: completed password 
prompt for callback :1.2@/org/gnome/keyring/Prompt/p4
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: encrypting data
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: sending the secret 
exchange: [sx-aes-1]\npublic=pub-base64\nsecret=secret-base64==\n
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: returned from the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: received 
PerformPrompt call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: closing the prompt
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptDone method on /org/gnome/keyring/Prompt/p4@:1.2, and ignoring reply

  
  This looks like debug logging to me. Also, it's probably best to avoid 
logging the secret exchange (obfuscated above).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gcr 3.18.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 12 10:54:14 2016
  SourcePackage: gcr
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1738629] Re: Cannot drag and drop files into open windows.

2018-01-23 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1704765 ***
https://bugs.launchpad.net/bugs/1704765

** This bug is no longer a duplicate of bug 1741777
   drag and drop between desktop and nautilus doesn't work
** This bug has been marked a duplicate of bug 1704765
   can't drag file from desktop to folder window on Artful

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

Title:
  Cannot drag and drop files into open windows.

Status in nautilus package in Ubuntu:
  New

Bug description:
  When trying to drag and drop a file into an open window, the file
  appears to go behind the window and the mouse then becomes
  unresponsive when over the main desktop; a restart is required to
  return to normal use. The only way to move files at the moment it copy
  and paste.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 15:15:44 2017
  InstallationDate: Installed on 2017-12-01 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1738629/+subscriptions

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


[Desktop-packages] [Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work

2018-01-23 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1704765 ***
https://bugs.launchpad.net/bugs/1704765

** This bug has been marked a duplicate of bug 1704765
   can't drag file from desktop to folder window on Artful

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

Title:
  drag and drop between desktop and nautilus doesn't work

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I open a nautilus window and try to drag a file from the desktop to this 
window. It's not done and the arrow pointer of the mouse become a close hand 
and you cannot use it anymore to click anywhere.
  Session Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  7 19:19:23 2018
  InstallationDate: Installed on 2016-04-30 (617 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-23 (76 days ago)

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

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


[Desktop-packages] [Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

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

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

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

Status in gedit package in Ubuntu:
  New

Bug description:
  If I paste a special character - say from the Character Map - into
  Gedit or medit in Ubuntu 16.04 into the middle of a line, then the
  space characters directly after the special character display with a
  "compressed" character spacing until the behaviour is "interrupted" by
  a standard text character.

  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines
  with the special character problem.

  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .

  https://askubuntu.com/questions/986258/why-do-special-characters-
  change-spacing-following-space-character-in-gedit-or-m

  Please see that post for full details, worked example, and
  screenshots.

  Additional comments:

  * As stated above:
  - running Ubuntu 16.04

  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0

  I am aware that it is thus not strictly a gedit issue, and probably
  affects multiple Gnome editors under multiple Linux variants - but
  Gedit is my favourite text editor and Ubuntu is my favourite Linux so
  I thought I would start here.

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

  $ apt-cache policy gedit
  gedit:
    Installed: 3.18.3-0ubuntu4
    Candidate: 3.18.3-0ubuntu4
    Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy medit
  medit:
    Installed: 1.2.0-2
    Candidate: 1.2.0-2
    Version table:
   *** 1.2.0-2 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1533267] Re: gcr-prompter is logging too much

2018-01-23 Thread Martin von Wittich
I've found an upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=773009

I've also devised a simple workaround:

martin@dogmeat ~ % cat /etc/rsyslog.d/20-gcr-prompter-discard.conf 
# gcr-prompter logs debug info to /var/log/auth.log
# https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1533267
# https://bugzilla.gnome.org/show_bug.cgi?id=773009
if $programname == 'gcr-prompter' then stop

Run `sudo systemctl restart rsyslog` after creating that file, then gcr-
prompter should no longer produce any logs.

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

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

Title:
  gcr-prompter is logging too much

Status in GCR:
  Unknown
Status in gcr package in Ubuntu:
  Triaged

Bug description:
  When prompted to unlock a SSH private key, gcr-prompter logs no less
  than 29 messages in auth.log:

Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: received 
BeginPrompting call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: preparing a prompt 
for callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: creating new 
GcrPromptDialog prompt
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: automatically 
selecting secret exchange protocol
Jan 12 10:55:42 simon-laptop gcr-prompter[7123]: Gcr: generating public key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: beginning the secret 
exchange: [sx-aes-1]\npublic=pub-base64\n
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: returned from the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: received 
PerformPrompt call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: receiving secret 
exchange: [sx-aes-1]\npublic=pub-base64\n
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: deriving shared 
transport key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: deriving transport key
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gcr: starting password 
prompt for callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:43 simon-laptop gcr-prompter[7123]: Gtk: GtkDialog mapped 
without a transient parent. This is discouraged.
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: completed password 
prompt for callback :1.2@/org/gnome/keyring/Prompt/p4
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: encrypting data
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: sending the secret 
exchange: [sx-aes-1]\npublic=pub-base64\nsecret=secret-base64==\n
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: returned from the 
PromptReady method on /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: received 
PerformPrompt call from callback /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: closing the prompt
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: stopping prompting 
for operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: couldn't find the 
callback for prompting operation /org/gnome/keyring/Prompt/p4@:1.2
Jan 12 10:55:44 simon-laptop gcr-prompter[7123]: Gcr: calling the 
PromptDone method on /org/gnome/keyring/Prompt/p4@:1.2, and ignoring reply

  
  This looks like debug logging to me. Also, it's probably best to avoid 
logging the secret exchange (obfuscated above).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gcr 3.18.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 12 10:54:14 2016
  SourcePackage: gcr
  UpgradeStatus: No upgrade log 

[Desktop-packages] [Bug 1744587] Re: hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720

2018-01-23 Thread Till Kamppeter
** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  hplip under Ubuntu 17.10 for HP OfficeJet Pro 8720

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  https://askubuntu.com/questions/990970/how-to-install-hplip-3-17-11
  -under-ubuntu-17-10-for-hp-officejet-pro-8720

  I'm using Ubuntu 17.10

  According to the release notes https://developers.hp.com/hp-linux-
  imaging-and-printing/release_notes I need hplip 3.17.11.


  When I install hplip from using apt-get I get the following error when
  I execute hp-check:

  The error is the following (distro not supported) File
  "/usr/share/hplip/installer/core_install.py", line 475, in init
  self.distro_name = self.distros_index[self.distro]




  I've tried installing from the shell installer with the following:

  error: Configure failed with error: libnetsnmp not found

  When I do the following:

  sudo apt-get install libsnmp-dev

  I get

  libsnmp-dev is already the newest version (5.7.3+dfsg-1.7ubuntu1)

  And apt is an older version

  apt-cache policy hplip
  hplip:
    Installed: 3.17.7+repack0-3
    Candidate: 3.17.7+repack0-3
    Version table:
   *** 3.17.7+repack0-3 500
    500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
    100 /var/lib/dpkg/status

  Anyone have any ideas on how I can install and/or debug this?

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

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


[Desktop-packages] [Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work

2018-01-23 Thread Pete
Looks like this may be the same issue as this bug still not resolved.

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1704765

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

Title:
  drag and drop between desktop and nautilus doesn't work

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I open a nautilus window and try to drag a file from the desktop to this 
window. It's not done and the arrow pointer of the mouse become a close hand 
and you cannot use it anymore to click anywhere.
  Session Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  7 19:19:23 2018
  InstallationDate: Installed on 2016-04-30 (617 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-23 (76 days ago)

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

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


[Desktop-packages] [Bug 1704765] Re: can't drag file from desktop to folder window on Artful

2018-01-23 Thread Pete
I confirm this issue as well. Using latest build of 17.10 and updated.
It requires me to log off/on to get things working again.

I found multiple duplicate bugs on this issue, and yes...wonder why its
not fixed?

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

Title:
  can't drag file from desktop to folder window on Artful

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

Bug description:
  I'm running Ubuntu 17.10 (Artful).  If I create a text file on my
  desktop and then attempt to drag it into a Nautilus folder window, it
  fails: when I release the mouse cursor over the folder window nothing
  happens and the file is not moved.

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

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


[Desktop-packages] [Bug 1741777] Re: drag and drop between desktop and nautilus doesn't work

2018-01-23 Thread Pete
I confirm I have this exact problem. Using latest build of Ubuntu 17.10
(Wayland)from Jan 2018.

Note: This bug also seems very similar to this one.

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1729887

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

Title:
  drag and drop between desktop and nautilus doesn't work

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  I open a nautilus window and try to drag a file from the desktop to this 
window. It's not done and the arrow pointer of the mouse become a close hand 
and you cannot use it anymore to click anywhere.
  Session Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  7 19:19:23 2018
  InstallationDate: Installed on 2016-04-30 (617 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-23 (76 days ago)

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

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


[Desktop-packages] [Bug 1101825] Re: IPv6 static default route added incorrectly by network-manager

2018-01-23 Thread leeA
Hi
I also have this problem and for me it seems this bug is not realy resolved. 
Are there any more insights on this?

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

Title:
  IPv6 static default route added incorrectly by network-manager

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The relevant part of the IPv6 routing table looks like this:

  fe80::/64 dev wlan0  proto kernel  metric 256
  default via fe80::5054:ff:fe64:aad0 dev wlan0  proto static  metric 1
  default via fe80::5054:ff:fe9c:741e dev wlan0  proto kernel  metric 1024  
expires 8sec
  default via fe80::5054:ff:fe64:aad0 dev wlan0  proto kernel  metric 1024  
expires 10sec

  I believe the proto static metric 1 route is an error, since it
  persists even when the router stops advertising.  This breaks the IPv6
  architecture for router redundancy.

  I am in control of this network and can alter router advertisement
  parameters if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
  Uname: Linux 3.5.0-22-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Sat Jan 19 10:47:05 2013
  InstallationDate: Installed on 2012-11-15 (65 days ago)
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 
(20121017.2)
  IpRoute:
   default via 192.168.4.1 dev wlan0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   192.168.4.0/24 dev wlan0  proto kernel  scope link  src 192.168.4.64  metric 
9
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog: Jan 19 10:17:54 pippin wpa_supplicant[1009]: wlan0: WPA: Group 
rekeying completed with 00:24:a5:f1:08:8e [GTK=CCMP]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2012-11-25T12:30:38.408468
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN
   running 0.9.6.0connected   enabled   enabled 
enabledenabled enabled

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

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


[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

2018-01-23 Thread Olivier Crête
Also, deja-dup seems to run the "cleanup" command when it tries to do a
backup after failing. So this list is after the cleanup is done.

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

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

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


[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

2018-01-23 Thread Olivier Crête
Duplicity is run by deja-dup in my case:

 python2 /usr/bin/duplicity --exclude=/mnt/Backup/duplicity
--include=/home/ocrete/.cache/deja-dup/metadata
--exclude=/home/ocrete/.ccache --exclude=/home/ocrete/.cache
--exclude=/home/ocrete/Videos --exclude=/home/ocrete/.local/share/Trash
--exclude=/home/ocrete/.thumbnails --exclude=/home/ocrete/.steam/root
--exclude=/home/ocrete/.gvfs --exclude=/home/ocrete/.ccache
--exclude=/home/ocrete/.adobe/Flash_Player/AssetCache
--exclude=/home/ocrete/.cache/deja-dup --exclude=/home/ocrete/.cache
--include=/home/ocrete --exclude=/var/cache --exclude=/var/tmp
--exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
--exclude=/tmp --exclude=** --dry-run --volsize=50 /
gio+file:///mnt/Backup/duplicity --verbosity=9 --gpg-options=--no-use-
agent --archive-dir=/home/ocrete/.cache/deja-dup --tempdir=/var/tmp
--log-fd=17


** Attachment added: "List of files"
   
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1730451/+attachment/5041788/+files/dup-files.txt

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

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

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


[Desktop-packages] [Bug 1744947] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2018-01-23 Thread dino99
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  don't know

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Tue Jan 23 15:09:36 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-KVDAm4/143-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-12-16 (38 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1744946] Re: Special characters change the width of trailing/leading space character in Gedit (and medit)

2018-01-23 Thread Tao Rich
** Description changed:

  If I paste a special character - say from the Character Map - into Gedit
  or medit in Ubuntu 16.04 into the middle of a line, then the space
  characters directly after the special character display with a
- "compressed" character spacing/display until the behaviour is
- "interrupted" by a standard text character.
+ "compressed" character spacing until the behaviour is "interrupted" by a
+ standard text character.
  
  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines with
  the special character problem.
  
  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .
  
  https://askubuntu.com/questions/986258/why-do-special-characters-change-
  spacing-following-space-character-in-gedit-or-m
  
  Please see that post for full details, worked example, and screenshots.
  
  Additional comments:
  
  * As stated above:
  - running Ubuntu 16.04
  
  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0
  
  I am aware that it is thus not strictly a gedit issue, and probably
- affects multiple Gnome editor under multiple Linux variants but Gedit is
- my favourite text editor and Ubuntu is my favourite Linux so I thought I
- would start here.
+ affects multiple Gnome editors under multiple Linux variants - but Gedit
+ is my favourite text editor and Ubuntu is my favourite Linux so I
+ thought I would start here.
  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  
  $ apt-cache policy gedit
  gedit:
-   Installed: 3.18.3-0ubuntu4
-   Candidate: 3.18.3-0ubuntu4
-   Version table:
-  *** 3.18.3-0ubuntu4 500
- 500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 3.18.3-0ubuntu4
+   Candidate: 3.18.3-0ubuntu4
+   Version table:
+  *** 3.18.3-0ubuntu4 500
+ 500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  $ apt-cache policy medit
  medit:
-   Installed: 1.2.0-2
-   Candidate: 1.2.0-2
-   Version table:
-  *** 1.2.0-2 500
- 500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.2.0-2
+   Candidate: 1.2.0-2
+   Version table:
+  *** 1.2.0-2 500
+ 500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ 100 /var/lib/dpkg/status

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

Title:
  Special characters change the width of trailing/leading space
  character in Gedit (and medit)

Status in gedit package in Ubuntu:
  New

Bug description:
  If I paste a special character - say from the Character Map - into
  Gedit or medit in Ubuntu 16.04 into the middle of a line, then the
  space characters directly after the special character display with a
  "compressed" character spacing until the behaviour is "interrupted" by
  a standard text character.

  So the basic problem result is that the uniform monospacing of
  characters gets out of alignment on lines above and below the lines
  with the special character problem.

  I posted a detailed question on AskUbuntu and the prevailing opinion was that 
I should log a bug report.
  Another user with different versions was easily able to reproduce the same 
issue .

  https://askubuntu.com/questions/986258/why-do-special-characters-
  change-spacing-following-space-character-in-gedit-or-m

  Please see that post for full details, worked example, and
  screenshots.

  Additional comments:

  * As stated above:
  - running Ubuntu 16.04

  * This affects:
  - Gedit 3.18.3
  - medit 1.2.0

  I am aware that it is thus not strictly a gedit issue, and probably
  affects multiple Gnome editors under multiple Linux variants - but
  Gedit is my favourite text editor and Ubuntu is my favourite Linux so
  I thought I would start here.

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

  $ apt-cache policy gedit
  gedit:
    Installed: 3.18.3-0ubuntu4
    Candidate: 3.18.3-0ubuntu4
    Version table:
   *** 3.18.3-0ubuntu4 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy medit
  medit:
    Installed: 1.2.0-2
    Candidate: 1.2.0-2
    Version table:
   *** 1.2.0-2 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

  1   2   >