[Desktop-packages] [Bug 357732] Re: cups always prints with the default page size

2019-09-13 Thread Phillip Jones
10 years after the initial bug report and it looks like I'm experiencing
the same bug.

In my case, I'm trying to print some pages that are 11" x 17" but it is
received at the printer as US Letter size. I did confirm that
/etc/papersize contains "letter", and changing that to "A4" also changes
what is received by the printer.

The print dialog confirms that 11x17 has been selected, but that's
overwritten behind the scenes somewhere. Since 11x17 is a custom size in
the print dialog, I'm not sure what I should put in /etc/papersize to
make it work correctly.

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

Title:
  cups always prints with the default page size

Status in GS-GPL:
  Invalid
Status in cups package in Ubuntu:
  Fix Released
Status in ghostscript package in Ubuntu:
  Invalid
Status in cups source package in Intrepid:
  Invalid
Status in ghostscript source package in Intrepid:
  Invalid
Status in cups source package in Jaunty:
  Fix Released
Status in ghostscript source package in Jaunty:
  Invalid

Bug description:
  After the upgrade to Jaunty some users experience that a part of the
  page is cut when printing, or other kinds of misalignment.  (A fix is
  available, see below)

  Details:
  Cups does not print in any other page size than the one set in 
/etc/papersize, if the requested page size is specified as a job option rather 
than within the PS file. Pages are passed through "gs -sDEVICE=pdfwrite ..." 
which sets the page size to the default page size. Yet, I don't know whether 
this is a bug in ghostscript or the intended behavior of ghostscript and a bug 
in cups.

  Since the upgrade to Jauny beta, I experienced that evince would shift
  a document up when printing. It is reproducible. I print in A4 on a
  Canon IR3170Ci.

  The printed output is translated up. The upper part of the contents in
  not visible. I also tried another printer driver (hpijs instead of
  post-script) and did not observe any improvement.

  Changing /etc/papersize from letter to a4 allows me to print in a4.

  Printing from evince also working fine in intrepid.

  To reproduce the bug:
  lpr -omedia=A3 testpage.ps
  There should not be a problem if the postscript file itself requests a page 
size.

  FIX:
  # (For simplicity, just paste this section to a terminal.)
  # Download the attached pstopdf and install it in /usr/lib/cups/filter/
  cd /tmp
  wget http://launchpadlibrarian.net/25537150/pstopdf
  sudo cp pstopdf /usr/lib/cups/filter/
  # Then change the permissions of the installed file:
  sudo chmod ugo+rx /usr/lib/cups/filter/pstopdf
  # that's all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/357732/+subscriptions

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


[Desktop-packages] [Bug 1843955] Re: Black zones in context menu appear in Firefox when I use GNOME on Wayland session

2019-09-13 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1581226.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-09-13T21:43:15+00:00 Artyom Pozharov wrote:

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0)
Gecko/20100101 Firefox/69.0

Steps to reproduce:

Details here:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843955

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843955/comments/2


On 2019-09-13T22:18:10+00:00 Release-mgmt-account-bot wrote:

[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should
belong to this component, but please revert this change in case of
error.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843955/comments/3


** Changed in: firefox
   Status: Unknown => New

** Changed in: firefox
   Importance: Unknown => Medium

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

Title:
  Black zones in context menu appear  in Firefox when I use GNOME on
  Wayland session

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Eyes are very tired because of this

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 2019091951
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 00:28:29 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/2019091951 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1838965]

2019-09-13 Thread Artyom Pozharov
(In reply to Martin Stránský [:stransky] from comment #2)
> I think you mean slow scrolling here instead of video playback tearing, right?

I mean tearing during thr scrolling here instead of video playback
tearing

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

Title:
  Screen tearing in Firefox on Wayland

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 68.0.1+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190719083815
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 13:36:32 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1141
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-08-04 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=68.0.1/20190719083815 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 854382] Re: Simple Scan window not responding to keyboard shortcuts

2019-09-13 Thread Bug Watch Updater
** Changed in: simple-scan (Debian)
   Status: Confirmed => 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/854382

Title:
  Simple Scan window not responding to keyboard shortcuts

Status in One Hundred Papercuts:
  Confirmed
Status in Simple Scan:
  Triaged
Status in simple-scan package in Ubuntu:
  Confirmed
Status in simple-scan package in Debian:
  Fix Released

Bug description:
  The menus indicate that a single page can be scanned by hitting Ctrl+1
  on the keyboard, but pressing Ctrl+1 does not cause a scan to occur.

  Additionally pressing the Delete key does not delete the currently
  selected page.

  Curiously, pressing Alt+D or Alt+P to open the Document or Page menu
  respectively does not result in the relevant menu opening.

  Pressing Tab does cause focus to shift back and forth between the page
  area and the toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: simple-scan 3.1.91-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: Tue Sep 20 12:45:41 2011
  DriverPackageVersions:
   libsane 1.0.22-2ubuntu1
   libsane-extras N/A
   hplip 3.11.7-0ubuntu5
   hpoj N/A
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic 
root=UUID=7ceba223-c023-4c5b-825d-6680919457f0 ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to oneiric on 2011-09-12 (7 days ago)
  dmi.bios.date: 04/04/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.05
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.05:bd04/04/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.10:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1842349] Re: Reconsider conditions for setting language and formats

2019-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu9

---
accountsservice (0.6.55-0ubuntu9) eoan; urgency=medium

  * debian/patches/0010-set-language.patch:
- Simplify logic when to set language and formats (LP: #1842349).
  * debian/control:
- Change Maintainer to Ubuntu Developers.

 -- Gunnar Hjalmarsson   Fri, 13 Sep 2019 22:05:00
+0200

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

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

Title:
  Reconsider conditions for setting language and formats

Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  In connection with the upgrade to 0.6.50 (bug #1789502) the fallback
  values from /etc/default/locale were set on initialization. While that
  addresses some aspects of the upstream changes, a need remains to
  reconsider the conditions in user_change_language_authorized_cb() and
  user_change_formats_locale_authorized_cb(). Currently it does not take
  into account if variables were previously set in ~/.pam_environment or
  not.

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

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


[Desktop-packages] [Bug 1843955] Re: Black zones in context menu appear in Firefox when I use GNOME on Wayland session

2019-09-13 Thread Artyom Pozharov
** Summary changed:

- Black zones in context menu appears  in Firefox when I use GNOME on Wayland 
session
+ Black zones in context menu appear  in Firefox when I use GNOME on Wayland 
session

** Bug watch added: Mozilla Bugzilla #1581226
   https://bugzilla.mozilla.org/show_bug.cgi?id=1581226

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1581226
   Importance: Unknown
   Status: Unknown

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

Title:
  Black zones in context menu appear  in Firefox when I use GNOME on
  Wayland session

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  New

Bug description:
  Eyes are very tired because of this

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 2019091951
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 00:28:29 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/2019091951 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1843955] [NEW] Black zones in context menu appears in Firefox when I use GNOME on Wayland session

2019-09-13 Thread Artyom Pozharov
Public bug reported:

Eyes are very tired because of this

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 69.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BuildID: 2019091951
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 14 00:28:29 2019
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
DefaultProfileThemes: extensions.sqlite corrupt or missing
InstallationDate: Installed on 2019-09-09 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=69.0/2019091951 (In use)
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan wayland-session

** Attachment added: "2019-09-14 00:27:46.269816.webm"
   
https://bugs.launchpad.net/bugs/1843955/+attachment/5288553/+files/2019-09-14%2000%3A27%3A46.269816.webm

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

Title:
  Black zones in context menu appears  in Firefox when I use GNOME on
  Wayland session

Status in firefox package in Ubuntu:
  New

Bug description:
  Eyes are very tired because of this

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 2019091951
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 00:28:29 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/2019091951 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1843948] Re: Artifacts appear when I watch video in Youtube

2019-09-13 Thread Artyom Pozharov
** Summary changed:

- Artifacts appears when I watch video in Youtube 
+ Artifacts appear when I watch video in Youtube

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

Title:
  Artifacts appear when I watch video in Youtube

Status in firefox package in Ubuntu:
  New

Bug description:
  Only with GNOME on Wayland session with Firefox

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 2019091951
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 23:37:25 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/2019091951 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1839030] Re: Artifacts appear when Chromium app is un-maximizing

2019-09-13 Thread Artyom Pozharov
** Summary changed:

- Artifacts appears when Chromium app is un-maximizing
+ Artifacts appear when Chromium app is un-maximizing

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

Title:
  Artifacts appear when Chromium app is un-maximizing

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Details here: https://photos.app.goo.gl/ummEcpamq3yYA7p38
  Device: Ubuntu 19.10 on Wayland (last build for 5 August 2019), HP 250 G6 
Notebook, Celeron N3350 (Apollo Lake), Intel HD 500.

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

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


[Desktop-packages] [Bug 1843952] [NEW] Artifacts appear when I un-maximize Chromium or Firefox windows

2019-09-13 Thread Artyom Pozharov
Public bug reported:

It's GNOME on Wayland bug.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: mutter 3.34.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 14 00:13:57 2019
InstallationDate: Installed on 2019-09-09 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan wayland-session

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

Title:
  Artifacts appear when I un-maximize Chromium or Firefox windows

Status in mutter package in Ubuntu:
  New

Bug description:
  It's GNOME on Wayland bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 00:13:57 2019
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1520033] Re: ftbfs on s390x

2019-09-13 Thread Timotheus Pokorra
Is this an ancient bug and should be closed? or is it ok to reuse this
bug report?

It used to build for
https://launchpad.net/ubuntu/+source/mono/5.18.0.240+dfsg-3/+build/17185141,
but now it does not anymore:
https://launchpad.net/ubuntu/+source/mono/5.18.0.240+dfsg-5/+build/17750817

One difference is gcc-8 vs gcc-9.

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

Title:
  ftbfs on s390x

Status in mono package in Ubuntu:
  Confirmed

Bug description:
  ftbfs on s390x

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

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


[Desktop-packages] [Bug 1843499] Re: [eoan] Wayland session misses non-GNOME apps theming

2019-09-13 Thread Francois Thirioux
solved with 3.34.0.2 Mutter update

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [eoan] Wayland session misses non-GNOME apps theming

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  Running GS 3.34 from proposed (or 3.33.92 too), the GNOME or Ubuntu
  sessions miss non-GNOME apps theming. I use Adwaita, it runs Yaru (if
  installed...) and picks up wrong fonts. Examples of such apps :
  wxMaxima, Thunderbird, Firefox.

  Running X session, all is fine. But here too there's something fishy :
  when I switch from a Wayland session to a X session, the first login
  sees Synaptic tell me that I run a Wayland session and that I cannot
  apply changes (etc.). The consecutively second login in a X session
  does not experience this bug.

  This behaviour began with 3.33.92 updates of gdm, gnome-session and
  gnome-settings-daemon some days ago. Upstream GNOME bugs tells me to
  report in Ubuntu bugs.

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

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


[Desktop-packages] [Bug 1843948] Re: Artifacts appears when I watch video in Youtube

2019-09-13 Thread Artyom Pozharov
** Attachment added: "Screenshot.png"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843948/+attachment/5288548/+files/Screenshot.png

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

Title:
  Artifacts appears when I watch video in Youtube

Status in firefox package in Ubuntu:
  New

Bug description:
  Only with GNOME on Wayland session with Firefox

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 2019091951
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 23:37:25 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/2019091951 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1843948] [NEW] Artifacts appears when I watch video in Youtube

2019-09-13 Thread Artyom Pozharov
Public bug reported:

Only with GNOME on Wayland session with Firefox

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 69.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
BuildID: 2019091951
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 13 23:37:25 2019
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
DefaultProfileThemes: extensions.sqlite corrupt or missing
InstallationDate: Installed on 2019-09-09 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=69.0/2019091951 (In use)
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan wayland-session

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

Title:
  Artifacts appears when I watch video in Youtube

Status in firefox package in Ubuntu:
  New

Bug description:
  Only with GNOME on Wayland session with Firefox

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 2019091951
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 23:37:25 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-09-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0/2019091951 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Dimitri John Ledkov
@laney

in that case the wallpaper background should too be centered and zoomed
on the 'content area', especially if such concept / area exists.

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

Title:
  gnome-shell calendar widget is not centered on the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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


[Desktop-packages] [Bug 1843744] Re: libdbusmenu ftbfs in eoan

2019-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package libdbusmenu -
16.04.1+18.10.20180917-0ubuntu2

---
libdbusmenu (16.04.1+18.10.20180917-0ubuntu2) eoan; urgency=medium

  * Build without Werror to fix the build with the new glib (lp:
#1843744)

 -- Sebastien Bacher   Fri, 13 Sep 2019 18:53:16
+0200

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

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

Title:
  libdbusmenu ftbfs in eoan

Status in libdbusmenu package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/441262368/buildlog_ubuntu-eoan-
  amd64.libdbusmenu_16.04.1+18.10.20180917-0ubuntu1_BUILDING.txt.gz

  /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../../libdbusmenu-glib -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  -Wall -Werror 
-Wno-error=deprecated-declarations -DG_LOG_DOMAIN="\"LIBDBUSMENU-GLIB\"" -g -O2 
-fdebug-prefix-map=/<>/libdbusmenu-16.04.1+18.10.20180917=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libdbusmenu_glib_la-defaults.lo `test -f 'defaults.c' || echo 
'../../../libdbusmenu-glib/'`defaults.c
  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../libdbusmenu-glib -I.. 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall -Werror 
-Wno-error=deprecated-declarations -DG_LOG_DOMAIN=\"LIBDBUSMENU-GLIB\" -g -O2 
-fdebug-prefix-map=/<>/libdbusmenu-16.04.1+18.10.20180917=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
../../../libdbusmenu-glib/defaults.c  -fPIC -DPIC -o 
.libs/libdbusmenu_glib_la-defaults.o
  ../../../libdbusmenu-glib/defaults.c: In function 
‘dbusmenu_defaults_class_init’:
  ../../../libdbusmenu-glib/defaults.c:67:2: warning: 
‘g_type_class_add_private’ is deprecated [-Wdeprecated-declarations]
 67 |  g_type_class_add_private (klass, sizeof (DbusmenuDefaultsPrivate));
|  ^~~~
  In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
   from /usr/include/glib-2.0/gobject/gbinding.h:29,
   from /usr/include/glib-2.0/glib-object.h:23,
   from ../../../libdbusmenu-glib/defaults.h:33,
   from ../../../libdbusmenu-glib/defaults.c:35:
  /usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here
   1308 | void g_type_class_add_private   (gpointer
g_class,
|  ^~~~
  ../../../libdbusmenu-glib/defaults.c: In function ‘dbusmenu_defaults_init’:
  ../../../libdbusmenu-glib/defaults.c:77:13: error: G_ADD_PRIVATE [-Werror]
 77 |  self->priv = DBUSMENU_DEFAULTS_GET_PRIVATE(self);
| ^~~
  cc1: all warnings being treated as errors
  make[5]: *** [Makefile:712: libdbusmenu_glib_la-defaults.lo] Error 1

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

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


[Desktop-packages] [Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34

2019-09-13 Thread Mario Vukelic
Sorry, "appear *behind* the Ubuntu dock" the

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

Title:
  Extensions don't load in gnome-shell 3.33/3.34

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Some extensions don't load in gnome-shell 3.33/3.34

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

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


[Desktop-packages] [Bug 1843798] Re: 19.10 Eoan default wallpapers

2019-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-wallpapers - 19.10.1-0ubuntu1

---
ubuntu-wallpapers (19.10.1-0ubuntu1) eoan; urgency=medium

  * New default wallpapers for disco (LP: #1843798).
+ This time the PNG is a PNG!
+ Once more there we don't contest wallpapers yet, so no
  ubuntu-wallpapers-eoan package is being created at this point. The
  greyscale wallpaper is being included in ubuntu-wallpapers itself for
  now and it'll move over later.

 -- Iain Lane   Fri, 13 Sep 2019 17:18:58 +0100

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  19.10 Eoan default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released

Bug description:
  Attached will be the Eoan default wallpapers.

  One in colour, one in black and white.  Both 4096 x 2304.

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

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


[Desktop-packages] [Bug 1835706] Re: Extensions don't load in gnome-shell 3.33/3.34

2019-09-13 Thread Mario Vukelic
gnome-shell-extension-workspaces-to-dock
universe, version: 51-1

When active, the Activities and Application menus stop working, incl.
Super key. In addition the window management breaks, windows appear
being the Ubuntu dock.

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

Title:
  Extensions don't load in gnome-shell 3.33/3.34

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Some extensions don't load in gnome-shell 3.33/3.34

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

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


[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

2019-09-13 Thread satmandu
I'm still seeing this issue on resume from sleep today on my updated
19.10 setup with gnome-shell 3.34.0-1ubuntu1.

For what it is worth I also see this in my dmesg at boot:

[   19.404177] gnome-shell[3485]: segfault at 18 ip 7f82407d4924 sp 
7ffeb4e50f08 error 4 in libmutter-5.so.0.0.0[7f82406e7000+f2000]
[   19.404192] Code: c3 0f 1f 44 00 00 f3 0f 1e fa 8b 47 30 c3 0f 1f 84 00 00 
00 00 00 f3 0f 1e fa 8b 47 34 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 47 
18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 41 54 53 48 89 fb

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Confirmed
Status in mutter source package in Disco:
  In Progress
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  

[Desktop-packages] [Bug 1843798] Re: 19.10 Eoan default wallpapers

2019-09-13 Thread Dilip
Beautiful.

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

Title:
  19.10 Eoan default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  Attached will be the Eoan default wallpapers.

  One in colour, one in black and white.  Both 4096 x 2304.

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

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


[Desktop-packages] [Bug 1843798] Re: 19.10 Eoan default wallpapers

2019-09-13 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu-wallpapers

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

Title:
  19.10 Eoan default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  Attached will be the Eoan default wallpapers.

  One in colour, one in black and white.  Both 4096 x 2304.

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

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


[Desktop-packages] [Bug 1843914] Re: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()

2019-09-13 Thread Apport retracing service
*** This bug is a duplicate of bug 1841794 ***
https://bugs.launchpad.net/bugs/1841794

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 #1841794, 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/1843914/+attachment/5288502/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1841794
   gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from 
ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an 
already freed object of type: Clutter.PropertyTransition"]

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  a gnome-shell crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 15:01:15 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1568117632
  InstallationDate: Installed on 2014-07-15 (1886 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/j-lallement
  RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ObjectInstance::~ObjectInstance() () at /usr/lib/libgjs.so.0
   GIWrapperBase::finalize(JSFreeOp*, JSObject*) () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
  Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (538 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1843914] [NEW] gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()

2019-09-13 Thread Jean-Baptiste Lallement
Public bug reported:

a gnome-shell crash.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 13 15:01:15 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1568117632
InstallationDate: Installed on 2014-07-15 (1886 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/j-lallement
RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ObjectInstance::~ObjectInstance() () at /usr/lib/libgjs.so.0
 GIWrapperBase::finalize(JSFreeOp*, JSObject*) () at /usr/lib/libgjs.so.0
 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()
UpgradeStatus: Upgraded to eoan on 2018-03-24 (538 days ago)
UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo
separator:

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


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

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  a gnome-shell crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 15:01:15 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1568117632
  InstallationDate: Installed on 2014-07-15 (1886 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/j-lallement
  RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ObjectInstance::~ObjectInstance() () at /usr/lib/libgjs.so.0
   GIWrapperBase::finalize(JSFreeOp*, JSObject*) () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0
  Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (538 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Iain Lane
This is on purpose; the clock widget is centred with respect to the
'content area'.

So IMO -1 for this being a bug, and certainly -1 for a release critical
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/1843899

Title:
  gnome-shell calendar widget is not centered on the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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


[Desktop-packages] [Bug 1843912] [NEW] Update to 9.0.0 next cycle

2019-09-13 Thread Sebastien Bacher
Public bug reported:

The new version has feature and small incompatibilities
http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes%3E

** Affects: qpdf (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: upgrade-software-version version-blocked-ff

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

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

Title:
  Update to 9.0.0 next cycle

Status in qpdf package in Ubuntu:
  Triaged

Bug description:
  The new version has feature and small incompatibilities
  http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes%3E

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

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


[Desktop-packages] [Bug 1843910] [NEW] cannot add public (unauthenticated) web ics calendar

2019-09-13 Thread Jérémie Bouttier
Public bug reported:

I am trying to import a public agenda in Gnome Calendar, for instance :
  https://indico.math.cnrs.fr/export/categ/180.ics?from=-31d
When adding this URL in the Gnome Calendar settings, I am asked for credentials 
which should not be needed (wget or Firefox download the ics file just fine 
without them).

In fact, the same problem seems to have been already reported here :
https://askubuntu.com/questions/1100027/gnome-calendar-asks-credentials-for-public-ical
Someone suggests to use evolution as a workaround, but IMO this is still a bug 
of Gnome Calendar which is the default calendar for Ubuntu 18.04...

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 13 16:12:25 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-09-04 (9 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/zsh
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  cannot add public (unauthenticated) web ics calendar

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I am trying to import a public agenda in Gnome Calendar, for instance :
https://indico.math.cnrs.fr/export/categ/180.ics?from=-31d
  When adding this URL in the Gnome Calendar settings, I am asked for 
credentials which should not be needed (wget or Firefox download the ics file 
just fine without them).

  In fact, the same problem seems to have been already reported here :
  
https://askubuntu.com/questions/1100027/gnome-calendar-asks-credentials-for-public-ical
  Someone suggests to use evolution as a workaround, but IMO this is still a 
bug of Gnome Calendar which is the default calendar for Ubuntu 18.04...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 16:12:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-09-04 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/zsh
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

2019-09-13 Thread Sebastien Bacher
Marco says he has a fix for this one

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Confirmed => In Progress

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

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress

Bug description:
  Very recently the ubuntu-dock has started displaying some right-click
  menus for pinned apps on the wrong monitor. It doesn't happen for all
  the apps, but when it does, the menu is permanent but you can't click
  on it and you have to restart gnome-shell with ALT-F2 'r' (which now
  always kills some apps like firefox).

  See attached screenshot where the menu for gnome-tweaks has appeared
  at the top left of the top monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1
  Uname: Linux 5.3.0-050300rc8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 11:42:07 2019
  InstallationDate: Installed on 2019-07-01 (71 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1843750] Re: libsecret ftbfs in eoan

2019-09-13 Thread Sebastien Bacher
https://bugs.launchpad.net/ubuntu/+source/libsecret/0.18.8-2

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

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

Title:
  libsecret ftbfs in eoan

Status in libsecret package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/441262252/buildlog_ubuntu-eoan-
  amd64.libsecret_0.18.8-1_BUILDING.txt.gz

  
  Testsuite summary for libsecret 0.18.8
  
  # TOTAL: 198
  # PASS:  13
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  0
  # XPASS: 0
  # ERROR: 185
  ==

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

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


[Desktop-packages] [Bug 562130] Re: Selecting an RTL language should install RTL capable terminal emulator

2019-09-13 Thread Danial Behzadi
** Changed in: language-selector (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Selecting an RTL language should install RTL capable terminal emulator

Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: language-selector

  the default terminal gnome-terminal which is using vte is not able to
  display RTL text like Arabic,Farsi, Urdu or  Hebrew and it's a known
  bug that is not likly to be fixed at all as vte developer said. see
  bug #263822

  How ever Mlterm is ready to support variant of scripts including Arabic 
,Hebrew and even Chinese.
  see https://wiki.ubuntu.com/Mlterm

  problem:
  no terminal with RTL support

  fix:
  installing Mlterm for RTL by default

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: language-selector 0.5.4
  ProcVersionSignature: Ubuntu 2.6.32-20.29-generic-pae 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-20-generic-pae i686
  Architecture: i386
  CheckboxSubmission: 4190bdfb1b8df71969b6cbad70f1beb6
  CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4
  Date: Tue Apr 13 11:38:45 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100113)
  PackageArchitecture: all
  ProcEnviron:
   LANG=ar_SA.utf8
   SHELL=/bin/bash
  SourcePackage: language-selector

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/562130/+subscriptions

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


[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Will Cooke
** Tags added: rls-ff-incoming

** Tags removed: rls-ff-incoming
** Tags added: rls-ee-incoming

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

Title:
  gnome-shell calendar widget is not centered on the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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


[Desktop-packages] [Bug 1843750] Re: libsecret ftbfs in eoan

2019-09-13 Thread Sebastien Bacher
** Changed in: libsecret (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  libsecret ftbfs in eoan

Status in libsecret package in Ubuntu:
  Fix Committed

Bug description:
  https://launchpadlibrarian.net/441262252/buildlog_ubuntu-eoan-
  amd64.libsecret_0.18.8-1_BUILDING.txt.gz

  
  Testsuite summary for libsecret 0.18.8
  
  # TOTAL: 198
  # PASS:  13
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  0
  # XPASS: 0
  # ERROR: 185
  ==

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

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


[Desktop-packages] [Bug 1843895] Re: Unable to launch seahorse

2019-09-13 Thread Olivier Febwin
This issue occurs only on Xorg session (ubuntu 19.04).
No problem on Wayland session.

** Attachment added: "seahorse.txt"
   
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1843895/+attachment/5288498/+files/seahorse.txt

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

Title:
  Unable to launch seahorse

Status in seahorse package in Ubuntu:
  Incomplete

Bug description:
  When I try to run seahorse, I've these errors:

  (seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trappe pour point d'arrêt et de trace

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

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


[Desktop-packages] [Bug 1843796] Re: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available

2019-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-drivers-common - 1:0.7.6

---
ubuntu-drivers-common (1:0.7.6) eoan; urgency=medium

  [ Alberto Milone ]
  * gpu-manager.c:
- Drop prime_is_action_on() (now that it isn't on/off any more)
  and update the description.
  * UbuntuDrivers/detect.py,
UbuntuDrivers/kerneldetection.py,
tests/ubuntu_drivers.py,
ubuntu-drivers:
- Provide DKMS fallback for the "install --gpgpu" case
  when no linux-modules-nvidia are available for the driver
  and for a specific kernel (LP: #1843796).
  We have new tests to cover this scenario now.
- Show provider of kernel modules in list --gpgpu
- Fix linux metapackage detection.
  This was meant to be driven by the latest kernel version
  But it was only partially implemented.
  Complete the implementation and update the relevant tests.

  [ Daniel Dadap ]
  * gpu-manager.c:
- Enable power management in NVIDIA on-demand mode:
  The NVIDIA driver can suspend the GPU when it's being used as a
  PRIME render offload source and it isn't actively being used.
  disable_power_management() sets the NVIDIA GPU's power/control
  mode to "on", which prevents the GPU from suspending when it
  might otherwise be possible to do so.
- Increase string storage on stack for path names. This fixes
  the warnings that gcc emits when building up path names.

 -- Alberto Milone   Fri, 13 Sep 2019
12:38:45 +0200

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ubuntu-drivers install --gpgpu should use a DKMS fallback when no
  linux-modules-nvidia package is available

Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-drivers install --gpgpu should use a DKMS fallback when no
  linux-modules-nvidia package is available.

  Currently, we do not deal with this kind of failure i.e. when no
  linux-modules-nvidia package is available for the kernel in use. If no
  such package can be found, we need to at least attempt installing the
  relevant DKMS package, so that users get the required kernel modules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1843796/+subscriptions

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


[Desktop-packages] [Bug 1843895] Re: Unable to launch seahorse

2019-09-13 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

Before using gdb do '$ export GDK_SYNCHRONIZE=1'

What version of Ubuntu are you using

** No longer affects: xorg (Ubuntu)

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

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

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

Title:
  Unable to launch seahorse

Status in seahorse package in Ubuntu:
  Incomplete

Bug description:
  When I try to run seahorse, I've these errors:

  (seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trappe pour point d'arrêt et de trace

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

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


[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Dimitri John Ledkov
With help from willcooke, it seems that the dock pushes the calendar to
be centered on the space between the dock right edge and the right edge
of the screen, when dock has "auto-hide" setting turned off.

With auto-hide on, calendar widget is correctly centered.

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

Title:
  gnome-shell calendar widget is not centered on the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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


[Desktop-packages] [Bug 1843895] Re: Unable to launch seahorse

2019-09-13 Thread Olivier Febwin
This issue occurs only on Xorg session (ubuntu 19.04). 
No problem on Wayland session.

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

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

Title:
  Unable to launch seahorse

Status in seahorse package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  When I try to run seahorse, I've these errors:

  (seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trappe pour point d'arrêt et de trace

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

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


[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Dimitri John Ledkov
** Description changed:

  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.
  
- It feels as if it is centered, between "right edge of the app menu" and
- "left edge of the top right indicators", instead of centered to the
- screen width.
+ It feels as if it is centered, with an offset / margin on the left.
  
- The blue line on the screenshot is the centre fold of the screen, you
- can see that the wallpaper is correctly centered with the animal circle
- in the centre.
+ between "right edge of the app menu" and "left edge of the top right
+ indicators", instead of centered to the screen width.The blue line on
+ the screenshot is the centre fold of the screen, you can see that the
+ wallpaper is correctly centered with the animal circle in the centre.

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

Title:
  gnome-shell calendar widget is not centered on the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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


[Desktop-packages] [Bug 1843798] Re: 19.10 Eoan default wallpapers

2019-09-13 Thread Will Cooke
Emailed docs team for UIFe

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

Title:
  19.10 Eoan default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  Attached will be the Eoan default wallpapers.

  One in colour, one in black and white.  Both 4096 x 2304.

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

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


[Desktop-packages] [Bug 1843899] [NEW] gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Dimitri John Ledkov
Public bug reported:

With the new eoan wallpaper it is obvious that calendar widget, is not
in fact, centered on the screen. Nor is like left/right aligned to the
centre either.

It feels as if it is centered, with an offset / margin on the left.

between "right edge of the app menu" and "left edge of the top right
indicators", instead of centered to the screen width.The blue line on
the screenshot is the centre fold of the screen, you can see that the
wallpaper is correctly centered with the animal circle in the centre.

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

** Attachment added: "gnome-shell-calendar.png"
   
https://bugs.launchpad.net/bugs/1843899/+attachment/5288494/+files/gnome-shell-calendar.png

** Description changed:

  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.
  
  It feels as if it is centered, between "right edge of the app menu" and
  "left edge of the top right indicators", instead of centered to the
  screen width.
+ 
+ The blue line on the screenshot is the centre fold of the screen, you
+ can see that the wallpaper is correctly centered with the animal circle
+ in the centre.

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

Title:
  gnome-shell calendar widget is not centered on the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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


[Desktop-packages] [Bug 1843798] Re: 19.10 Eoan default wallpapers

2019-09-13 Thread Dimitri John Ledkov
** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-wallpapers (Ubuntu)
   Importance: Undecided => High

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

Title:
  19.10 Eoan default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  Attached will be the Eoan default wallpapers.

  One in colour, one in black and white.  Both 4096 x 2304.

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

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


[Desktop-packages] [Bug 1843895] [NEW] Unable to launch seahorse

2019-09-13 Thread Olivier Febwin
Public bug reported:

When I try to run seahorse, I've these errors:

(seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received 
an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trappe pour point d'arrêt et de trace

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

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

Title:
  Unable to launch seahorse

Status in seahorse package in Ubuntu:
  New

Bug description:
  When I try to run seahorse, I've these errors:

  (seahorse:11732): Gdk-ERROR **: 14:45:20.702: The program 'seahorse' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1008 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trappe pour point d'arrêt et de trace

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

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


[Desktop-packages] [Bug 1842256] Re: ~/.pam_environment overridden by /etc/default/locale

2019-09-13 Thread Gunnar Hjalmarsson
I can't reproduce this with gdm3 3.34.0-1ubuntu1. Something seems to
have happened. Possibly this:

https://gitlab.gnome.org/GNOME/gdm/merge_requests/82

But I don't really know. Still closing this bug.

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

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

** Changed in: gdm3 (Ubuntu Eoan)
 Assignee: Olivier Tilloy (osomon) => (unassigned)

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

Title:
  ~/.pam_environment overridden by /etc/default/locale

Status in gdm3 package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Invalid

Bug description:
  Bug #1662031 has resurrected. The patch dont_set_language_env.patch,
  which fixed it last time, is still there, but it seems not to be
  sufficient in 3.33.90.

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

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


[Desktop-packages] [Bug 562130] Re: Selecting an RTL language should install RTL capable terminal emulator

2019-09-13 Thread Egmont Koblinger
GNOME Terminal 3.34 (as well as all other terminals using VTE 0.58)
support RTL.

These versions appear in Ubuntu 19.10 Eoan Ermine.

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

Title:
  Selecting an RTL language should install RTL capable terminal emulator

Status in language-selector package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: language-selector

  the default terminal gnome-terminal which is using vte is not able to
  display RTL text like Arabic,Farsi, Urdu or  Hebrew and it's a known
  bug that is not likly to be fixed at all as vte developer said. see
  bug #263822

  How ever Mlterm is ready to support variant of scripts including Arabic 
,Hebrew and even Chinese.
  see https://wiki.ubuntu.com/Mlterm

  problem:
  no terminal with RTL support

  fix:
  installing Mlterm for RTL by default

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: language-selector 0.5.4
  ProcVersionSignature: Ubuntu 2.6.32-20.29-generic-pae 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-20-generic-pae i686
  Architecture: i386
  CheckboxSubmission: 4190bdfb1b8df71969b6cbad70f1beb6
  CheckboxSystem: 9c26adf6eed2f681ba41f94dd24c07e4
  Date: Tue Apr 13 11:38:45 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100113)
  PackageArchitecture: all
  ProcEnviron:
   LANG=ar_SA.utf8
   SHELL=/bin/bash
  SourcePackage: language-selector

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/562130/+subscriptions

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


[Desktop-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()

2019-09-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/evolution/issues/616

  ---

  I don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:41:26 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2018-12-02 (282 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f36355653ae) ok
   source "(%r8)" (0x7f36) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=32) at malloc.c:3051
   g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Desktop-packages] [Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

2019-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package mutter - 3.34.0-2ubuntu1

---
mutter (3.34.0-2ubuntu1) eoan; urgency=medium

  * Merge with debian. Remaining changes:
+ debian/control:
  - Update VCS flags to point to launchpad
  - Update maintainer to ubuntu
+ debian/gbp.conf: update branch to point to ubuntu/master
+ debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

mutter (3.34.0-2) experimental; urgency=medium

  * d/p/core-Split-x11-display-initialization-in-2-signals.patch: Cherry-pick.
Fixes starting up of gsd-xsettings on Wayland. (LP: #1843107)

 -- Iain Lane   Fri, 13 Sep 2019 11:13:49 +0100

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

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in Mutter:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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


[Desktop-packages] [Bug 721786] Re: (Non-overlay) scroll-bar lacks sufficient contrast to easily identify its position in the scroll-track

2019-09-13 Thread Will Cooke
** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  (Non-overlay) scroll-bar lacks sufficient contrast to easily identify
  its position in the scroll-track

Status in Ayatana Design:
  Fix Committed
Status in One Hundred Papercuts:
  Fix Released
Status in Ubuntu MATE:
  Won't Fix
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: gnome-session

  The scroll-bars that appear on the right-side and bottom of gnome
  windows lack sufficient contrast to the scroll-track. I have
  difficulty identifying where in the scroll-track the bar is
  positioned. I often mistake the background of the scroll-track as the
  scroll-bar itself. I'm using Inverted Control theme. More contrast and
  better color separation is needed here.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-session-bin 2.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic i686
  Architecture: i386
  Date: Sat Feb 19 09:19:22 2011
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  ProcEnviron:
   LC_TIME=en_GB.UTF-8
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  XsessionErrors: (polkit-gnome-authentication-agent-1:1387): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/721786/+subscriptions

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


[Desktop-packages] [Bug 1843798] Re: 19.10 Eoan default wallpapers

2019-09-13 Thread Will Cooke
** Attachment added: "19.10_eaon_ermine_default_wallpaper.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1843798/+attachment/5288488/+files/19.10_eaon_ermine_default_wallpaper.tar.xz

** Changed in: ubuntu-wallpapers (Ubuntu)
 Assignee: Will Cooke (willcooke) => (unassigned)

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

Title:
  19.10 Eoan default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Attached will be the Eoan default wallpapers.

  One in colour, one in black and white.  Both 4096 x 2304.

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

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


[Desktop-packages] [Bug 1843737] Re: gnome-keyring ftbfs in eoan

2019-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-keyring - 3.31.91-1ubuntu3

---
gnome-keyring (3.31.91-1ubuntu3) eoan; urgency=medium

  * Backport some test fixes from Debian (lp: #1843737)

  [ Simon McVittie ]
  * d/p/test-gkd-ssh-agent-service-Avoid-race-condition-with-serv.patch:
Add proposed patch to avoid a race condition that can result in the
tests hanging, which seems to be particularly likely on a
single-CPU machine (Closes: #909416)
  * d/p/Remove-tap-gtester-rely-on-GLib-2.38-built-in-TAP-output-.patch:
Fix FTBFS with GLib 2.62+ (Closes: #940157)

 -- Sebastien Bacher   Fri, 13 Sep 2019 11:56:17
+0200

** Changed in: gnome-keyring (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-keyring ftbfs in eoan

Status in gnome-keyring package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/441262649/buildlog_ubuntu-eoan-amd64
  .gnome-keyring_3.31.91-1ubuntu2_BUILDING.txt.gz

  Testsuite summary for gnome-keyring 3.31.91
  
  # TOTAL: 636
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  0
  # XPASS: 0
  # ERROR: 636
  ===

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

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


[Desktop-packages] [Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

2019-09-13 Thread Iain Lane
Taken that patch, thanks!

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in Mutter:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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


[Desktop-packages] [Bug 1843740] Re: indicator-messages ftbfs in eoan

2019-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package indicator-messages -
13.10.1+18.10.20180918-0ubuntu2

---
indicator-messages (13.10.1+18.10.20180918-0ubuntu2) eoan; urgency=medium

  * src/im-accounts-service.c, src/indicator-desktop-shortcuts.c:
- don't use deprecated g_type_class_add_private, fix the build with the
  current libglib version (lp: #1843740)

 -- Sebastien Bacher   Fri, 13 Sep 2019 11:30:08
+0200

** Changed in: indicator-messages (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  indicator-messages ftbfs in eoan

Status in indicator-messages package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/441262676/buildlog_ubuntu-eoan-amd64
  .indicator-messages_13.10.1+18.10.20180918-0ubuntu1_BUILDING.txt.gz

  gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/accountsservice-1.0  -I../common -Wall -Wl,-Bsymbolic-functions 
-Wl,-z,defs -Wl,--as-needed -Werror -Wno-error=deprecated-declarations 
-DG_LOG_DOMAIN=\"Indicator-Messages\" -g -O2 
-fdebug-prefix-map=/<>/indicator-messages-13.10.1+18.10.20180918=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
indicator_messages_service-im-accounts-service.o `test -f 
'im-accounts-service.c' || echo './'`im-accounts-service.c
  im-accounts-service.c: In function ‘im_accounts_service_class_init’:
  im-accounts-service.c:54:2: warning: ‘g_type_class_add_private’ is deprecated 
[-Wdeprecated-declarations]
 54 |  g_type_class_add_private (klass, sizeof (ImAccountsServicePrivate));
|  ^~~~
  In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
   from /usr/include/glib-2.0/gobject/gbinding.h:29,
   from /usr/include/glib-2.0/glib-object.h:23,
   from 
/usr/include/accountsservice-1.0/act/act-user-enum-types.h:7,
   from /usr/include/accountsservice-1.0/act/act.h:24,
   from im-accounts-service.c:24:
  /usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here
   1308 | void g_type_class_add_private   (gpointer
g_class,
|  ^~~~
  im-accounts-service.c: In function ‘im_accounts_service_init’:
  im-accounts-service.c:63:13: error: G_ADD_PRIVATE [-Werror]
 63 |  ImAccountsServicePrivate * priv = 
IM_ACCOUNTS_SERVICE_GET_PRIVATE(self);
| ^~~
  im-accounts-service.c: In function ‘im_accounts_service_dispose’:
  im-accounts-service.c:81:13: error: G_ADD_PRIVATE [-Werror]
 81 |  ImAccountsServicePrivate * priv = 
IM_ACCOUNTS_SERVICE_GET_PRIVATE(object);
| ^~~
  im-accounts-service.c: In function ‘user_changed’:
  im-accounts-service.c:107:13: error: G_ADD_PRIVATE [-Werror]
107 |  ImAccountsServicePrivate * priv = 
IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data);
| ^~~
  im-accounts-service.c: In function ‘security_privacy_ready’:
  im-accounts-service.c:138:13: error: G_ADD_PRIVATE [-Werror]
138 |  ImAccountsServicePrivate * priv = 
IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data);
| ^~~
  im-accounts-service.c: In function ‘on_user_manager_loaded’:
  im-accounts-service.c:149:13: error: G_ADD_PRIVATE [-Werror]
149 |  ImAccountsServicePrivate * priv = 
IM_ACCOUNTS_SERVICE_GET_PRIVATE(user_data);
| ^~~
  im-accounts-service.c: In function ‘im_accounts_service_set_draws_attention’:
  im-accounts-service.c:183:13: error: G_ADD_PRIVATE [-Werror]
183 |  ImAccountsServicePrivate * priv = 
IM_ACCOUNTS_SERVICE_GET_PRIVATE(service);
| ^~~
  im-accounts-service.c: In function ‘im_accounts_service_get_show_on_greeter’:
  im-accounts-service.c:209:13: error: G_ADD_PRIVATE [-Werror]
209 |  ImAccountsServicePrivate * priv = 
IM_ACCOUNTS_SERVICE_GET_PRIVATE(service);
| ^~~
  cc1: all warnings being treated as errors
  make[3]: *** [Makefile:622: indicator_messages_service-im-accounts-service.o] 
Error 1
  make[3]: Leaving directory 
'/<>/indicator-messages-13.10.1+18.10.20180918/src'
  make[2]: *** [Makefile:491: all-recursive] Error 1
  make[2]: Leaving directory 
'/<>/indicator-messages-13.10.1+18.10.20180918'
  make[1]: *** [Makefile:422: all] Error 2
  make[1]: Leaving directory 
'/<>/indicator-messages-13.10.1+18.10.20180918'
  dh_auto_build: make -j1 returned exit code 2
  make: *** [debian/rules:6: build] Error 255
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

To manage notifications about 

[Desktop-packages] [Bug 1843737] Re: gnome-keyring ftbfs in eoan

2019-09-13 Thread Sebastien Bacher
** Changed in: gnome-keyring (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  gnome-keyring ftbfs in eoan

Status in gnome-keyring package in Ubuntu:
  Fix Committed

Bug description:
  https://launchpadlibrarian.net/441262649/buildlog_ubuntu-eoan-amd64
  .gnome-keyring_3.31.91-1ubuntu2_BUILDING.txt.gz

  Testsuite summary for gnome-keyring 3.31.91
  
  # TOTAL: 636
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  0
  # XPASS: 0
  # ERROR: 636
  ===

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

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


[Desktop-packages] [Bug 1843878] Re: /org/gnome/desktop/wm/preferences/button-layout not being respected after alt-f2 r enter

2019-09-13 Thread shemgp
Just a follow up: running gsettings set org.gnome.desktop.wm.preferences
button-layout 'close,minimize,maximize:appmenu' does nothing.

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

Title:
  /org/gnome/desktop/wm/preferences/button-layout not being respected
  after alt-f2 r enter

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When pressing alt-f2 r enter, the /org/gnome/desktop/wm/preferences
  /button-layout is not being respected. I've set it to:
  close,minimize,maximize:appmenu, but the buttons go to the right.
  When I start gnome-shell from gdm3, the buttons are left as expected.
  Only when I refresh or kill gnome-shell do they go to the right.

  Thank you for looking into this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 13 17:51:54 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1445 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-07-26 (48 days ago)

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

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


[Desktop-packages] [Bug 1843872] Re: libexec migration incomplete

2019-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-terminal - 3.34.0-1ubuntu2

---
gnome-terminal (3.34.0-1ubuntu2) eoan; urgency=medium

  * gnome-terminal.wrap: Update gnome-terminal-server path for libexec
migration (LP: #1843872)

 -- Iain Lane   Fri, 13 Sep 2019 09:43:11 +0100

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Fix Released

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

Title:
  libexec migration incomplete

Status in gnome-terminal package in Ubuntu:
  Fix Released

Bug description:
  Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary
  from /usr/lib/gnome-terminal to /usr/libexec.

  The Ubuntu package ships a wrapper script as /usr/bin/gnome-terminal.
  This one still looks for the server at its old location in
  spawn_terminal_server().

  It's unclear to me what this wrapper script exactly does, and how/why
  it still manages to successfully start up gnome-terminal (probably in
  a different way than it intends to).

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

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


[Desktop-packages] [Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

2019-09-13 Thread Iain Lane
** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Invalid

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

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in Mutter:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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


[Desktop-packages] [Bug 1843878] [NEW] /org/gnome/desktop/wm/preferences/button-layout not being respected after alt-f2 r enter

2019-09-13 Thread shemgp
Public bug reported:

When pressing alt-f2 r enter, the /org/gnome/desktop/wm/preferences
/button-layout is not being respected. I've set it to:
close,minimize,maximize:appmenu, but the buttons go to the right.  When
I start gnome-shell from gdm3, the buttons are left as expected. Only
when I refresh or kill gnome-shell do they go to the right.

Thank you for looking into this bug.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Sep 13 17:51:54 2019
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (1445 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-07-26 (48 days ago)

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


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

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

Title:
  /org/gnome/desktop/wm/preferences/button-layout not being respected
  after alt-f2 r enter

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When pressing alt-f2 r enter, the /org/gnome/desktop/wm/preferences
  /button-layout is not being respected. I've set it to:
  close,minimize,maximize:appmenu, but the buttons go to the right.
  When I start gnome-shell from gdm3, the buttons are left as expected.
  Only when I refresh or kill gnome-shell do they go to the right.

  Thank you for looking into this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep 13 17:51:54 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1445 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions: mutter-common 3.34.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-07-26 (48 days ago)

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

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


[Desktop-packages] [Bug 1843880] [NEW] GtkSpinButton's context menu changes the width of '+'

2019-09-13 Thread Egmont Koblinger
Public bug reported:

GtkSpinButton consists of a (typically numeric) input field, followed by
a '-' and finally a '+' sign. The width of the '+' sign shrinks a little
bit when you open the right-click context menu of the input field. It
shouldn't, it should have a constant width.

Happens with Ubuntu's old default Ambiance and Radiance themes. Does not
happen with Ubuntu's new default Yaru, or with GTK's default Adwaita.

Example: Open gnome-terminal, right click on its terminal canvas, choose
Preferences. You're taken to the profile's Text tab which contains four
such widgets. Right-click on one of these input fields, e.g. on "80" for
the initial number of columns. In addition to the context menu
appearing, the '+' button becomes narrower, and thus the label on its
right (e.g. "columns") shifts to the left. For some of the spinbuttons
(the ones that stretch the window) the entire window also shrinks.
Dismiss the context menu and it goes back to its previous width.

(This is similar to former bug 1740709.)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: light-themes 19.04-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Fri Sep 13 11:48:51 2019
InstallationDate: Installed on 2016-11-09 (1037 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to eoan on 2019-09-08 (4 days ago)

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan visual-quality

** Tags added: visual-quality

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

Title:
  GtkSpinButton's context menu changes the width of '+'

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  GtkSpinButton consists of a (typically numeric) input field, followed
  by a '-' and finally a '+' sign. The width of the '+' sign shrinks a
  little bit when you open the right-click context menu of the input
  field. It shouldn't, it should have a constant width.

  Happens with Ubuntu's old default Ambiance and Radiance themes. Does
  not happen with Ubuntu's new default Yaru, or with GTK's default
  Adwaita.

  Example: Open gnome-terminal, right click on its terminal canvas,
  choose Preferences. You're taken to the profile's Text tab which
  contains four such widgets. Right-click on one of these input fields,
  e.g. on "80" for the initial number of columns. In addition to the
  context menu appearing, the '+' button becomes narrower, and thus the
  label on its right (e.g. "columns") shifts to the left. For some of
  the spinbuttons (the ones that stretch the window) the entire window
  also shrinks. Dismiss the context menu and it goes back to its
  previous width.

  (This is similar to former bug 1740709.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: light-themes 19.04-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Sep 13 11:48:51 2019
  InstallationDate: Installed on 2016-11-09 (1037 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to eoan on 2019-09-08 (4 days ago)

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

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


[Desktop-packages] [Bug 1843872] Re: libexec migration incomplete

2019-09-13 Thread Egmont Koblinger
> What the script does, since you ask,

Sorry for the loose phrasing. I was aware of the global picture, just
wasn't sure (and was lazy to investigate) when exactly a bug would be
triggered, i.e. when that code would be reached, which you answered:

> It is broken if you pass --app-id

Thanks for the libexec migration by the way, it's one less thing for me
to worry about (Ubuntu doing something differently than mainstream, and
if I forget to pass --libexec= then I end up with a server here and a
server there and who knows if the right one is started up, it's a source
of all kinds of confusions... you must know the feeling. Anyway, it's
probably just me, most users don't care about this change :)

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

Title:
  libexec migration incomplete

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary
  from /usr/lib/gnome-terminal to /usr/libexec.

  The Ubuntu package ships a wrapper script as /usr/bin/gnome-terminal.
  This one still looks for the server at its old location in
  spawn_terminal_server().

  It's unclear to me what this wrapper script exactly does, and how/why
  it still manages to successfully start up gnome-terminal (probably in
  a different way than it intends to).

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

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


[Desktop-packages] [Bug 1843872] Re: libexec migration incomplete

2019-09-13 Thread Iain Lane
Right, thanks. It is broken if you pass --app-id. I fixed that last
night, but I went to bed before testing it :-). What the script does,
since you ask, is restore some options that were dropped several
releases ago, and broke lots of peoples' desktop launchers. I complained
loudly at the time but I couldn't get traction on having them
reinstated, so we carry this wrapper to keep compatibility.

https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/gnome-
terminal/commit/?id=b88cca55ea6380e8e7e916d2649508fdcd7b9b7b

Going to upload that in a minute, thanks again for the report.

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

Title:
  libexec migration incomplete

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary
  from /usr/lib/gnome-terminal to /usr/libexec.

  The Ubuntu package ships a wrapper script as /usr/bin/gnome-terminal.
  This one still looks for the server at its old location in
  spawn_terminal_server().

  It's unclear to me what this wrapper script exactly does, and how/why
  it still manages to successfully start up gnome-terminal (probably in
  a different way than it intends to).

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

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


[Desktop-packages] [Bug 1843736] Re: gnome-initial-setup ftbfs in eoan

2019-09-13 Thread Iain Lane
https://launchpad.net/ubuntu/+source/gnome-initial-setup/3.34.0-1ubuntu1

This build was done a while ago, before cheese 3.33.90.1-2.

** Changed in: gnome-initial-setup (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gnome-initial-setup ftbfs in eoan

Status in gnome-initial-setup package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/441262595/buildlog_ubuntu-eoan-amd64
  .gnome-initial-setup_3.33.91-1ubuntu2_BUILDING.txt.gz

  
  Could not generate cargs for cheese:

  
  CMake binary for MachineChoice.HOST is not cached
  CMake binary missing from cross or native file, or env var undefined.
  Trying a default CMake fallback at cmake
  Trying CMake binary cmake for machine MachineChoice.HOST at [None]
  Did not find CMake 'cmake'
  Found CMake: NO
  No CMake binary for machine MachineChoice.HOST not found. Giving up.
  Run-time dependency cheese found: NO 

  meson.build:47:0: ERROR: Could not generate cargs for cheese:

  
  dh_auto_configure: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled 
-Dsoftware-sources=disabled 
-Dvendor-conf-file=/usr/lib/gnome-initial-setup/vendor.conf returned exit code 1

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

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


[Desktop-packages] [Bug 1843872] [NEW] libexec migration incomplete

2019-09-13 Thread Egmont Koblinger
Public bug reported:

Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary
from /usr/lib/gnome-terminal to /usr/libexec.

The Ubuntu package ships a wrapper script as /usr/bin/gnome-terminal.
This one still looks for the server at its old location in
spawn_terminal_server().

It's unclear to me what this wrapper script exactly does, and how/why it
still manages to successfully start up gnome-terminal (probably in a
different way than it intends to).

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

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

Title:
  libexec migration incomplete

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Debian/Ubuntu package of gnome-terminal 3.34.0 moved the server binary
  from /usr/lib/gnome-terminal to /usr/libexec.

  The Ubuntu package ships a wrapper script as /usr/bin/gnome-terminal.
  This one still looks for the server at its old location in
  spawn_terminal_server().

  It's unclear to me what this wrapper script exactly does, and how/why
  it still manages to successfully start up gnome-terminal (probably in
  a different way than it intends to).

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

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


[Desktop-packages] [Bug 1843869] Re: System crashes randomly each time with different application

2019-09-13 Thread Sreeram P A
** Package changed: linux-signed-hwe (Ubuntu) => xorg (Ubuntu)

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

Title:
  System crashes randomly each time with different application

Status in xorg package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  Package version: 7.7+13ubuntu3.1

  Fresh system install with Ubuntu 16.04 crashes the system after some
  time. We are running high CPU intensive jobs, but CPU usage never
  crosses 80%.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-62-generic 4.15.0-62.69~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  NonfreeKernelModules: snapapi26
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Fri Sep 13 11:46:12 2019
  InstallationDate: Installed on 2019-09-11 (1 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1843869] [NEW] System crashes randomly each time with different application

2019-09-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Description:Ubuntu 16.04.6 LTS
Release:16.04

Package version: 7.7+13ubuntu3.1

Fresh system install with Ubuntu 16.04 crashes the system after some
time. We are running high CPU intensive jobs, but CPU usage never
crosses 80%.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.15.0-62-generic 4.15.0-62.69~16.04.1
ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-62-generic x86_64
NonfreeKernelModules: snapapi26
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Fri Sep 13 11:46:12 2019
InstallationDate: Installed on 2019-09-11 (1 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial
-- 
System crashes randomly each time with different application
https://bugs.launchpad.net/bugs/1843869
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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


[Desktop-packages] [Bug 1772520]

2019-09-13 Thread Miikka-Markus Alhonen
Still reproducible on:

Version: 6.3.1.2 (x64)
Build ID: b79626edf0065ac373bd1df5c28bd630b4424273
Threads CPU : 4; OS : Windows 6.3; UI Render : par défaut; VCL: win; 
Locale : fr-FR (fr_FR); Langue IHM : fr-FR
Calc: threaded

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

Title:
  Font metrics mixed up when selecting Arabic characters in Writer

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  In most fonts, many characters in the Arabic script change their width
  and height as typing progresses. For example the letter ب (U+0628) is
  reduced to about a half or even a third of its width if it's followed
  by another character such as ا (U+0627): با. Usually LibreOffice
  understands the changes in font metrics pretty well but not always.

  See the attached screenshot where I've written the sentence "مرحبا يا
  صديقي العزيز" in Writer and started selecting letters from the
  beginning of the line. The selection shown in the screenshot looks
  like the whole first word plus the following space but actually it
  only covers the first 4 letters of the first word out of 5 total:
  مرحب. From a user's point of view, this is very confusing, as I can't
  tell how far I've already selected without counting the characters in
  my mind. Even more surprisingly, LibreOffice Calc shows the selection
  as expected, i.e. different from Writer, so this does not feel like a
  font problem per se, although only some fonts display this behavior.

  The font I'm using in this example is Scheherazade, available through
  a third-party repository at packages.sil.org. The font is designed to
  cover a very wide variety of characters used for Arabic-script
  minority languages in both Asia and Africa, and in many cases it's the
  only professionally made font available for people working on many of
  these languages.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 21:03:43 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (197 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772520/+subscriptions

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


[Desktop-packages] [Bug 1772430]

2019-09-13 Thread Miikka-Markus Alhonen
Still reproducible on:

Version: 6.3.1.2 (x64)
Build ID: b79626edf0065ac373bd1df5c28bd630b4424273
Threads CPU : 4; OS : Windows 6.3; UI Render : par défaut; VCL: win; 
Locale : fr-FR (fr_FR); Langue IHM : fr-FR
Calc: threaded

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

Title:
  Proportional line spacing under 100 % makes first line too low in
  LibreOffice Writer

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Using proportional line spacing with less than 100 % makes the first
  line of each paragraph and each page considerably lower than all the
  other lines.

  This problem is an issue particularly with fonts designed for Arabic,
  where the default line spacing is very big so as to allow for space
  for optional vowel marks below and above the line. If these marks are
  not used, the space between the lines is often too big. If I change
  line spacing to proportional 80 %, most of the lines look fine but the
  first line of each paragraph and of each page (even without a
  paragraph break) gets crammed into the second line. As a user, I would
  rather expect the first line to have the same visual height as all the
  other lines. See the attached document and screenshots using Noto
  Naskh Arabic and 80 % line spacing.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 14:50:01 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772430/+subscriptions

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


[Desktop-packages] [Bug 1721614] Re: Firefox menus are misplaced

2019-09-13 Thread Bug Watch Updater
Launchpad has imported 7 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1411398.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-10-24T20:26:01+00:00 gpothier wrote:

Created attachment 8921616
firefox-bug.mp4

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171024001719

Steps to reproduce:

Computer has two monitors configured (laptop's + external). Open
Firefox. Then unplug the external monitor. Click on UI elements that
cause a popup menu to appear (eg. right click to display context menu,
click on bookmark folder, or on "burger" menu icon)


Actual results:

The popup menus appear at seemingly random locations. Moreover, the menu item 
highlighting do not match the actual mouse position (see attached video).
Happens on v56 and v57 beta.


Expected results:

The popup menus should appear at their correct location: right next to
the mouse cursor for context menu, or next to the UI element that
triggers the popup).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1721614/comments/11


On 2017-10-24T20:26:35+00:00 gpothier wrote:

Original bug report in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1721614

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1721614/comments/12


On 2017-12-19T15:37:04+00:00 gpothier wrote:

The bug is still present in v58.0b11. I'll try to give more precisions.
As I wrote earlier, pop up menus appear at incorrect locations after
reconfiguring monitors. As shown in the attached video, they can appear
quite far away from their correct location. Maybe an important point is
that the DPI settings change between configurations. One configuration
is with only the internal laptop monitor at 3200 x 1800 with high DPI
settings, and the other one is internal + external monitor, both at 1920
x 1080 (normal DPI settings).

It seems there is some kind of caching of individual menu positions, and
this caching seems to be invalidated when the requested menu position
changes; afterwards the menus appear in their correct positions until
the next monitor reconfiguration. This invalidation can be triggered in
two ways:

- For the context menu (right click), simply closing the menu and right
clicking somewhere else solves the problem. The context menu is thus
misplaced only once after reconfiguring the monitors (unless one right
clicks again at the exact same position)

- For the bookmarks and search menus, one has to move the window by a
few pixels in order to get rid of the problem. However, it is necessary
to open each menu once before moving the window to get rid of the
problem for that particular menu. For instance with two bookmarks menus,
after reconfiguring the screens I open the first one, it is misplaced.
Then I move the window and open the first menu again, then it is
correctly placed. However if after that I open the second menu, it is
also misplaced. I have to move the window again to fix it. On the other
hand, if after reconfiguring the screens I open both menus (both are
then misplaced) and then move the window, after that both menus are
correctly placed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1721614/comments/15


On 2018-05-31T20:31:07+00:00 gpothier wrote:

Following up on this report: this bug is 100% reproducible with the
Ubuntu 18.04 Live usb image, so it is not a configuration/package issue
on my system.

Steps to reproduce:
0. Use a laptop with high resolution display (eg. 3200 x 1800).
1. Boot from live image with external monitor plugged in.
2. Launch Firefox and enable the bookmarks toolbar.
3. Open and close the first item in the toolbar (or any other menu actually) => 
no problem.
4. Open the display configuration app and change config, eg. change scale from 
200% to 100%, or change built in display's resolution to 1900 x 1080.
5. Open the first item in Firefox's bookmarks toolbar => it usually appears at 
wrong location. If not, try disconnecting the external monitor and opening the 
menu. At some point it will appear at the wrong location.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1721614/comments/17


On 2018-06-02T16:32:47+00:00 gpothier wrote:

I did a bisection and found that the problem started appearing here:

13:29.43 INFO: Last good revision: 8e5c888d0d89 (2015-07-22)
13:29.43 INFO: First bad revision: 1f77b78797d6 (2015-07-23)

I think it has to do