date:20190924

** Changed in: oem-priority/bionic
   Status: New => Confirmed

** Changed in: oem-priority/bionic
   Importance: Undecided => High

** Changed in: oem-priority/bionic
 Assignee: (unassigned) => Cyrus Lien (cyruslien)

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

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  Confirmed
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  SRU Request:

  [Impact]
  xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  Which config let Wacom touchscreen using wacom input driver and makes
  the touchscreen act incorrectly.

  https://bugs.launchpad.net/ubuntu/+source/xf86-input-
  wacom/+bug/1774242 (comment #14)

  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

  2) Restart and see if the Wacom touchscreen works correctly. Also
  check /var/log/Xorg.0.log to see if Wacom touchscreen using libinput
  driver instead wacom driver.

  [Regression Potential]
  Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan 
and Disco.

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

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

[Desktop-packages] [Bug 1819207] Proposed package upload rejected

2019-09-24 Thread Chris Halse Rogers

An upload of ubuntu-drivers-common to bionic-proposed has been rejected
from the upload queue for the following reason: "Includes a bunch of
(hopefully!) non-functional whitespace changes. Changelog links to LP:#
1819207, marked as Won't Fix, and doesn't match the description in the
changelog.".

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

Title:
  [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic
  installation by ubuntu-drivers

Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  Won't Fix
Status in ubuntu-drivers-common source package in Bionic:
  Won't Fix
Status in open-vm-tools source package in Cosmic:
  Fix Released
Status in ubiquity source package in Cosmic:
  Won't Fix
Status in ubuntu-drivers-common source package in Cosmic:
  Won't Fix
Status in open-vm-tools source package in Disco:
  Fix Released
Status in ubiquity source package in Disco:
  Fix Released
Status in ubuntu-drivers-common source package in Disco:
  Fix Released

Bug description:
  [Rationale]
  On Ubuntu Desktop, we want to install automatically at installation time 
open-vm-tools-desktop and its dependencies to provide an improved user 
experience on first boot after installation of the guest. This method also 
provides an easy way to install the drivers after installation if they have not 
been installed at installation time.

  It is achieved adding an XB-Modaliases field to the control file for
  the record 'open-vm-tools-desktop' so ubuntu-drivers can detect the
  packages to install when running in a VMware guest and adding open-vm-
  tools to the list of whitelisted packages in ubuntu-drivers

  [Impact]
  The change adds an additional field to the control file used by 
ubuntu-drivers to detect the drivers to install automatically. In the worst 
case scenario either the field is not added or the detection by ubuntu-drivers 
fails. In both cases the package o-v-t-desktop is not installed and can still 
be installed manually.

  Note: open-vm-tools-desktop is in universe and for the final feature
  (>=Disco) it must be in main (already promoted). But for the SRU
  context (as this was accepted by Debian in 10.3.5-8) in our regular
  MRE we only cover the open-vm-tools change to "provide" the modalias.
  We do not change the ubuntu-drivers or ubiquity to depend on it - so
  no need to promote it on the SRU.

  [Test Case]
  With the patched versions of ubuntu-drivers and open-vm-tools
  1. Boot a daily ISO of Ubuntu Desktop to the live session in a VMware Guest 
(with VMWare Workstation for example)
  2. Open a terminal, make sure the package cache is up to date with the 
version of o-v-t containing the Modaliases field
  3. Run the command:
     $ ubuntu-drivers list
     and verify that o-v-t-desktop is in the output
  4. Run the command:
     $ ubuntu-drivers devices
     And verify that the output shows the details of the sys entry for this 
device
  5. Run the command:
     $ sudo ubuntu-drivers install
     and verify that the package o-v-t-desktop is installed

  [Regression Potential]
  Very Low. Package may fail to build if for some reason dh-gencontrol fails. 
Otherwise, given that the package is not already installed automatically, if 
automated installation doesn't work then we're still in the same situation than 
today.
  On ubuntu-drivers side, the change just adds o-v-t-desktop to the whitelist 
using an existing mechanism so other than a typo there is no risk of regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: open-vm-tools-desktop (not installed)
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 20:02:49 2019
  InstallationDate: Installed on 2014-07-15 (1697 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: open-vm-tools
  UpgradeStatus: Upgraded to disco on 2018-03-24 (349 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1819207/+subscriptions

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

[Desktop-packages] [Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

** Also affects: oem-priority/bionic
   Importance: Undecided
   Status: New

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

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  SRU Request:

  [Impact]
  xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  Which config let Wacom touchscreen using wacom input driver and makes
  the touchscreen act incorrectly.

  https://bugs.launchpad.net/ubuntu/+source/xf86-input-
  wacom/+bug/1774242 (comment #14)

  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

  2) Restart and see if the Wacom touchscreen works correctly. Also
  check /var/log/Xorg.0.log to see if Wacom touchscreen using libinput
  driver instead wacom driver.

  [Regression Potential]
  Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan 
and Disco.

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

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

[Desktop-packages] [Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

Please apply the patch comes from 1:0.36.1-0ubuntu2.

** Patch added: "skip-touchscreens.diff"
   
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1845285/+attachment/5291036/+files/skip-touchscreens.diff

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Cyrus Lien (cyruslien)

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in xf86-input-wacom package in Ubuntu:
  New

Bug description:
  SRU Request:

  [Impact]
  xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  Which config let Wacom touchscreen using wacom input driver and makes
  the touchscreen act incorrectly.

  https://bugs.launchpad.net/ubuntu/+source/xf86-input-
  wacom/+bug/1774242 (comment #14)

  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

  2) Restart and see if the Wacom touchscreen works correctly. Also
  check /var/log/Xorg.0.log to see if Wacom touchscreen using libinput
  driver instead wacom driver.

  [Regression Potential]
  Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan 
and Disco.

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

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

[Desktop-packages] [Bug 1845285] [NEW] SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

Public bug reported:

SRU Request:

[Impact]
xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

Section "InputClass"
Identifier "Wacom touchscreen class"
MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
MatchDevicePath "/dev/input/event*"
MatchIsTouchscreen "true"
Driver "wacom"
EndSection

Which config let Wacom touchscreen using wacom input driver and makes
the touchscreen act incorrectly.

https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242
(comment #14)

[Test Case]
1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

2) Restart and see if the Wacom touchscreen works correctly. Also check
/var/log/Xorg.0.log to see if Wacom touchscreen using libinput driver
instead wacom driver.

[Regression Potential]
Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan and 
Disco.

** Affects: xf86-input-wacom (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority

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

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

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

Bug description:
  SRU Request:

  [Impact]
  xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

  Section "InputClass"
  Identifier "Wacom touchscreen class"
  MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
  MatchDevicePath "/dev/input/event*"
  MatchIsTouchscreen "true"
  Driver "wacom"
  EndSection

  Which config let Wacom touchscreen using wacom input driver and makes
  the touchscreen act incorrectly.

  https://bugs.launchpad.net/ubuntu/+source/xf86-input-
  wacom/+bug/1774242 (comment #14)

  [Test Case]
  1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

  2) Restart and see if the Wacom touchscreen works correctly. Also
  check /var/log/Xorg.0.log to see if Wacom touchscreen using libinput
  driver instead wacom driver.

  [Regression Potential]
  Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan 
and Disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1845285/+subscriptions

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

[Desktop-packages] [Bug 1845285] [NEW] SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

You have been subscribed to a public bug:

SRU Request:

[Impact]
xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

Section "InputClass"
Identifier "Wacom touchscreen class"
MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
MatchDevicePath "/dev/input/event*"
MatchIsTouchscreen "true"
Driver "wacom"
EndSection

Which config let Wacom touchscreen using wacom input driver and makes
the touchscreen act incorrectly.

https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242
(comment #14)

[Test Case]
1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

2) Restart and see if the Wacom touchscreen works correctly. Also check
/var/log/Xorg.0.log to see if Wacom touchscreen using libinput driver
instead wacom driver.

[Regression Potential]
Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan and 
Disco.

** Affects: xf86-input-wacom (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority
-- 
SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04 
https://bugs.launchpad.net/bugs/1845285
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xf86-input-wacom in Ubuntu.

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

[Desktop-packages] [Bug 1714387] Re: browser crashes

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  browser crashes

Status in firefox package in Ubuntu:
  Expired

Bug description:
  browser crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ralix  1931 F pulseaudio
  BuildID: 20170816210634
  Channel: Unavailable
  CurrentDesktop: X-Cinnamon
  Date: Thu Aug 31 19:01:20 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)
  InstallationDate: Installed on 2017-05-08 (115 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-b1958b34-bf96-47eb-9115-57bad1170831
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816210634 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-b1958b34-bf96-47eb-9115-57bad1170831
   bp-7275c730-82cc-42ce-8a4b-5d7541170831
   bp-e79b7f29-816f-4cc1-b1c4-13e521170828
   bp-fbc669b3-0c7a-4d50-a898-dd0fb1170824
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET52W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS3PN00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: 20915
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET52W(1.20):bd11/30/2016:svnLENOVO:pn20FAS3PN00:pvrThinkPadT460s:rvnLENOVO:rn20FAS3PN00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FAS3PN00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1835957] Re: cupsd gobbles up resources

[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  cupsd gobbles up resources

Status in cups package in Ubuntu:
  Expired

Bug description:
  My computer has got very slow since 4 or 5 weeks. Finally, I checked
  resource usage with  and the culprit seems to be cupsd. Here is
  an output line from a few minutes after boot:

  30900 root  20   0  305452 287396   5768 S   5,3  9,3   0:41.34
  cupsd

  Then after an hour and a half (with nothing printed):

  30900 root  20   0 2565692 2,125g   2240 R  79,0 71,9  93:01.45
  cupsd

  So %CPU grows 5,3 -> 79,0 and %MEM, 9,3 -> 71,9. Not good.

  A user on a local forum asked whether printing anything helped, and,
  certainly, it did. After I did (print something), cupsd was happy with
  less than 1% of CPU and MEM.

  So if I print something after every boot, the problem does go away.
  But that is not really a solution, is it?

  Running Lubuntu 16.04.6 LTS (32-bit). cups version is
  2.1.3-4ubuntu0.9.

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

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

[Desktop-packages] [Bug 1675202] Re: Error Code: F7363-1260 trying to use Netflix on Firefox

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Error Code: F7363-1260 trying to use Netflix on Firefox

Status in firefox package in Ubuntu:
  Expired

Bug description:
  How to watch Netflix using Firefox normally?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 52.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-41-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomasz 1555 F pulseaudio
  BuildID: 20170317212436
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Wed Mar 22 23:13:07 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)
  InstallationDate: Installed on 2017-03-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  IpRoute:
   default via 192.168.1.1 dev wlp5s0  proto static  metric 600 
   169.254.0.0/16 dev wlp5s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp5s0  proto kernel  scope link  src 192.168.1.103  
metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   prefs.js
   
[Profile]/extensions/flashli...@stephennolan.com.au/defaults/preferences/prefs.js
  ProcEnviron:
   LANGUAGE=pl
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=52.0.1/20170317212436 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K50IN
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr207:bd05/08/2009:svnASUSTeKComputerInc.:pnK50IN:pvr1.0:rvnASUSTeKComputerInc.:rnK50IN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.name: K50IN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 61002]

2019-09-24 Thread Bencriss64

(In reply to Joseph from comment #0)
> User-Agent:   Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.8.1b1) Gecko/20060803 BonEcho/2.0b1
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.8.1b1) Gecko/20060803 BonEcho/2.0b1
> 
> Bug 337654 removed UI elements from the Quick Find bar under the assumption
> that Quick Find is an accessibility feature with different needs than Find. 
> While this may be true for users who choose to invoke it using / or '
> instead of Ctrl+F, one class of users was overlooked: those who use the
> typeaheadfind.autostart pref as a way to invoke Find behavior without any
> extra keystroke.
> 
> For these users, an appropriate behavior change would be to make the
> autostart pref bring up the Find bar rather than QuickFind bar, leaving
> QuickFind as a separate feature focused on accessibility needs.  Since
> autostart FAYT always searches text rather than just links as in QuickFind
> invoked with the apostrophe, there is little search functionality difference
> between auto FAYT and the Find bar except the now missing UI elements. 
> Without this change, the visual differentiation (from bug 337654) has
> reduced user confusion but also acts as a functional regression, since there
> is now no way to truly start FINDing when you begin typing.
> 
> Discussion of the loss of autostart FAYT functionality due to the QuickFind
> changes can be found in these three MozillaZine threads:
> https://pornogratisaqu.com/es/category/242/Facial/popular/1/
> http://forums.mozillazine.org/viewtopic.php?t=437010
> http://forums.mozillazine.org/viewtopic.php?t=436989
> http://forums.mozillazine.org/viewtopic.php?t=446362
> 
> Reproducible: Always

thx nice

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

Title:
  Mozilla Firefox: No buttons at Quick Find

Status in Mozilla Firefox:
  Won't Fix
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: mozilla-firefox

  Hello,

  i just install Ubuntu Edgy (6.10) to test it. And one of the first
  failures i saw was that there a no buttons at Quick Find (Edit »
  Preferences » Advanced » General » Search for text when i typing) in
  firefox. Hope this is a bug and not intention.

  Find » http://img206.imageshack.us/img206/1818/firefoxbug2gy7.png
  Quick Find » http://img224.imageshack.us/img224/7149/firefoxbugcp6.png

  cheers
  Sascha

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

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

[Desktop-packages] [Bug 1845000] Re: evince assert failure: double free or corruption (!prev)

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

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

Title:
  evince assert failure: double free or corruption (!prev)

Status in Evince:
  New
Status in evince package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/evince/issues/1246

  ---

  I'm working with .pdf

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evince 3.32.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: double free or corruption (!prev)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 09:20:00 2019
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2018-12-02 (294 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: evince
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption 
(!prev)") at malloc.c:5332
   _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, 
have_lock=) at malloc.c:4317
   g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: evince assert failure: double free or corruption (!prev)
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

** Changed in: ibus
   Status: New => Fix Released

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in ibus:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Unknown

Bug description:
  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed! 
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845281] [NEW] /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_get_workspaces

2019-09-24 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic cosmic disco eoan

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

Title:
  /usr/bin/gnome-
  
shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_get_workspaces

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1832651] Re: jackdbus fails to start: cannot allocate memory

2019-09-24 Thread Brian Murray

I was unable to recreate this on an installation of Eoan, which will
become Ubuntu 19.10, using systemd version 241-7ubuntu1 and jackd2
version 1.9.12~dfsg-2build1 subsequently I'm setting the Eoan task to
Fix Released.

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

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

Title:
  jackdbus fails to start: cannot allocate memory

Status in systemd:
  Fix Released
Status in jackd2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in jackd2 source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  The `.log/jack/jackdbus.log` shows the following after trying to
  start/restart jack using "Ubuntu Studio Controls" (also tried using
  `jack_control start`):

  ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate
  memory)

  This is a fresh install of Ubuntu Studio 19.04, installed via USB. The
  first thing I did after installing was check to see if jack was
  running, but unfortunately it's not working. The error would seem to
  indicate that I'm not in the `audio` group, however checking `groups`
  shows that I am in the audio group.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: jackd2 1.9.12~dfsg-2build1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6
  Uname: Linux 5.0.0-13-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jun 12 18:13:25 2019
  InstallationDate: Installed on 2019-06-12 (0 days ago)
  InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 
(20190416)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: jackd2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2019-09-24 Thread pepster

Still a problem for me (Kubuntu 19.04), even with uBlock installed.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

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

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.

  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

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

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

[Desktop-packages] [Bug 452073]

2019-09-24 Thread Qa-admin-q

Dear Jérôme,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [Upstream] Shouldn't detect configuration at each invocation

Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  New
Status in libreoffice package in Ubuntu:
  Incomplete
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  At each invocation of oocalc, oowriter or ooimpress, the
  /usr/lib/openoffice/program/soffice shell script is executed.

  This script will quite always guess the same environment variables.
  Moreover, guessing those values is time consuming at the well known
  critical startup time of openoffice.

  I think we could cache the below environment settings into a 
/var/lib/openoffice/basis3.1/program/environment.sh file:
  -
  FILE_LOCKING=auto
  OPENGL_SUPPORT=no
  SAL_ENABLE_FILE_LOCKING=1
  SAL_NOOPENGL=true
  JITC_PROCESSOR_TYPE=6
  sd_cwd=/usr/lib/openoffice/program
  sd_binary=/usr/lib/openoffice/program/oosplash.bin
  -

  Those environment settings could be calculated again by an apt trigger
  or a daily cron task.

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct 15 12:46:20 2009
  Dependencies:
   
  DistroRelease: Ubuntu 9.10
  Package: openoffice.org-common 1:3.1.1-4ubuntu1 [modified: 
var/lib/openoffice/basis3.1/share/config/javasettingsunopkginstall.xml]
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic i686

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

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

[Desktop-packages] [Bug 1772439]

2019-09-24 Thread Qa-admin-q

Dear vaaydayaasra,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  Arabic text gets deformed when creating a PDF in LibreOffice Writer

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

Bug description:
  Creating a PDF from a document written in the Arabic script deforms
  the textual content of the document, although it looks fine on the
  screen.

  For example, see the attached PDF created with Writer, where the
  example sentence "اشترى بلال خمسة آلاف كتاب وَأَنَا اشْتَرَيْتُهَا
  مِنْهُ" looks as it should, but when you view it with any PDF reader,
  such as evince, copying the text deforms most of the words. Some
  characters are clearly visible but cannot be selected or searched
  (such as ى at the end of the first word اشترى). If I search for the
  second word بلال, evince tells me there are no matches in the
  document. The same happens when converting the file with pdftotext,
  which produces the following output:

  ‫اشتر‬

  ‫للا مسة لفا كتاب وَأَنَا ْ‬
  ‫ه‬
  ‫اشت َ َريْتُهَا ِ‬
  ‫من ْ ُ‬

  Here only two of the seven words are intact, the rest are garbled in
  one way or another. If the text is in Latin script, both evince and
  pdftotext behave as expected, meaning that the textual content is
  transferred correctly from Writer to the PDF.

  Description:  Ubuntu 17.10
  Release:  17.10

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

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

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

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

[Desktop-packages] [Bug 1772445]

2019-09-24 Thread Qa-admin-q

Dear vaaydayaasra,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  Text cannot be rotated in a RTL table in LibreOffice Writer

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

Bug description:
  Text can normally be rotated either 90 or 270 degrees through the
  Character > Position dialog box. This works even in tables, but only
  if the table’s text direction is set to Left-to-right. If the table’s
  text direction is set to Right-to-left through the Table properties
  dialog, no rotation takes effect. See the screenshot of a document,
  where there are two identical tables, one marked as LTR and the other
  as RTL. Text is rotated as expected in the LTR table, while nothing
  seems to happen in the other one.

  Description:  Ubuntu 17.10
  Release:  17.10

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

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

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

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

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

2019-09-24 Thread hellscream

I found a workaround this problem.
Check my git
https://github.com/WillyWeiss/-Avahi-daemon-withdraws-address-record-/blob/master/README.md

I just a simple bash that check for a valid IP Address on a given card. 
If the IP is not found then 'dhclient' will be called on that given 
interface(card)
It is working by default on eth0 but you can add more cards in the script. Just 
read the readme in the git above. 

Hope it helps.

Prove of functionality:
Sep 24 16:47:40 MyHostName rngd[395]: stats: Entropy starvations: 0
Sep 24 16:47:40 MyHostName rngd[395]: stats: Time spent starving for entropy: 
(min=0; avg=0.000; max=0)us
Sep 24 16:47:46 MyHostName avahi-daemon[380]: Withdrawing address record for 
192.168.0.13 on eth0.
Sep 24 16:47:46 MyHostName avahi-daemon[380]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.13.
Sep 24 16:47:46 MyHostName avahi-daemon[380]: Interface eth0.IPv4 no longer 
relevant for mDNS.
Sep 24 16:47:47 MyHostName dhclient[4487]: DHCPREQUEST for 192.168.0.13 on eth0 
to 255.255.255.255 port 67
Sep 24 16:47:47 MyHostName dhclient[4487]: DHCPACK of 192.168.0.13 from 
192.168.0.1
Sep 24 16:47:47 MyHostName avahi-daemon[380]: Joining mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.13.
Sep 24 16:47:47 MyHostName avahi-daemon[380]: New relevant interface eth0.IPv4 
for mDNS.
Sep 24 16:47:47 MyHostName avahi-daemon[380]: Registering new address record 
for 192.168.0.13 on eth0.IPv4.
Sep 24 16:47:47 MyHostName dhclient[4487]: bound to 192.168.0.13 -- renewal in 
41664 seconds.

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

Title:
  Avahi-daemon withdraws address record

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

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

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

  
  for no known reason.

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

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

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

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

[Desktop-packages] [Bug 1603430] Re: Firefox dropdowns in wrong location

2019-09-24 Thread Joshua Trees

I'm on elementary OS (based on Ubuntu 18.04) and also experience this
issue. As Tigran mentioned, disabling the Title Bar functions as a
workaround.

I presume the Client Side Decoration feature is what introduced this bug
in the first place.

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

Title:
  Firefox dropdowns in wrong location

Status in Linux Mint:
  New
Status in cinnamon-desktop-environment package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  On Mint 17.3 Cinnamon 64bit.

  Steps to reproduce:
   * Do a fresh install.
   * Run mintupdate and update all packages.
   * Run firefox. 
   * Start right clicking on the page to open the context menu. Resize the 
window and perhaps move it around the screen a couple of times. Right click 
some more. 
   * Observer that, eventually, the context menu will start to appear in 
incorrect locations on the screen. The same also happens with the search bar, 
text fields and any other dropdown box.

  In the worst embodiment of the bug, the menu opens underneath the
  pointer and treats the release of the mouse button as a click, and so
  does things the user does not want to do.

  I believe the root cause is the following bug in GTK+ 3.10.8. Firefox
  switched over to using GTK+3 in version 46 which is when this bug
  appeared and has been there ever since.

  https://bugzilla.gnome.org/show_bug.cgi?id=758609
  https://bugzilla.mozilla.org/show_bug.cgi?id=1022241

  Mozilla aren't going to fix it because it's a GTK bug. GTK have
  already fixed it. But Mint 17.3 remains on GTK+ 3.10.8 which does not
  have the patch.

  Please roll out the patch for us 17.3 users who cannot upgrade. I can
  confirm that the problem is solved in Mint 18.

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

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

[Desktop-packages] [Bug 1691693] Re: package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitt

2019-09-24 Thread seebers

Hi Jeff, thanks that helped. Same problem was here.

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

Title:
  package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade:
  unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new':
  Operation not permitted

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I was trying to upgrade to 17.04 and the error plus loads of others
  came up. Even after partial upgrade again.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-common 1:5.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Thu May 18 10:27:56 2017
  DuplicateSignature:
   package:libreoffice-common:1:5.2.2-0ubuntu2
   Unpacking libreoffice-common (1:5.3.1-0ubuntu2) over (1:5.2.2-0ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-lHfAqY/17-libreoffice-common_1%3a5.3.1-0ubuntu2_all.deb 
(--unpack):
unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': Operation not permitted
  InstallationDate: Installed on 2016-02-19 (453 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.2.2-0ubuntu2 failed to install/upgrade: 
unable to open '/usr/lib/libreoffice/share/gallery/sg36.sdg.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1402793] Re: [ABRA A7 V1, VIA VT1802, Green Headphone Out, Front] No sound at all

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

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

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

Title:
  [ABRA A7 V1, VIA VT1802, Green Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I can get sound from speakers but I can't get my jack to work. I tried
  many things with no help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fma2341 F pulseaudio
   /dev/snd/controlC1:  fma2341 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Dec 15 21:04:39 2014
  InstallationDate: Installed on 2014-07-08 (159 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1601 F pulseaudio
fma2341 F pulseaudio
   /dev/snd/controlC1:  lightdm1601 F pulseaudio
fma2341 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [ABRA A7 V1, VIA VT1802, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: MONSTER
  dmi.bios.version: ABRA A7 V1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: ABRA A7 V1
  dmi.board.vendor: MONSTER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: MONSTER
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnMONSTER:bvrABRAA7V1:bd04/08/2014:svnMONSTER:pnABRAA7V1:pvrNotApplicable:rvnMONSTER:rnABRAA7V1:rvrNotApplicable:cvnMONSTER:ct9:cvrN/A:
  dmi.product.name: ABRA A7 V1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: MONSTER
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-12-04T18:12:09.578053

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

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

[Desktop-packages] [Bug 1822351] Re: Nautilus does not open after updating to 19.04

2019-09-24 Thread Dominic Mayers

Also in case that helps, I experience the same bug. In addition, #2 did
not work for me. Immediately after executing "tracker reset -e" on a
shell, nautilus shows instantly after a click, but the problem comes
back at the next reboot.

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

Title:
  Nautilus does not open after updating to 19.04

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 19.04 dev branch, nautilus does not open at
  all. Moreover, trying to open nautilus from the terminal does not give
  any error, nor any output at all, and no window opens.

  I don't really know how to report this bug without any terminal
  output.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 29 13:58:12 2019
  InstallationDate: Installed on 2018-02-23 (398 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1845000] Re: evince assert failure: double free or corruption (!prev)

2019-09-24 Thread El jinete sin cabeza

https://gitlab.gnome.org/GNOME/evince/issues/1246

** No longer affects: evince

** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1246
   https://gitlab.gnome.org/GNOME/evince/issues/1246

** Also affects: evince via
   https://gitlab.gnome.org/GNOME/evince/issues/1246
   Importance: Unknown
   Status: Unknown

** Description changed:

- https://gitlab.gnome.org/GNOME/evince/issues/1259
+ https://gitlab.gnome.org/GNOME/evince/issues/1246
  
  ---
  
  I'm working with .pdf
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evince 3.32.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: double free or corruption (!prev)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 09:20:00 2019
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2018-12-02 (294 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: evince
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption 
(!prev)") at malloc.c:5332
   _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, 
have_lock=) at malloc.c:4317
   g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: evince assert failure: double free or corruption (!prev)
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

Title:
  evince assert failure: double free or corruption (!prev)

Status in Evince:
  Unknown
Status in evince package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/evince/issues/1246

  ---

  I'm working with .pdf

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evince 3.32.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: double free or corruption (!prev)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 09:20:00 2019
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2018-12-02 (294 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: evince
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption 
(!prev)") at malloc.c:5332
   _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, 
have_lock=) at malloc.c:4317
   g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: evince assert failure: double free or corruption (!prev)
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1845000] Re: evince assert failure: double free or corruption (!prev)

** Changed in: evince
   Status: New => Fix Released

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

Title:
  evince assert failure: double free or corruption (!prev)

Status in Evince:
  Fix Released
Status in evince package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/evince/issues/1259

  ---

  I'm working with .pdf

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evince 3.32.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: double free or corruption (!prev)
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 09:20:00 2019
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2018-12-02 (294 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  Signal: 6
  SourcePackage: evince
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption 
(!prev)") at malloc.c:5332
   _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, 
have_lock=) at malloc.c:4317
   g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: evince assert failure: double free or corruption (!prev)
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1845236] [NEW] ukuu won't stop alerting

2019-09-24 Thread Jason H

Public bug reported:

I left the computer on, and there was a ukuu message about a new kernel
version. I left it on for some time, ignoring the message. Now I have
88(!) ukuus to close.

It should stop with just one.

** Affects: ukuu
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot from 2019-09-24 13-06-53.png"
   
https://bugs.launchpad.net/bugs/1845236/+attachment/5290982/+files/Screenshot%20from%202019-09-24%2013-06-53.png

** Package changed: libreoffice (Ubuntu) => ukuu

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

Title:
  ukuu won't stop alerting

Status in Ubuntu Kernel Upgrade Utility:
  New

Bug description:
  I left the computer on, and there was a ukuu message about a new
  kernel version. I left it on for some time, ignoring the message. Now
  I have 88(!) ukuus to close.

  It should stop with just one.

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

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

[Desktop-packages] [Bug 1845232] [NEW] Launcher mouse input only working on 1 of 2 monitors installed

2019-09-24 Thread Rick

Public bug reported:

unity-lens-applications "Ubuntu 16.04.6 LTS"

I have two monitors stacked above/below. Launcher set for bottom and
available to be seen on both monitors. If the SUPER key is hit while the
mouse is in the upper monitor window the mouse is able to click on any
icon loaded via search. If the SUPER key is hit while the mouse is in
the lower no mouse click input works and I must resort to using the
arrow keys to highlight any returned search icons.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity-lens-applications 7.1.0+16.04.20160701-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-64-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 24 12:00:30 2019
InstallationDate: Installed on 2018-08-31 (388 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: unity-lens-applications
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-lens-applications (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-lens-applications in Ubuntu.
Matching subscriptions: dp-unity-lens-music
https://bugs.launchpad.net/bugs/1845232

Title:
  Launcher mouse input only working on 1 of 2 monitors installed

Status in unity-lens-applications package in Ubuntu:
  New

Bug description:
  unity-lens-applications "Ubuntu 16.04.6 LTS"

  I have two monitors stacked above/below. Launcher set for bottom and
  available to be seen on both monitors. If the SUPER key is hit while
  the mouse is in the upper monitor window the mouse is able to click on
  any icon loaded via search. If the SUPER key is hit while the mouse is
  in the lower no mouse click input works and I must resort to using the
  arrow keys to highlight any returned search icons.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-lens-applications 7.1.0+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-64.73~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 24 12:00:30 2019
  InstallationDate: Installed on 2018-08-31 (388 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: unity-lens-applications
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1845232/+subscriptions

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

[Desktop-packages] [Bug 1424201]

2019-09-24 Thread Robert Mader

That should be bug 1572697 for Wayland.

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

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

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

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

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

[Desktop-packages] [Bug 1845017] Re: Desktop hard lockup in 19.10

https://paste.ubuntu.com/p/x8NhtvZXG5/

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

Title:
  Desktop hard lockup in 19.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris).

  Had a few desktop shell lockups. Pattern seems to be when running snap
  refresh, but this time happened when running snapcraft --use-lxd.
  Feels like something related to mounting / unmounting devices. Got
  this from the journal.

  Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: 
dock._settings is undefined
   
_showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1
   
_enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 23 16:52:06 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (595 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago)

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

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

[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login

https://paste.ubuntu.com/p/x8NhtvZXG5/

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

Title:
  GNOME Shell seemingly locked up at login

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Eoan:
  Confirmed

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

[Desktop-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode

2019-09-24 Thread Imre Péntek

Hello, if I can help you (by providing more info, etc) to fix this
please let me know. Thank you in advance

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

Title:
  click position is flipped to cursor position when in tent mode

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  same bug is present 18.04 and 18.10:

  after I log in in tent mode the screen goes upside down, and after

  xrandr --output eDP-1 --rotate normal

  it goes back to normal however now the cursor is upside down, and
  click position and cursor position isnt the same, they are flipped

  thank you for the fix in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: coreutils 8.28-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 04:28:21 2018
  ExecutablePath: /bin/sleep
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1950 F pulseaudio
   /dev/snd/controlC1:  imi1950 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.60
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1333 F pulseaudio
   /dev/snd/controlC1:  imi1333 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-10-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/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.49
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.71
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1424201]

2019-09-24 Thread Akarshanbiswas

@grmat libplacebo is a renderer not a hardware decoder and is unfit to
be used in a browser. First thing we need dmabuf support so that we can
import decoded frames without copying them back to the system RAM and
then display it on the screen. If I understand it correctly this is the
toughest part.

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

Title:
  Web browsers lacking hardware-accelerated video decoding

Status in Chromium Browser:
  Unknown
Status in Mozilla Firefox:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in chromium-browser package in CentOS:
  Unknown

Bug description:
  The chromium team has done a great job to totally disable hardware
  decoding on Linux.

  Even ignoring the GPU blacklist does not enable GPU decoding.

  How ever the patch is quite simple and it's already working using this
  PPA ( using libVA ) :

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

  the corresponding patch is here :

  http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium-
  browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff

  that would be great if we could have this patch indefault Ubuntu
  chromium build, this situation is really sad right now, google use
  linux to make chromeOS so chromebook are really good at playing videos
  but GNU/Linux chromium is slow at doing it.

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

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

[Desktop-packages] [Bug 1845210] Re: Software Centre flickers alot during use on Eoan beta

2019-09-24 Thread David Pearson

Update, this only seems to happen when Gnome Software ids the only
window open. Although it still causes the XFCE Panel to flicker

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

Title:
  Software Centre flickers alot during use on Eoan beta

Status in gnome-software package in Ubuntu:
  New

Bug description:
  After fresh install of the Beta of Eoan for Xubuntu, the window for
  Software keeps flickering as you try to use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 24 14:31:55 2019
  InstallationDate: Installed on 2019-09-24 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190924.1)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu10
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.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/ubuntu/+source/gnome-software/+bug/1845210/+subscriptions

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

[Desktop-packages] [Bug 1748429] Re: [snap] Libreoffice uses the adwaita gtk theme

2019-09-24 Thread Marcus Tomlinson

Is this still an issue? Please run `snap connections` and ensure that
the following appears in the output:

content[gtk-3-themes] libreoffice:gtk-3-themes gtk-common-themes:gtk-3-themes -
content[icon-themes]  libreoffice:icon-themes  gtk-common-themes:icon-themes  -
content[sound-themes] libreoffice:sound-themes gtk-common-themes:sound-themes -

If not, you'll need to run `snap install gtk-common-themes` to install
the required themes. Then try LibreOffice again to see if there is any
improvement.

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

Title:
  [snap] Libreoffice uses the adwaita gtk theme

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10

  Installed the snap via

  https://forum.snapcraft.io/t/call-for-testing-libreoffice-6-0-0/3917 
  sudo snap install libreoffice --candidate

  

  Libreoffice 6 snap uses adwaita gtk

  Libreoffice 6 snap uses a hard path to the icon instead of the
  freedesktop spec

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

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

[Desktop-packages] [Bug 1845210] Re: Software Centre flickers alot during use on Eoan beta

2019-09-24 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845210

** Tags added: iso-testing

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

Title:
  Software Centre flickers alot during use on Eoan beta

Status in gnome-software package in Ubuntu:
  New

Bug description:
  After fresh install of the Beta of Eoan for Xubuntu, the window for
  Software keeps flickering as you try to use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 24 14:31:55 2019
  InstallationDate: Installed on 2019-09-24 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190924.1)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu10
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.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/ubuntu/+source/gnome-software/+bug/1845210/+subscriptions

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

[Desktop-packages] [Bug 505765] Re: gedit problem with long lines

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

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

Title:
  gedit problem with long lines

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

Bug description:
  Binary package hint: gedit

  Hi,

  I was editing a text file when the cursor began to behave strangely.
  The file contained these lines:

  CREATE TABLE people(
   integer primary key,
   name varchar(50),
   age integer
  )

  When I put the cursor after the 'l' in 'people', the arrow key would
  not move the cursor to the right. Instead it jumped to the next line.
  Similarly, I could not add text at this position.

  Viewing the file in a hex editor revealed a lot of spaces (284 to be
  accurate) after the opening parenthesis. Probably I've added those
  spaces without knowing it (resting my book "beginning Ruby" on the
  space bar ^ ^). Still, I feel the editor should handle a few hundred
  chars on a line without misbehaviour.

  I attached a copy of the text file.

  Thanks for developing and maintaining this simple but useful editor!

  Tor

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gedit
  Package: gedit 2.26.1-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  Tags:  ubuntu-unr
  Uname: Linux 2.6.28-17-generic i686

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

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

[Desktop-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon

This bug was fixed in the package unity - 7.5.0+19.10.20190924-0ubuntu1

---
unity (7.5.0+19.10.20190924-0ubuntu1) eoan; urgency=medium

  [ Khurshid Alam ]
  * Port media keys to use com.canonical.unity.settings-daemon. LP:
#1842324 (LP: #1842324)

  [ Tasos Sahanidis ]
  * Fix gcc 7.2 build errors

 -- Marco Trevisan (Treviño)   Tue, 24 Sep 2019 09:46:52
+

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

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

Title:
  Port schemas from gnome-settings-daemon-common to com.canonical.unity
  .settings-daemon

Status in indicator-session package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  Unity-settings-daemon still depends on gnome-settings-daemon schemas.
  It is undesired as it requires to modify code in all unity related
  components when upstream drops some gsettings schemas.

  gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an
  undesired way that it can't easily be reverted. Keyboard & mouse
  schemas are modified and unity-settings-daemon is crashing. So it's
  better unity uses it's own schema as suggested by Laney. We will of-
  course keep using settings migration (org.gnome.settings-daemon->
  org.gnome.desktop) wherever possible.

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768

  Since this is a huge task it can be achieved gradually.

  1) Ubuntu 19.10

  - Port media keys to use com.canonical.unity.settings-daemon

  - u-s-d will still use org.gnome.settings-daemon name in dbus

  - u-s-d will still respects activation toggle in org.gnome.settings-
  daemon

  - everything else remains the same

  2) Ubuntu 20.04

  - Port rest of plugins to use com.canonical.unity.settings-daemon

  - u-s-d will still use org.gnome.settings-daemon name in dbus

  - Activation toggle key will now use com.canonical.unity.settings-
  daemon

  - Everything else will remain the same

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

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

[Desktop-packages] [Bug 1842904] Re: New upstream release 19.01.4

2019-09-24 Thread Sebastien Bacher

(we untargetted in team review since it didn't go through the rls-dd-
incoming process, but feel free to reassign to yourself if you want to
work on it)

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

Title:
  New upstream release 19.01.4

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  New upstream release 19.01.4 is mostly needed to get the fix for bug
  1815550 (memory leaks) into disco. But we also need eoan to update to
  that release before we can do disco, presumably.

  https://gitlab.gnome.org/World/ShellExtensions/desktop-
  icons/-/releases

  [Test Case]

  See bug 1815550.

  [Regression Potential]

  Low. The current upstream stable release is just a bug fix release on
  the same series as what's already in disco and eoan.

  [Other Info]

  Most of the SRU for disco will be tracked in bug 1815550. But we need
  this bug separately to track the release of 19.01.4 into eoan first.

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

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

[Desktop-packages] [Bug 1842904] Re: New upstream release 19.01.4

** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu Disco)

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

Title:
  New upstream release 19.01.4

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  New upstream release 19.01.4 is mostly needed to get the fix for bug
  1815550 (memory leaks) into disco. But we also need eoan to update to
  that release before we can do disco, presumably.

  https://gitlab.gnome.org/World/ShellExtensions/desktop-
  icons/-/releases

  [Test Case]

  See bug 1815550.

  [Regression Potential]

  Low. The current upstream stable release is just a bug fix release on
  the same series as what's already in disco and eoan.

  [Other Info]

  Most of the SRU for disco will be tracked in bug 1815550. But we need
  this bug separately to track the release of 19.01.4 into eoan first.

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

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

[Desktop-packages] [Bug 1843763] Re: [SRU] libreoffice 6.2.7 for disco

2019-09-24 Thread Marcus Tomlinson

** Changed in: libreoffice-l10n (Ubuntu)
   Status: In Progress => Fix Released

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

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

Title:
  [SRU] libreoffice 6.2.7 for disco

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.2.7 is in its seventh bugfix release of the 6.2 line.
     For a list of fixed bugs compared to 6.2.6 see:
   https://wiki.documentfoundation.org/Releases/6.2.7/RC1#List_of_fixed_bugs
     (that's a total of 32 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 32 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke 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/1843763/+subscriptions

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

[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login

** Also affects: gnome-shell (Ubuntu Eoan)
   Importance: Critical
   Status: Confirmed

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

** Tags removed: rls-ee-incoming

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

Title:
  GNOME Shell seemingly locked up at login

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Eoan:
  Confirmed

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

[Desktop-packages] [Bug 1845188] Re: Ubuntu 19.10 Community Wallpapers

** Changed in: ubuntu-wallpapers (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Tags removed: rls-ee-incoming

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

Title:
  Ubuntu 19.10 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.10 (minus one where the artists didn't reply to my emails).

  These have been resized (and where needed cropped) to 3840 x 2160.

  I've put them all through Squoosh.  Most are JPGs, but one is a PNG,
  the gradients didn't respond well to being JPGed.  I have tried to
  keep the size below 500k where ever I can, but in some cases it has
  gone over in order to keep the quality acceptable.

  Total size of the wallpapers is 5.6MB.

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

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

[Desktop-packages] [Bug 1844575] Re: Pixelated fonts sometimes

Marking as rls-ee-notfixing.  This doesn't mean that this bug won't get
fixed, but that it won't block release if it is not fixed in time.


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

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

Title:
  Pixelated fonts sometimes

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

Bug description:
  Running under wayland, with fractional scaling enabled and set to 175%
  on laptop screen, 100% on external screen, sometimes windows like
  nautilus or the file chooser get pixelated fonts (see screenshot).
  Seen this mostly on the 100% external screen, and it goes away if
  maximizing the window or moving the window back and forth between
  screens a few times.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 18 12:59:50 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-17 (32 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1845188] Re: Ubuntu 19.10 Community Wallpapers

2019-09-24 Thread Olivier Tilloy

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

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

Title:
  Ubuntu 19.10 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.10 (minus one where the artists didn't reply to my emails).

  These have been resized (and where needed cropped) to 3840 x 2160.

  I've put them all through Squoosh.  Most are JPGs, but one is a PNG,
  the gradients didn't respond well to being JPGed.  I have tried to
  keep the size below 500k where ever I can, but in some cases it has
  gone over in order to keep the quality acceptable.

  Total size of the wallpapers is 5.6MB.

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

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

[Desktop-packages] [Bug 1845210] [NEW] Software Centre flickers alot during use on Eoan beta

2019-09-24 Thread David Pearson

Public bug reported:

After fresh install of the Beta of Eoan for Xubuntu, the window for
Software keeps flickering as you try to use it.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Tue Sep 24 14:31:55 2019
InstallationDate: Installed on 2019-09-24 (0 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190924.1)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.30.6-2ubuntu10
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan testing

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

Title:
  Software Centre flickers alot during use on Eoan beta

Status in gnome-software package in Ubuntu:
  New

Bug description:
  After fresh install of the Beta of Eoan for Xubuntu, the window for
  Software keeps flickering as you try to use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Tue Sep 24 14:31:55 2019
  InstallationDate: Installed on 2019-09-24 (0 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190924.1)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu10
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.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/ubuntu/+source/gnome-software/+bug/1845210/+subscriptions

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

[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login

2019-09-24 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845198

** Tags added: iso-testing

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

Title:
  GNOME Shell seemingly locked up at login

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

[Desktop-packages] [Bug 505765] Re: gedit problem with long lines

2019-09-24 Thread Paul White

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #229
   https://gitlab.gnome.org/GNOME/gtk/issues/229

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

** Changed in: gedit
   Status: Expired => Unknown

** Changed in: gedit
 Remote watch: GNOME Bug Tracker #127731 => gitlab.gnome.org/GNOME/gtk/issues 
#229

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

Title:
  gedit problem with long lines

Status in gedit:
  Unknown
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  Hi,

  I was editing a text file when the cursor began to behave strangely.
  The file contained these lines:

  CREATE TABLE people(
   integer primary key,
   name varchar(50),
   age integer
  )

  When I put the cursor after the 'l' in 'people', the arrow key would
  not move the cursor to the right. Instead it jumped to the next line.
  Similarly, I could not add text at this position.

  Viewing the file in a hex editor revealed a lot of spaces (284 to be
  accurate) after the opening parenthesis. Probably I've added those
  spaces without knowing it (resting my book "beginning Ruby" on the
  space bar ^ ^). Still, I feel the editor should handle a few hundred
  chars on a line without misbehaviour.

  I attached a copy of the text file.

  Thanks for developing and maintaining this simple but useful editor!

  Tor

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gedit
  Package: gedit 2.26.1-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  Tags:  ubuntu-unr
  Uname: Linux 2.6.28-17-generic i686

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

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

[Desktop-packages] [Bug 1845205] [NEW] Cannot submit crash reports from firefox' "this tab crashed" page

2019-09-24 Thread Gabriele Svelto

Public bug reported:

Steps to reproduce:

- Launch firefox
- Enter "about:crashcontent" in the URL bar
- Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
- Ensure that the checkmark to send the crash report is ticked
- Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
- Click on "Restore this tab"
- Go to the "about:crashes" page

Expected behaviour:

In the "about:crashes" page the crash is displayed among the submitted
crash reports, showing that the crash report was indeed submitted
correctly.

Actual behaviour:

The crash appears among the unsubmitted crashes.

This bug is specific to the packaged version of Firefox that comes with
Ubuntu. I've tried reproducing using Mozilla's builds and crash
submission works correctly there. See this bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
tracker regarding this behaviour. In Mozilla we noticed the issue
because we've started properly processing crash reports coming from
Ubuntu and tab crashes were strangely few. Feel free to contact me
directly at gsve...@mozilla.com about this issue since I'm in charge of
Firefox crash reporting machinery.

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

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

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

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

[Desktop-packages] [Bug 1843763] Re: [SRU] libreoffice 6.2.7 for disco

This bug was fixed in the package libreoffice-l10n -
1:6.2.7-0ubuntu0.19.04.1

---
libreoffice-l10n (1:6.2.7-0ubuntu0.19.04.1) disco-security; urgency=medium

  * New upstream release (LP: #1843763)
  * Fixes CVE-2019-9854: Unsafe URL assembly flaw in allowed script location 
check

 -- Marcus Tomlinson   Thu, 12 Sep 2019
15:53:48 +0100

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

Title:
  [SRU] libreoffice 6.2.7 for disco

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice-l10n package in Ubuntu:
  In Progress
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.2.7 is in its seventh bugfix release of the 6.2 line.
     For a list of fixed bugs compared to 6.2.6 see:
   https://wiki.documentfoundation.org/Releases/6.2.7/RC1#List_of_fixed_bugs
     (that's a total of 32 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 32 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke 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/1843763/+subscriptions

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

[Desktop-packages] [Bug 1843763] Re: [SRU] libreoffice 6.2.7 for disco

This bug was fixed in the package libreoffice - 1:6.2.7-0ubuntu0.19.04.1

---
libreoffice (1:6.2.7-0ubuntu0.19.04.1) disco-security; urgency=medium

  * New upstream release (LP: #1843763)
  * Fixes CVE-2019-9854: Unsafe URL assembly flaw in allowed script location 
check

 -- Marcus Tomlinson   Thu, 12 Sep 2019
15:53:48 +0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9854

** Changed in: libreoffice-l10n (Ubuntu Disco)
   Status: In Progress => Fix Released

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

Title:
  [SRU] libreoffice 6.2.7 for disco

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice-l10n package in Ubuntu:
  In Progress
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 6.2.7 is in its seventh bugfix release of the 6.2 line.
     For a list of fixed bugs compared to 6.2.6 see:
   https://wiki.documentfoundation.org/Releases/6.2.7/RC1#List_of_fixed_bugs
     (that's a total of 32 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 32 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke 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/1843763/+subscriptions

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

[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login

Potential dupe: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1845017

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

Title:
  GNOME Shell seemingly locked up at login

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login

2019-09-24 Thread Jean-Baptiste Lallement

confirmed on the live session with build 20190924, no ppa here.

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

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

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

Title:
  GNOME Shell seemingly locked up at login

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

[Desktop-packages] [Bug 1845017] Re: Desktop hard lockup in 19.10

Attaching logs as requested by Trevinho

** Attachment added: "With DRI logs"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+attachment/5290948/+files/withdri.txt

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

Title:
  Desktop hard lockup in 19.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris).

  Had a few desktop shell lockups. Pattern seems to be when running snap
  refresh, but this time happened when running snapcraft --use-lxd.
  Feels like something related to mounting / unmounting devices. Got
  this from the journal.

  Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: 
dock._settings is undefined
   
_showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1
   
_enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 23 16:52:06 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (595 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago)

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

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

[Desktop-packages] [Bug 1845017] Re: Desktop hard lockup in 19.10

Potential dupe: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1845198

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

Title:
  Desktop hard lockup in 19.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris).

  Had a few desktop shell lockups. Pattern seems to be when running snap
  refresh, but this time happened when running snapcraft --use-lxd.
  Feels like something related to mounting / unmounting devices. Got
  this from the journal.

  Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: 
dock._settings is undefined
   
_showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1
   
_enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 23 16:52:06 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (595 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago)

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

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

[Desktop-packages] [Bug 1845017] Re: Desktop hard lockup in 19.10

The most recent log (but missing dri for some reason)


** Attachment added: "latest_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+attachment/5290949/+files/latest_log.txt

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

Title:
  Desktop hard lockup in 19.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris).

  Had a few desktop shell lockups. Pattern seems to be when running snap
  refresh, but this time happened when running snapcraft --use-lxd.
  Feels like something related to mounting / unmounting devices. Got
  this from the journal.

  Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: 
dock._settings is undefined
   
_showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1
   
_enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 23 16:52:06 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (595 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago)

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

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

[Desktop-packages] [Bug 505765] Re: gedit problem with long lines

2019-09-24 Thread Tgkprog

see this issue when opening a json file without new lines between
elements. will be cool if horizontal scrolling works as well, has short
cuts and is stable like vertical scrolling. thank you

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

Title:
  gedit problem with long lines

Status in gedit:
  Expired
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  Hi,

  I was editing a text file when the cursor began to behave strangely.
  The file contained these lines:

  CREATE TABLE people(
   integer primary key,
   name varchar(50),
   age integer
  )

  When I put the cursor after the 'l' in 'people', the arrow key would
  not move the cursor to the right. Instead it jumped to the next line.
  Similarly, I could not add text at this position.

  Viewing the file in a hex editor revealed a lot of spaces (284 to be
  accurate) after the opening parenthesis. Probably I've added those
  spaces without knowing it (resting my book "beginning Ruby" on the
  space bar ^ ^). Still, I feel the editor should handle a few hundred
  chars on a line without misbehaviour.

  I attached a copy of the text file.

  Thanks for developing and maintaining this simple but useful editor!

  Tor

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/gedit
  Package: gedit 2.26.1-0ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  Tags:  ubuntu-unr
  Uname: Linux 2.6.28-17-generic i686

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

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

[Desktop-packages] [Bug 1845198] [NEW] GNOME Shell seemingly locked up at login

Public bug reported:

In 19.10, and also running the X PPA from
http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

When I logged in (after having attached a Bluetooth speaker in order to
test if it was being reconnected correctly) GNOME Shell isn't responding
to mouse or keyboard input.

The clock continues to tell the right time, and the mouse moves around
the screen and is repainted correctly.

Most recent output from gdb here:
https://paste.ubuntu.com/p/pSshP8V2SZ/

Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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


** Tags: rls-ee-incoming

** Tags added: rls-ee-incoming

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

Title:
  GNOME Shell seemingly locked up at login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

[Desktop-packages] [Bug 1845197] [NEW] GNOME Shell seemingly locked up at login

Public bug reported:

In 19.10, and also running the X PPA from
http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

When I logged in (after having attached a Bluetooth speaker in order to
test if it was being reconnected correctly) GNOME Shell isn't responding
to mouse or keyboard input.

The clock continues to tell the right time, and the mouse moves around
the screen and is repainted correctly.

Most recent output from gdb here:
https://paste.ubuntu.com/p/pSshP8V2SZ/

Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

Title:
  GNOME Shell seemingly locked up at login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

-- 
Mailing list: https://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 1842643] Re: [ffe] Update to 1.44.6

2019-09-24 Thread Iain Lane

On Mon, Sep 23, 2019 at 10:12:14AM -, Sebastien Bacher wrote:
> We failed to have consensus in Paris and I feel like it's getting late
> now and we have enough other work to do to wrap the cycle so would
> prefer to delay to next cycle now. Iain, what do you think? (you opened
> the FFe but so you should be the one deciding if we withdraw the
> request)

Right, yes, I think so. Sorry about this - maybe I was being overly
conservative here, not sure. Agreed we probably have enough work to do
and don't want to have to deal with any (unknown) fallout from this.

For the record, I saw mclasen saying on IRC somewhere (can't find it
right now) that some commits from cairo git ara cairo snapshot needed to
work properly with this new pango but there is no maintainer to release
it - not sure of the details. We should bear this in mind next cycle.

 status wontfix

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


** Changed in: pango1.0 (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  [ffe] Update to 1.44.6

Status in pango1.0 package in Ubuntu:
  Won't Fix

Bug description:
  There are a lot of changes in pango1.0 since the version we currently
  have in eoan. We held off updating because there was a test failure.
  This has been resolved in the latest release, so we'd like to go for
  the update now.

  Overview of changes in 1.44.6
  =
  - docs: Fix symbol indices
  - Fix Thai line breaking
  - Re-add symbols needed by some bindings
  - Don't insert hyphens for some languages
  - Fix a crash with hyphenation

  Overview of changes in 1.44.5
  =
  - Revert a broken change (causing crashes on OS X)

  Overview of changes in 1.44.4
  =
  - Add an insert-hyphens attribute
  - Reinstate the return type of pango_fc_font_lock_face
  - Fix a problem with ellipses getting the wrong font
  - fc: Improve filtering by font format
  - Re-add PangoFcFont to public headers
  - Install PangoFc and PangoOT introspection files
  - Fix ink rectangles to have positive height
  - Fix mark positioning
  - Switch to using harfbuzz for metrics

  Overview of changes in 1.44.3
  =
  - Install pango-ot headers
  - Make subpixel positioning optional
  - fc: Ignore fonts with unsupported formats

  Overview of changes in 1.44.2
  =
  - Disable ligatures when letterspacing
  - Set design coords on hb_font_t
  - Expose more font options in pango-view
  - OS X: Make 'system-ui' font work
  - Keep deprecated pango-fc apis in headers
  - Make hex boxes work, always
  - introspection: Various build fixes
  - introspection: Add PangoPT, PangoFT2 namespaces
  - layout: Make the new line-spacing opt-in

  Overview of changes in 1.44.1
  =
  - Fix a crash with allow_break attributes
  - Fix Emoji spacing
  - Fix up includes and pkg-config requires
  - Correct some cases for hyphen insertion

  Overview of changes in 1.44.0
  =
  - Use harfbuzz for shaping on all platforms
  - Stop using freetype for font loading; this
  drops support for type1 and bitmap fonts
  - Add a getter for hb_font_t
  - Make PangoCoverage a GObject
  - Add a pango_tailor_break api
  - font metrics: Add line height
  - layout: Support line spacing
  - layout: Draw hyphens for line breaks
  - Add an attribute to suppress line breaking
  - cairo: Don't render hex boxes for space
  - Add an attribute to show invisible characters
  - Stop quantizing glyph positions
  - Add tests for itemization and line breaking
  - Remove language and shape engine remnants
  - Rename meson options: gtk_doc, introspection
  - Require GLib 2.59.2
  - Require Harfbuzz 2.0

  Overview of changes in 1.43.0
  =
  - Drop autotools
  - Drop Visual Studio build
  - Build with meson everywhere
  - Update Emoji tables for Unicode 11
  - Update test data for Unicode 11
  - Fix a crash with Thai breaking
  - Fix a crash with font variations
  - Deprecate bidi apis in favor of fribidi
  - Add a variable font family api
  - Improve font fallback handling on win32

  And see posts from upstream

  https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/
  https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/
  https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/

  for the new features.

  We'd like to update to it, if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1845017] Re: Desktop hard lockup in 19.10

2019-09-24 Thread Alan Pope  濾

Had another lockup, it seemed to lock up the gpu, so when trying to
reboot via ssh it was hanging.

** Attachment added: "pb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+attachment/5290940/+files/pb.txt

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

Title:
  Desktop hard lockup in 19.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris).

  Had a few desktop shell lockups. Pattern seems to be when running snap
  refresh, but this time happened when running snapcraft --use-lxd.
  Feels like something related to mounting / unmounting devices. Got
  this from the journal.

  Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: 
dock._settings is undefined
   
_showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1
   
_enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 23 16:52:06 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (595 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago)

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

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

[Desktop-packages] [Bug 1845188] Re: Ubuntu 19.10 Community Wallpapers

They are all named Image_Title_by_Author_Name


** Tags added: rls-ee-incoming

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

Title:
  Ubuntu 19.10 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Attached are the winning entries from the wallpaper competition for
  19.10 (minus one where the artists didn't reply to my emails).

  These have been resized (and where needed cropped) to 3840 x 2160.

  I've put them all through Squoosh.  Most are JPGs, but one is a PNG,
  the gradients didn't respond well to being JPGed.  I have tried to
  keep the size below 500k where ever I can, but in some cases it has
  gone over in order to keep the quality acceptable.

  Total size of the wallpapers is 5.6MB.

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

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

[Desktop-packages] [Bug 1845188] [NEW] Ubuntu 19.10 Community Wallpapers

Public bug reported:

Attached are the winning entries from the wallpaper competition for
19.10 (minus one where the artists didn't reply to my emails).

These have been resized (and where needed cropped) to 3840 x 2160.

I've put them all through Squoosh. Most are JPGs, but one is a PNG, the
gradients didn't respond well to being JPGed. I have tried to keep the
size below 500k where ever I can, but in some cases it has gone over in
order to keep the quality acceptable.

Total size of the wallpapers is 5.6MB.

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

** Tags: rls-ee-incoming

** Attachment added: "free_culture_showcase_1910.tar.xz"

https://bugs.launchpad.net/bugs/1845188/+attachment/5290939/+files/free_culture_showcase_1910.tar.xz

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

Title:
Ubuntu 19.10 Community Wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
New

Bug description:
Attached are the winning entries from the wallpaper competition for
19.10 (minus one where the artists didn't reply to my emails).

These have been resized (and where needed cropped) to 3840 x 2160.

I've put them all through Squoosh. Most are JPGs, but one is a PNG,
the gradients didn't respond well to being JPGed. I have tried to
keep the size below 500k where ever I can, but in some cases it has
gone over in order to keep the quality acceptable.

Total size of the wallpapers is 5.6MB.

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

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

[Desktop-packages] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

2019-09-24 Thread Tim Richardson

A very similar thing just happened to me, with the 435 drivers via ppa.
Reverting to 430 solved it. Ubuntu 19.04, P50. USB mouse works.

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

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  
  On a Lenovo Thinkpad P50 with a Synaptics touchpad, the touchpad (or 
trackpoint), does not respond to any input after installing ubuntu 19.04.

  The same machine has been working fine with ubuntu 16.04 and 18.10. To
  be more correct it is still working in 16.04 hwe which I'm dual
  booting.

  If I uninstall the nvidia drivers (right now 418.56-0ubuntu1), and
  replace with noveau drivers it works just fine (by the way there seems
  to be no other issues with the nvidia driver as of yet).

  I have also the nvidia-driver-390 also suggested in the graphical
  software updates tool, to no avail.

  I will attach relevant logs. Please let me know if there is more I should 
supply.
  And thanks for all your hard (and brilliant) work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-libinput 0.28.2-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Adgang nægtet: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 26 20:36:18 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  InstallationDate: Installed on 2019-04-26 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b596 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 0458:0007 KYE Systems Corp. (Mouse Systems) 
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20EQS0PQ00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=21f288a0-da9c-46ea-8b64-056770908297 ro quiet splash 
synaptic_intertouch=0 vt.handoff=1
  SourcePackage: xserver-xorg-input-libinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET83W (1.56 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS0PQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET83W(1.56):bd02/21/2019:svnLENOVO:pn20EQS0PQ00:pvrThinkPadP50:rvnLENOVO:rn20EQS0PQ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS0PQ00
  dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  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/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

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

[Desktop-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers

2019-09-24 Thread Treviño

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

** Changed in: mesa
 Remote watch: freedesktop.org Bugzilla #64202 => 
gitlab.freedesktop.org/mesa/mesa/issues #727

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

Title:
  [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
  hardware and 943/945 graphics controllers

Status in Mesa:
  Unknown
Status in Nux:
  Fix Released
Status in Release Notes for Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in nux package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  After the upgrade to Mesa 9.2.0 unity is barely usable.
  Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, 
using 100% cpu.

  A downgrade to mesa 9.1.6-2ubuntu2 restores full performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-glx 9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  9 01:51:45 2013
  DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
  InstallationDate: Installed on 2013-09-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago)
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep  9 01:46:55 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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

[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS

2019-09-24 Thread Alexandros Kontogiannis

Playing with different resolutions and rates using xrandr solved the
problem for me on a DELL XPS 15 with Ubuntu 18.04. If I go with a
resolution of 1920x1080 and a rate of 60 Hz the TV shows a black screen.
Changing to other modes and rates solves the problem. For example,
typing in a terminal

xrandr --output DP-1-3 --mode 1360x768 --rate 60

made it work. If I go for a resolution of 1920x1080, I have output only
for a rate of 25 Hz. I don't know why exactly this happens. Maybe it
depends on the TV?

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

Title:
  Secondary monitor not connecting in 18.04 LTS

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M
  (nvidia driver v390) and a Benq W1070 projector.

  I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects
  for a split second and then gets disconnected. In Ubuntu 16.04
  projector was working fine as a mirror display and extended desktop.
  Here's what I already tried:

  - enable the nouveau driver instead of the nvidia driver -> no result
  - enable the on-board intel board with sudo prime-select intel -> no result
  - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> 
no result
  - disable nouveau driver, disable nvidia driver from the repository and 
install nvidia driver from nvidia website (both 390 and 396) -> no result
  - installed CCSM (CompizConfig Settings Manager) and disabled display 
auto-detection -> no result
  - played around with the refresh rate (some forums say that the two outputs 
have to be in sync -> no result
  - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still 
the same issue
  - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 
1920x1920 -> nothing
  - under settings -> devices -> displays I don't see a secondary display (just 
the main one)

  I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to
  day)

  Here is the output of xrandr the very second when I connect the
  projector (then HDMI-1-2 goes disconnected and no modes are
  displayed):

  ~$ xrandr
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x 
axis y axis) 345mm x 194mm
     1920x1080 60.02*+  60.0159.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 disconnected (normal left inverted right x axis y axis)
    1920x1080 (0x258) 148.500MHz +HSync +VSync
  h: width  1920 start 2008 end 2052 total 2200 skew0 clock  
67.50KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
60.00Hz
    1920x1080 (0x259) 148.500MHz +HSync +VSync
  h: width  1920 start 2448 end 2492 total 2640 skew0 clock  
56.25KHz
  v: height 1080 start 1084 end 1089 total 1125   clock  
50.00Hz
    1920x1080 (0x25a) 148.352MHz

[Desktop-packages] [Bug 1845179] Re: gnome-shell crashed with SIGSEGV in __GI_raise()

2019-09-24 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in __GI_raise()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  That seem to happen when I try to update a gnome extension from gnome-
  tweaks

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 12:11:56 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50
   ()
() at /lib/x86_64-linux-gnu/libc.so.6
   meta_get_stage_for_display () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
   meta_stage_is_focused () at /usr/lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV in __GI_raise()
  UpgradeStatus: Upgraded to eoan on 2018-11-14 (313 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo video
  separator:

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

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

[Desktop-packages] [Bug 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series

2019-09-24 Thread Alberto Milone

** Changed in: nvidia-settings (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nvidia-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update NVIDIA the 430 series and introduce the 435 series

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  In Progress

Bug description:
  Update NVIDIA the 430 series and introduce the 435 series from 19.10.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  
  [Discussion]

  430.50:

    * New upstream release (LP: #1844126):
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

  435.21:

    * New upstream release:
  - Fixed a bug that caused the X server to crash when using
    HardDPMS with an NVIDIA-driven GPU Screen.
  - Fixed a bug which caused the kernel to panic when exiting a
    single X server when multiple X servers were active and in an
    SLI configuration.
  - Fixed a regression introduced in the 430.* series of releases
    that caused a segmentation fault in libnvcuvid.so while using
    Video Codec SDK APIs on certain graphics boards.
  - Added initial experimental support for runtime D3 (RTD3) power
    management on Turing notebook GPUs.
  - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3)
    power management information.
  - Improved nvidia-bug-report.sh to collect ACPI tables when the
    acpidump tool is available.
  - Added Vulkan and OpenGL+GLX support for PRIME render offload.
    Please see the PRIME Render Offload chapter in the README for
    system requirements and configuration details.
  - Added support for changing Digital Vibrance in the display
    controls section of nvidia-settings on Turing hardware.
  - Fixed the cuvidParseVideoData API in the NVCUVID driver to
    correctly propagate errors returned by the
    PFNVIDSEQUENCECALLBACK callback function to the application.
  - Fixed a bug that caused the NVIDIA X driver to behave
    incorrectly or crash when a client queried Xinerama information
    on X servers with a non-NVIDIA X screen as screen 0.
  - Fixed the "Image Settings" options in the "OpenGL Settings"
    page of nvidia-settings for Quadro GPUs.  Previously, OpenGL
    rendering on Quadro would behave as if the "High Quality"
    option were selected regardless of the selection.  Now, the
    setting will default to "High Quality" for Quadro but selecting
    a lower option will affect rendering accordingly. (Other GPUs
    are unchanged: the default remains "Quality", but other options
    can be selected if desired.)
  - Fixed a bug that could cause Vulkan applications to generate
    spurious warning messages about a missing NV-GLX extension.
  - Fixed a bug that prevented nvidia-drm from marking preferred
    modes properly when reporting display information via the DRM-
    KMS API.
  - Fixed the NvEncodeAPI driver to correctly reject the encoding
    of sequences with resolutions smaller than what the NVENC
    supports.
  - Fixed display color range handling on pre-Turing GPUs, such
    that when limited color range is selected through the display
    controls page in nvidia-settings, output pixel values will be
    correctly clamped to Consumer Technology Association (CTA)
    range.

To manage notifications about

[Desktop-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

2019-09-24 Thread Cigar Zh

same problem here
Ubuntu 18.04

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/gnome-desktop/+bug/1825626/+subscriptions

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

[Desktop-packages] [Bug 1845165] ThreadStacktrace.txt

2019-09-24 Thread Apport retracing service

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1845165/+attachment/5290907/+files/ThreadStacktrace.txt

** Tags added: apport-failed-retrace

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in  in ??() [non-native
  amd64 package]

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu desktop netboot install on i386.

  Session crashes on login.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic i686
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 11:07:13 2019
  Disassembly: value is not available
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1897 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SegvAnalysis: Failure: invalid literal for int() with base 16: ''
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  StacktraceTop:  in ?? ()
  Title: gnome-shell crashed with SIGSEGV in  in ??() [non-native 
amd64 package]
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (548 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1845165] gnome-shell crashed with SIGSEGV in in ??() [non-native amd64 package]

2019-09-24 Thread Apport retracing service

Stacktrace:
 #0  0xb6b7def5 in ?? ()
 No symbol table info available.
 #1  0x in ?? ()
 No symbol table info available.
StacktraceSource:
 #0  0xb6b7def5 in ?? ()
 #1  0x in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

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

Title:
  gnome-shell crashed with SIGSEGV in  in ??() [non-native
  amd64 package]

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu desktop netboot install on i386.

  Session crashes on login.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic i686
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 11:07:13 2019
  Disassembly: value is not available
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1897 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SegvAnalysis: Failure: invalid literal for int() with base 16: ''
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  StacktraceTop:  in ?? ()
  Title: gnome-shell crashed with SIGSEGV in  in ??() [non-native 
amd64 package]
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (548 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard

2019-09-24 Thread Leon Liao

** Summary changed:

- The cancel button of the paring dialog does not work during paring a 
bluetooth keyboard 
+ The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard

** Description changed:

- The cancel button of the paring dialog does not work during paring a 
bluetooth keyboard.
+ The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard.
  The dialog can be cancel via press the "ESC" on the keyboard.
  But, sometimes after around 1 minute, the gnome-control-center is crashed.
  
  Reproduce steps:
  1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
- 2. When the paring XXX dialog show up
+ 2. When the pairing XXX dialog show up
  3. click the Cancel button (on the top left of the dialog).
  
- Expected: the Cancel button is work. And, the paring is canceled normally.
- Actually: the Cancel button does not work. The paring action can not be 
canceled via the button.
+ Expected: the Cancel button is work. And, the pairing is canceled normally.
+ Actually: the Cancel button does not work. The pairing action can not be 
canceled via the button.
  
  Ubuntu: 18.04
  gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

** Also affects: oem-priority
   Importance: Undecided
   Status: 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/1845163

Title:
  The cancel button of the paring dialog does not work during pairing a
  bluetooth keyboard

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard.
  The dialog can be cancel via press the "ESC" on the keyboard.
  But, sometimes after around 1 minute, the gnome-control-center is crashed.

  Reproduce steps:
  1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
  2. When the pairing XXX dialog show up
  3. click the Cancel button (on the top left of the dialog).

  Expected: the Cancel button is work. And, the pairing is canceled normally.
  Actually: the Cancel button does not work. The pairing action can not be 
canceled via the button.

  Ubuntu: 18.04
  gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

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

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

[Desktop-packages] [Bug 1845163] [NEW] The cancel button of the paring dialog does not work during paring a bluetooth keyboard

2019-09-24 Thread Leon Liao

Public bug reported:

The cancel button of the paring dialog does not work during paring a bluetooth
keyboard.
The dialog can be cancel via press the "ESC" on the keyboard.
But, sometimes after around 1 minute, the gnome-control-center is crashed.

Reproduce steps:
1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
2. When the paring XXX dialog show up
3. click the Cancel button (on the top left of the dialog).

Expected: the Cancel button is work. And, the paring is canceled normally.
Actually: the Cancel button does not work. The paring action can not be
canceled via the button.

Ubuntu: 18.04
gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

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

** Description changed:

The cancel button of the paring dialog does not work during paring a
bluetooth keyboard.
The dialog can be cancel via press the "ESC" on the keyboard.
- But, after around 1 minute, the gnome-control-center is crashed.
-
+ But, sometimes after around 1 minute, the gnome-control-center is crashed.

Reproduce steps:
1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
2. When the paring XXX dialog show up
3. click the Cancel button (on the top left of the dialog).

Expected: the Cancel button is work. And, the paring is canceled normally.
Actually: the Cancel button does not work. The paring action can not be
canceled via the button.

-
Ubuntu: 18.04
gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

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

Title:
The cancel button of the paring dialog does not work during paring a
bluetooth keyboard

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

Bug description:
The cancel button of the paring dialog does not work during paring a
bluetooth keyboard.
The dialog can be cancel via press the "ESC" on the keyboard.
But, sometimes after around 1 minute, the gnome-control-center is crashed.

Reproduce steps:
1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
2. When the paring XXX dialog show up
3. click the Cancel button (on the top left of the dialog).

Expected: the Cancel button is work. And, the paring is canceled normally.
Actually: the Cancel button does not work. The paring action can not be
canceled via the button.

Ubuntu: 18.04
gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

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

[Desktop-packages] [Bug 1845165] [NEW] gnome-shell crashed with SIGSEGV in in ??() [non-native amd64 package]

2019-09-24 Thread Jean-Baptiste Lallement

Public bug reported:

Ubuntu desktop netboot install on i386.

Session crashes on login.

ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic i686
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: i386
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 24 11:07:13 2019
Disassembly: value is not available
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2014-07-15 (1897 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
PackageArchitecture: amd64
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
SegvAnalysis: Failure: invalid literal for int() with base 16: ''
Signal: 11
SourcePackage: gnome-shell
Stacktrace:
 #0   in ?? ()
 PC unavailable, cannot determine locals.
 Backtrace stopped: not enough registers or memory available to unwind further
StacktraceTop:  in ?? ()
Title: gnome-shell crashed with SIGSEGV in  in ??() [non-native 
amd64 package]
UpgradeStatus: Upgraded to eoan on 2018-03-24 (548 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

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


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

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV in  in ??() [non-native
  amd64 package]

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu desktop netboot install on i386.

  Session crashes on login.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic i686
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 11:07:13 2019
  Disassembly: value is not available
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1897 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SegvAnalysis: Failure: invalid literal for int() with base 16: ''
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  StacktraceTop:  in ?? ()
  Title: gnome-shell crashed with SIGSEGV in  in ??() [non-native 
amd64 package]
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (548 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0

2019-09-24 Thread Timo Aaltonen

** Changed in: libclc (Ubuntu Eoan)
   Status: New => Fix Released

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

Title:
  FFe: Mesa 19.2.0

Status in libclc package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in libclc source package in Eoan:
  Fix Released
Status in mesa source package in Eoan:
  Confirmed

Bug description:
  It would be great to get 19.2.0 in eoan, though it's release cycle has
  slipped. It's working fine on a typical desktop use here on i915 (Kaby
  Lake). It would also migrate to llvm-9.

  It is currently at rc3, and final version is expected to arrive next
  week (week 39).

  New features:

  Full support for Intel Ice Lake
  Support for AMD Navi

  GL_ARB_post_depth_coverage on radeonsi (Navi)
  GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports 
SEAMLESS_CUBE_MAP)
  GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10)
  GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR)
  GL_EXT_texture_shadow_lod on i965, iris
  EGL_EXT_platform_device
  VK_AMD_buffer_marker on radv
  VK_EXT_index_type_uint8 on radv
  VK_EXT_post_depth_coverage on radv
  VK_EXT_queue_family_foreign on radv
  VK_EXT_sample_locations on radv
  VK_EXT_shader_demote_to_helper_invocation on Intel.
  VK_KHR_depth_stencil_resolve on radv
  VK_KHR_imageless_framebuffer on radv
  VK_KHR_shader_atomic_int64 on radv
  VK_KHR_uniform_buffer_standard_layout on radv

  (note: iris is the new DRI driver for newer Intel, not enabled by
  default yet)

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

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

[Desktop-packages] [Bug 1724810] Re: 17.10/wayland causing flashes in virtualbox

2019-09-24 Thread DanglingPointer

Just stating here that it currently affects 18.04 and 19.04 as guests on
Vbox 6 on Macos (Mac Pro 2018).

Flickering white screen happens only with Wayland and not X.
X works fine.

Guest additions installed as well.
VBox extensions installed as well.

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

Title:
  17.10/wayland causing flashes in virtualbox

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

Bug description:
  Hi,

  just as a quick response:

  I've installed the new 17.10 Desktop for testing in a virtual machine
  (VirtualBox 5.1.20 running on MacOS), and while it installed smoothly
  and booted instantly, there's a problem with the graphics (probably
  related to wayland): Especially when moving the mouse or starting new
  programs the screen flashes white every few seconds or sometimes shows
  just a blank grey screen for about a second. Not suited for regular
  work.

  But I have no clue which component precisely is causing that problem.

  regards

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

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

[Desktop-packages] [Bug 1818920] Re: Snap without icons use old asset

This bug was fixed in the package gnome-software -
3.28.1-0ubuntu4.18.04.12

---
gnome-software (3.28.1-0ubuntu4.18.04.12) bionic; urgency=medium

  * 
debian/patches/0001-Fix-apps-that-were-previously-uninstalled-from-not-s.patch:
- Fix apps that are reinstalled from disappearing from installed page
  (LP: #1742997)

gnome-software (3.28.1-0ubuntu4.18.04.11) bionic; urgency=medium

  * debian/patches/0031-shell-Don-t-progate-CTRL-F-key-pressed-event.patch:
- Fix Ctrl-F not opening search bar (LP: #1735071)
  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
  * debian/patches/0017-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)
  * debian/patches/0032-snap-Update-Snap-store-category-mapping.patch:
- Update snap store categories (LP: #1836826)

 -- Robert Ancell   Tue, 17 Sep 2019
09:49:03 +0200

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Fix Committed => 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/1818920

Title:
  Snap without icons use old asset

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Released
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Released

Bug description:
  [Impact]
  GNOME Software uses an outdated icon for snaps without icons.

  [Test Case]
  1. Open GNOME Software
  2. Look for a snap that has a default icon (e.g. youtube-dl)

  Expected behaviour:
  - The new icon is shown (grey circle with lines)

  Observed behaviour:
  - The old icon is shown (grey origami bird snapcraft logo)

  [Regression Potential]
  Low, this is just an asset change.

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

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

[Desktop-packages] [Bug 1742997] Re: Newly installed applications are not showing in "Installed"

This bug was fixed in the package gnome-software -
3.28.1-0ubuntu4.18.04.12

---
gnome-software (3.28.1-0ubuntu4.18.04.12) bionic; urgency=medium

  * 
debian/patches/0001-Fix-apps-that-were-previously-uninstalled-from-not-s.patch:
- Fix apps that are reinstalled from disappearing from installed page
  (LP: #1742997)

gnome-software (3.28.1-0ubuntu4.18.04.11) bionic; urgency=medium

  * debian/patches/0031-shell-Don-t-progate-CTRL-F-key-pressed-event.patch:
- Fix Ctrl-F not opening search bar (LP: #1735071)
  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
  * debian/patches/0017-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)
  * debian/patches/0032-snap-Update-Snap-store-category-mapping.patch:
- Update snap store categories (LP: #1836826)

 -- Robert Ancell   Tue, 17 Sep 2019
09:49:03 +0200

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Fix Committed => 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/1742997

Title:
  Newly installed applications are not showing in "Installed"

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in gnome-software source package in Bionic:
  Fix Released
Status in packagekit source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Removing and installing an app stops it showing in the installed apps page.

  [Test Case]
  1. Open GNOME Software
  2. Go to installed tab
  3. Click on an installed app
  4. Remove this app
  5. Install this app
  6. Click back button to return to installation page.

  Expected result:
  App shows on page.

  Observed result:
  App does not show on page.

  [Regression Potential]
  Change is small, and just fixes and ordering issue. Unlikely to trigger other 
major issues.

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

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

[Desktop-packages] [Bug 1836826] Re: Snaps not showing in categories due to store section name changes

This bug was fixed in the package gnome-software -
3.28.1-0ubuntu4.18.04.12

---
gnome-software (3.28.1-0ubuntu4.18.04.12) bionic; urgency=medium

  * 
debian/patches/0001-Fix-apps-that-were-previously-uninstalled-from-not-s.patch:
- Fix apps that are reinstalled from disappearing from installed page
  (LP: #1742997)

gnome-software (3.28.1-0ubuntu4.18.04.11) bionic; urgency=medium

  * debian/patches/0031-shell-Don-t-progate-CTRL-F-key-pressed-event.patch:
- Fix Ctrl-F not opening search bar (LP: #1735071)
  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
  * debian/patches/0017-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)
  * debian/patches/0032-snap-Update-Snap-store-category-mapping.patch:
- Update snap store categories (LP: #1836826)

 -- Robert Ancell   Tue, 17 Sep 2019
09:49:03 +0200

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Fix Committed => 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/1836826

Title:
  Snaps not showing in categories due to store section name changes

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Released
Status in gnome-software source package in Disco:
  Fix Released
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The Snap Store changed the names of some of the sections. This means that 
these are no longer mapped to the XDG categories used in GNOME Software. See 
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/279

  [Test Case]
  1. Open GNOME Software
  2. Go to graphics categeory.

  Expected result:
  Snaps are shown

  Observer result:
  Only .debs are shown

  [Regression Potential]
  Fix is just to change the name mappings, should be low risk.

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

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

[Desktop-packages] [Bug 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed

This bug was fixed in the package gnome-software -
3.28.1-0ubuntu4.18.04.12

---
gnome-software (3.28.1-0ubuntu4.18.04.12) bionic; urgency=medium

  * 
debian/patches/0001-Fix-apps-that-were-previously-uninstalled-from-not-s.patch:
- Fix apps that are reinstalled from disappearing from installed page
  (LP: #1742997)

gnome-software (3.28.1-0ubuntu4.18.04.11) bionic; urgency=medium

  * debian/patches/0031-shell-Don-t-progate-CTRL-F-key-pressed-event.patch:
- Fix Ctrl-F not opening search bar (LP: #1735071)
  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
  * debian/patches/0017-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)
  * debian/patches/0032-snap-Update-Snap-store-category-mapping.patch:
- Update snap store categories (LP: #1836826)

 -- Robert Ancell   Tue, 17 Sep 2019
09:49:03 +0200

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Fix Committed => 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/1735071

Title:
  Ctrl + F search disengages immediately after CTRL + F pressed

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Released
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Released

Bug description:
  * Impact
  ctrl-F doesn't open the search widget

  * Test case
  - open gnome-software
  - hit ctrl-F 
  -> the search widget should display

  * Regression potential
  The change is in the event handler for the specific keybinding so it 
shouldn't have any side effect if that feature is working

  --

  I press Ctrl + F to open up the search bar to search but I find that
  immediately after I press Ctrl + F, the bar closes and resets to its
  original state. I can visibly see the bar show up as well as it
  closing immediately. I have tested this functionality in the gnome-
  software-center from other distributions and the master branch and
  this works. I think this is a theme issue. I am using the default
  Ubuntu theme by the way.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.3-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 20:28:44 2017
  InstallationDate: Installed on 2017-07-20 (131 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.3-2ubuntu1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2017-11-23 (6 days ago)

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

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

[Desktop-packages] [Bug 1806697] Re: Status of interface connections not properly updated in the UI

This bug was fixed in the package gnome-software -
3.28.1-0ubuntu4.18.04.12

---
gnome-software (3.28.1-0ubuntu4.18.04.12) bionic; urgency=medium

  * 
debian/patches/0001-Fix-apps-that-were-previously-uninstalled-from-not-s.patch:
- Fix apps that are reinstalled from disappearing from installed page
  (LP: #1742997)

gnome-software (3.28.1-0ubuntu4.18.04.11) bionic; urgency=medium

  * debian/patches/0031-shell-Don-t-progate-CTRL-F-key-pressed-event.patch:
- Fix Ctrl-F not opening search bar (LP: #1735071)
  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
  * debian/patches/0017-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)
  * debian/patches/0032-snap-Update-Snap-store-category-mapping.patch:
- Update snap store categories (LP: #1836826)

 -- Robert Ancell   Tue, 17 Sep 2019
09:49:03 +0200

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Fix Committed => 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/1806697

Title:
  Status of interface connections not properly updated in the UI

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Released
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Released
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  Steps to reproduce the problem:
  1. Go to the Chromium snap store page by e.g. right clicking on its icon and 
selecting Show details and then the specific app.
  2. Press the Permissions button.
  3. Press/slide the Read/write files on removable storage devices slider.
  4. Close the permissions and the store window.
  5. Reopen the windows.
  6. The permission should be enabled, but it isn't.

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

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

[Desktop-packages] [Bug 1845149] [NEW] set fallback drivers to avoid updating pci-id lists

2019-09-24 Thread Timo Aaltonen

Public bug reported:

[Impact]
The AMD/Intel pci-id's keep changing when new platforms are enabled. Currently, 
the new ones need to be added to the kernel, libdrm, mesa and xorg-server. This 
duplication is silly, as there's a limited number of drivers for a platform, so 
use a default (fallback) DRI driver for a vendor. For Intel it's i965, for AMD 
it's radeonsi.


[Test case]
check that the correct driver is still used on an Xorg session and DRI works

[Regression potential]
shouldn't be any

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

** Affects: xorg-server-hwe-18.04 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xorg-server (Ubuntu Bionic)
 Importance: Undecided
 Status: Invalid

** Affects: xorg-server-hwe-18.04 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

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

** Also affects: xorg-server-hwe-18.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  set fallback drivers to avoid updating pci-id lists

Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-18.04 package in Ubuntu:
  New
Status in xorg-server source package in Bionic:
  Invalid
Status in xorg-server-hwe-18.04 source package in Bionic:
  New

Bug description:
  [Impact]
  The AMD/Intel pci-id's keep changing when new platforms are enabled. 
Currently, the new ones need to be added to the kernel, libdrm, mesa and 
xorg-server. This duplication is silly, as there's a limited number of drivers 
for a platform, so use a default (fallback) DRI driver for a vendor. For Intel 
it's i965, for AMD it's radeonsi.

  
  [Test case]
  check that the correct driver is still used on an Xorg session and DRI works

  [Regression potential]
  shouldn't be any

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

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

[Desktop-packages] [Bug 1836826] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Snaps not showing in categories due to store section name changes

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Disco:
  Fix Released
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The Snap Store changed the names of some of the sections. This means that 
these are no longer mapped to the XDG categories used in GNOME Software. See 
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/279

  [Test Case]
  1. Open GNOME Software
  2. Go to graphics categeory.

  Expected result:
  Snaps are shown

  Observer result:
  Only .debs are shown

  [Regression Potential]
  Fix is just to change the name mappings, should be low risk.

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

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

[Desktop-packages] [Bug 1742997] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Newly installed applications are not showing in "Installed"

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Invalid
Status in gnome-software source package in Bionic:
  Fix Committed
Status in packagekit source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Removing and installing an app stops it showing in the installed apps page.

  [Test Case]
  1. Open GNOME Software
  2. Go to installed tab
  3. Click on an installed app
  4. Remove this app
  5. Install this app
  6. Click back button to return to installation page.

  Expected result:
  App shows on page.

  Observed result:
  App does not show on page.

  [Regression Potential]
  Change is small, and just fixes and ordering issue. Unlikely to trigger other 
major issues.

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

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

[Desktop-packages] [Bug 1818920] Update Released

The verification of the Stable Release Update for gnome-software has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Snap without icons use old asset

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Released

Bug description:
  [Impact]
  GNOME Software uses an outdated icon for snaps without icons.

  [Test Case]
  1. Open GNOME Software
  2. Look for a snap that has a default icon (e.g. youtube-dl)

  Expected behaviour:
  - The new icon is shown (grey circle with lines)

  Observed behaviour:
  - The old icon is shown (grey origami bird snapcraft logo)

  [Regression Potential]
  Low, this is just an asset change.

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

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

[Desktop-packages] [Bug 1836826] Re: Snaps not showing in categories due to store section name changes

This bug was fixed in the package gnome-software -
3.30.6-2ubuntu4.19.04.2

---
gnome-software (3.30.6-2ubuntu4.19.04.2) disco; urgency=medium

  * debian/control:
- Set git branch for vcs
- Bump build-depends on snapd-glib
  * debian/patches/0001-snap-Update-Snap-store-category-mapping.patch:
- Update snap store categories (LP: #1836826)
  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
  * debian/patches/0016-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)
  * debian/patches/0028-Added-u2f-devices-to-interfaces-UI.patch
- Merged into 0014-Add-a-basic-permissions-system.patch

 -- Robert Ancell   Mon, 16 Sep 2019
14:35:59 +0200

** Changed in: gnome-software (Ubuntu Disco)
   Status: Fix Committed => 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/1836826

Title:
  Snaps not showing in categories due to store section name changes

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Disco:
  Fix Released
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  The Snap Store changed the names of some of the sections. This means that 
these are no longer mapped to the XDG categories used in GNOME Software. See 
https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/279

  [Test Case]
  1. Open GNOME Software
  2. Go to graphics categeory.

  Expected result:
  Snaps are shown

  Observer result:
  Only .debs are shown

  [Regression Potential]
  Fix is just to change the name mappings, should be low risk.

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

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

[Desktop-packages] [Bug 1806697] Re: Status of interface connections not properly updated in the UI

This bug was fixed in the package gnome-software -
3.30.6-2ubuntu4.19.04.2

---
gnome-software (3.30.6-2ubuntu4.19.04.2) disco; urgency=medium

  * debian/control:
- Set git branch for vcs
- Bump build-depends on snapd-glib
  * debian/patches/0001-snap-Update-Snap-store-category-mapping.patch:
- Update snap store categories (LP: #1836826)
  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
  * debian/patches/0016-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)
  * debian/patches/0028-Added-u2f-devices-to-interfaces-UI.patch
- Merged into 0014-Add-a-basic-permissions-system.patch

 -- Robert Ancell   Mon, 16 Sep 2019
14:35:59 +0200

** Changed in: gnome-software (Ubuntu Disco)
   Status: Fix Committed => 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/1806697

Title:
  Status of interface connections not properly updated in the UI

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Released
Status in gnome-software source package in Eoan:
  Fix Released

Bug description:
  Steps to reproduce the problem:
  1. Go to the Chromium snap store page by e.g. right clicking on its icon and 
selecting Show details and then the specific app.
  2. Press the Permissions button.
  3. Press/slide the Read/write files on removable storage devices slider.
  4. Close the permissions and the store window.
  5. Reopen the windows.
  6. The permission should be enabled, but it isn't.

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

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

[Desktop-packages] [Bug 1818920] Re: Snap without icons use old asset

This bug was fixed in the package gnome-software -
3.30.6-2ubuntu4.19.04.2

---
gnome-software (3.30.6-2ubuntu4.19.04.2) disco; urgency=medium

  * debian/control:
- Set git branch for vcs
- Bump build-depends on snapd-glib
  * debian/patches/0001-snap-Update-Snap-store-category-mapping.patch:
- Update snap store categories (LP: #1836826)
  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)
  * debian/patches/0016-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)
  * debian/patches/0028-Added-u2f-devices-to-interfaces-UI.patch
- Merged into 0014-Add-a-basic-permissions-system.patch

 -- Robert Ancell   Mon, 16 Sep 2019
14:35:59 +0200

** Changed in: gnome-software (Ubuntu Disco)
   Status: Fix Committed => 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/1818920

Title:
  Snap without icons use old asset

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Won't Fix
Status in gnome-software source package in Disco:
  Fix Released

Bug description:
  [Impact]
  GNOME Software uses an outdated icon for snaps without icons.

  [Test Case]
  1. Open GNOME Software
  2. Look for a snap that has a default icon (e.g. youtube-dl)

  Expected behaviour:
  - The new icon is shown (grey circle with lines)

  Observed behaviour:
  - The old icon is shown (grey origami bird snapcraft logo)

  [Regression Potential]
  Low, this is just an asset change.

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

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

[Desktop-packages] [Bug 1806697] Update Released