[Desktop-packages] [Bug 1821648] Re: Gnome Shell froze GUI entirely with 100% CPU usage

2019-05-24 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Gnome Shell froze GUI entirely with 100% CPU usage

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  Without warning or apparent user action, my entire system froze aside
  from the mouse cursor.  I was able to switch to a VT to log in and
  capture this bug report.  After that, I had to `kill -9 gnome-shell`
  after which it restarted properly and my session is now working fine
  again.

  Possibly a dupe of #1709597 but that is quite old.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  Uname: Linux 5.0.1-050001-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 25 17:31:56 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-12-09 (470 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to cosmic on 2018-10-19 (157 days ago)

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

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


[Desktop-packages] [Bug 1830449] Re: Power control panel does not provide suspend on lid close dependent on battery power

2019-05-24 Thread Dan Kortschak
** Attachment added: "lid-suspend.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830449/+attachment/5266394/+files/lid-suspend.png

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

Title:
  Power control panel does not provide suspend on lid close dependent on
  battery power

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

Bug description:
  In previous versions of Ubuntu (16.04) it was possible to set an
  automatic suspend on laptop lid closure when the laptop was battery
  powered, but not when on mains. This is no longer available; automatic
  suspend provided by the power control panel is purely time-based. The
  gnome tweak tool does offer a lid-based suspend trigger, but this is
  independent of power source.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:33:46 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830448] Re: gnome shell does not respect "Photos: Do nothing" for removable media

2019-05-24 Thread Dan Kortschak
With this setting Shotwell is still started on insertion.

** Attachment added: "do-nothing-for-photos.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830448/+attachment/5266388/+files/do-nothing-for-photos.png

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

Title:
  gnome shell does not respect "Photos: Do nothing" for removable media

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

Bug description:
  Setting "Photos: Do nothing" in the removable media panel of the gnome
  control center had no effect in that inserting a removable volume with
  photos/video (GoPro SD card) results in Shotwell being opened. The
  only way to prevent this from happening is to check "Never prompt or
  start programs on media insertion" which then prevents convenient
  starting of e.g. DVD playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:24:20 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830448] Re: gnome shell does not respect "Photos: Do nothing" for removable media

2019-05-24 Thread Dan Kortschak
This setting prevents Shotwell from starting, but obviously block
everything else as well.

** Attachment added: "never-do-anything.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830448/+attachment/5266389/+files/never-do-anything.png

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

Title:
  gnome shell does not respect "Photos: Do nothing" for removable media

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

Bug description:
  Setting "Photos: Do nothing" in the removable media panel of the gnome
  control center had no effect in that inserting a removable volume with
  photos/video (GoPro SD card) results in Shotwell being opened. The
  only way to prevent this from happening is to check "Never prompt or
  start programs on media insertion" which then prevents convenient
  starting of e.g. DVD playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:24:20 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830448] [NEW] gnome shell does not respect "Photos: Do nothing" for removable media

2019-05-24 Thread Dan Kortschak
Public bug reported:

Setting "Photos: Do nothing" in the removable media panel of the gnome
control center had no effect in that inserting a removable volume with
photos/video (GoPro SD card) results in Shotwell being opened. The only
way to prevent this from happening is to check "Never prompt or start
programs on media insertion" which then prevents convenient starting of
e.g. DVD playing.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 25 09:24:20 2019
InstallationDate: Installed on 2019-05-22 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  gnome shell does not respect "Photos: Do nothing" for removable media

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

Bug description:
  Setting "Photos: Do nothing" in the removable media panel of the gnome
  control center had no effect in that inserting a removable volume with
  photos/video (GoPro SD card) results in Shotwell being opened. The
  only way to prevent this from happening is to check "Never prompt or
  start programs on media insertion" which then prevents convenient
  starting of e.g. DVD playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:24:20 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830449] Re: Power control panel does not provide suspend on lid close dependent on battery power

2019-05-24 Thread Dan Kortschak
** Attachment added: "automatic-suspend.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830449/+attachment/5266393/+files/automatic-suspend.png

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

Title:
  Power control panel does not provide suspend on lid close dependent on
  battery power

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

Bug description:
  In previous versions of Ubuntu (16.04) it was possible to set an
  automatic suspend on laptop lid closure when the laptop was battery
  powered, but not when on mains. This is no longer available; automatic
  suspend provided by the power control panel is purely time-based. The
  gnome tweak tool does offer a lid-based suspend trigger, but this is
  independent of power source.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:33:46 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830449] [NEW] Power control panel does not provide suspend on lid close dependent on battery power

2019-05-24 Thread Dan Kortschak
Public bug reported:

In previous versions of Ubuntu (16.04) it was possible to set an
automatic suspend on laptop lid closure when the laptop was battery
powered, but not when on mains. This is no longer available; automatic
suspend provided by the power control panel is purely time-based. The
gnome tweak tool does offer a lid-based suspend trigger, but this is
independent of power source.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 25 09:33:46 2019
InstallationDate: Installed on 2019-05-22 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Power control panel does not provide suspend on lid close dependent on
  battery power

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

Bug description:
  In previous versions of Ubuntu (16.04) it was possible to set an
  automatic suspend on laptop lid closure when the laptop was battery
  powered, but not when on mains. This is no longer available; automatic
  suspend provided by the power control panel is purely time-based. The
  gnome tweak tool does offer a lid-based suspend trigger, but this is
  independent of power source.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:33:46 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830444] Re: IPv4 does not provide "Shared to other computers" method

2019-05-24 Thread Dan Kortschak
Image of nm-connection editor control, including shared to other.

** Attachment added: "with-shared-to-other.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830444/+attachment/5266383/+files/with-shared-to-other.png

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830444] Re: IPv4 does not provide "Shared to other computers" method

2019-05-24 Thread Dan Kortschak
Image of current directly available control panel.

** Attachment added: "no-shared-to-other.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830444/+attachment/5266382/+files/no-shared-to-other.png

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830336] Re: [needs-packaging] enchant 1.6.0 outdated, pipe command '*' (save personal dictionary) does nothing

2019-05-24 Thread Brian Murray
*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

- enchant 1.6.0 outdated, pipe command '*' (save personal dictionary) does 
nothing
+ [needs-packaging] enchant 1.6.0 outdated, pipe command '*' (save personal 
dictionary) does nothing

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

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

Title:
  [needs-packaging] enchant 1.6.0 outdated, pipe command '*' (save
  personal dictionary) does nothing

Status in enchant package in Ubuntu:
  New

Bug description:
  [needs-packaging] enchant

  enchant is a meta-spellchecker supporting multiple spellchecking
  backends (hunspell, GNU aspell, hspell, Voikko, Zemberek, Apple Spell
  (on Mac OS)), with an ispell-compatible pipe mode for use within
  applications.

  URL: https://github.com/AbiWord/enchant
  License: LGPL 2.1
  Notes: Enchant homepage has moved to GitHub. The old homepage at 
abisource.com was last updated in 2010.

  The build steps for a released version seem standard; for details, see
  e.g.
  http://www.linuxfromscratch.org/blfs/view/svn/general/enchant.html

  Ubuntu currently has a package for enchant 1.6.0, but it is seriously
  out of date (2010); latest release is 2.2.3 (2018).

  Why this is important:

  Enchant is the recommended interface for Voikko, the spellchecker for
  Finnish. The older tmispell interface (that comes with Voikko) is
  deprecated by the developers of Voikko, so Enchant is currently the
  only supported option for checking both Finnish and English using the
  same frontend. A common frontend is important for easy switching of
  spellcheck language within applications such as Emacs and LyX.

  Finnish is an agglutinative language. This prevents common
  spellcheckers such as aspell from working properly, so Voikko itself
  is really necessary.

  The old version lacks support for the '*' command in pipe mode, so it
  is unable to update the personal dictionary. This is important
  especially in Emacs, because Emacs's flyspell (on-the-fly spell
  checker) package uses the pipe mode and sends this command to save new
  words into the personal dictionary.

  With Enchant 2.2.3, this works properly. (Does not even need
  configuration in Emacs other than telling it to use enchant as "the
  ispell program"; Enchant itself knows where its personal dictionaries
  are (~/.config/enchant), as well as which file to use for each
  language.)

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

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


[Desktop-packages] [Bug 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot window

2019-05-24 Thread Toru Hironaka
I think you may need to press "Ctrl" button with "Print Screen" button
for copying a screen image in clip board.

https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html

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

Title:
  Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot window

Status in gnome-screenshot package in Ubuntu:
  Opinion

Bug description:
  Ubuntu 18.04
  gnome-screenshot v 3.25.0-0ubuntu2 (amd64)

  Using the PrtSc button, alone or in combination with shift, alt or
  ctrl, doesn't trigger the gnome-screenshot window that asks to save
  the image.

  The screen blinks (so the button is intercepted) but no window is
  triggered.

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

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


[Desktop-packages] [Bug 1830444] [NEW] IPv4 does not provide "Shared to other computers" method

2019-05-24 Thread Dan Kortschak
Public bug reported:

In previous versions of Ubuntu (16.04 and before), it was possible to
specify the IPv4 method to use "Shared to other computers" directly from
the top bar (via the via the nm-connection-editor/nm-applet).

This ability is no longer available via the preferred network
configuration panel in the gnome control center, i.e. without invoking
either nm-connection-editor directly or via the nm-applet (which then
doubles up the network controls in the top bar).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 25 09:12:16 2019
InstallationDate: Installed on 2019-05-22 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  IPv4 does not provide "Shared to other computers" method

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

Bug description:
  In previous versions of Ubuntu (16.04 and before), it was possible to
  specify the IPv4 method to use "Shared to other computers" directly
  from the top bar (via the via the nm-connection-editor/nm-applet).

  This ability is no longer available via the preferred network
  configuration panel in the gnome control center, i.e. without invoking
  either nm-connection-editor directly or via the nm-applet (which then
  doubles up the network controls in the top bar).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 25 09:12:16 2019
  InstallationDate: Installed on 2019-05-22 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1749936] Re: GNOME Web not appearing in search results

2019-05-24 Thread Bug Watch Updater
** Changed in: gnome-software
   Status: Unknown => Fix Released

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

Title:
  GNOME Web not appearing in search results

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

Bug description:
  ** GNOME BUG TRACKER URL: https://goo.gl/VsSNtb
  Long URL: https://gitlab.gnome.org/GNOME/gnome-software/issues/304 **

  The GNOME Web Browser is not appearing in search results.
  I have tried a variety of combinations thereof, such as "web, gnome web, 
browser, internet," etc..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.1-0ubuntu2.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 06:06:51 2018
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1401245] Re: Duplicity crashes when called -- UnicodeDecodeError

2019-05-24 Thread Joachim R.
Solved for me in Ubuntu 19.04, I guess the dist-upragde ugraded
duplicity with the fixed upstream version.

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

Title:
  Duplicity crashes when called -- UnicodeDecodeError

Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Since some time ago, duplicity, called automatically by ubuntu's deja-
  dup, crashes upon each startup. I cannot even change the settings.
  Some online posts suggested deleting the backup, which I did. There
  are some corrupted files I could not delete (with non-unicode
  characters in their names). I have seen that there was a bug with
  unicode decoding in an earlier version, but I am running the updated
  one.
  (https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1311176)

  Here's the output of duplicity:
  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1494, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1488, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1337, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1366, in do_backup
  sync_archive(decrypt)
File "/usr/bin/duplicity", line 1100, in sync_archive
  remote_metafiles, ignored, rem_needpass = get_metafiles(remlist)
File "/usr/bin/duplicity", line 992, in get_metafiles
  pr = file_naming.parse(fn)
File "/usr/lib/python2.7/dist-packages/duplicity/file_naming.py", line 389, 
in parse
  pr = check_full()
File "/usr/lib/python2.7/dist-packages/duplicity/file_naming.py", line 308, 
in check_full
  t = str2time((m1 or m2).group("time"), short)
File "/usr/lib/python2.7/dist-packages/duplicity/file_naming.py", line 281, 
in str2time
  t = dup_time.genstrtotime(timestr.upper())
File "/usr/lib/python2.7/dist-packages/duplicity/dup_time.py", line 278, in 
genstrtotime
  return override_curtime - intstringtoseconds(timestr)
File "/usr/lib/python2.7/dist-packages/duplicity/dup_time.py", line 190, in 
intstringtoseconds
  error()
File "/usr/lib/python2.7/dist-packages/duplicity/dup_time.py", line 181, in 
error
  raise TimeException(bad_interval_string % interval_string)
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xee in position 15: 
ordinal not in range(128)

  Duplicity version: 0.6.23-1ubuntu5
  Deja-dup version: 32.0-0ubuntu1
  Python version: 32.0-0ubuntu1
  OS version: ubuntu 14.10

  Sorry I do not know how to extract the exact command line deja-dup
  uses to call duplicity.

  Philippe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: duplicity 0.6.23-1ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 10 21:05:07 2014
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to utopic on 2014-11-14 (26 days ago)

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

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


[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off

2019-05-24 Thread FrankStefani
Where can I find and download "cups-filters (1.23.0-1)" right now?

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

Title:
  Installed network printer removed automatically when turned off

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  After installing artful, I configured my HP LaserJet M1212nf via network as 
usual via hp-setup.
  Installation worked and I could print/scan via network, but next time I 
needed to print, the printer was gone from the system.
  Basically, every time I need to print, I have to install the printer again.
  I'm not sure when the printer disappears, but I can reproduce consistently.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:33:12 2017
  InstallationDate: Installed on 2017-07-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1731417] Re: Installed network printer removed automatically when turned off

2019-05-24 Thread Till Kamppeter
The 1.23.0-1 version got uploaded to the development of 19.10 (Eoan).
For getting it into an already released Ubuntu version, a Stable Release
Update (SRU) would be needed. But note that if you are still using 18.10
(Cosmic), that in a few months (end-July) the support for Cosmic ends,
so SRUs for this version do not make much sense. So I recommend you to
upgrade to 19.04 (Disco) and try whether the problem still persists for
you and report back here.

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

Title:
  Installed network printer removed automatically when turned off

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  After installing artful, I configured my HP LaserJet M1212nf via network as 
usual via hp-setup.
  Installation worked and I could print/scan via network, but next time I 
needed to print, the printer was gone from the system.
  Basically, every time I need to print, I have to install the printer again.
  I'm not sure when the printer disappears, but I can reproduce consistently.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:33:12 2017
  InstallationDate: Installed on 2017-07-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2019-05-24 Thread Amir Omidi
Experiencing this:
Device 9C:64:8B:7D:C7:3D (public)
Name: Amir’s AirPods
Alias: Amir’s AirPods
Class: 0x00240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Vendor specific   (74ec2172-0bad-4d01-8f77-997b2be0722a)
UUID: Vendor specific   (9bd708d7-64c7-4e9f-9ded-f6b6c4551967)
Modalias: bluetooth:v004Cp200Fd0A00
RSSI: -54

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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


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

2019-05-24 Thread Amir Omidi
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559

Experiencing this
Device 9C:64:8B:7D:C7:3D (public)
Name: Amir’s AirPods
Alias: Amir’s AirPods
Class: 0x00240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Vendor specific   (74ec2172-0bad-4d01-8f77-997b2be0722a)
UUID: Vendor specific   (9bd708d7-64c7-4e9f-9ded-f6b6c4551967)
Modalias: bluetooth:v004Cp200Fd0A00
RSSI: -54

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

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

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

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

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


[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen

2019-05-24 Thread Paul Johnston
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

Fri May 24 15:13:53 EDT 2019 
I can confirm this is happening in 19.04 (fresh installation)

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

Title:
  Icon dock visible on lock screen

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

Bug description:
  When locking the machine with alt-L the icon dock is still visible.

  After Login, the dock does not get adjusted to the top menu.

  In rare cases, the dock does not respond any more. This requires a
  reboot of the machine

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: mutter 3.30.1-1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 12:59:27 2018
  InstallationDate: Installed on 2018-04-30 (176 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

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

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


[Desktop-packages] [Bug 1830422] [NEW] Long Gtk menu into appindicator1 cannot be scrolled: arrow bars are absent

2019-05-24 Thread Dmytro
Public bug reported:

I am using appindicator-1.0 in conjunction with Gtk+2.0 menu. Menu
consist of constant items and many dynamically added items. If the
screen pixel resolution is not so good as it must be then the last menu
items are not visible. Ubuntu 16.04 automatically add top and bottom
bars with "^" and "v" arrows to scroll menu when mouse pointer is over
these bars. But in Linux Ubuntu 18.04 (and 19.04 too) such scrolling
bars are not appearing.

On the other hand menu scrolling is working fine anywhere into usual GTK
window with menu bar (without using appindicator). Ubuntu 16.04 and
Ubuntu 18.04 use the same 12.10.1 libappindicator version.

Here is the test c program which illustrates the issue. It works fine in
Linux Ubuntu 16.04 and has the described above problem in Linux 18.04:

#include 
#include 

#define LOGO_PNG "/home/super/my-project/menu-test/logo.png"

AppIndicator* c_indicator;
GtkWidget* c_menu;

void menu_quit_cb(GtkMenuItem* menuitem, gpointer user_data)
{
gtk_main_quit();
}

int main(int argc, char *argv[])
{
gtk_init(, );

int i;
GtkWidget* item;
char title[128];

c_menu = gtk_menu_new();

item = gtk_menu_item_new_with_label("Quit");
g_signal_connect(item, "activate", G_CALLBACK(menu_quit_cb), NULL);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);

gtk_menu_shell_append(GTK_MENU_SHELL(c_menu),
gtk_separator_menu_item_new());

for (i = 1; i <= 100; ++i) {
snprintf(title, sizeof(title), "Item #%03u", i);
item = gtk_menu_item_new_with_label(title);
gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
gtk_widget_show(item);
}

//

c_indicator = app_indicator_new("Menu Test", LOGO_PNG, 
APP_INDICATOR_CATEGORY_APPLICATION_STATUS);
app_indicator_set_status(c_indicator, APP_INDICATOR_STATUS_ACTIVE);
app_indicator_set_icon(c_indicator, LOGO_PNG);
app_indicator_set_menu(c_indicator, GTK_MENU(c_menu));

gtk_main();

return 0;
}

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libappindicator1 12.10.1+18.04.20180322.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 21:15:59 2019
InstallationDate: Installed on 2018-07-03 (325 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: libappindicator
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Long Gtk menu into appindicator1 cannot be scrolled: arrow bars are
  absent

Status in libappindicator package in Ubuntu:
  New

Bug description:
  I am using appindicator-1.0 in conjunction with Gtk+2.0 menu. Menu
  consist of constant items and many dynamically added items. If the
  screen pixel resolution is not so good as it must be then the last
  menu items are not visible. Ubuntu 16.04 automatically add top and
  bottom bars with "^" and "v" arrows to scroll menu when mouse pointer
  is over these bars. But in Linux Ubuntu 18.04 (and 19.04 too) such
  scrolling bars are not appearing.

  On the other hand menu scrolling is working fine anywhere into usual
  GTK window with menu bar (without using appindicator). Ubuntu 16.04
  and Ubuntu 18.04 use the same 12.10.1 libappindicator version.

  Here is the test c program which illustrates the issue. It works fine
  in Linux Ubuntu 16.04 and has the described above problem in Linux
  18.04:

  #include 
  #include 

  #define LOGO_PNG "/home/super/my-project/menu-test/logo.png"

  AppIndicator* c_indicator;
  GtkWidget* c_menu;

  void menu_quit_cb(GtkMenuItem* menuitem, gpointer user_data)
  {
  gtk_main_quit();
  }

  int main(int argc, char *argv[])
  {
  gtk_init(, );

  int i;
  GtkWidget* item;
  char title[128];

  c_menu = gtk_menu_new();

  item = gtk_menu_item_new_with_label("Quit");
  g_signal_connect(item, "activate", G_CALLBACK(menu_quit_cb), NULL);
  gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
  gtk_widget_show(item);

  gtk_menu_shell_append(GTK_MENU_SHELL(c_menu),
  gtk_separator_menu_item_new());

  for (i = 1; i <= 100; ++i) {
  snprintf(title, sizeof(title), "Item #%03u", i);
  item = gtk_menu_item_new_with_label(title);
  gtk_menu_shell_append(GTK_MENU_SHELL(c_menu), item);
  gtk_widget_show(item);
  }

  //

  c_indicator = app_indicator_new("Menu Test", LOGO_PNG, 
APP_INDICATOR_CATEGORY_APPLICATION_STATUS);
  app_indicator_set_status(c_indicator, APP_INDICATOR_STATUS_ACTIVE);
  

[Desktop-packages] [Bug 1830416] [NEW] Firefox shows multiple master password prompts on startup when user has multiple home tabs that require passwords

2019-05-24 Thread Steve Chadsey
Public bug reported:

Ubuntu 18.04.2 LTS

I have two URLs configured for Firefox startup.  They are for different
sites.  Each one will go to a login page.  I have a master password
configured in Firefox.  When I start Firefox, two tabs will open to the
two URLs, and up until recently, I was prompted once for my master
password.  Once I entered it, my credentials would auto-fill on both
tabs as expected.  Today I noticed that on Firefox startup, I was
getting two master password prompts.  Although entering the master
password for one would suffice, it is annoying to have to close out the
second one.  Also, the second one often pops up and steals focus from
the first when I am entering the master password (depending on the
relative page load times of the two tabs).

I was running Firefox 66.0.5+build1-0ubuntu0.18.04.1 when I first
noticed this.  I updated to 67.0+build2-0ubuntu0.18.04.1 and the problem
persists.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 67.0+build2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BuildID: 20190517140819
Channel: Unavailable
CurrentDesktop: XFCE
Date: Fri May 24 12:09:21 2019
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePlugins: Shockwave Flash - 
[HomeDir]/.mozilla/plugins/libflashplayer.so
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-12-12 (527 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
IpRoute:
 default via 10.55.12.1 dev enx9cebe8551508 proto dhcp metric 100 
 default via 10.55.216.1 dev wlp3s0 proto dhcp metric 600 
 10.55.12.0/23 dev enx9cebe8551508 proto kernel scope link src 10.55.13.57 
metric 100 
 10.55.216.0/21 dev wlp3s0 proto kernel scope link src 10.55.217.198 metric 600
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1Plugins: Shockwave Flash - [HomeDir]/.mozilla/plugins/libflashplayer.so
Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 - LastVersion=67.0/20190517140819 (In use)
 Profile0 (Default) - LastVersion=67.0/20190517140819 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: Upgraded to bionic on 2018-10-30 (206 days ago)
dmi.bios.date: 09/12/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.4
dmi.board.name: 0FH6CJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: L05248
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.4:bd09/12/2017:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn0FH6CJ:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5580
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

** Attachment removed: "DefaultProfilePrefs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1830416/+attachment/5266330/+files/DefaultProfilePrefs.txt

** Attachment removed: "Profile1Prefs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1830416/+attachment/5266337/+files/Profile1Prefs.txt

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

Title:
  Firefox shows multiple master password prompts on startup when user
  has multiple home tabs that require passwords

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.2 LTS

  I have two URLs configured for Firefox startup.  They are for
  different sites.  Each one will go to a login page.  I have a master
  password configured in Firefox.  When I start Firefox, two tabs will
  open to the two URLs, and up until recently, I was prompted once for
  my master password.  Once I entered it, my credentials would auto-fill
  on both tabs as expected.  Today I noticed that on Firefox startup, I
  was getting two master password prompts.  Although entering the master
  password for one would suffice, it is annoying to have to close out
  the second one.  

[Desktop-packages] [Bug 1740508] Re: Web fonts take a considerable amount of time to load [over a high-speed connection]

2019-05-24 Thread Paul White
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Upstream report was closed "RESOLVED INCOMPLETE" on 2018-01-18 due to lack 
information.

@Jeb E, do you still see an issue with the currently supported versions
of Ubuntu and Firefox?

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Web fonts take a considerable amount of time to load [over a high-
  speed connection]

Status in Mozilla Firefox:
  Expired
Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Even over a high-speed connection, web fonts seem to take far too long
  to download for websites in which the default font is not installed on
  the drive of my system.

  
  Example site with issue on my system: 'https://www.kraken.com/'
  Basic font family information, extracted from CSS: 'font-family:sans-serif'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 57.0.1+build2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-lowlatency 4.13.13
  Uname: Linux 4.13.0-21-lowlatency x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeb1236 F pulseaudio
  BuildID: 20171129230227
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 29 09:23:41 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.86.1 dev wlp1s0 proto static metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.86.0/24 dev wlp1s0 proto kernel scope link src 192.168.86.30 metric 
600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1c664c74-b6f2-471a-9aa4-e303d1171129
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=57.0.1/20171129230227 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-1c664c74-b6f2-471a-9aa4-e303d1171129
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 01DC01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd09/14/2017:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn01DC01:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 13-5368
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1749936] Re: GNOME Web not appearing in search results

2019-05-24 Thread Paul White
** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #304
   https://gitlab.gnome.org/GNOME/gnome-software/issues/304

** Changed in: gnome-software
   Importance: Undecided => Unknown

** Changed in: gnome-software
   Status: New => Unknown

** Changed in: gnome-software
 Remote watch: Email to gnome-software-list@gnome # => 
gitlab.gnome.org/GNOME/gnome-software/issues #304

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

Title:
  GNOME Web not appearing in search results

Status in GNOME Software:
  Unknown
Status in gnome-software package in Ubuntu:
  New

Bug description:
  ** GNOME BUG TRACKER URL: https://goo.gl/VsSNtb
  Long URL: https://gitlab.gnome.org/GNOME/gnome-software/issues/304 **

  The GNOME Web Browser is not appearing in search results.
  I have tried a variety of combinations thereof, such as "web, gnome web, 
browser, internet," etc..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.1-0ubuntu2.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 06:06:51 2018
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 209048] Re: Suggests using an online service for webcal links instead of evolution

2019-05-24 Thread Paul White
Reporter not subscribed to bug report and doesn't appear to use
Launchpad any longer. Last confirmation of this bug was over 11 years
ago in comment #1.

Using Firefox 67.0 in Ubuntu 19.10 (dev) I see that entering
'webcal://test' in the URL bar does produce a prompt to use evolution.
So closing this as being fixed.

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

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

Title:
  Suggests using an online service for webcal links instead of evolution

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox-3.0

  Using 3.0b4 in Hardy. Enter an url like webcal:/test into the url bar
  to see the problem.

  When clicking a webcal url into firefox3, it suggests using an online service
  even though evolution and its evolution-webcal handler are in the default
  install. Since it's associated in /desktop/gnome/url-handlers/webcal, Epiphany
  is the only browser that will use it

  Shouldn't Firefox ideally know how to read /desktop/gnome/url-handlers
  for this? This would also fix bug 206274

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

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


[Desktop-packages] [Bug 632629] Re: problem sorting files in upload-file file-chooser

2019-05-24 Thread Paul White
Thanks Allo. Closing as being fixed as problem was confirmed by another
user.

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

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

Title:
  problem sorting files in upload-file file-chooser

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox

  1) go to some image upload site
  2) click on the file-field
  3) if files are sorted by name, click to sort them by date. if sorted by 
date, sort by name
  4) now try to click on a file to upload it.
  5) BUG you cannot select the file

  workaround:
  6) click cancel
  7) open the file-chooser again
  8) the files are still sorted by the column you clicked last time
  9) you can now select the file to upload

  now it would be nice, if step 5 already worked.

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

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


[Desktop-packages] [Bug 632629] Re: problem sorting files in upload-file file-chooser

2019-05-24 Thread Allo
I cannot reproduce the bug anymore. It's okay to close it, I will open a
new bug when I encounter the problem again.

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

Title:
  problem sorting files in upload-file file-chooser

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  1) go to some image upload site
  2) click on the file-field
  3) if files are sorted by name, click to sort them by date. if sorted by 
date, sort by name
  4) now try to click on a file to upload it.
  5) BUG you cannot select the file

  workaround:
  6) click cancel
  7) open the file-chooser again
  8) the files are still sorted by the column you clicked last time
  9) you can now select the file to upload

  now it would be nice, if step 5 already worked.

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

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


[Desktop-packages] [Bug 1830408] [NEW] Do not see login screen after screen is blanked

2019-05-24 Thread crysman
Public bug reported:

I've just upgraded to 18.10 from 18.04. Now when power manager (or
whoever) puts the screen to blank, I cannot login, because I do not see
anything. Befeore the upgrade, mouse move or keypress led to login
screen. Now does not.

Workaround:
When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears.

Where is the problem and how to fix it please?

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
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: XFCE
Date: Fri May 24 17:59:31 2019
DistUpgraded: 2019-05-24 13:40:45,847 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
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1682]
 NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF119M [GeForce GT 520M] [1043:1682]
InstallationDate: Installed on 2018-09-03 (263 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
MachineType: ASUSTeK Computer Inc. U36SD
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic 
root=UUID=aa87c0a2-5b06-40fb-82dd-fbccd7c800e6 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to cosmic on 2019-05-24 (0 days ago)
dmi.bios.date: 07/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U36SD.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U36SD
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU36SD.205:bd07/12/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.family: U
dmi.product.name: U36SD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic third-party-packages 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/1830408

Title:
  Do not see login screen after screen is blanked

Status in xorg package in Ubuntu:
  New

Bug description:
  I've just upgraded to 18.10 from 18.04. Now when power manager (or
  whoever) puts the screen to blank, I cannot login, because I do not
  see anything. Befeore the upgrade, mouse move or keypress led to login
  screen. Now does not.

  Workaround:
  When I go to terminal on tty1 and then back CTRL+ALT+F7, login screen appears.

  Where is the problem and how to fix it please?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  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: XFCE
  Date: Fri May 24 17:59:31 2019
  DistUpgraded: 2019-05-24 13:40:45,847 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
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-24 Thread Marcus Tomlinson
Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.5 to
1:6.0.7-0ubuntu0.18.04.6 from bionic-proposed in a clean and up-to-date
bionic amd64 VM, and verified that the [Test Case] now passes.

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

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice source package in Xenial:
  Fix Committed
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in openjdk-lts source package in Disco:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  [Impact]

   * A recent OpenJDK update changes the value of the "java.vendor"
  property from "Oracle Corporation" to "Private Build". This breaks the
  code in LibreOffice that detects an installed JVM.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Launch the LibreOffice Start Center
   2. Open Tools > Options
   3. Navigate to LibreOffice > Advanced
   4. A JRE should be listed with Location: /usr/lib/jvm/...

  [Regression Potential]

   * This fix is small and concentrated so potential for regression
  should be relatively low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

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

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


[Desktop-packages] [Bug 1820062] Re: LibreOffice Impress embed video problem (libreoffice-gtk3)

2019-05-24 Thread Marcus Tomlinson
Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.5 to
1:6.0.7-0ubuntu0.18.04.6 from bionic-proposed in a clean and up-to-date
bionic amd64 VM, and verified that the [Test Case] now passes.

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

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

Title:
  LibreOffice Impress embed video problem (libreoffice-gtk3)

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  LibreOffice Impress has problematic embedded video playback.

  In Ubuntu 18.04, 18.10 and 19.04-alpha if you insert video in Impress
  slide, when played video stretches in fullscreen. (LO versions
  affected at least 6.0.x, 6.1.y and 6.2.1.1)

  The video of miss-behavior: https://youtu.be/77E6IzVJ5jA

  The issue is with current Libre Office vlc GTK3 (libreoffice-gtk3).

  Solution #1
  install  gstreamer1.0-gtk3 (probably missing dependency)

  Solution #2
  Remove libreoffice-gtk3 and install libreoffice-gtk2

  reference to Document Funtation bugzilla:
  https://bugs.documentfoundation.org/show_bug.cgi?id=124068

  [Impact]

   * This effects all libreoffice-gtk3 users wishing to embed videos
  into an Impress slide.

   * The fix is currently in LibreOffice 6.2.2+ on disco and eoan.

  [Test Case]

   1. Insert a video into an Impress slide
   2. Play the video
   3. The video should play within the slide (not fullscreen like this: 
https://youtu.be/77E6IzVJ5jA)

  [Regression Potential]

   * The fix is one line in the control file so potential for regression
  is low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

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

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


[Desktop-packages] [Bug 1827451] Re: Japanese new era "Reiwa(令和)" support

2019-05-24 Thread Marcus Tomlinson
Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.5 to
1:6.0.7-0ubuntu0.18.04.6 from bionic-proposed in a clean and up-to-date
bionic amd64 VM, and verified that the [Test Case] now passes.

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

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

Title:
  Japanese new era "Reiwa(令和)" support

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Xenial:
  Fix Committed
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This effects all users who use the Japanese era date format in
  LibreOffice.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Start Calc
   2. Put "01/05/2019" into a cell
   3. Right-click on the cell and select "Format Cells"
   4. Set “Language" to "Japanese"
   5. Set “Format" to "H11.12.31"
   6. Cell should show "R1.05.01" (not "N1.05.01”)
   7. Set “Format" to "平成11年12月31日"
   8. Cell should show "令和1年5月1日" (not "平成31年5月1日")

  [Regression Potential]

   * The fix is minor so potential for regression is low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

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

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


Re: [Desktop-packages] [Bug 1830231] Re: Firefox will not connect to any website

2019-05-24 Thread Tony Morton
OK - this fixed the problem;

https://askubuntu.com/questions/1145311/internet-is-working-but-firefox-
browser-cannot-connect

Answer 2

2

I was having the same issue. Removing prefs.js did not fix the problem 
for me.

Restarting firefox via Menu -> Help -> "Restart with Add-ons Disabled" 
and choosing to restart in "safe mode" gave me a working browser.

I opened a regular instance of firefox again and it was still not 
working (obviously). I repeated the "Restart with Add-ons Disabled" but 
selected "Refresh Firefox" at the final step and it seems to have fixed 
the problem.

I went back through the preferences section and have changed back all of 
my settings there and I haven't broken the browser yet.

Again, this doesn't get to the root of the problem, but perhaps it 
narrows it down some? Maybe someone else knows more about what all gets 
reset when you choose "Refresh Firefox"?

So this works - and the problem seems to be something inside Firefox, 
possibly due to Add-Ons, the basis of which seems to have been changed.

This bug can be closed.

Regards
Tony Morton


Yes, the same issue. I am using the Opera browser while Firefox is out 
of action, and Opera works fine. Does that help pin down a difference? 
This problem only began after the Ubuntu update on Tuesday 21st which 
was a list of system files, so maybe something that Firefox depends upon 
was changed then?

The journalctl package is not installed on my system.


On 23/05/2019 22:01, Sebastien Bacher wrote:
> Thank you for your bug report. do you get the same issue if you start a
> private browsing session? Could you add your journalctl bug?
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Firefox will not connect to any website

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Firefox will not connect to any website, it opens properly and will
  open files from my PC, there is nothing wrong with my wi-fi or
  internet connection. Any request for a web address results in the
  continuing spinning icon in the tab and it never connects to any web
  address. This follows upon Ubuntu software updates on Tuesday 21st May
  2019

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 67.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tony   2152 F pulseaudio
   /dev/snd/controlC0:  tony   2152 F pulseaudio
  BrokenPermissions:
   healthreport/state.json (0o600, wrong owner)
   sessionstore.bak (0o600, wrong owner)
  BuildID: 20190517140819
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 23 15:15:36 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2018-09-30 (234 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.10 metric 600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=67.0/20190517140819
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0478VN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnInspiron660s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 660s
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-24 Thread Marcus Tomlinson
Upgraded libreoffice from 1:5.1.6~rc2-0ubuntu1~xenial6 to
1:5.1.6~rc2-0ubuntu1~xenial7 from xenial-proposed in a clean and up-to-
date xenial amd64 VM, and verified that the [Test Case] now passes.

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

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice source package in Xenial:
  Fix Committed
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in openjdk-lts source package in Disco:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  [Impact]

   * A recent OpenJDK update changes the value of the "java.vendor"
  property from "Oracle Corporation" to "Private Build". This breaks the
  code in LibreOffice that detects an installed JVM.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Launch the LibreOffice Start Center
   2. Open Tools > Options
   3. Navigate to LibreOffice > Advanced
   4. A JRE should be listed with Location: /usr/lib/jvm/...

  [Regression Potential]

   * This fix is small and concentrated so potential for regression
  should be relatively low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

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

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


[Desktop-packages] [Bug 1827451] Re: Japanese new era "Reiwa(令和)" support

2019-05-24 Thread Marcus Tomlinson
Upgraded libreoffice from 1:5.1.6~rc2-0ubuntu1~xenial6 to
1:5.1.6~rc2-0ubuntu1~xenial7 from xenial-proposed in a clean and up-to-
date xenial amd64 VM, and verified that the [Test Case] now passes.

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

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

Title:
  Japanese new era "Reiwa(令和)" support

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Xenial:
  Fix Committed
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released

Bug description:
  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This effects all users who use the Japanese era date format in
  LibreOffice.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Start Calc
   2. Put "01/05/2019" into a cell
   3. Right-click on the cell and select "Format Cells"
   4. Set “Language" to "Japanese"
   5. Set “Format" to "H11.12.31"
   6. Cell should show "R1.05.01" (not "N1.05.01”)
   7. Set “Format" to "平成11年12月31日"
   8. Cell should show "令和1年5月1日" (not "平成31年5月1日")

  [Regression Potential]

   * The fix is minor so potential for regression is low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Sebastien Bacher
The runtime are for snaps righT? You might be able to uninstall 3.26
(unless you have snaps still using it)

You might want to report the segfault upstream, they might have a better idea 
since they write the code
https://gitlab.gnome.org/GNOME/gnome-control-center/issues

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1826052] Re: [upstream] LibreOffice on Ubuntu 19.04 screws up text paragraph styling

2019-05-24 Thread Marcus Tomlinson
** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [upstream] LibreOffice on Ubuntu 19.04 screws up text paragraph
  styling

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:

  After updating Ubuntu to 19.04 documents previously created in
  LibreOffice had some of their paragraph styling wiped, e.g. a custom
  heading style was arbitrarily removed in some but not all instances in
  a document and was replaced with 'Default Style'.

  LibreOffice Version: 6.2.2.2
  Build ID: 1:6.2.2-0ubuntu2
  CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
  Calc: threaded

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Ioannis Vardas
Thanks a lot for your time, sorry I couldnt provide you with more
information. Btw is it normal that i have two different gnome runtimes
installed? I see versions 3.26 and 3.28. 3.28 is running

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Sebastien Bacher
Thanks for all the details, marking is unconfirmed, unsure what's going
on there but maybe someone else an idea...

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

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


Re: [Desktop-packages] [Bug 1830231] Re: Firefox will not connect to any website

2019-05-24 Thread Tony Morton
Yes, the same issue. I am using the Opera browser while Firefox is out 
of action, and Opera works fine. Does that help pin down a difference? 
This problem only began after the Ubuntu update on Tuesday 21st which 
was a list of system files, so maybe something that Firefox depends upon 
was changed then?

The journalctl package is not installed on my system.


On 23/05/2019 22:01, Sebastien Bacher wrote:
> Thank you for your bug report. do you get the same issue if you start a
> private browsing session? Could you add your journalctl bug?
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Firefox will not connect to any website

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Firefox will not connect to any website, it opens properly and will
  open files from my PC, there is nothing wrong with my wi-fi or
  internet connection. Any request for a web address results in the
  continuing spinning icon in the tab and it never connects to any web
  address. This follows upon Ubuntu software updates on Tuesday 21st May
  2019

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 67.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tony   2152 F pulseaudio
   /dev/snd/controlC0:  tony   2152 F pulseaudio
  BrokenPermissions:
   healthreport/state.json (0o600, wrong owner)
   sessionstore.bak (0o600, wrong owner)
  BuildID: 20190517140819
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 23 15:15:36 2019
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2018-09-30 (234 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.10 metric 600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=67.0/20190517140819
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0478VN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnInspiron660s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 660s
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Ioannis Vardas
Drive(0): Micron 1100 SATA 256GB
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
  ids:
   unix-device: '/dev/sda'
  themed icons:  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]  
[drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  
[drive-symbolic]
  symbolic themed icons:  [drive-harddisk-solidstate-symbolic]  
[drive-harddisk-symbolic]  [drive-symbolic]  [drive-harddisk-solidstate]  
[drive-harddisk]  [drive]
  is_removable=0
  is_media_removable=0
  has_media=1
  is_media_check_automatic=1
  can_poll_for_media=0
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=shutdown
  sort_key=00coldplug/00fixed/sda
  Volume(0): 185 GB Volume
Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
ids:
 class: 'device'
 unix-device: '/dev/sda4'
 uuid: 'AAF8C0AAF8C0765B'
uuid=AAF8C0AAF8C0765B
themed icons:  [drive-harddisk-solidstate]  [drive-harddisk]  [drive]  
[drive-harddisk-solidstate-symbolic]  [drive-harddisk-symbolic]  
[drive-symbolic]
symbolic themed icons:  [drive-harddisk-solidstate-symbolic]  
[drive-harddisk-symbolic]  [drive-symbolic]  [drive-harddisk-solidstate]  
[drive-harddisk]  [drive]
can_mount=1
can_eject=0
should_automount=0
sort_key=gvfs.time_detected_usec.1558706367193360
Drive(1): HGST HTS721010A9E630
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
  ids:
   unix-device: '/dev/sdb'
  themed icons:  [drive-harddisk]  [drive]  [drive-harddisk-symbolic]  
[drive-symbolic]
  symbolic themed icons:  [drive-harddisk-symbolic]  [drive-symbolic]  
[drive-harddisk]  [drive]
  is_removable=0
  is_media_removable=0
  has_media=1
  is_media_check_automatic=1
  can_poll_for_media=0
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=shutdown
  sort_key=00coldplug/00fixed/sdb
  Volume(0): Storage
Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
ids:
 class: 'device'
 unix-device: '/dev/sdb1'
 uuid: 'bdb1510a-fa72-46fc-a750-d189bfdad213'
 label: 'Storage'
uuid=bdb1510a-fa72-46fc-a750-d189bfdad213
themed icons:  [drive-harddisk]  [drive]  [drive-harddisk-symbolic]  
[drive-symbolic]
symbolic themed icons:  [drive-harddisk-symbolic]  [drive-symbolic]  
[drive-harddisk]  [drive]
can_mount=1
can_eject=0
should_automount=0
sort_key=gvfs.time_detected_usec.1558706367193231
Drive(2): HL-DT-ST DVD+/-RW GU90N
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
  ids:
   unix-device: '/dev/sr0'
  themed icons:  [drive-optical]  [drive]  [drive-optical-symbolic]  
[drive-symbolic]
  symbolic themed icons:  [drive-optical-symbolic]  [drive-symbolic]  
[drive-optical]  [drive]
  is_removable=1
  is_media_removable=1
  has_media=0
  is_media_check_automatic=1
  can_poll_for_media=0
  can_eject=1
  can_start=0
  can_stop=0
  start_stop_type=shutdown
  sort_key=00coldplug/11removable/sr0

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266282/+files/journal.log

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Sebastien Bacher
Weird, that looks like https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/285 but that one was fixed and shouldn't impact the glib
version installed :/(

Could you give the output of "gio mount -li" and attach the "journalctl
-b 0" log from a session after triggering the issue?

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #285
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/285

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-05-24 Thread Ville Ranki
I'm probably experiencing the same bug, although it happens right after
login. I can't click on windows and keyboard doesn't do anything. It can
take minutes until gnome starts working. Really annoying.

The links to related gnome bugs don't work btw.

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1829785] Re: Evince: ∞ not found

2019-05-24 Thread Md Ayquassar
And thanks very much for the fast and good solution!

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

Title:
  Evince: ∞ not found

Status in Evince:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Disco:
  Fix Committed

Bug description:
  Impact
  Case-insensitive search of unicde chars in PDF documents is broken

  Test case
  1) Open the attached document in Evince
  2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard
  3) Press Ctrl+F and paste the symbol from the clipboard into the search field

  The symbol should be found in the document

  Regression potential
  Check in different pdf renderer using poppler than search still work correctly

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

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


[Desktop-packages] [Bug 1829785] Re: Evince: ∞ not found

2019-05-24 Thread Md Ayquassar
I've tested the updated version on the input file. Looks good so far,
job well done! Feel free to close the bug report.

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

Title:
  Evince: ∞ not found

Status in Evince:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Disco:
  Fix Committed

Bug description:
  Impact
  Case-insensitive search of unicde chars in PDF documents is broken

  Test case
  1) Open the attached document in Evince
  2) Select the infinity symbol ∞ (U+221E) and copy it into clipboard
  3) Press Ctrl+F and paste the symbol from the clipboard into the search field

  The symbol should be found in the document

  Regression potential
  Check in different pdf renderer using poppler than search still work correctly

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Ioannis Vardas
** Attachment added: "dpkg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266261/+files/dpkg.txt

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Ioannis Vardas
** Attachment added: "ldd.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266260/+files/ldd.txt

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1485321] Re: Firefox 40 blank with no menu

2019-05-24 Thread Paul White
Further to comment #5 by the reporter the issue was fixed by a
configuration change.

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

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

Title:
  Firefox 40 blank with no menu

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Please do not ignore this bug report because it has not been submitted via 
Apport. Due to the severe issue with Firefox 40 I cannot currently complete the 
Apport submission process so am having to report this manually.
  Firefox was upgraded from 39.0.3+build2-0ubuntu0.12.04.1 to 
40.0+build4-0ubuntu0.12.04.1 yesterday evening (15/08/2015) and now when it 
runs the entire window is grey with no content and there is no menu. The 
computer is running Xubuntu 12.04
  Trying to run Firefox in safe mode results in a small window titled Firefox 
Safe Mode which contains just grey.
  When it is used to open help in the Xubuntu applications menu (no help 
displayed, only blank grey window) and the top right X window close symbol is 
clicked the 'Confirm close' window appears but it too is grey and has no 
content and I can only terminate the application using Task Manager. The same 
happens when I run Apport when it reaches the stage where Firefox is invoked. 
This may not be relevant but tcpdump shows when it was first opened Firefox 40 
did communicate to ec2-54-200-163-149.us-west-2.compute.amazonaws.com so it is 
capable of connections. Disabling the Firefox Apparmor profile does not make 
any difference. I will try to provide any further information requested as best 
I can. If I can provide the requested information via e-mail that would be 
preferable as Firefox is not operational and if the previous version is 
reverted to it will not exhibit the bug.

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

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


[Desktop-packages] [Bug 1826936] Re: Upgrade to 3.32.1 and SRU it

2019-05-24 Thread Iain Lane
That yaru upload is in disco-proposed now, so once it's ready to release
we can push both out together.

(Marco, maybe if you smile sweetly at the SRU team they'll let us have
less than 10 days...)

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

Title:
  Upgrade to 3.32.1 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Disco:
  Fix Committed
Status in mutter source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  The first stable release in the 3.32 series.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Most of commits were already included in stable ubuntu release, as per
  git snapshot. There are new fixes related to startup notifications and
  an X11 crash fix.

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

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


[Desktop-packages] [Bug 1000294] Re: popup rejection fails when video is selected

2019-05-24 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

Does anyone still see a problem related to the one that was reported
when using currently supported versions of Ubuntu and Firefox? Please
let us know if you do otherwise this report can be left to expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  popup rejection fails when video is selected

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  the ofending popup is zedo.com, When I sellect a video on a page it
  pops up. Used to be able to block by name but that's no longer
  available.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: firefox 12.0+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
  Uname: Linux 3.0.0-19-generic i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jack   1419 F pulseaudio
  BuildID: 20120423123513
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfdff8000 irq 44'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,1297,0011'
 Controls  : 35
 Simple ctrls  : 19
  Channel: release
  Date: Tue May 15 19:57:39 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.3  metric 2
  Plugins:
   Shockwave Flash - Lib=libflashplayer.so, Location=/usr/lib/adobe-flashplugin
   DivX® Web Player - Lib=libtotem-mully-plugin.so, 
Location=/usr/lib/mozilla/plugins
   Windows Media Player Plug-in 10 (compatible; Totem) - 
Lib=libtotem-gmp-plugin.so, Location=/usr/lib/mozilla/plugins
   VLC Multimedia Plugin (compatible Totem 3.0.1) - 
Lib=libtotem-cone-plugin.so, Location=/usr/lib/mozilla/plugins
   QuickTime Plug-in 7.6.6 - Lib=libtotem-narrowspace-plugin.so, 
Location=/usr/lib/mozilla/plugins
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=12.0/20120423123513 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to oneiric on 2012-04-28 (18 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: FP35
  dmi.board.vendor: Shuttle Inc
  dmi.board.version: V10
  dmi.chassis.type: 3
  dmi.chassis.vendor: Shuttle Inc
  dmi.chassis.version: G5
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnShuttleInc:pnSP35:pvrV10:rvnShuttleInc:rnFP35:rvrV10:cvnShuttleInc:ct3:cvrG5:
  dmi.product.name: SP35
  dmi.product.version: V10
  dmi.sys.vendor: Shuttle Inc

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

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


[Desktop-packages] [Bug 1068883] Re: firefox spams console

2019-05-24 Thread Paul White
Upstream bug #785200 is showing "RESOLVED FIXED" on 2012-09-01 in Firefox 17.
No further comments here or upstream for over 6 years so closing as fixed.

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

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

Title:
  firefox spams console

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Since the most recent upgrade, firefox emits console messages like

  OS Determining best projection for type int (size:  4 ) signed
  OS Projected as a regular number
  OS Determining best projection for type unsigned_int (size:  4 ) unsigned
  OS Projected as a regular number
  OS Determining best projection for type long (size:  8 ) signed
  OS Projected as a large signed integer
  OS Determining best projection for type int (size:  4 ) signed
  OS Projected as a regular number
  OS Determining best projection for type int (size:  4 ) signed
  OS Projected as a regular number
  OS Determining best projection for type off_t (size:  8 ) signed
  OS Projected as a large signed integer
  OS Determining best projection for type size_t (size:  8 ) unsigned
  OS Projected as a large unsigned integer
  OS Determining best projection for type ssize_t (size:  8 ) signed
  OS Projected as a large signed integer
  OS Unix Could not open libc libsystem.B.dylib
  OS Unix dirent is: ctypes.StructType("dirent", [{ "padding_0": 
ctypes.uint8_t.array(18) }, { "d_type": ctypes.uint8_t }, { "d_name": 
ctypes.char.array(261) }])
  OS Attempting to declare FFI  access
  OS Function access declared
  OS Attempting to declare FFI  chdir
  OS Function chdir declared
  OS Attempting to declare FFI  chmod
  OS Function chmod declared
  OS Attempting to declare FFI  chown
  OS Function chown declared
  OS Attempting to declare FFI  copyfile
  OS Could not declare function copyfile Error: couldn't find function symbol 
in library
  OS Attempting to declare FFI  dup
  OS Function dup declared
  OS Attempting to declare FFI  chdir
  OS Function chdir declared
  OS Attempting to declare FFI  fchdir
  OS Function fchdir declared
  OS Attempting to declare FFI  fchown
  OS Function fchown declared
  OS Attempting to declare FFI  fsync
  OS Function fsync declared
  OS Attempting to declare FFI  getcwd
  OS Function getcwd declared
  OS Attempting to declare FFI  getwd
  OS Function getwd declared
  OS Attempting to declare FFI  get_current_dir_name
  OS Function get_current_dir_name declared
  ...

  This is debugging output that was never meant for a production
  environment.

  % lsb_release -rd
  Description:Ubuntu 12.04.1 LTS
  Release:12.04

  Architecture: amd64

  % apt-cache policy firefox
  firefox:
Installed: 16.0.1+build1-0ubuntu0.12.04.1
Candidate: 16.0.1+build1-0ubuntu0.12.04.1
Version table:
   *** 16.0.1+build1-0ubuntu0.12.04.1 0
  500 http://nl.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   11.0+build1-0ubuntu4 0
  500 http://nl.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  Expected: no debugging output
  What happened: terminal window spammed with debugging output

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

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


[Desktop-packages] [Bug 1830203] Re: 1px gap next to some lists

2019-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package yaru-theme - 19.04.3

---
yaru-theme (19.04.3) disco; urgency=medium

  * gbp.conf: Update branch for ubuntu/disco
  * Sync Yaru with changes in GNOME Shell 3.32.1
- Fixes switches in VPN submenu (LP: #1829699)
- Fixes region screenshots (Shift + Print Screen) not displaying the
  region properly (LP: #1830003)
- Fixes 1px gap next to some lists (e.g. gnome-control-center's users
  panel) (LP: #1830203)
- Fixes clock on lock screen not being very readable with very bright
  backgrounds (LP: #1830335)

 -- Iain Lane   Fri, 24 May 2019 09:36:47 +0100

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  1px gap next to some lists

Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  From the upstream PR (https://github.com/ubuntu/yaru/pull/1368)

  When a viewport is inside a scrolledwindow there is 1 px gap due to
  separator's min-width visible only when the row is selected, since
  otherwise viewport and separator have the same bg color.

  To fix this, let separator's min-width be zero.

  [ QA ]

  See the attached screenshot. In the gnome-control-center users panel,
  make sure the 1px gap is gone.

  [ Regression potential ]

  As with any theme change, this could accidentally break unrelated
  applications (probably subtly given the nature of the change).

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

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


[Desktop-packages] [Bug 1830003] Re: Region screenshots don't show area being selected

2019-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package yaru-theme - 19.04.3

---
yaru-theme (19.04.3) disco; urgency=medium

  * gbp.conf: Update branch for ubuntu/disco
  * Sync Yaru with changes in GNOME Shell 3.32.1
- Fixes switches in VPN submenu (LP: #1829699)
- Fixes region screenshots (Shift + Print Screen) not displaying the
  region properly (LP: #1830003)
- Fixes 1px gap next to some lists (e.g. gnome-control-center's users
  panel) (LP: #1830203)
- Fixes clock on lock screen not being very readable with very bright
  backgrounds (LP: #1830335)

 -- Iain Lane   Fri, 24 May 2019 09:36:47 +0100

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Region screenshots don't show area being selected

Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  The region being screenshotted with Shift + PrintScreen isn't visible.

  [ QA ]

  1. Using GNOME Shell, press Shift + Print Screen. The cursor should change to 
a crosshair.
  2. Click and drag to select a region
  3. Release

  At 2, if the bug is happening, there is no visual indicator of the
  selected area.

  When it's fixed, you can see a highlight - using colours from the
  theme.

  [ Fix ]

  There was a fix in GNOME Shell's upstream theme to use the theme
  colours for this selection, and that makes it work for Yaru. The fix
  is to sync back up with upstream.

  [ Regression potential ]

  In order of most to least likely

- The fix accidentally regresses another area of the theme that we don't 
know about
- There's a syntax error, we break the theme and Shell stops loading for 
everyone (I think that's the failure mode)

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

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


[Desktop-packages] [Bug 1829699] Re: Switches are gone from the VPN menu

2019-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package yaru-theme - 19.04.3

---
yaru-theme (19.04.3) disco; urgency=medium

  * gbp.conf: Update branch for ubuntu/disco
  * Sync Yaru with changes in GNOME Shell 3.32.1
- Fixes switches in VPN submenu (LP: #1829699)
- Fixes region screenshots (Shift + Print Screen) not displaying the
  region properly (LP: #1830003)
- Fixes 1px gap next to some lists (e.g. gnome-control-center's users
  panel) (LP: #1830203)
- Fixes clock on lock screen not being very readable with very bright
  backgrounds (LP: #1830335)

 -- Iain Lane   Fri, 24 May 2019 09:36:47 +0100

** Changed in: yaru-theme (Ubuntu Eoan)
   Status: Triaged => Fix Released

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

Title:
  Switches are gone from the VPN menu

Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Disco:
  Fix Committed
Status in yaru-theme source package in Eoan:
  Fix Released

Bug description:
  [ Description ]

  There is no more switch in the system menu for the VPN entries.
  Although the VPN can still be turned on/off by clicking on the menu
  entry (cf screenshot)

  [ Fix ]

  GNOME Shell 3.32.1 shuffled some theme bits around. Yaru generally
  needs to follow Shell's changes to remain compatible. The fix is to
  sync those changes and make the corresponding modifications to Yaru.

  NOTE: there are changes in the gnome-shell/upstream directory for
  this. These are not shipped anywhere. Yaru keeps a copy of the
  upstream theme it's currently based on for three way merging purposes.

  [ QA ]

  With multiple VPNs configured, check that you get switches in the top-
  right menu. Check the attached screenshot for reference.

  [ Regression potential ]

  As with any theme change, this could accidentally break other parts of
  the shell (probably subtly given the nature of the change). This
  particular change is in the shell - not the GTK - theme, so look out
  for breakage there.

  [ ... ]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 20 06:48:13 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1769 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (421 days ago)

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

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


[Desktop-packages] [Bug 1830335] Re: Clock on lock screen isn't very readable with very bright backgrounds

2019-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package yaru-theme - 19.04.3

---
yaru-theme (19.04.3) disco; urgency=medium

  * gbp.conf: Update branch for ubuntu/disco
  * Sync Yaru with changes in GNOME Shell 3.32.1
- Fixes switches in VPN submenu (LP: #1829699)
- Fixes region screenshots (Shift + Print Screen) not displaying the
  region properly (LP: #1830003)
- Fixes 1px gap next to some lists (e.g. gnome-control-center's users
  panel) (LP: #1830203)
- Fixes clock on lock screen not being very readable with very bright
  backgrounds (LP: #1830335)

 -- Iain Lane   Fri, 24 May 2019 09:36:47 +0100

** Changed in: yaru-theme (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Clock on lock screen isn't very readable with very bright backgrounds

Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  On very bright backgrounds, such as the pictured one which is one of
  disco's default backgrounds, the clock on the lockscreen is a bit
  unreadable.

  [ Fix ]

  Increase the shadows a bit to make the text stand out. See the
  attached screenshots for reference.

  [ QA ]

  Confirm with some bright backgrounds that the legibility is better
  than before (doesn't have to be perfect, just not get worse and
  ideally be better).

  [ Regression potential ]

  As with any theme change, this could accidentally break other parts of
  the shell (probably subtly given the nature of the change). This
  particular change is in the shell - not the GTK - theme, so look out
  for breakage there.

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

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


[Desktop-packages] [Bug 1053265] Re: firefox update pane lacks controls to manage autoupdate

2019-05-24 Thread Paul White
Firefox no longer uses a panel interface to manage preferences.
Closing as bug report is no longer valid.

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

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

Title:
  firefox update pane lacks controls to manage autoupdate

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  When opening update pane in the firefox preferences window it appears
  to lack controls to manage firefox autoupdate policy (please see
  screenshot attached).

  Additional info:
  1) ~$ lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2) ~$ apt-cache policy firefox
  firefox:
Installed: 15.0.1+build1-0ubuntu0.12.04.1
Candidate: 15.0.1+build1-0ubuntu0.12.04.1
Version table:
   *** 15.0.1+build1-0ubuntu0.12.04.1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/main i386 
Packages
  100 /var/lib/dpkg/status
   11.0+build1-0ubuntu4 0
  500 http://ru.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

  3) ER: update pane contains the controls to manage firefox autoupdate
  policy

  4) AR: update pane does not contain the controls to manage firefox
  autoupdate policy

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

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


[Desktop-packages] [Bug 1010358] Re: After upgrade to Firefox 13 extensions and skins aren't fully loaded

2019-05-24 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Does anyone still see a problem related to the one that was reported
when using a currently supported version of Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  After upgrade to Firefox 13 extensions and skins aren't fully loaded

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  After upgrading the Firefox to version 13 it doesn't completely loads
  the extensions and skins any more. When going to Extras->Add-ons the
  lists for both extensions and skins are completely empty, even though
  the default skin and quite some extensions are installed. Some of the
  them are working (No-Script, Ghostery) while others display an error
  message on the start of firefox and are not working (Flagfox).

  Going to about:support also displays an empty list of extensions.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 13.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan1847 F pulseaudio
   /dev/snd/pcmC0D0p:   jan1847 F...m pulseaudio
  BuildID: 20120601175215
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf850 irq 45'
 Mixer name : 'Intel Cantiga HDMI'
 Components : 'HDA:10ec0269,144dc06d,0014 
HDA:80862802,80860101,0010'
 Controls  : 24
 Simple ctrls  : 11
  Channel: release
  CurrentDmesg:
   [   15.524361] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   22.002172] IPv6 over IPv4 tunneling driver
   [   26.240062] eth0: no IPv6 routers present
   [   31.840041] sixxs: no IPv6 routers present
  Date: Fri Jun  8 09:40:30 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.51  metric 1
  PrefErrors: Unexpected character before comma @ 
[Profile]/extensions/fire...@ghostery.com/defaults/preferences/defaults.js:26
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=13.0/20120601175215 (In use)
  RelatedPackageVersions:
   gnome-shell   3.4.1-0ubuntu2
   rhythmbox-mozilla 2.96-0ubuntu4
   totem-mozilla 3.0.1-0ubuntu21
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 05JD.M017.20100325.KSJ
  dmi.board.name: R530/R730
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr05JD.M017.20100325.KSJ:bd03/25/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: R530/R730
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Desktop-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

2019-05-24 Thread Ji-min Hong
@hui.wang

Wow, thank you.
Have a nice weekend. :-)

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 632629] Re: problem sorting files in upload-file file-chooser

2019-05-24 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported a long time ago
and there have been many changes in Ubuntu since that time.

Does anyone still see a problem related to the one that was reported
when using currently supported versions of Ubuntu and Firefox? Please
let us know if you do otherwise this report can be left to expire in
approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  problem sorting files in upload-file file-chooser

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  1) go to some image upload site
  2) click on the file-field
  3) if files are sorted by name, click to sort them by date. if sorted by 
date, sort by name
  4) now try to click on a file to upload it.
  5) BUG you cannot select the file

  workaround:
  6) click cancel
  7) open the file-chooser again
  8) the files are still sorted by the column you clicked last time
  9) you can now select the file to upload

  now it would be nice, if step 5 already worked.

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

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


[Desktop-packages] [Bug 992512] Re: Flash not working correctly

2019-05-24 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Does anyone still see a problem related to the one that was reported
when using a currently supported version of Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Flash not working correctly

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  I installed the latest Flash plugin for Firefox and noticed that the arrow 
keys are not working properly. To do a test to find this out is when going on 
this page where the arrow keys should work: 
  http://www.kinderspelletjes.nl/funspelletjes/goofyhotdogbezorger.html

  Also did other tests with other browsers like Chromium or Chrome where
  the flash content and also arrow keys were working.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 12.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hosoka 1496 F pulseaudio
   /dev/snd/pcmC0D0p:   hosoka 1496 F...m pulseaudio
   /dev/snd/controlC1:  hosoka 1496 F pulseaudio
  BuildID: 20120423122624
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'ICH5'/'Intel ICH5 with AD1980 at irq 17'
 Mixer name : 'Analog Devices AD1980'
 Components : 'AC97a:41445370'
 Controls  : 40
 Simple ctrls  : 29
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x819'/'USB Device 0x46d:0x819 at usb-:00:1d.7-6, high 
speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0819'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 6144
 Mono: Capture 6144 [100%] [27.00dB] [on]
  Channel: release
  CurrentDmesg: [   39.336030] eth0: no IPv6 routers present
  Date: Tue May  1 12:31:44 2012
  ForcedLayersAccel: False
  InstallationMedia: Lubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  IpRoute:
   default via 192.168.1.254 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.52  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Profiles: Profile0 (Default) - LastVersion=12.0/20120423122624 (Running)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-04-21 (9 days ago)
  dmi.bios.date: 07/21/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A03
  dmi.board.name: 02Y832
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA03:bd07/21/2003:svnDellComputerCorporation:pnDimension4600:pvr:rvnDellComputerCorp.:rn02Y832:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: Dimension 4600
  dmi.sys.vendor: Dell Computer Corporation

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

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


[Desktop-packages] [Bug 1734735] Re: [xenial] nm-openvpn continuously retries with bad password after receiving AUTH_FAIL locking out my account

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

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

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

Title:
  [xenial] nm-openvpn continuously retries with bad password after
  receiving AUTH_FAIL locking out my account

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

Bug description:
  I have nm-openvpn configured via the network manager gui on Xenial
  with a saved password. My organization has a password expiration
  policy of X days. If I forgot to update the saved password for nm-
  openvpn and try to VPN in, nm-openvpn tries the connection, fails
  without notice in the UI and retries until I stop it. This ultimately
  causes my account to get locked out for too many invalid auth
  attempts.

  sanitized/censored from syslog:
  Nov 27 09:11:06 carbon NetworkManager[1173]: nm-openvpn-Message: 
openvpn[4971] started
  Nov 27 09:11:06 carbon nm-openvpn[4971]: OpenVPN 2.3.10 x86_64-pc-linux-gnu 
[SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 22 2017
  Nov 27 09:11:07 carbon nm-openvpn[4971]: library versions: OpenSSL 1.0.2g  1 
Mar 2016, LZO 2.08
  Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: file 
'/home/myusername/Downloads/certs/ta.key' is group or others accessible
  Nov 27 09:11:07 carbon nm-openvpn[4971]: Control Channel Authentication: 
using '/home/myusername/Downloads/certs/ta.key' as a OpenVPN static key file
  Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: chroot will be delayed because 
of --client, --pull, or --up-delay
  Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
  Nov 27 09:11:07 carbon nm-openvpn[4971]: UDPv4 link local: [undef]
  Nov 27 09:11:07 carbon nm-openvpn[4971]: UDPv4 link remote: 
[AF_INET]10.0.28.166:1195
  Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: this cipher's block size is 
less than 128 bit (64 bit).  Consider using a --cipher with a larger block size.
  Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: this cipher's block size is 
less than 128 bit (64 bit).  Consider using a --cipher with a larger block size.
  Nov 27 09:11:07 carbon nm-openvpn[4971]: [VPNGate.example.com] Peer 
Connection Initiated with [AF_INET]10.0.28.166:1195
  Nov 27 09:11:10 carbon nm-openvpn[4971]: AUTH: Received control message: 
AUTH_FAILED
  Nov 27 09:11:10 carbon nm-openvpn[4971]: SIGUSR1[soft,auth-failure] received, 
process restarting
  Nov 27 09:11:10 carbon NetworkManager[1173]: (nm-openvpn-service:4894): 
nm-openvpn-WARNING **: Password verification failed
  Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
  Nov 27 09:11:12 carbon nm-openvpn[4971]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
  Nov 27 09:11:12 carbon nm-openvpn[4971]: UDPv4 link local: [undef]
  Nov 27 09:11:12 carbon nm-openvpn[4971]: UDPv4 link remote: 
[AF_INET]10.0.28.166:1195
  Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: this cipher's block size is 
less than 128 bit (64 bit).  Consider using a --cipher with a larger block size.
  Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: this cipher's block size is 
less than 128 bit (64 bit).  Consider using a --cipher with a larger block size.
  Nov 27 09:11:12 carbon nm-openvpn[4971]: [VPNGate.example.com] Peer 
Connection Initiated with [AF_INET]10.0.28.166:1195
  Nov 27 09:11:15 carbon nm-openvpn[4971]: AUTH: Received control message: 
AUTH_FAILED
  Nov 27 09:11:15 carbon nm-openvpn[4971]: SIGUSR1[soft,auth-failure] received, 
process restarting
  ...
  ...
  [eventually I caught on to what was happening and stopped it]
  ...
  ...
  Nov 27 09:12:00 carbon NetworkManager[1173]: nm-openvpn-Message: 
openvpn[4971]: send SIGTERM
  Nov 27 09:12:00 carbon nm-openvpn[4971]: event_wait : Interrupted system call 
(code=4)
  Nov 27 09:12:00 carbon nm-openvpn[4971]: SIGTERM[hard,] received, process 
exiting
  Nov 27 09:12:00 carbon NetworkManager[1173]: nm-openvpn-Message: 
openvpn[4971] exited with success

  
  (and yes, I know I should fix the cipher and key file permissions)

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

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

[Desktop-packages] [Bug 987146] Re: Firefox upload window opens in back sometimes

2019-05-24 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. This bug was reported some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

Does anyone still see a problem related to the one that was reported
when using a currently supported version of Ubuntu? Please let us know
if you do otherwise this report can be left to expire in approximately
60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Firefox upload window opens in back sometimes

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Use flash upload button as in zip.lv
  pressing it makes "upload select file window" in back
  http://videobin.org/+5n9/650.html

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 11.0+build1-0ubuntu0.10.04.2
  ProcVersionSignature: Ubuntu 2.6.32-40.87-generic 2.6.32.57+drm33.23
  Uname: Linux 2.6.32-40-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kangarooo   1228 F pulseaudio
   /dev/snd/pcmC0D0p:   kangarooo   1228 F...m pulseaudio
  BuildID: 20120310193829
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7df8000 irq 22'
 Mixer name : 'Realtek ALC269'
 Components : 'HDA:10ec0269,104384d3,00100100'
 Controls  : 12
 Simple ctrls  : 7
  Channel: release
  Date: Mon Apr 23 10:32:16 2012
  EtcFirefoxSyspref: Cannot parse /etc/firefox/syspref.js - [Errno 2] No such 
file or directory: '/etc/firefox/syspref.js'
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 
(20100429.4)
  IpRoute:
   10.64.64.64 dev ppp0  proto kernel  scope link  src 10.37.104.140 
   169.254.0.0/16 dev ppp0  scope link  metric 1000 
   default via 10.64.64.64 dev ppp0  proto static
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=11.0/20120310193829 (Running)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0502
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: X101
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0502:bd10/17/2011:svnASUSTeKComputerINC.:pnX101:pvrx.x:rvnASUSTeKComputerINC.:rnX101:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: X101
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.

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

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


[Desktop-packages] [Bug 982060] Re: firefox video and audio disabled

2019-05-24 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

Presumably this issue was resolved some time ago and this bug report can
now be closed? I'm changing the status to "Incomplete" to allow this
report to expire in the absence of any further comments.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
   firefox video and audio disabled

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  after loading a canonical upload sent by ubuntu on update manager, all
  video and almost all audio, went disabled on firefox only. this
  occurred prior to switching to ubuntu 11point whatever. i was still on
  10point something.   google chrome continues to operate normally w/a
  buttload of advertisement, which makes me want to choke a baby kitten.
  i want firefox enabled again. and if you really want me to use google
  chrome, help me load some ad blockers, for god sake!!(or for kitty's
  sake.)  thanks,ken

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 11.0+build1-0ubuntu0.11.04.1
  ProcVersionSignature: Ubuntu 2.6.38-14.58-generic 2.6.38.8
  Uname: Linux 2.6.38-14-generic i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kenny  1324 F pulseaudio
  BuildID: 20120310010757
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'CK8'/'NVidia CK8 with ALC850 at irq 21'
 Mixer name : 'Realtek ALC850 rev 0'
 Components : 'AC97a:414c4790'
 Controls  : 42
 Simple ctrls  : 27
  Channel: release
  Date: Sat Apr 14 20:19:49 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Ubuntu Firefox Modifications - ID=ubu...@ubuntu.com, 
Version=0.9.4, minVersion=4.0b6, maxVersion=10.*, Location=app-system-share, 
Type=extension, Active=Yes
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  IpRoute:
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.10  metric 
1 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   default via 192.168.1.1 dev eth0  proto static
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=11.0/20120310010757 (Running)
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to natty on 2012-04-11 (3 days ago)
  WifiSyslog:
   
  dmi.bios.date: 02/08/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: nVidia-nForce
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/08/2006:svn:pn:pvr:rvn:rnnVidia-nForce:rvr:cvn:ct3:cvr:

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

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


Re: [Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Ioannis Vardas
I have also sent the apport output in a previous attachment

On Fri, May 24, 2019, 2:05 PM Sebastien Bacher 
wrote:

> it would have been better to user apport to open the bug ...
>
> anyway, can you provide those info manually since you didn't use the
> reporting tool
> $ which gnome-control-cenhter
> $ ldd -r /usr/bin/gnome-control-center
> $ dpkg -l | grep libglib
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1830223
>
> Title:
>   gnome control center segmentation fault when clicking details tab
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Description:  Ubuntu 18.04.2 LTS
>   Release:  18.04
>   gnome-control-center:
> Installed: 1:3.28.2-0ubuntu0.18.04.4
> Candidate: 1:3.28.2-0ubuntu0.18.04.4
> Version table:
>*** 1:3.28.2-0ubuntu0.18.04.4 500
>   500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main
> amd64 Packages
>   100 /var/lib/dpkg/status
>1:3.28.1-0ubuntu1 500
>   500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64
> Packages
>
>   When opening the gnome-control-center it may close after some seconds.
> Additionally, if I open "Details" tab it closes and returns a segmentation
> fault. I know this issue is not new but I have
>   experienced it now.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+subscriptions
>

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Sebastien Bacher
it would have been better to user apport to open the bug ...

anyway, can you provide those info manually since you didn't use the reporting 
tool
$ which gnome-control-cenhter
$ ldd -r /usr/bin/gnome-control-center
$ dpkg -l | grep libglib

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1181807] Re: Firefox refuses to load, cannot find profile

2019-05-24 Thread Paul White
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.

Presumably your issue was resolved some time ago and this bug report can
now be closed? I'm changing the status to "Incomplete" to allow this
report to expire in the absence of any further comments.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Firefox refuses to load, cannot find profile

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Platform: Ubuntu 12.04 LTS (64-bit)
  Firefox version: 21

  What happens:
  After upgrading to Firefox 21 any attempt to launch the Firefox application 
displays an error saying the user's profile cannot be found or is invalid. (The 
exact error message is "Your Firefox profile cannot be loaded. It may be 
missing or inaccessible.") The Firefox browser then closes. Trying to launch 
the profile manager or launch Firefox with an alternative profile or in safe 
mode all produce the same error, followed by Firefox closing.

  What is expected:
  Firefox should open, or at least display the profile manager to allow users 
to fix the problem.

  Work around:
  I tried deleting my profile and, indeed, the entire ~/.mozilla directory. 
Made sure Firefox was not running. Removed/purged Firefox and re-installed. 
None of these steps corrected the problem. The only work around I've found 
which allows Firefox to run is removing Firefox 21 and installer an older 
version. Firefox 11.0, for example, is in the repositories. Warning, upgrading 
to Firefox 21 after successfully installing and running an older version causes 
the problem to occur again.

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

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


Re: [Desktop-packages] [Bug 1829540] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all

2019-05-24 Thread Luciana
Hi,
This problem is still ongoing...The comment you told me to put on that path is 
not a viable solution since the document can not be changed with the 
modifications I bring. Please figure something else. It is more than annoying, 
literally every time my computer becomes inactive this happens. 
On Monday, May 20, 2019, 5:40:45 AM GMT+3, Daniel van Vugt 
 wrote:  
 
 ** Changed in: alsa-driver (Ubuntu)
      Status: New => Incomplete

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1829540

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After computer returns from being locked, after I type my password,
  the option of where to hear the sounds from the computer appears,
  selecting speaker, still I can not hear any sound from the
  computer!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/pcmC0D0p:  luciana    2245 F...m pulseaudio
  /dev/snd/controlC0:  luciana    2245 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 17 17:07:11 2019
  DistributionChannelDescriptor:
  # This is a distribution channel descriptor
  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
  canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2019-02-15 (91 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/pcmC0D0p:  luciana    2245 F...m pulseaudio
  /dev/snd/controlC0:  luciana    2245 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0C77WG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0C77WG:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3573
  dmi.product.version: 1.4.0
  dmi.sys.vendor: Dell Inc.

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

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  After computer returns from being locked, after I type my password,
  the option of where to hear the sounds from the computer appears,
  selecting speaker, still I can not hear any sound from the
  computer!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   luciana2245 F...m pulseaudio
   /dev/snd/controlC0:  luciana2245 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May 17 17:07:11 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2019-02-15 (91 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   luciana2245 F...m pulseaudio
   /dev/snd/controlC0:  luciana2245 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0C77WG
  dmi.board.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1830358] [NEW] Screen flickering

2019-05-24 Thread Alexei Koltsov
Public bug reported:

Using Intel Graphics HD 520

Constant flickering begins after some usage. Rebooting resolves the
issue for a short while.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 06:42:19 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
InstallationDate: Installed on 2019-04-05 (49 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=26ae1f0c-87cf-450a-82e8-a4034f51425d ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.1
dmi.board.name: 07TYC2
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: NULL
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1830358

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Using Intel Graphics HD 520

  Constant flickering begins after some usage. Rebooting resolves the
  issue for a short while.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 24 06:42:19 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
  InstallationDate: Installed on 2019-04-05 (49 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=26ae1f0c-87cf-450a-82e8-a4034f51425d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Ioannis Vardas
** Attachment added: "gdb backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266192/+files/gdb_bt.txt

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

2019-05-24 Thread Ioannis Vardas
Don't know if this is done correctly

** Attachment added: "Stack Trace from  apport-retrace"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266191/+files/gnome_error.txt

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

Title:
  gnome control center segmentation fault when clicking details tab

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

Bug description:
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.4
Candidate: 1:3.28.2-0ubuntu0.18.04.4
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.4 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  When opening the gnome-control-center it may close after some seconds. 
Additionally, if I open "Details" tab it closes and returns a segmentation 
fault. I know this issue is not new but I have
  experienced it now.

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

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


[Desktop-packages] [Bug 1811230] Re: Xserver 1.20.3 stable release

2019-05-24 Thread Timo Aaltonen
will be handled as part of hwe stack update, see bug 1824111

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
   Status: New => Won't Fix

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

Title:
  Xserver 1.20.3 stable release

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Bionic:
  Won't Fix
Status in xorg-server-hwe-18.04 source package in Bionic:
  Won't Fix
Status in xorg-server source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  New upstream bugfix release for cosmic and bionic HWE backport.

  Upstream changes:

  1.20.2
  Lots of bugfixes all over the map. Thanks to all for testing and
  patches!

  Adam Jackson (8):
modesetting: Lie less in the man page
modesetting: Document Option "DoubleShadow" in the man page
xfree86: Fix Option "MaxClients" validation
modesetting: Don't free(dst) in drmmode_prop_info_copy
glamor_egl: Don't initialize on llvmpipe
glamor/egl: Avoid crashing on broken configurations
fbdevhw: Refuse to touch PCI devices on the fallback probe path
xserver 1.20.2

  Alex Goins (1):
randr: rrCheckPixmapBounding should only increase screen size

  Alexander Volkov (1):
os/xdmcp: Don't create a new socket in XdmcpReset()

  Cedric Roux (1):
miext/damage: take care of the coordinate mode in damagePolyPoint

  Dave Airlie (9):
shm: move shmsize verify before allocating the drawable.
xi: free modifiers_failed on error path. (v2)
fboverlay: move bpp checks above malloc
glamor: fix leak of fs_getcolor_source.
modesetting: get pEnt after error checks
posix_tty: free leak of xf86SetStrOption return value.
xkb: fix what looks to be a copy-paste error with first vs firstMM
mibltblt: free prgnSrcClip on error path.
devices: break after finding and removing device from lists

  Jim Qu (1):
modesetting: code refactor for PRIME sync

  Lionel Landwerlin (2):
present: fix freed pointer access
xwayland: fix access to invalid pointer

  Olivier Fourdan (3):
glx: check for indirect context in CreateContextAttribsARB()
xwayland: Remove xwl_present_window from privates on cleanup
xwayland: Use `double` for `xwl_tablet_tool`

  Peter Hutterer (1):
dix: check_modmap_change() returns Success, not true

  Pierre Ossman (1):
Switch automatic composite update to WorkQueue

  Scott Anderson (1):
xwayland: use wayland axis_discrete event

  1.20.3:
  Fixes CVE-2018-14665 (local file overwrite bugs), and a trivial fix in
  fbdevhw initialization. All users are advised to upgrade. Thanks to
  Narendra Shinde and Thomas Hoger for the report, and Matthieu Herrb for
  the fix.

  Adam Jackson (1):
xserver 1.20.3

  Matthieu Herrb (2):
Disable -logfile and -modulepath when running with elevated privileges
LogFilePrep: add a comment to the unsafe format string.

  Peter Hutterer (1):
xfree86: fix readlink call

  [Test case]
  Normal desktop usage.

  
  [Regression potential]
  This has been in disco for two months without any regressions filed, so it 
should be safe.

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

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


[Desktop-packages] [Bug 1824157] Re: Regression: Can not copy/paste files from nautilus to terminal (19.04)

2019-05-24 Thread Peter Würtz
*** This bug is a duplicate of bug 1826266 ***
https://bugs.launchpad.net/bugs/1826266

Seems to be a design choice, known for at least 8 months.

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826266

https://gitlab.gnome.org/GNOME/nautilus/issues/634

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #634
   https://gitlab.gnome.org/GNOME/nautilus/issues/634

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

Title:
  Regression: Can not copy/paste files from nautilus to terminal (19.04)

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 19.04 beta.

  I can not copy/paste nautilus folder/file path in terminal anymore. I
  think it's huge regression and should be fixed.

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

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


[Desktop-packages] [Bug 404100] Re: Merge time bar and control buttons

2019-05-24 Thread Paul White
This bug report was raised against the old interface so is no longer
valid. The new interface includes features that avoid wasting screen
space so I'm marking this as being fixed.


** Changed in: totem (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Merge time bar and control buttons

Status in One Hundred Papercuts:
  Invalid
Status in Totem:
  Invalid
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem UI should avoid wasting space in small screens. I suggest
  merging the time bar with the control buttons !!! See the screenshot
  attached

  
  Any thoughts ?

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

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


[Desktop-packages] [Bug 1830255] Re: Gnome shell freezes for about 1 minute after screen blanks. high disk usage

2019-05-24 Thread Frank van Wensveen
@Sebastien Bacher: journalctl output attached.

@Daniel van Vugt: I'll do so and get back to you.

** Attachment added: "Journal ctl output as requested"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830255/+attachment/5266185/+files/curjournal.zip

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

Title:
  Gnome shell freezes for about 1 minute after screen blanks. high disk
  usage

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After the screen is blanked following a few minutes of inactivity, the
  UI freezes for about a minute as soon as the password has been
  entered. During this time there is a lot of harddisk I/O (close to
  100%) until eventually the UI eventually unlocks and the regular
  desktop environment (showing windows, applications, desktop icons and
  what not) reappears. This happens irregularly but frequently. System
  is a Dell Inspiron 3576 laptop running Ubuntu 18.04.2 LTS and gnome-
  shell 3.28.3+git20190124-0ubuntu18.04.2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May 23 18:17:53 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-10 (378 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1830335] [NEW] Clock on lock screen isn't very readable with very bright backgrounds

2019-05-24 Thread Iain Lane
Public bug reported:

[ Description ]

On very bright backgrounds, such as the pictured one which is one of
disco's default backgrounds, the clock on the lockscreen is a bit
unreadable.

[ Fix ]

Increase the shadows a bit to make the text stand out.

[ QA ]

Confirm with some bright backgrounds that the legibility is better than
before (doesn't have to be perfect, just not get worse and ideally be
better).

[ Regression potential ]

As with any theme change, this could accidentally break other parts of
the shell (probably subtly given the nature of the change). This
particular change is in the shell - not the GTK - theme, so look out for
breakage there.

** Affects: yaru-theme (Ubuntu)
 Importance: Low
 Assignee: Iain Lane (laney)
 Status: In Progress

** Affects: yaru-theme (Ubuntu Disco)
 Importance: Low
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: yaru-theme (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: New => In Progress

** Changed in: yaru-theme (Ubuntu Disco)
   Status: New => In Progress

** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Low

** Changed in: yaru-theme (Ubuntu Disco)
   Importance: Undecided => Low

** Changed in: yaru-theme (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: yaru-theme (Ubuntu Disco)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  Clock on lock screen isn't very readable with very bright backgrounds

Status in yaru-theme package in Ubuntu:
  In Progress
Status in yaru-theme source package in Disco:
  In Progress

Bug description:
  [ Description ]

  On very bright backgrounds, such as the pictured one which is one of
  disco's default backgrounds, the clock on the lockscreen is a bit
  unreadable.

  [ Fix ]

  Increase the shadows a bit to make the text stand out.

  [ QA ]

  Confirm with some bright backgrounds that the legibility is better
  than before (doesn't have to be perfect, just not get worse and
  ideally be better).

  [ Regression potential ]

  As with any theme change, this could accidentally break other parts of
  the shell (probably subtly given the nature of the change). This
  particular change is in the shell - not the GTK - theme, so look out
  for breakage there.

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

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


[Desktop-packages] [Bug 1830225] Re: X server crashes and restarts

2019-05-24 Thread Nicola Soranzo
Hi,
thanks for the replies!
I submitted a crash at 
https://errors.ubuntu.com/oops/94fdcddc-7d5c-11e9-a64f-fa163e6cac46 .

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

Title:
  X server crashes and restarts

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Every once and then, while using the system normally, the Xwayland
  server suddendly restarts, closing all existing windows, and brings me
  back to the gdm3 login screen.

  I'm using the "GNOME" session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu4.2
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu May 23 14:39:58 2019
  DistUpgraded: 2019-03-13 22:27:08,908 DEBUG got a conffile-prompt from dpkg 
for file: '/etc/ntp.conf'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-48-generic, x86_64: installed
   virtualbox, 5.2.18, 4.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:087c]
  InstallationDate: Installed on 2019-03-11 (72 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Dell Inc. XPS 15 9570
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to bionic on 2019-03-13 (70 days ago)
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1830336] [NEW] enchant 1.6.0 outdated, pipe command '*' (save personal dictionary) does nothing

2019-05-24 Thread Juha Jeronen
Public bug reported:

[needs-packaging] enchant

enchant is a meta-spellchecker supporting multiple spellchecking
backends (hunspell, GNU aspell, hspell, Voikko, Zemberek, Apple Spell
(on Mac OS)), with an ispell-compatible pipe mode for use within
applications.

URL: https://github.com/AbiWord/enchant
License: LGPL 2.1
Notes: Enchant homepage has moved to GitHub. The old homepage at abisource.com 
was last updated in 2010.

The build steps for a released version seem standard; for details, see
e.g. http://www.linuxfromscratch.org/blfs/view/svn/general/enchant.html

Ubuntu currently has a package for enchant 1.6.0, but it is seriously
out of date (2010); latest release is 2.2.3 (2018).

Why this is important:

Enchant is the recommended interface for Voikko, the spellchecker for
Finnish. The older tmispell interface (that comes with Voikko) is
deprecated by the developers of Voikko, so Enchant is currently the only
supported option for checking both Finnish and English using the same
frontend. A common frontend is important for easy switching of
spellcheck language within applications such as Emacs and LyX.

Finnish is an agglutinative language. This prevents common spellcheckers
such as aspell from working properly, so Voikko itself is really
necessary.

The old version lacks support for the '*' command in pipe mode, so it is
unable to update the personal dictionary. This is important especially
in Emacs, because Emacs's flyspell (on-the-fly spell checker) package
uses the pipe mode and sends this command to save new words into the
personal dictionary.

With Enchant 2.2.3, this works properly. (Does not even need
configuration in Emacs other than telling it to use enchant as "the
ispell program"; Enchant itself knows where its personal dictionaries
are (~/.config/enchant), as well as which file to use for each
language.)

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


** Tags: needs-packaging

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

Title:
  enchant 1.6.0 outdated, pipe command '*' (save personal dictionary)
  does nothing

Status in enchant package in Ubuntu:
  New

Bug description:
  [needs-packaging] enchant

  enchant is a meta-spellchecker supporting multiple spellchecking
  backends (hunspell, GNU aspell, hspell, Voikko, Zemberek, Apple Spell
  (on Mac OS)), with an ispell-compatible pipe mode for use within
  applications.

  URL: https://github.com/AbiWord/enchant
  License: LGPL 2.1
  Notes: Enchant homepage has moved to GitHub. The old homepage at 
abisource.com was last updated in 2010.

  The build steps for a released version seem standard; for details, see
  e.g.
  http://www.linuxfromscratch.org/blfs/view/svn/general/enchant.html

  Ubuntu currently has a package for enchant 1.6.0, but it is seriously
  out of date (2010); latest release is 2.2.3 (2018).

  Why this is important:

  Enchant is the recommended interface for Voikko, the spellchecker for
  Finnish. The older tmispell interface (that comes with Voikko) is
  deprecated by the developers of Voikko, so Enchant is currently the
  only supported option for checking both Finnish and English using the
  same frontend. A common frontend is important for easy switching of
  spellcheck language within applications such as Emacs and LyX.

  Finnish is an agglutinative language. This prevents common
  spellcheckers such as aspell from working properly, so Voikko itself
  is really necessary.

  The old version lacks support for the '*' command in pipe mode, so it
  is unable to update the personal dictionary. This is important
  especially in Emacs, because Emacs's flyspell (on-the-fly spell
  checker) package uses the pipe mode and sends this command to save new
  words into the personal dictionary.

  With Enchant 2.2.3, this works properly. (Does not even need
  configuration in Emacs other than telling it to use enchant as "the
  ispell program"; Enchant itself knows where its personal dictionaries
  are (~/.config/enchant), as well as which file to use for each
  language.)

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

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


[Desktop-packages] [Bug 1586822] Re: Ability to set default save destination for new bookmarks

2019-05-24 Thread Sebastien Bacher
** Changed in: firefox (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Ability to set default save destination for new bookmarks

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

Bug description:
  Though I can understand the rationale for making all new bookmarks go
  into an "Unsorted Bookmarks" area, I think that it would be good if
  Firefox provided an option to allow the user to change the default
  save location for new bookmarks, because I for one don't want to have
  to move every new bookmark I make to the "Bookmarks Toolbar", I would
  like to be able to have them just go there automatically, but I can't
  currently so it would be good if there were an option to change the
  default save location of bookmarks.

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

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


[Desktop-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers

2019-05-24 Thread bjo
I'm on disco now, but I will set up a VM and test it.

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

Title:
  connection issues with Kopano IMAP servers

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

Bug description:
  * Impact
  Evolution doesn't work with Kopano IMAP servers:

  * Test case
  Configure an account on a Kopano IMAP server and try to use it from evolution

  * Regression potential
  The change is in the imap handling code so it would be good to test on a few 
different type of server that things still work correctly

  -

  3.30.1-1 has the following issue with Kopano IMAP servers:

  Disable request of BODYSTRUCTURE when its response is broken
  https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37

  In 3.30.4-1 it's fixed, so a backport to cosmic would be great.

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

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


[Desktop-packages] [Bug 1830163] Re: [nouveau] icons disappered, system unusable

2019-05-24 Thread Daniel Martinek
It started happening while I was avay from the computer. Backspace was
stuck on and delete every character of password and after it crashed wit
read only file syster error spamming something in console I did not take
picture. Might be different error/bug.


** Attachment added: "output from  journalctl command"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830163/+attachment/5266149/+files/jctl

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

Title:
  [nouveau] icons disappered, system unusable

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  the launcher bar goes into miniscule size most icons are gone (all
  icons like close button etc. look like "broken image" icon, all icons
  near the menu, where you can log out including the bar) login does not
  work and commands do not run or for example sudo throws error (I had
  to hard restart pc), but I do not remember the message. Cannot find
  anything, that would trigger it (I had some system programs failing
  before this happened). I cannot provide screenshots, becouse I do not
  know how to take one on my Zbook while not using external keyboard.

  Sorry if I mixed two issues together.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 23 08:09:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 4.18.0-20-generic, x86_64: installed
   als, master, 5.0.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] (P1000 
[Zbook 17 G5 mobile workstation]) [103c:842f]
  MachineType: HP HP ZBook 17 G5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.06.03
  dmi.board.name: 842D
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.35.00
  dmi.chassis.asset.tag: 5CD8501DGX
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.06.03:bd02/15/2019:svnHP:pnHPZBook17G5:pvr:rvnHP:rn842D:rvrKBCVersion15.35.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 17
  dmi.product.name: HP ZBook 17 G5
  dmi.product.sku: 4QH25EA#BCM
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1830096] Re: Firefox 67 in Ubuntu 18.10 thinks it's an older version

2019-05-24 Thread Olivier Tilloy
Reverting the status to "Fix Committed" because the updates to bionic,
cosmic and disco haven't been released yet.

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

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

Title:
  Firefox 67 in Ubuntu 18.10 thinks it's an older version

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

Bug description:
  Today I installed the Firefox 67 update on Ubuntu 18.04, then updated
  to Ubuntu 18.10. After this, launching Firefox gave me a "Using an
  older version of Firefox" message with only two options: create a new
  profile or quit.

  Apparently the Firefox 67 build for 18.10 thinks it's an older version
  than the Firefox 67 build for 18.04.

  For now I worked around the issue by manually installing the Firefox
  67 build for Ubuntu 18.04, which did load the existing user profile
  correctly.

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

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


[Desktop-packages] [Bug 1828665] Re: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May

2019-05-24 Thread Daniel van Vugt
It sounds like this bug is now fixed(?). If so then we don't need any
further investigation thanks.

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

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

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

Title:
  [regression] Reboot after dpkg update set invalid Graphics resolutions
  (Dual Monitor) since ~7th/8th May

Status in linux package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Now at Ubuntu 18.04.2 LTS, Gnome 3.28.2

  Deduction.  The user device settings menu for desktop control dual
  monitors offer the correct modes available.  The Bionic Beaver update
  does something different.

  Dual monitor configuration (Formerly Primary on Display Port 3840x2160
  30Hz, Secondary on HDMI 3840x2160 30Hz on a three video output Intel
  HD620) for Cancer Research using LibreOffice Calc across both.
  Upgrades permitted manually rather than auto and usually done within a
  day.  Since five months both monitors were operating HDMI (Display
  port not connected, not used) with Primary on HDMI2 and Secondary on
  HDMI1, both at 3840x2160 30Hz.  Neither monitor is capable of 60Hz at
  UHD which is quite alright for office work.  When installing such
  devices, strictly only the 3840x2160 30Hz mode is available on the
  settings page.

  After the most recent update (7/8th may), the primary screen was blank
  on reboot (abnormal) and the secondary screen showed the extended
  desktop without menus (as usual). Rebooting to see the primary was
  unsuccessful and then the secondary monitor failed completely
  (confirmed the next day as graphics card hardware, broken).  Cold
  disconnect of the secondary (awaiting repair), another boot brought up
  Primary display only yet flickering occasionally.

  Primary Display.   Considering the possibility of error in the
  graphics since the update - the Device settings (normal user page)
  revealed that the update had changed the output to HDMI 4096 lines
  (which the PC monitor can't do and the user can't select - outside
  specification).  I was in such a hurry to save it also from damage
  that I put back the resolution to 3840x2160 30Hz immediately, without
  looking at which frequency had been set with the 4096 value.  Now on
  rebooting, the display settings menu shows appropriately only
  3840x2160 30 Hz as choice.   It seems the Bionic Beaver update needed
  something else and set 4096 (which the user can't and notwithstanding
  the original user configuration).

  Secondary Display.  I don't know what it set, but it blew the monitor
  card.  The linux sent either 3840 at 60 Hz or 4096 at any frequency
  without negociation, without being able to respect the user settings.
  It's also possible that it used a very low resolution for a few
  seconds which the secondary monitor can't do either;  it's (well, it
  was) a real PC monitor with choices of DP or HDMI yet can jump into
  various modes (such as 60/75Hz for gamers). After some Ubuntu upgrades
  in the past (blank secondary screen), it was necessary to go back into
  the monitor menu to switch off again the gamer mode.

  Something similar happened in 2017 with Light Ubuntu Update.   The
  Secondary (very expensive) display making very alarming noises and
  staying blank for half a day.  Now it's truly broken (I know it's the
  driver circuit and which parts). Waiting for repair or replacement,
  the system is in use now with the same Primary PC monitor and a UHD
  television as secondary to get by.

  I worked 20 years on PC systems and monitors (for ship control) and
  accept that in the past we nearly always used a simple basic portable
  VGA monitor for system upgrades, then reconnected the user's gear
  later.  I think I'll only do (and postpone) Linux upgrades from now
  using a spare single desktop monitor at 1920x1080. That was a very
  worrying experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 11 11:21:30 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 620 
[1297:4052]
  InstallationDate: Installed on 2018-09-13 (239 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 

[Desktop-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)

2019-05-24 Thread Hui Wang
Reported to realtek.

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

Title:
  [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole
  combo jack mic doesn't detect)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple 
type. not europe type.).
  When I plug 4 pole mic into jack, It doesn't detect.
  So I can't my voice through external mic.

  My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio 
device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series High Definition Audio Controller (rev 21)).
  Internal mic works well.

  Please check 4pole external mic detection.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   jimnong1441 F...m pulseaudio
   /dev/snd/pcmC0D0p:   jimnong1441 F...m pulseaudio
   /dev/snd/controlC0:  jimnong1441 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 22 11:30:39 2019
  InstallationDate: Installed on 2017-07-27 (603 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: 내장 오디오 - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_Type: No auto-switch between inputs
  Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch
  UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago)
  dmi.bios.date: 09/06/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Garp_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BSW
  dmi.product.name: Aspire ES1-131
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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


[Desktop-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)

2019-05-24 Thread Matthew Walker
Thankyou (my bug report a duplicate of this one).

Although my third monitor is defective at the moment I will be using
three 4K horizontal (Intel HD620) to run Libreoffice Calc across all
three.

Thankyou again.

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

Title:
  Triple 4K monitor display failed (modesetting driver limited to
  8192x8192)

Status in DRI:
  Fix Released
Status in X.Org X server:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed
Status in mesa source package in Bionic:
  Fix Released
Status in xorg-server source package in Bionic:
  Confirmed

Bug description:
  Title: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Summary: Triple monitor display failed with Dell Dock (HiDPI)
  (modesetting)

  Steps:
  1. a laptop with Built-in 4K LCD
  2. Cold boot system with Dell Dock connected
  3. Connect a 4K monitor to Dock
  4. Connect 2nd 4K monitor to Dock
  5. Go to [All Settings]=>[Displays] to have the following configuration.
  Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors)
  Mirror displays: disable

  Expected results: Triple monitor display should works without issues
  Actual results: Triple monitor display failed with Dell Dock

  Additional information:
  1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04
  2. Laptop: Dell Precision 5520
  3. Dell Business Thunderbolt Dock - TB16
  https://goo.gl/vFDjpi

  WORKAROUND (UBUNTU 18.04+):
  Log in to "Ubuntu on Wayland" instead of "Ubuntu".

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07bf]
     Subsystem: Dell Device [1028:07bf]
  InstallationDate: Installed on 2017-08-29 (2 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Precision 5520
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed 
root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.11.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Desktop-packages] [Bug 1828665] Re: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May

2019-05-24 Thread Matthew Walker
For the confirmation, I'd need guidance.  Which source/mutter link to
click to reinstall the prior version (or is it all of them?).

Since writing the above report, by reflex more Ubuntu updates have been
accepted (there have been very many this week - perhaps four or five) -
new dpkg.log attached.  After each new update the resolutions and
frequencies sent to both monitors were correct;  without problem. This
morning, monitor 2 (the new one) followed the boot sequence in a mode
I've never seen before - all pink and at ordinary HD 1920 (it seems).
Then it went blank for half a second.  Then it put up the usual message
that it was changing to 4K at 30 Hz, then the desktop came up fine.

[Coincidentally, an email arrived that bug 1714178 (and my bug duplicate
1795439) have been fixed (released) to overcome the modesetting driver
8192x8192 limitation.  I may try again using three 4K horizontal
monitors - when the third is repaired.   Are the patchset and merge to
drm-tip before or after this particular incident?].

I feel to add (by experience) that the former damaged monitor 2 was
perhaps more vulnerable than most to sudden fast mode changes.  With a
previous PC (ubuntu 16.04) with Intel HD600, that monitor had to receive
a valid mode at a very specific moment (which meant the user had to
learn to push on the power buttons precisely one second apart) else the
monitor would revert immediately to high Hz modes at inferior
resolutions or shut down.   With this configuration Intel HD620 and
Ubuntu Bionic Beaver, both monitors can be on, will move to sleep mode
and wait - great!  The user can switch on the PC when they're ready.
Just to say that, perhaps monitor 2 was vulnerable to even a blip at
60Hz.

On the other hand, that doesn't explain how monitor 1 found itself
attempting 4096 which is also part of this bug report.

Can I still help in confirmation work by going back to the prior
version?


** Attachment added: "dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828665/+attachment/5266146/+files/dpkg.log

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

Title:
  [regression] Reboot after dpkg update set invalid Graphics resolutions
  (Dual Monitor) since ~7th/8th May

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Now at Ubuntu 18.04.2 LTS, Gnome 3.28.2

  Deduction.  The user device settings menu for desktop control dual
  monitors offer the correct modes available.  The Bionic Beaver update
  does something different.

  Dual monitor configuration (Formerly Primary on Display Port 3840x2160
  30Hz, Secondary on HDMI 3840x2160 30Hz on a three video output Intel
  HD620) for Cancer Research using LibreOffice Calc across both.
  Upgrades permitted manually rather than auto and usually done within a
  day.  Since five months both monitors were operating HDMI (Display
  port not connected, not used) with Primary on HDMI2 and Secondary on
  HDMI1, both at 3840x2160 30Hz.  Neither monitor is capable of 60Hz at
  UHD which is quite alright for office work.  When installing such
  devices, strictly only the 3840x2160 30Hz mode is available on the
  settings page.

  After the most recent update (7/8th may), the primary screen was blank
  on reboot (abnormal) and the secondary screen showed the extended
  desktop without menus (as usual). Rebooting to see the primary was
  unsuccessful and then the secondary monitor failed completely
  (confirmed the next day as graphics card hardware, broken).  Cold
  disconnect of the secondary (awaiting repair), another boot brought up
  Primary display only yet flickering occasionally.

  Primary Display.   Considering the possibility of error in the
  graphics since the update - the Device settings (normal user page)
  revealed that the update had changed the output to HDMI 4096 lines
  (which the PC monitor can't do and the user can't select - outside
  specification).  I was in such a hurry to save it also from damage
  that I put back the resolution to 3840x2160 30Hz immediately, without
  looking at which frequency had been set with the 4096 value.  Now on
  rebooting, the display settings menu shows appropriately only
  3840x2160 30 Hz as choice.   It seems the Bionic Beaver update needed
  something else and set 4096 (which the user can't and notwithstanding
  the original user configuration).

  Secondary Display.  I don't know what it set, but it blew the monitor
  card.  The linux sent either 3840 at 60 Hz or 4096 at any frequency
  without negociation, without being able to respect the user settings.
  It's also possible that it used a very low resolution for a few
  seconds which the secondary monitor can't do either;  it's (well, it
  was) a real PC monitor with choices of DP or HDMI yet can jump into
  various modes (such as 60/75Hz for gamers). After some 

[Desktop-packages] [Bug 1830096] Re: Firefox 67 in Ubuntu 18.10 thinks it's an older version

2019-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package firefox - 67.0+build2-0ubuntu2

---
firefox (67.0+build2-0ubuntu2) eoan; urgency=medium

  * No-change rebuild to fix the BuildID ordering between the same version of
firefox on all supported Ubuntu releases (LP: #1830096)

 -- Olivier Tilloy   Thu, 23 May 2019
13:00:20 +0200

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

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

Title:
  Firefox 67 in Ubuntu 18.10 thinks it's an older version

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

Bug description:
  Today I installed the Firefox 67 update on Ubuntu 18.04, then updated
  to Ubuntu 18.10. After this, launching Firefox gave me a "Using an
  older version of Firefox" message with only two options: create a new
  profile or quit.

  Apparently the Firefox 67 build for 18.10 thinks it's an older version
  than the Firefox 67 build for 18.04.

  For now I worked around the issue by manually installing the Firefox
  67 build for Ubuntu 18.04, which did load the existing user profile
  correctly.

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

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