[Desktop-packages] [Bug 1820371] [NEW] PCI/internal sound card not detected

[dirk dröge]

Public bug reported:

 no sound in dell inspirion soundcard unknown

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39
Uname: Linux 3.13.0-166-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Sat Mar 16 06:55:24 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2019-03-15 (1 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/05/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 04XH5N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn04XH5N:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3551
dmi.product.version: A00
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
   no sound in dell inspirion soundcard unknown

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-166-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sat Mar 16 06:55:24 2019
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2019-03-15 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 04XH5N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn04XH5N:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3551
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1794033]

[Oss-linuxpf]

I saw this problem three times from yesterday.
All of them occurred during file sync over LAN with rsync.
I think this problem might be related to load by disk i/o or network i/o.
But unfortunately I have not re-compiled kernel with CONFIG_DRM_I915_DEBUG_GEM 
yet.
I will try to it next week.

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Confirmed

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

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

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

[Desktop-packages] [Bug 1811674] Re: Even withg WaylandEnable=false gdm3 only loads sometimes

[Launchpad Bug Tracker]

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

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

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

Title:
  Even withg WaylandEnable=false gdm3 only loads sometimes

Status in gdm3 package in Ubuntu:
  Expired

Bug description:
  gdm3:
    Installed: 3.28.3-0ubuntu18.04.3

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  I expect the greeter to load every boot.

  Instead, gdm3 is not stable on my system, it will work for either one
  or several boots after I take corrective action, but inevitably this
  results in the greeter not loading. The graphics card on my Intel Core
  i5 system is an Nvidia GTX 970, and I manually installed nvidia-
  driver-415 using apt when I could not load a greeter as soon as I had
  installed.

  Searching here and elsewhere, I have tried many things to resolve
  this, which I will outline below. If you know something else I can try
  - to get make gdm3 stable - please let me know.

  Even with WaylandEnable=false uncommented in /etc/gdm3/custom.conf, I
  usually cannot login, instead of the greeter I would see either a
  black screen or graphic distortion like a black screen with some pink
  lines across the top, and I am only able to login setting nomodeset.

  With gd3 not working, I tried lightdm, and on encountering similar
  issues switched back to gdm3 again:

  sudo apt-get install gdm3
  sudo dpkg-reconfigure gdm3

  This seemed to work - kind of, for the first few days I could boot
  most of the time. I have quiet splash permanently removed from my boot
  options, and boot was sometimes hanging on Started NVIDIA Persistence
  Daemon as in the attached images.

  Another time with gdm3 I saw the following output instead of the
  greeter, also attached.

  How can I begin to resolve this issue please?

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

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

[Desktop-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

[Launchpad Bug Tracker]

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

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

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1811731] Re: compuer freeze

[Launchpad Bug Tracker]

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

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

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

Title:
  compuer freeze

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  computer system freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jan 14 14:57:48 2019
  DistUpgraded: 2018-09-05 17:29:52,691 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 620] [10de:0f01] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF108 [GeForce GT 620] [3842:2625]
  InstallationDate: Installed on 2015-01-24 (1451 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 062a: Creative Labs Optical mouse
   Bus 002 Device 002: ID 413c:2005 Dell Computer Corp. RT7D50 Keyboard
   Bus 002 Device 004: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=c599b74a-de09-473c-b0e9-39538d42a83d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-06 (130 days ago)
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68C-GS FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-GSFX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Sep  5 09:58:08 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDELL DELL USB Keyboard KEYBOARD, id 8
   inputHID 062a:MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1811511] Re: package libreoffice-sdbc-firebird 1:5.3.0~rc3-0ubuntu1~trusty1.1 failed to install/upgrade: new libreoffice-sdbc-firebird package pre-installation script subproces

[Launchpad Bug Tracker]

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

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

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

Title:
  package libreoffice-sdbc-firebird 1:5.3.0~rc3-0ubuntu1~trusty1.1
  failed to install/upgrade: new libreoffice-sdbc-firebird package pre-
  installation script subprocess returned error exit status 1

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  after upgrading to the system version 18.04.1, this error is issued.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-sdbc-firebird 1:5.3.0~rc3-0ubuntu1~trusty1.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Tue Jan  8 01:36:58 2019
  Dependencies:
   
  ErrorMessage: new libreoffice-sdbc-firebird package pre-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-08-30 (1230 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libreoffice
  Title: package libreoffice-sdbc-firebird 1:5.3.0~rc3-0ubuntu1~trusty1.1 
failed to install/upgrade: new libreoffice-sdbc-firebird package 
pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-01-08 (4 days ago)

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

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

[Desktop-packages] [Bug 1811555] Re: package libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png.

[Launchpad Bug Tracker]

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

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

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

Title:
  package libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 failed to
  install/upgrade: unable to open
  '/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png
  .dpkg-new': Operation not permitted

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  Libreoffice will not update, leading to seeral applications reporting
  errors when being installed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libreoffice-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jan 12 12:24:13 2019
  DpkgTerminalLog:
   Preparing to unpack 
.../libreoffice-common_1%3a6.0.7-0ubuntu0.18.04.2_all.deb ...
   Unpacking libreoffice-common (1:6.0.7-0ubuntu0.18.04.2) over 
(1:6.0.6-0ubuntu0.18.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-common_1%3a6.0.7-0ubuntu0.18.04.2_all.deb 
(--unpack):
unable to open 
'/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-10-07 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 failed to 
install/upgrade: unable to open 
'/usr/lib/libreoffice/share/gallery/arrows/A29-CurvedArrow-Green.png.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/1811555/+subscriptions

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

[Desktop-packages] [Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound

[Launchpad Bug Tracker]

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

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

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

Title:
  USB type C audio adapter (from a Pixel 3) doesn't produce any sound

Status in linux package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  I use a logitech z200 that works fine, i use it with a usb type c adapter 
that came with my pixel 3, my speakers arent shown at all in the settings or 
make sound, its not the usb c adapter because it works fine on my windows dual 
boot and has worked at one point on ubuntu, regardless of the fact that ubuntu 
has never recognized my thunderbolt port, i use ubuntu 18.10 by the way when i 
use lsusb, one of the results is google inc., which is my headphone adapter, i 
can tell because when i unplug it it goes away, even when i plug it into the 
3.5 mm headphone jack it doesn't work, i don't know if im forgetting something 
or not, this is the second time im typing this because i accidentally closed 
the first tab of this, whats interesting, is now that i go to alsamixer, and 
press f6 i see option 1.Headphone Adapter, i select it and set the volume all 
the way up and go to something that makes audio and nothing happens, then i 
unplug it and see if it disappears, surely enough it does
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/controlC2', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-21 (78 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: pulseaudio 1:12.2-0ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=db7dbcfb-4be9-4405-88a9-8d91489e5a68 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   
  Tags:  cosmic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/05/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.00
  dmi.board.name: AB350 Gaming K4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP5.00:bd07/05/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1820368] [NEW] x

[Müller]

Public bug reported:

xx

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Mar 16 04:31:02 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
InstallationDate: Installed on 2017-05-23 (661 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 4291BD2
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=71ccb682-9ba5-4c82-8ab3-e914e7f1835d ro rootflags=sync drm.debug=0xe 
plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/21/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET76WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4291BD2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: BB70354824
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn4291BD2:pvrThinkPadX220:rvnLENOVO:rn4291BD2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X220
dmi.product.name: 4291BD2
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Oct 11 18:41:18 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 723 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.8

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


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

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

Title:
  x

Status in xorg package in Ubuntu:
  New

Bug description:
  xx

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Mar 16 04:31:02 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2017-05-23 (661 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 4291BD2
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=71ccb682-9ba5-4c82-8ab3-e914e7f1835d ro rootflags=sync drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291BD2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: BB70354824
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn4291BD2:pvrThinkPadX220:rvnLENOVO:rn4291BD2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 4291BD2
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 

[Desktop-packages] [Bug 1095534] Re: Remmina remote desktop client goes fullscreen on the wrong display

[Majik Bear]

This bug was confirmed and marked high importance 3 years ago in 2016
yet no action has been taken on it.

Any way we can speed this up?

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

Title:
  Remmina remote desktop client goes fullscreen on the wrong display

Status in remmina package in Ubuntu:
  Confirmed
Status in remmina package in Arch Linux:
  New

Bug description:
  When the fullscreen button on the toolbar is used with multiple
  displays enabled, Remmina maximizes on a random display rather than on
  the display where it is placed.

  To replicate on a computer with multiple displays:

  1. Launch Remmina.
  2. Connect to a computer using RDP protocol.
  3. Click the full screen button.

  The application flips over to the other display and goes full screen.

  4. Restore the application.
  5. Drag it back to the display where you want it.
  6. Click the full screen button again.

  The application flips over to the other display and goes full screen.

  The expectation is that the application should stay on the display
  where I put it or it should offer an option to allow me to specify the
  screen I want it on.

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

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

[Desktop-packages] [Bug 1095534] Re: Remmina remote desktop client goes fullscreen on the wrong display

[Majik Bear]

@howerkraft The bug you cited doesn't exist (404 when navigating to that
link). #15

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

Title:
  Remmina remote desktop client goes fullscreen on the wrong display

Status in remmina package in Ubuntu:
  Confirmed
Status in remmina package in Arch Linux:
  New

Bug description:
  When the fullscreen button on the toolbar is used with multiple
  displays enabled, Remmina maximizes on a random display rather than on
  the display where it is placed.

  To replicate on a computer with multiple displays:

  1. Launch Remmina.
  2. Connect to a computer using RDP protocol.
  3. Click the full screen button.

  The application flips over to the other display and goes full screen.

  4. Restore the application.
  5. Drag it back to the display where you want it.
  6. Click the full screen button again.

  The application flips over to the other display and goes full screen.

  The expectation is that the application should stay on the display
  where I put it or it should offer an option to allow me to specify the
  screen I want it on.

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

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

[Desktop-packages] [Bug 1819744] Re: 19.04 Disco default wallpapers

[TuxThePenguin]

It's cool that the box is removed but a small thing I noticed is that the 
greyscale version still does not quite match the patterns on the coloured 
version.
In the colured version there are two diagonal lines to the top right of the 
Dingo, however in the updated greyscale version there is only one.

My best guess is that the element for the second line accidentally had
it's rotation reset in the original greyscale image and was removed
entirely for the updated version?

Either way both wallpapers look awesome and I am excited to see them
being used as the default in 19.04 :)

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

Title:
  19.04 Disco default wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released

Bug description:
  Attached will be the Disco default wallpapers.

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

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

-- 
Mailing list: https://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 1803681] Re: osmesa doesn't suport core contexts but could

[Greg]

Fully patched 64-bit Ubuntu 18.04LTS Intel I7 AMD Radeon HD 7950
open-source drivers.  Is this fixed in 18.10 or 19.04?  And did you try the
test program?  And looking at
https://packages.ubuntu.com/bionic/libs/libosmesa6, I don't see the
dependency on llvm.

   -- Greg

On Thu, Mar 14, 2019, 01:50 Timo Aaltonen  wrote:

> gallium osmesa is already enabled where it's supported, so what's your
> platform?
>
> ** Changed in: mesa (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1803681
>
> Title:
>   osmesa doesn't suport core contexts but could
>
> Status in mesa package in Ubuntu:
>   Incomplete
>
> Bug description:
>   If the --enable-osmesa in the mesa configuration were replaced with
>   --enable-gallium-osmesa, then the OSMesaCreateContextAttribs would be
>   able to return OpenGL core contexts.  To show this I'm attaching a
>   modified version of mesa-demos-8.4.0/src/osdemos/osdemo.c (from
>   ftp://ftp.freedesktop.org/pub/mesa/demos/mesa-demos-8.4.0.tar.gz).
>   The modified code is all within the #ifdef USE_CORE_CONTEXT.  To
>   compile it, do "gcc osdemo.c -lGLU -lOSMesa -lm".  With the
>   libOSMesa.so.8 from Ubuntu 18.04, it fails with "OSMesaCreateContext
>   failed!".  But with a libOSmesa.so from a mesa that is configured with
>   --enable-galliums-osmesa instead of --enable-osmesa, it works!
>
>   Also note that libOSMesa.so on Ubuntu 18.04 only supports OpenGL 2.1.
>   While --enable-gallium-osmesa gets it up to OpenGL 3.3.  My testing
>   was with mesa 17.3.9 and mesa 18.2.5.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803681/+subscriptions
>

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

Title:
  osmesa doesn't suport core contexts but could

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  If the --enable-osmesa in the mesa configuration were replaced with
  --enable-gallium-osmesa, then the OSMesaCreateContextAttribs would be
  able to return OpenGL core contexts.  To show this I'm attaching a
  modified version of mesa-demos-8.4.0/src/osdemos/osdemo.c (from
  ftp://ftp.freedesktop.org/pub/mesa/demos/mesa-demos-8.4.0.tar.gz).
  The modified code is all within the #ifdef USE_CORE_CONTEXT.  To
  compile it, do "gcc osdemo.c -lGLU -lOSMesa -lm".  With the
  libOSMesa.so.8 from Ubuntu 18.04, it fails with "OSMesaCreateContext
  failed!".  But with a libOSmesa.so from a mesa that is configured with
  --enable-galliums-osmesa instead of --enable-osmesa, it works!

  Also note that libOSMesa.so on Ubuntu 18.04 only supports OpenGL 2.1.
  While --enable-gallium-osmesa gets it up to OpenGL 3.3.  My testing
  was with mesa 17.3.9 and mesa 18.2.5.

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

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

[Desktop-packages] [Bug 1819920] Re: gnome-session-quit --power-off option ignored

[Bug Watch Updater]

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

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

Title:
  gnome-session-quit --power-off option ignored

Status in gnome-session:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  OS: Ubuntu 18.04

  Command: gnome-session-quit --power-off
  Expected behaviour: Power off dialogue, with "Power Off" selected
  Actual behaviour:  Power off dialogue, with "Cancel" selected

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

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

[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

[Łukasz Zemczak]

** Changed in: gradle (Ubuntu Cosmic)
   Status: New => Fix Committed

** Changed in: jameica (Ubuntu Cosmic)
   Status: New => Fix Committed

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in ca-certificates-java package in Ubuntu:
  New
Status in fonts-liberation2 package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in libjogl2-java package in Ubuntu:
  New
Status in libpdfbox-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mongo-java-driver package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openhft-chronicle-threads package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New
Status in virtualbox-hwe package in Ubuntu:
  New
Status in activemq source package in Bionic:
  Fix Committed
Status in afterburner.fx source package in Bionic:
  Fix Committed
Status in annotation-indexer source package in Bionic:
  Fix Committed
Status in apache-directory-server source package in Bionic:
  Fix Committed
Status in aspectj source package in Bionic:
  Fix Committed
Status in aspectj-maven-plugin source package in Bionic:
  Fix Committed
Status in batik source package in Bionic:
  Fix Committed
Status in bindex source package in Bionic:
  Fix Committed
Status in bridge-method-injector source package in Bionic:
  Fix Committed
Status in carrotsearch-hppc source package in Bionic:
  Fix Committed
Status in clojure source package in Bionic:
  Fix Committed
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in commons-httpclient source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in ecj source package in Bionic:
  Fix Committed
Status in eclipselink source package in Bionic:
  Fix Committed
Status in elki source package in Bionic:
  Fix Committed
Status in figtree source package in Bionic:
  Fix Committed
Status in fontawesomefx source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gluegen2 source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gradle-debian-helper source package in Bionic:
  Fix Committed
Status in groovy source package in Bionic:
  Fix Committed
Status in hikaricp source package in Bionic:
  Fix Committed
Status in hsqldb source package in Bionic:
  Fix Committed
Status in hsqldb1.8.0 source package in Bionic:
  Fix Committed
Status in insubstantial source package in Bionic:
  Fix Committed
Status in jabref source package in Bionic:
  Fix Committed
Status in jackson-core source package in Bionic:
  Fix Committed
Status in jackson-databind source package in Bionic:
  Fix Committed
Status in jackson-dataformat-xml source package in Bionic:
  Fix Committed
Status in jackson-module-jaxb-annotations source package in Bionic:
  Fix Committed
Status in java-common source package in Bionic:
  Fix Committed
Status in javafxsvg source package in Bionic:
  Fix Committed
Status in javamail source package in Bionic:
  Fix Committed
Status in javatools source package in Bionic:
  Fix Committed
Status in jboss-classfilewriter source package in Bionic:
  Fix Committed
Status in jboss-jdeparser2 source package in Bionic:
  Fix Committed
Status in jboss-modules source package in Bionic:
  Fix Committed
Status in jcommander source package in Bionic:
  Fix Committed
Status in jersey1 source package in Bionic:
  Fix Committed
Status in jftp source package in Bionic:
  Fix Committed
Status in jhove source package in Bionic:
  Fix Committed
Status in jmdns source package in Bionic:
  Fix Committed
Status in jnr-posix source package in Bionic:
  Fix Committed
Status in jruby source package in Bionic:
  Fix Committed
Status in jruby-openssl source package in Bionic:
  Fix Committed
Status in jtreg source package in Bionic:
  Fix Committed
Status in jts source package in Bionic:
  Fix Committed
Status in junit4 source package in Bionic:
  Fix Committed
Status in jxgrabkey source package in Bionic:
  Fix Committed
Status in jython source package in Bionic:
  Fix Committed
Status in libapache-poi-java source package in Bionic:
  Fix Committed
Status in libbtm-java source package in Bionic:
  Fix Committed
Status in libcommons-collections3-java source pack

[Desktop-packages] [Bug 1820355] [NEW] Firefox icon missing

[Joe Barnett]

Public bug reported:

I have firefox bookmarked in the gnome-shell dash.  When starting the
shell in disco, the firefox logo is missing and the launcher is a small
but clickable blank area.  If I use gnome-tweaks to change icon theme,
the logo reappears for the rest of the session.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0-1ubuntu1
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: GNOME
Date: Fri Mar 15 14:22:32 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-26 (170 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago)

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


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

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

Title:
  Firefox icon missing

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have firefox bookmarked in the gnome-shell dash.  When starting the
  shell in disco, the firefox logo is missing and the launcher is a
  small but clickable blank area.  If I use gnome-tweaks to change icon
  theme, the logo reappears for the rest of the session.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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: GNOME
  Date: Fri Mar 15 14:22:32 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-26 (170 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago)

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

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

[Desktop-packages] [Bug 1704740]

[Oliver-brinzing]

this issue is no longer reproducible with:

Version: 6.3.0.0.alpha0+ (x64)
Build ID: 3140194a85fe4a6ac69c8cddc4d3b019430cd6e8
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-US
Calc: threaded

-> F2 is 22 now after pasting

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

Title:
  calc: move cell does not update row sum

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

Bug description:
  See attached test case.  Sum two rows: A1 + B1 = C1; A2 + B2 = C2
  where B1 is blank.  Cut B2 and paste into B1.  Result C2 is
  decremented correctly by old B2 value; but result C1 is NOT
  incremented by new B1 value.  Formula of C1 remains correct
  =SUM($Sheet1.A1:B1) as is C2's formula but C1 result is wrong.  Saving
  file, close and re-open does not fix incorrect C1 result.  Undo undo
  to return to initial state results in C2 now having incorrect result.
  Bug occurs whether drag and drop or control-x/control-v used. This is
  a data integrity issue as the wrong answer is being displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 17 17:33:42 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-08 (435 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812754]

[Kevin O'Gorman]

Sorry, I do not have a spare machine to download the software.

When I first reported this to Ubuntu I got immediate confirmation, and
they suggested I re-submit to you.  If you have the latest  software,
please give it a try.  It will either fail or not in a hurry.  Maybe 5
minutes max will any downloading and directory prep you decide to do.

I set it back to unconfirmed.

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

Title:
  Libreoffice writer adds blank pages on multiple inputs

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

Bug description:
  When I have multiple .txt files on the command line and start
  libreoffice writer, it adds (many) blank pages to the documents.
  These blanks contain nothing at all and I have not figured out how to
  remove them.  But they are included when I print them.

  I'm attaching a file on which this happens.  It contains an anonymized
  fragment of the original, repeates a number of times.  I suggest you
  create two copies, called perhaps junk1.txt and junk2.txt.

  I use the command "soffice junk*" to load them into the writer, and I
  get the extra blank pages.

  If, however, I just do soffice junk1.txt, I get a document of the
  correct size.

  I can do that of course, but it is still an annoying and inconvenient
  error for my workflow.

  ---

  One hint to debugging: if I do this:

  for i in junk1.txt junk2.txt
  do
soffice $i &
  done

  I see the problem.  If, however, I introduce a delay the problem does
  not appear.  Like so:

  for i in junk1.txt junk2.txt
  do
sleep 2
soffice $i &
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.7-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jan 21 13:58:01 2019
  InstallationDate: Installed on 2018-10-18 (95 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812754] Re: Libreoffice writer adds blank pages on multiple inputs

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Incomplete => New

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

Title:
  Libreoffice writer adds blank pages on multiple inputs

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

Bug description:
  When I have multiple .txt files on the command line and start
  libreoffice writer, it adds (many) blank pages to the documents.
  These blanks contain nothing at all and I have not figured out how to
  remove them.  But they are included when I print them.

  I'm attaching a file on which this happens.  It contains an anonymized
  fragment of the original, repeates a number of times.  I suggest you
  create two copies, called perhaps junk1.txt and junk2.txt.

  I use the command "soffice junk*" to load them into the writer, and I
  get the extra blank pages.

  If, however, I just do soffice junk1.txt, I get a document of the
  correct size.

  I can do that of course, but it is still an annoying and inconvenient
  error for my workflow.

  ---

  One hint to debugging: if I do this:

  for i in junk1.txt junk2.txt
  do
soffice $i &
  done

  I see the problem.  If, however, I introduce a delay the problem does
  not appear.  Like so:

  for i in junk1.txt junk2.txt
  do
sleep 2
soffice $i &
  done

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer 1:6.0.7-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jan 21 13:58:01 2019
  InstallationDate: Installed on 2018-10-18 (95 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 201391] Re: Headset volume control doesn't change headset volume

[CuTeBoi]

Sorry, forgot to mention I'm on


```
workstation:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic
```

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

Title:
  Headset volume control doesn't change headset volume

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I use Kubuntu Hardy and have a Plantronics USB headset that has its
  own volume and mute controls.

  When using its volume controls, they affect the master volume only and
  have no effect on the headset volume.  I can only alter the headset
  volume by going into kmix and selecting the appropriate device and
  altering its PCM volume.

  The master volume setting should affect the headset volume too.

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

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

[Desktop-packages] [Bug 201391] Re: Headset volume control doesn't change headset volume

[CuTeBoi]

This occurs with G933 Logitech.

I have my default audio as the line out.  But I use the G933 headset for
chrome output.  Changing volume on the headset results in a default
media key volume up and down.  It's only controlling the configured
default audio in the volume controls.

Anything I can provide?

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

Title:
  Headset volume control doesn't change headset volume

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I use Kubuntu Hardy and have a Plantronics USB headset that has its
  own volume and mute controls.

  When using its volume controls, they affect the master volume only and
  have no effect on the headset volume.  I can only alter the headset
  volume by going into kmix and selecting the appropriate device and
  altering its PCM volume.

  The master volume setting should affect the headset volume too.

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

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

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

[Gašper Sedej]

I disagree with "invalid" bug in launchpad. Problem in in packaging.
User should not manually install " gstreamer1.0-gtk3" package

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

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

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

Bug description:
  LibreOffice Impress has problematic embedded video playback.

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS

[Bruno Haible]

The FTBFS was fixed upstream, in gnulib (from which libunistring takes most of 
its source files), through this commit:
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=cca32830b57e91f837c01d15b8732f23ff97fc36

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

Title:
  libunistring ftbfs on 18.04 LTS

Status in libunistring package in Ubuntu:
  Fix Released
Status in libunistring source package in Bionic:
  In Progress
Status in libunistring package in Debian:
  Won't Fix

Bug description:
  Impact
  --
  libunistring doesn't build from source which means someone would need to fix 
that problem before fixing any bugs in the libunistring package for Ubuntu 
18.04 LTS.

  Test Case
  -
  Does libunistring build successfully?

  Regression Potential
  
  We are simply backporting the workaround we applied in Ubuntu 18.10.

  Original Bug Report
  ---
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  libunistring ftbfs.

  FAIL: test-thread_create
  

  glthread_create failed
  FAIL test-thread_create (exit status: 1)

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

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

[Desktop-packages] [Bug 1820331] Re: gnome-shell crashed with SIGABRT

[Anders Kaseorg]

** 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/1820331

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In the last few weeks, gnome-shell has been crashing almost every time
  I open my laptop to wake it from suspend.  The rapid pace of package
  updates has stopped Apport from letting me report it until now, but
  the problem persists.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 15 11:22:20 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (1120 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to disco on 2018-12-15 (90 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd 
mock plugdev sambashare sbuild sudo wireshark
  separator:

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

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

[Desktop-packages] [Bug 1577927] Re: After upgrade, can no longer set tab titles

[Tobin Davis]

This was fixed upstream in 3.20 (with a rather nasty commit message),
but even on 3.28 it is not working in Ubuntu 18.04.  A brief (5 minute)
examination of the code shows that it is there in the Ubuntu source
package.  Someone that actually maintains this will know more of why it
is still broken.

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

Title:
  After upgrade, can no longer set tab titles

Status in GNOME Terminal:
  Unknown
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in gnome-terminal package in Debian:
  Confirmed
Status in gnome-terminal package in Fedora:
  Unknown

Bug description:
  Under the previous version, 14.04 LTS, I could quickly hit 'ALT-t',
  then 's', then type in the text that would appear on that terminal
  tab. This is HUGELY IMPORTANT, as the main reason I run Linux is so
  that I can quickly and easily do my work, involving dozens of terminal
  tabs, ssh'ed into dozens of different servers. Generally, when I open
  a new tab, I label it for future reference. Imagine having a dozen
  tabs open, some of them connected to production databases, and others
  connected to development databases. I need to be able to easily
  identify which ones are which. (I also edited the config files, to
  make the active tab be red instead of grey.)

  But now that I've upgraded to 16.04 LTS, I'm crippled! I can't find
  any way to set the names of the terminal tabs. I'm not sure what I'll
  do! Go hunting for a different terminal program, maybe?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_uvm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  3 14:23:28 2016
  InstallationDate: Installed on 2016-04-27 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

[Caleb Brinkley]

This also affects me on a fresh Arch Linux install with the RX 580 8GB
GPU. I have found a temporary workaround to this issue until it is
finally solved. I used Budgie Settings to enable the execution of this
command each time it enters the environment:

xrandr --output HDMI-A-0 --mode 1920x1080 -r 60

This disables the flickering if executed as the system enters the
desktop environment. Replace your output with whatever you use (in my
case, I use HDMI-A-0). Of course, it will cap your frame-rate at 60Hz
but it's better than having the flickering lines at the bottom of the
screen.

Your use may vary, but this worked for me.

** Also affects: archlinux
   Importance: Undecided
   Status: New

** Package changed: archlinux => linux (Arch Linux)

** No longer affects: linux (Arch Linux)

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

Title:
  [amdgpu] Flickering graphics corruption (but none observed in kernels
  4.18.10-4.18.12)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 
60 and 50 GHz, if you switch to any other than 75, the flickering will 
disappear until the display turns off. After switching on, flicker returns. At 
the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is 
not visible. More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1820323] [NEW] xorg crash

[Jill Manfield]

Public bug reported:

This is on Precision 3620, Precision 5820, Precision 7820 - systems with
AMD bundled for OEM fail to properly boot after update/upgrade.  I
believe this is related to this issue:

https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory

Since our image contains the amdgpu-pro package we are impacted.
Canonical image is not impacted.

Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues 
with AMD GPUs after running system updates on the OEM Ubuntu image.
After running sudo apt-get update && apt-get upgrade, the system will exhibit 
one of a few different behaviors:
•   Boots to a black screen
•   Loops at login
•   Boots to a screen indicating the system has been forced to low graphics 
mode and hard locks.
I have a systems in the lab that exhibits this issue and I don’t know how to 
get around it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
Uname: Linux 4.4.0-143-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
BootLog:
 Scanning for Btrfs filesystems
 UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Mar 15 13:22:36 2019
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: Dell Device [1028:06c7]
 Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] 
[1002:6995] (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0b0c]
InstallationDate: Installed on 2019-03-14 (0 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
MachineType: Dell Inc. Precision Tower 3420
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic 
root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.11.2
dmi.board.name: 02K9CR
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr:
dmi.product.name: Precision Tower 3420
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Mar 15 13:21:28 2019
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug crash ubuntu xenial

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

Title:
  xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  This is on Precision 3620, Precision 5820, Precision 7820 - systems
  with AMD bundled for OEM fail to properly boot after update/upgrade.
  I believe this is related to this issue:

  https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory

  Since our image contains the amdgpu-pro package we are impacted.
  Canonical image is not impacted.

  Various systems (Precision 3420, 3620, 5820, and 7820) are having login 
issues with AMD GPUs after running system updates on the OEM Ubuntu image.
  After running sudo apt-get update && apt-get upgrade, the system will exhibit 
one of a few different behaviors:
  • Boots to a black screen
  • Loops at login
  • Boots to a screen indicating the system has been forced to low graphics 
mode and hard locks.
  I have a systems in the lab that exhibits this issue and I don’t know how to 
get around it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13

[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic

[Stefan]

This should also be fixed in the PPA:
ppa:graphics-drivers/ppa

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

Title:
  Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04
  in bionic

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released

Bug description:
  I am trying to test new HWE stack from 18.10 in my destkop Ubuntu
  18.04.1 (expected release 18.04.2 this week) and I have broken
  dependencies when installing `xserver-xorg-hwe-18.04` package with
  NVidia drivers:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
xserver-xorg-video-nvidia-390 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-nvidia-390 is already the newest version 
(390.77-0ubuntu0.18.04.1).
  xserver-xorg-video-nvidia-390 set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 
2:1.17.2-2) but it is not going to be installed
Conflicts: xserver-xorg-core (>= 0~)
Recommends: xserver-xorg-video-all-hwe-18.04 but it 
is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` 
this happens:

  me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 
libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 
libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386
libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 
libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 
libnvidia-compute-390:i386 libnvidia-decode-390
libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 
libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 
libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386
libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 
libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 
libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386
libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 
libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 
libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers
nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 
nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 
pkg-config screen-resolution-extra vdpau-driver-all
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 
xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 
xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 
xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 
xserver-xorg-video-radeon-hwe-18.04
xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04
  Suggested packages:
xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 
xserver-xorg-video-mach64 firmware-misc-nonfree
  Recommended packages:
xserver-xorg-input-wacom-hwe-18.04
  The following packages will be REMOVED:
nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all 
xserver-xorg-input-libinput xserver-xorg-video-nvidia-390
  The following NEW packages will be installed:
xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 
xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 
xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04
xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 
xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 
xserver-xorg-video-qxl-hwe-18.04
xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 
xserver-xorg-video-vmware-hwe-18.04
  0 upgraded, 14 newly installed, 6 to 

[Desktop-packages] [Bug 1820062]

[kompilainenn]

Close as WFM after comment 4 and comment 5

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

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

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

Bug description:
  LibreOffice Impress has problematic embedded video playback.

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

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

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

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

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

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

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

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

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

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

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

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

Bug description:
  LibreOffice Impress has problematic embedded video playback.

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1820314] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all

[nicola]

In the summary it is shown xubuntu 16.04 by I upgraded a long time ago to 18.04 
lts both the problem occured even under 16.04 lts
https://forum.ubuntuusers.de/topic/audio-problem-wie-folgend/

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  cannot hear any sound even with headphones from any of 2 rear output
  port (green and blue) of my asrock fm2a75m-dgs or the front unique
  one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:32:51 2019
  InstallationDate: Installed on 2016-09-07 (918 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel 
model=auto
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882

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

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

[Desktop-packages] [Bug 1820314] [NEW] [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all

[nicola]

Public bug reported:

cannot hear any sound even with headphones from any of 2 rear output
port (green and blue) of my asrock fm2a75m-dgs or the front unique one.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 15 17:32:51 2019
InstallationDate: Installed on 2016-09-07 (918 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: Audio interno - HD-Audio Generic
Symptom_Jack: Green Line Out, Rear
Symptom_Type: No sound at all
Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.70
dmi.board.name: FM2A75M-DGS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel 
model=auto
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  cannot hear any sound even with headphones from any of 2 rear output
  port (green and blue) of my asrock fm2a75m-dgs or the front unique
  one.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:32:51 2019
  InstallationDate: Installed on 2016-09-07 (918 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel 
model=auto
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882

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

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

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[ekimai]

I have a theory, and it isust a theory...

The hotkey to change desktops is Ctrl+Alt+UP/DOWN
The hotkey on the Android emulator to pinch zoom is Ctrl+Alt with mouse drag.

When the emulator is the active window, and you press Ctrl+Alt, then a
graphic appears on the emulator showing the pinch zoom function.  This
graphic is often left on the display as an artefact overlayed on the new
desktop, when the crash occurs.

As I said, just a theory, and I don't want to point anyone in the wrong
direction :)

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gjs source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717951] Re: UIFe: Drop imagemagick-display from the default install

[amano]

As Sebastien Bacher pointed out, ImageMagick can be removed for good now
as CUPS does no longer depend on it in Disco.

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

Title:
  UIFe: Drop imagemagick-display from the default install

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in imagemagick package in Debian:
  New

Bug description:
  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.

  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.

  I am proposing splitting the display app to a separate binary package
  so that it is available for install for the few who do want to use the
  app.

  I tried proposing this to Debian. See comment #60 on the attached
  Debian bug but the Debian maintainer doesn't seem interested in
  accepting my proposal any time soon. (I emailed him directly a few
  months ago too.)

  List Notifications
  ==
  https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html
  
https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html

  Other Info
  ==
  I will be attaching a patch for review by the Desktop Team here soon.

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

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

[Desktop-packages] [Bug 1815742] Re: latest network-manager segfaults in disco

[Sebastien Bacher]

Do you still get the issue with the .91 update? 
Upstream would like to get 'the /etc/network/interfaces file (and interfaces.d 
directory, if applicable)', can you get those if you still have the issue?

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

** Changed in: network-manager (Ubuntu)
 Assignee: Till Kamppeter (till-kamppeter) => (unassigned)

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1815759] Re: Does not recognize connected HDMI monitor

[Timo Aaltonen]

The actual driver is in the kernel, which in your case is ancient

If 5.0 doesn't work, file a bug upstream and hope for the best

** Package changed: xserver-xorg-video-nouveau (Ubuntu) => linux
(Ubuntu)

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

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

Title:
  Does not recognize connected HDMI monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Strandely 'sudo lshw -c video' told nouveau is in use even if xserver-
  xorg-video-nouveau was not installed. With or without, HDMI does not
  work unlike with proprietary driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog: root: clean, 318243/1281120 files, 2346720/512 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Feb 13 14:16:02 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-140-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-141-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-143-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2015-11-21 (1179 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (970) killed by TERM signal
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash 
vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Feb 13 14:12:08 2019
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

[Knut Sindre Åbjørsbråten]

Hi. On 18.10 with proposed enabled the screen now renders at > 60 Hz and
feels smooth (:  This fixes the issue for me. Thank you for you hard
work guys.

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

Title:
  144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Released
Status in mutter source package in Disco:
  Fix Released

Bug description:
  [Impact]

  Gnome Shell redraws at 60 FPS at most, regardless of the hardware
  refresh rate, and regardless of the current display mode. This is
  particularly annoying for owners of 144Hz/120Hz/240Hz displays.

  [Test Case]

  0. Find a monitor or laptop with a high refresh rate (120Hz or more),
  noting NOT to trust gnome-control-center or xrandr because an
  unrelated bug in mutter may cause those to report 120Hz even on 60Hz
  displays. Make sure the advertised hardware specs show the display is
  a high frame rate.

  1. Edit /etc/environment and add:
     CLUTTER_SHOW_FPS=1

  2. Reboot.

  3. Open a terminal window and run:
     journalctl -f | grep FPS

  4. In a new window run 'glmark2' or some other OpenGL benchmark that
  is not frame rate limited (note: glxgears for unrelated reasons IS
  frame rate limited in Wayland sessions, but can be used in Xorg
  sessions).

  5. Verify the terminal window from step 4 shows high FPS values coming
  from the journalctl log that match the hardware spec, and are much
  higher than 60.

  [Regression Potential]

  Medium to low. This patch has been used upstream and in Ubuntu 19.04
  for some months already without any issues. Although minor syntactical
  changes had to be made to avoid conflicts when backporting it from
  mutter 3.32 to mutter 3.30. If regressions did occur they would be
  visible in the frame rate of the entire screen.

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

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

[Desktop-packages] [Bug 1820303] [NEW] Ubuntu 18.04 LTS

[Christopher Wilson]

Public bug reported:

Failure to display prior desktop login GUI (Cinnamon).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Mar 15 11:46:27 2019
DistUpgraded: 2019-03-15 10:30:23,145 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 7340] [1043:14e7]
InstallationDate: Installed on 2019-03-11 (4 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
MachineType: ASUSTeK COMPUTER INC. X55U
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-03-15 (0 days ago)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X55U.423
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X55U
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX55U.423:bd08/06/2013:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X55U
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Mar 15 11:19:59 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2
xserver.video_driver: radeon

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


** Tags: apport-bug bionic i386 ubuntu

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

Title:
  Ubuntu 18.04 LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  Failure to display prior desktop login GUI (Cinnamon).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Mar 15 11:46:27 2019
  DistUpgraded: 2019-03-15 10:30:23,145 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 7340] [1043:14e7]
  InstallationDate: Installed on 2019-03-11 (4 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  MachineType: ASUSTeK COMPUTER INC. X55U
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-15 (0 days ago)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X55U.423
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X55U
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset 

[Desktop-packages] [Bug 1819503] Re: Drop imagemagick-display from the default install [disco regression]

[Sebastien Bacher]

Thank you for your bug report, the change was reverted from the ubuntu-
settings overide and done in imagemagick itself, that has been removed
in disco with the rtaional that imagemagick is not installed by default

https://launchpad.net/ubuntu/+source/imagemagick/8:6.9.10.14+dfsg-
7ubuntu1

'  * Dropped changes:
- Stop installing the Debian-specific .desktop for the display program.
  + 'imagemagick' is no longer installed by default for default Ubuntu
so let's try dropping this change for now.'

You can probably install it, but maybe that should be done automatically
on upgrade...

** Package changed: ubuntu-settings (Ubuntu) => imagemagick (Ubuntu)

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

** Changed in: imagemagick (Ubuntu)
   Status: New => Opinion

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

Title:
  Drop imagemagick-display from the default install  [disco regression]

Status in imagemagick package in Ubuntu:
  Opinion

Bug description:
  This is actually a regression in Disco from Artful, Bionic and Cosmic,
  where this was fixed in https://bugs.launchpad.net/bugs/1717951

  
  I tested this in the "Ubuntu", "Ubuntu on Wayland" and "GNOME" session and 
the bug is visible in all three instances.

  Since the update to Disco the rather unprofessional ImageMagick icon
  is back. It was removed in Artful, Bionic and Cosmic for the following
  reasons, perfectly summed up by Jeremy Bicha (a copy and paste from
  Bug #171951):

  
  Impact
  ==
  I'm proposing to drop the ImageMagick app from the default Ubuntu 17.10.

  It is visible in the Show Applications view of the Activities Overview
  so this could impact screenshots.

  Justification
  =
  imagemagick is a collection of commandline utilities for working with images, 
photos, etc. It is a required dependency for many things and will still be 
installed by default.

  Bundled with imagemagick is the "display" app, which is an app with an
  unusual, difficult-to-use UI. It was not intentionally included in the
  default Ubuntu install but was only there because it was packaged
  together.

  I am proposing splitting the display app to a separate binary package
  so that it is available for install for the few who do want to use the
  app.

  I tried proposing this to Debian. See comment #60 on the attached
  Debian bug but the Debian maintainer doesn't seem interested in
  accepting my proposal any time soon. (I emailed him directly a few
  months ago too.)

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

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

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus

[Olivier Tilloy]

Fully up-to-date Fedora 29 VM, the chromium snap still fails to launch
with the same error.

** Also affects: snapd
   Importance: Undecided
   Status: New

** Summary changed:

- [snap] core18-based snap fails to start on Solus
+ [snap] core18-based snap fails to start on Solus/fedora29

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

Title:
  [snap] core18-based snap fails to start on Solus/fedora29

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  After installation of chromium and I try to start it I get this error
  inside my terminal.

  fredu  ~  chromium 
  execv failed: No such file or directory

  System:
  Description:Solus
  Release:3.

  Chromium:   stable
  snapd:  2.36.2

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

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

[Desktop-packages] [Bug 1795121] Re: 18.10: Indicator icons not shown in the panel

[Sebastien Bacher]

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

The description from comment #3 and the recent log with
'[AppIndicatorSupport-WARN] Failed to acquire org.kde.StatusNotifierWatcher'
suggests it's a duplicate of bug #1819103 and a conflict with 
indicator-applications being fixed/SRUed

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Importance: Undecided => High

** This bug has been marked a duplicate of bug 1819103
   Indicator Application and indicator-applet does not show indicators

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

Title:
  18.10: Indicator icons not shown in the panel

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  The indicator icons are not showing on a fresh installation of Ubuntu
  18.10 beta. On 18.04 I can see the tray icons of Chrome, Hangouts,
  Dropbox and InSync but on 18.10 they are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell-extension-appindicator 22-1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 29 10:00:34 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-09-28 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers

[Iain Lane]

OK for the FFe - please could you work with Christian to get this
uploaded / upstream / etc in the best way?

Thanks :>

-- 
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:
  Triaged
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in open-vm-tools source package in Disco:
  Triaged
Status in ubiquity source package in Disco:
  Triaged
Status in ubuntu-drivers-common source package in Disco:
  In Progress

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 must be in main.

  [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 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => 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/1819890

Title:
  Restarting gnome-shell displays images of applications running on
  other workspaces

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

Bug description:
  Restarting gnome-shell with 'Alt-F2,r and enter' displays images of
  applications running on other workspaces which are not clickable.

  Steps to reproduce:

  1) Enable multiple workspaces
  2) Start an application on each workspace
  3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter'

  Expected outcome:

  As with Ubuntu 18.04, each application is displayed only the workspace
  on which it was started.

  Actual outcome:

  All applications are displayed on the current workspace. The
  applications running on other workspaces are displayed as images, i.e.
  they cannot be 'clicked' but he 'wanted' application, the dock, top
  bar etc all function correctly.

  Workaround:

  To remove the unwanted images move to another workspace and return.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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: Wed Mar 13 10:15:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-20 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

[fessmage]

Same thing.

gnome-shell/bionic-updates,now 3.28.3-0ubuntu0.18.04.4 amd64 [installed]
gnome-shell-common/bionic-updates,bionic-updates,now 3.28.3-0ubuntu0.18.04.4 
all [installed]

but the bug is still here. Reboot don't help.

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  [ Impact ]

  Keyboard Layout indicator don't display current layout (empty selected
  drop down box)

  [ Test case ]

  1. Boot
  2. Suspend or lock the screen
  3. Log again with your user
  4. The keyboard indicator should display current layout

  [ Regression Potential ]

  Really low, we properly pass a null value instead of an undefined one,
  without breaking JS.

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  [ Workarounds ]

  - Switch with keyboard (Super+space) or mouse. BUT if you then logout
  on the login screen *when you press the first character* of the
  password the shown selected keyboard layout resets.

  - Restart Gnome Shell (Alt+F2 r):
  https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

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

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

[Desktop-packages] [Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces

[Sebastien Bacher]

Thanks!

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

Title:
  Restarting gnome-shell displays images of applications running on
  other workspaces

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

Bug description:
  Restarting gnome-shell with 'Alt-F2,r and enter' displays images of
  applications running on other workspaces which are not clickable.

  Steps to reproduce:

  1) Enable multiple workspaces
  2) Start an application on each workspace
  3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter'

  Expected outcome:

  As with Ubuntu 18.04, each application is displayed only the workspace
  on which it was started.

  Actual outcome:

  All applications are displayed on the current workspace. The
  applications running on other workspaces are displayed as images, i.e.
  they cannot be 'clicked' but he 'wanted' application, the dock, top
  bar etc all function correctly.

  Workaround:

  To remove the unwanted images move to another workspace and return.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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: Wed Mar 13 10:15:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-20 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820230] Re: spotify (snap) starts in fullscreen without windows decorations

[Jean-Baptiste Lallement]

The id matches the id of the window manager warning.

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

Title:
  spotify (snap) starts in fullscreen without windows decorations

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Disco up to date
  spotify 1.1.0.237.g378f6f25-11
  session: Ubuntu on Xorg
  1 display
  screen #0:
dimensions:1920x1080 pixels (508x285 millimeters)
resolution:96x96 dots per inch

  When spotify is closed in fullscreen mode, on next start it starts
  like a fullscreen app without any window decoration. There is then no
  way to control the app. window.

  The following message is displayed in the logs
  mars 15 10:45:06 sark org.gnome.Shell.desktop[4668]: Window manager warning: 
Treating resize request of legacy application 0x421 as a fullscreen request 

  

  Test Case:
  1. Start Spotify
  2. Switch to fullscreen (arrows on the bottom right corner)
  3. Close Spotify with ALT+F4
  4. Open Spotify again

  Actual Result
  The apps launches in fullscreen without any windows control and no way to 
switch to normal mode.

  Workaround
  click on the arrow to switch to fullscreen then again to switch to normal 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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 15 10:38:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1704 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-03-24 (355 days ago)

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

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

[Desktop-packages] [Bug 1820230] Re: spotify (snap) starts in fullscreen without windows decorations

[Jean-Baptiste Lallement]

xwininfo: Window id: 0x3a1 "Spotify"

  Absolute upper-left X:  0
  Absolute upper-left Y:  0
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 1920
  Height: 1080
  Depth: 24
  Visual: 0x21
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x20 (installed)
  Bit Gravity State: ForgetGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +0+0  -0+0  -0-0  +0-0
  -geometry 1920x1080+0+0

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

Title:
  spotify (snap) starts in fullscreen without windows decorations

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Disco up to date
  spotify 1.1.0.237.g378f6f25-11
  session: Ubuntu on Xorg
  1 display
  screen #0:
dimensions:1920x1080 pixels (508x285 millimeters)
resolution:96x96 dots per inch

  When spotify is closed in fullscreen mode, on next start it starts
  like a fullscreen app without any window decoration. There is then no
  way to control the app. window.

  The following message is displayed in the logs
  mars 15 10:45:06 sark org.gnome.Shell.desktop[4668]: Window manager warning: 
Treating resize request of legacy application 0x421 as a fullscreen request 

  

  Test Case:
  1. Start Spotify
  2. Switch to fullscreen (arrows on the bottom right corner)
  3. Close Spotify with ALT+F4
  4. Open Spotify again

  Actual Result
  The apps launches in fullscreen without any windows control and no way to 
switch to normal mode.

  Workaround
  click on the arrow to switch to fullscreen then again to switch to normal 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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 15 10:38:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1704 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-03-24 (355 days ago)

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

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

[Desktop-packages] [Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces

[Paul White]

Reported upstream as requested.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1059
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1059

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1059
   Importance: Unknown
   Status: Unknown

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

Title:
  Restarting gnome-shell displays images of applications running on
  other workspaces

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

Bug description:
  Restarting gnome-shell with 'Alt-F2,r and enter' displays images of
  applications running on other workspaces which are not clickable.

  Steps to reproduce:

  1) Enable multiple workspaces
  2) Start an application on each workspace
  3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter'

  Expected outcome:

  As with Ubuntu 18.04, each application is displayed only the workspace
  on which it was started.

  Actual outcome:

  All applications are displayed on the current workspace. The
  applications running on other workspaces are displayed as images, i.e.
  they cannot be 'clicked' but he 'wanted' application, the dock, top
  bar etc all function correctly.

  Workaround:

  To remove the unwanted images move to another workspace and return.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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: Wed Mar 13 10:15:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-20 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820230] Re: spotify (snap) starts in fullscreen without windows decorations

[Jean-Baptiste Lallement]

xprop 
_NET_WM_ICON(CARDINAL) = 
WM_CLASS(STRING) = "spotify", "Spotify"
_NET_WM_STATE(ATOM) = _NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_FOCUSED
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_DESKTOP(CARDINAL) = 0
_GTK_EDGE_CONSTRAINTS(CARDINAL) = 170
_NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 0, 0
WM_NAME(STRING) = "Spotify"
_NET_WM_NAME(UTF8_STRING) = "Spotify"
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_FULLSCREEN, 
_NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, 
_NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW
XdndProxy(WINDOW): window id # 0x3a2
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified location: 0, 0
window gravity: Static
_NET_WM_PID(CARDINAL) = 10041
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "sark"
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, _NET_WM_PING

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

Title:
  spotify (snap) starts in fullscreen without windows decorations

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Disco up to date
  spotify 1.1.0.237.g378f6f25-11
  session: Ubuntu on Xorg
  1 display
  screen #0:
dimensions:1920x1080 pixels (508x285 millimeters)
resolution:96x96 dots per inch

  When spotify is closed in fullscreen mode, on next start it starts
  like a fullscreen app without any window decoration. There is then no
  way to control the app. window.

  The following message is displayed in the logs
  mars 15 10:45:06 sark org.gnome.Shell.desktop[4668]: Window manager warning: 
Treating resize request of legacy application 0x421 as a fullscreen request 

  

  Test Case:
  1. Start Spotify
  2. Switch to fullscreen (arrows on the bottom right corner)
  3. Close Spotify with ALT+F4
  4. Open Spotify again

  Actual Result
  The apps launches in fullscreen without any windows control and no way to 
switch to normal mode.

  Workaround
  click on the arrow to switch to fullscreen then again to switch to normal 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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 15 10:38:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1704 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-03-24 (355 days ago)

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

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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-340 -
340.107-0ubuntu0.14.04.1

---
nvidia-graphics-drivers-340 (340.107-0ubuntu0.14.04.1) trusty; urgency=medium

  * New upstream release:
- Added support for X.Org xserver ABI 24 (xorg-server 1.20).
- Improved nvidia-bug-report.sh to check for kern.log which is
  the default kernel log-file location for many Debian-based
  Linux distributions.
- Fixed a bug which could cause X servers that export a Video
  Driver ABI earlier than 0.8 to crash when running X11
  applications which call XRenderAddTraps().
  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_4.4_get_user_pages.patch:
   - Drop buildfix_kernel_4.9.patch and buildfix_kernel_4.10.patch.
   - Add support for new 7 argument get_user_pages() (LP: #1573508).
  * debian/substvars:
   - Add support for X ABI 24.

 -- Alberto Milone   Mon, 04 Mar 2019
11:18:48 +0100

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions

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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-384 -
384.130-0ubuntu0.14.04.2

---
nvidia-graphics-drivers-384 (384.130-0ubuntu0.14.04.2) trusty; urgency=medium

  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_4.4_get_user_pages.patch:
- Add support for new 7 argument get_user_pages() (LP: #1573508).

 -- Alberto Milone   Mon, 04 Mar 2019
11:10:42 +0100

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions

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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-304 -
304.135-0ubuntu0.14.04.2

---
nvidia-graphics-drivers-304 (304.135-0ubuntu0.14.04.2) trusty; urgency=medium

  * debian/dkms_nvidia/patches/buildfix_kernel_4.10.patch:
- Remove part that affected get_user_pages.
  * debian/dkms_nvidia/patches/buildfix_kernel_4.4_get_user_pages.patch:
   - Add support for backported 7 argument linux get_user_pages call (LP: 
#1573508).

 -- Alberto Milone   Fri, 01 Mar 2019
19:30:07 +0100

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions

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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-340 -
340.107-0ubuntu0.16.04.2

---
nvidia-graphics-drivers-340 (340.107-0ubuntu0.16.04.2) xenial; urgency=medium

  * debian/templates/dkms_nvidia.conf.in:
- Re-enable buildfix_kernel_4.11.patch (LP: #1819077).

nvidia-graphics-drivers-340 (340.107-0ubuntu0.16.04.1) xenial;
urgency=medium

  * New upstream release:
- Added support for X.Org xserver ABI 24 (xorg-server 1.20).
- Improved nvidia-bug-report.sh to check for kern.log which is
  the default kernel log-file location for many Debian-based
  Linux distributions.
- Fixed a bug which could cause X servers that export a Video
  Driver ABI earlier than 0.8 to crash when running X11
  applications which call XRenderAddTraps().
  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_4.4_get_user_pages.patch:
   - Drop buildfix_kernel_4.11.patch.
   - Add support for new 7 argument get_user_pages() (LP: #1573508).
  * debian/substvars:
   - Add support for X ABI 24.

 -- Alberto Milone   Fri, 08 Mar 2019
12:04:12 +0100

** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions

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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-384 -
384.130-0ubuntu0.16.04.2

---
nvidia-graphics-drivers-384 (384.130-0ubuntu0.16.04.2) xenial; urgency=medium

  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_4.4_get_user_pages.patch:
- Add support for new 7 argument get_user_pages() (LP: #1573508).

 -- Alberto Milone   Mon, 04 Mar 2019
11:02:10 +0100

** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions

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

[Desktop-packages] [Bug 1573508] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for nvidia-graphics-
drivers-304 has completed successfully and the package has now been
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 nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1573508

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions

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

[Desktop-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-304 -
304.135-0ubuntu0.16.04.3

---
nvidia-graphics-drivers-304 (304.135-0ubuntu0.16.04.3) xenial; urgency=medium

  * debian/dkms_nvidia/patches/buildfix_kernel_4.10.patch:
- Remove part that affected get_user_pages.
  * debian/dkms_nvidia/patches/buildfix_kernel_4.4_get_user_pages.patch:
   - Add support for backported 7 argument linux get_user_pages call (LP: 
#1573508).

 -- Alberto Milone   Mon, 04 Mar 2019
12:55:36 +0100

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+subscriptions

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

[Desktop-packages] [Bug 1819077] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for nvidia-graphics-
drivers-340 has completed successfully and the package has now been
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 nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1819077

Title:
  SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel
  module failed to build (nvidia_uvm_lite.c:857:14: error:
  initialization from incompatible pointer type [-Werror=incompatible-
  pointer-types])

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  nvidia-340 (from xenial-proposed) breaks compatibility with 
linux-generic-hwe-16.04.

  [Test Case]
  1) Enable the -proposed repository, and install the new 340 NVIDIA driver 
(340.107-0ubuntu0.16.04.2).

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The update simply re-enables a patch that had been disabled in 
340.107-0ubuntu0.16.04.1

  _

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.107-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 4.15.0-46-generic
  Date: Fri Mar  8 01:23:53 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed
   nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed
  DuplicateSignature: 
dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2015-11-21 (1202 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (970) killed by TERM signal
  PackageVersion: 340.107-0ubuntu0.16.04.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MVD Ver. F.20
  dmi.board.name: 30C5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr:
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04

[Desktop-packages] [Bug 1819077] Re: SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build (nvidia_uvm_lite.c:857:14: error: initialization from incompatible point

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-340 -
340.107-0ubuntu0.16.04.2

---
nvidia-graphics-drivers-340 (340.107-0ubuntu0.16.04.2) xenial; urgency=medium

  * debian/templates/dkms_nvidia.conf.in:
- Re-enable buildfix_kernel_4.11.patch (LP: #1819077).

nvidia-graphics-drivers-340 (340.107-0ubuntu0.16.04.1) xenial;
urgency=medium

  * New upstream release:
- Added support for X.Org xserver ABI 24 (xorg-server 1.20).
- Improved nvidia-bug-report.sh to check for kern.log which is
  the default kernel log-file location for many Debian-based
  Linux distributions.
- Fixed a bug which could cause X servers that export a Video
  Driver ABI earlier than 0.8 to crash when running X11
  applications which call XRenderAddTraps().
  * debian/templates/dkms_nvidia.conf.in,
debian/dkms_nvidia/patches/buildfix_kernel_4.4_get_user_pages.patch:
   - Drop buildfix_kernel_4.11.patch.
   - Add support for new 7 argument get_user_pages() (LP: #1573508).
  * debian/substvars:
   - Add support for X ABI 24.

 -- Alberto Milone   Fri, 08 Mar 2019
12:04:12 +0100

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel
  module failed to build (nvidia_uvm_lite.c:857:14: error:
  initialization from incompatible pointer type [-Werror=incompatible-
  pointer-types])

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  nvidia-340 (from xenial-proposed) breaks compatibility with 
linux-generic-hwe-16.04.

  [Test Case]
  1) Enable the -proposed repository, and install the new 340 NVIDIA driver 
(340.107-0ubuntu0.16.04.2).

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The update simply re-enables a patch that had been disabled in 
340.107-0ubuntu0.16.04.1

  _

  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.107-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog: root: clean, 221224/1281120 files, 2095043/512 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 4.15.0-46-generic
  Date: Fri Mar  8 01:23:53 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-46-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-142-generic, x86_64: installed
   nvidia-340, 340.107, 4.4.0-142-generic, x86_64: installed
  DuplicateSignature: 
dkms:nvidia-340:340.107-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia_uvm_lite.c:857:14:
 error: initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  GraphicsCard:
   NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5]
  InstallationDate: Installed on 2015-11-21 (1202 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (970) killed by TERM signal
  PackageVersion: 340.107-0ubuntu0.16.04.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh insta

[Desktop-packages] [Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces

[Sebastien Bacher]

Indeed, confirmed, it looks like an upstream regression and would be
nice if someone could report it on https://gitlab.gnome.org/GNOME/gnome-
shell/issues

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

** 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/1819890

Title:
  Restarting gnome-shell displays images of applications running on
  other workspaces

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Restarting gnome-shell with 'Alt-F2,r and enter' displays images of
  applications running on other workspaces which are not clickable.

  Steps to reproduce:

  1) Enable multiple workspaces
  2) Start an application on each workspace
  3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter'

  Expected outcome:

  As with Ubuntu 18.04, each application is displayed only the workspace
  on which it was started.

  Actual outcome:

  All applications are displayed on the current workspace. The
  applications running on other workspaces are displayed as images, i.e.
  they cannot be 'clicked' but he 'wanted' application, the dock, top
  bar etc all function correctly.

  Workaround:

  To remove the unwanted images move to another workspace and return.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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: Wed Mar 13 10:15:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-20 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1667208] Re: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu

[Launchpad Bug Tracker]

This bug was fixed in the package chromium-browser -
73.0.3683.75-0ubuntu3

---
chromium-browser (73.0.3683.75-0ubuntu3) disco; urgency=medium

  * debian/patches/fix-build-with-libstdc++.patch: added

 -- Olivier Tilloy   Wed, 13 Mar 2019
21:12:47 +0100

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

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

Title:
  Ubuntu's selenium hardcodes a path that is valid for Debian, but not
  for Ubuntu

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in python-selenium package in Ubuntu:
  Invalid

Bug description:
  Hi.

  The package python{,3}-selenium uses a hardcoded path of
  '/usr/lib/chromium/chromedriver' when instantiating a Chrome
  webdriver.

  That path is correct for Debian (in particular, it was directly
  inherited from https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=805733#5), but since Ubuntu uses chromium-
  browser instead of Debian's chromium naming. The package chromium-
  chromedriver in Ubuntu installs the webdriver at '/usr/lib/chromium-
  browser/chromedriver'.

  There needs to be a synchronization between the selenium Python module
  and the webdriver package.

  
  Thanks,

  Rogério Brito.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: python3-selenium 2.53.2+dfsg1-1
  Uname: Linux 4.10.0-041000-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 01:38:24 2017
  Dependencies:
   
  InstallationDate: Installed on 2016-12-11 (73 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: python-selenium
  UpgradeStatus: Upgraded to zesty on 2017-01-31 (23 days ago)

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

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

[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

[Egor Tensin]

I don't really get it, when's the fix going to be available for Bionic?
I have -updates enabled, but the bug is still present on my system.

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

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913

  [ Impact ]

  Keyboard Layout indicator don't display current layout (empty selected
  drop down box)

  [ Test case ]

  1. Boot
  2. Suspend or lock the screen
  3. Log again with your user
  4. The keyboard indicator should display current layout

  [ Regression Potential ]

  Really low, we properly pass a null value instead of an undefined one,
  without breaking JS.

  --

  Steps to reproduce the bug:

  1. After normal boot, suspend or lock.
  2. Login again.

  Result: Keyboard Layout indicator don't display current layout (empty
  selected drop down box)

  [ Workarounds ]

  - Switch with keyboard (Super+space) or mouse. BUT if you then logout
  on the login screen *when you press the first character* of the
  password the shown selected keyboard layout resets.

  - Restart Gnome Shell (Alt+F2 r):
  https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools

  - Also asked here https://askubuntu.com/q/1109555/349837
  - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173

  $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status
  System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3
     Distro: Ubuntu 18.04.1 LTS
  Graphics:  Card-1: Intel HD Graphics 520
     Card-2: NVIDIA GM108M [GeForce 940M]
     Display Server: x11 (X.Org 1.19.6 )
     drivers: fbdev (unloaded: modesetting,vesa)
     Resolution: 1920x1080@60.00hz
     OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
     version: 4.5 Mesa 18.0.5
  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="es"
  XKBVARIANT="en"
  XKBOPTIONS="terminate:ctrl_alt_bksp"

  BACKSPACE="guess"
     System Locale: LANG=en_US.UTF-8
    LC_NUMERIC=es_AR.UTF-8
    LC_MONETARY=es_AR.UTF-8
    LC_PAPER=es_AR.UTF-8
    LC_NAME=es_AR.UTF-8
    LC_ADDRESS=es_AR.UTF-8
    LC_TELEPHONE=es_AR.UTF-8
    LC_MEASUREMENT=es_AR.UTF-8
    LC_IDENTIFICATION=es_AR.UTF-8
     VC Keymap: n/a
    X11 Layout: es
     X11 Model: pc105
   X11 Variant: en
   X11 Options: terminate:ctrl_alt_bksp

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

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

[Desktop-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set

[Bootch]

The Adwaita theme was helped to me, switching the input method was not.

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue when
  GTK_IM_MODULE=xim is set

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Confirmed

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1760818/+subscriptions

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

[Desktop-packages] [Bug 1820230] Re: spotify (snap) starts in fullscreen without windows decorations

[Daniel van Vugt]

Sounds like this might not be a gnome-shell bug.

Can you use xwininfo or xwininfo -all to get more information about the
window?

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

Title:
  spotify (snap) starts in fullscreen without windows decorations

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Disco up to date
  spotify 1.1.0.237.g378f6f25-11
  session: Ubuntu on Xorg
  1 display
  screen #0:
dimensions:1920x1080 pixels (508x285 millimeters)
resolution:96x96 dots per inch

  When spotify is closed in fullscreen mode, on next start it starts
  like a fullscreen app without any window decoration. There is then no
  way to control the app. window.

  The following message is displayed in the logs
  mars 15 10:45:06 sark org.gnome.Shell.desktop[4668]: Window manager warning: 
Treating resize request of legacy application 0x421 as a fullscreen request 

  

  Test Case:
  1. Start Spotify
  2. Switch to fullscreen (arrows on the bottom right corner)
  3. Close Spotify with ALT+F4
  4. Open Spotify again

  Actual Result
  The apps launches in fullscreen without any windows control and no way to 
switch to normal mode.

  Workaround
  click on the arrow to switch to fullscreen then again to switch to normal 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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 15 10:38:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1704 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-03-24 (355 days ago)

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

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

[Desktop-packages] [Bug 1820230] [NEW] spotify (snap) starts in fullscreen without windows decorations

[Jean-Baptiste Lallement]

Public bug reported:

Ubuntu Disco up to date
spotify 1.1.0.237.g378f6f25-11
session: Ubuntu on Xorg
1 display
screen #0:
  dimensions:1920x1080 pixels (508x285 millimeters)
  resolution:96x96 dots per inch

When spotify is closed in fullscreen mode, on next start it starts like
a fullscreen app without any window decoration. There is then no way to
control the app. window.

The following message is displayed in the logs
mars 15 10:45:06 sark org.gnome.Shell.desktop[4668]: Window manager warning: 
Treating resize request of legacy application 0x421 as a fullscreen request 

  

Test Case:
1. Start Spotify
2. Switch to fullscreen (arrows on the bottom right corner)
3. Close Spotify with ALT+F4
4. Open Spotify again

Actual Result
The apps launches in fullscreen without any windows control and no way to 
switch to normal mode.

Workaround
click on the arrow to switch to fullscreen then again to switch to normal mode.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0-1ubuntu1
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 15 10:38:59 2019
DisplayManager: gdm3
InstallationDate: Installed on 2014-07-15 (1704 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2018-03-24 (355 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  spotify (snap) starts in fullscreen without windows decorations

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Disco up to date
  spotify 1.1.0.237.g378f6f25-11
  session: Ubuntu on Xorg
  1 display
  screen #0:
dimensions:1920x1080 pixels (508x285 millimeters)
resolution:96x96 dots per inch

  When spotify is closed in fullscreen mode, on next start it starts
  like a fullscreen app without any window decoration. There is then no
  way to control the app. window.

  The following message is displayed in the logs
  mars 15 10:45:06 sark org.gnome.Shell.desktop[4668]: Window manager warning: 
Treating resize request of legacy application 0x421 as a fullscreen request 

  

  Test Case:
  1. Start Spotify
  2. Switch to fullscreen (arrows on the bottom right corner)
  3. Close Spotify with ALT+F4
  4. Open Spotify again

  Actual Result
  The apps launches in fullscreen without any windows control and no way to 
switch to normal mode.

  Workaround
  click on the arrow to switch to fullscreen then again to switch to normal 
mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  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 15 10:38:59 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1704 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2018-03-24 (355 days ago)

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

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

[Desktop-packages] [Bug 1637988] Re: Enable the nfs backend

[Rui Salvaterra]

Hi again, Łukasz

I dist-upgraded the cosmic-proposed packages, tried browsing a couple of
nfs shares and it worked perfectly on caja. I suppose nautilus will work
fine too.

Thanks,
Rui

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

Title:
  Enable the nfs backend

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  The gio/nautilus nfs:// locations handling is missing

  * Test case
  Try to connect to/browse a nfs server from nautilus by using a nfs:// location

  * Regression potential
  It's a new backend being enabled, it shouldn't have an impact on the existing 
ones

  Note that the backend relies on libnfs which got promoted in disco and
  would need to be promoted in cosmic/bionic as well then

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

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

[Desktop-packages] [Bug 1817338] Re: Changing sound output doesn't work in gnome-control-center 3.32

[Silvio Bierman]

I can confirm it is working properly now. Thanks a lot for the fix.

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

Title:
  Changing sound output doesn't work in gnome-control-center 3.32

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Disco:
  Fix Released

Bug description:
  In 19.04, HDMI sound stopped working after some upgrade.

  The sink is somehow availalbe, but cannot be selected.
  In gnome-control-center, HDMI output device is listed, but if I choose it, no 
configuration list appears (see screen capture attached).

  aplay -l gives me:
  ~$ aplay -l
   Liste des Périphériques Matériels PLAYBACK 
  carte 0: PCH [HDA Intel PCH], périphérique 0: ALC269VC Analog [ALC269VC 
Analog]
Sous-périphériques: 0/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 3: HDMI 0 [HDMI 0]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 7: HDMI 1 [HDMI 1]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0
  carte 0: PCH [HDA Intel PCH], périphérique 8: HDMI 2 [HDMI 2]
Sous-périphériques: 1/1
Sous-périphérique #0: subdevice #0

  pavucontrol shows HDMI as unplugged.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  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-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  franck 5998 F pulseaudio
   /dev/snd/pcmC1D0c:   franck 5998 F...m pulseaudio
   /dev/snd/controlC0:  franck 5998 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 22 16:16:56 2019
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2353CTO
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETA9WW(2.69):bd09/27/2017:svnLENOVO:pn2353CTO:pvrThinkPadT430s:rvnLENOVO:rn2353CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2353CTO
  dmi.product.sku: LENOVO_MT_2353
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1795121] Re: 18.10: Indicator icons not shown in the panel

[crunch]

I'm also having this problem (I'm on 18.04). It's exactly like Robin
Sheat described - usually the icons don't load on the first boot, and
then if you reboot they might load, but sometimes not. It's either all
the icons on or all off. Clearly it's some kind of a race condition...

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

Title:
  18.10: Indicator icons not shown in the panel

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  The indicator icons are not showing on a fresh installation of Ubuntu
  18.10 beta. On 18.04 I can see the tray icons of Chrome, Hangouts,
  Dropbox and InSync but on 18.10 they are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell-extension-appindicator 22-1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 29 10:00:34 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-09-28 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

Status in OEM Priority Project:
  Fix Released
Status in gnome-menus package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in gnome-menus source package in Xenial:
  Confirmed
Status in ubuntu-release-upgrader source package in Xenial:
  Invalid
Status in gnome-menus source package in Bionic:
  Confirmed
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Upgrades on some systems fail with trigger issues related to gnome-menus. 
Upgrading libc6 first fixes that, so we modified u-r-u to upgrade it first.

  [Test case]
  Restore apt-clone file from comment #20 and upgrade to bionic with u-r-u.

  [Regression potential]
  (1) Upgrade of libc6 fails, upgrade would revert
  (2) If upgrade of libc6 succeeds, but we cannot find an ordering for the 
remaining upgrades, we are stuck with just libc6 upgraded. It seems unlikely 
that we find an ordering for all packages, but none for the set without libc6 
though.

  
  # Original bug report

  
  Dell XPS 13 9360 (CID 201606-22338)
  pre-installed (oem) image Xenial

  [Description]

  When I tried to perform 16.04 --> 18.04 update, the update process
  failed. The process guide me to file this bug report.

  [Steps to reproduce]
  1. Update the system to the latest stack by "sudo apt-get update; sudo 
apt-get dist-upgrade -y"
  2. Reboot
  3. Make sure /etc/update-manager/release-upgrades is able to update (The 
configuration value of "Prompt" should be "lts", namely "Prompt=lts", not 
"Prompt=never").
  4. Perform the release update: "sudo apt-get update; sudo do-release-upgrade 
-d"
  5. During the update process, it prompts for "Configuring gdm3". There are 
two choices "gdm3" and "lightdm". I picked up "gdm3". Please refer to the 
attachment for the prompt details as well.

  We should use "-d" because bionic beaver has not been officially
  released yet.

  [Expected Result]

  The release update completed and I could start using Bionic instead of
  Xenial.

  [Actual Result]

  The update process failed. It shows the error message[1] and
  automatically asking for filing this bug report.

  [1]

  Preparing to unpack .../qml-module-qtquick-dialogs_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-dialogs:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-1ubuntu1) ...
  Preparing to unpack .../qml-module-qtquick-window2_5.9.5-0ubuntu1_amd64.deb 
...
  Unpacking qml-module-qtquick-window2:amd64 (5.9.5-0ubuntu1) over 
(5.5.1-2ubuntu6) ...
  (Reading database ... 253705 files and directories currently installed.)
  Removing unity-webapps-common (2.4.17+15.10.20150616-0ubuntu2) ...
  Removing unity-webapps-service (2.5.0~+16.04.20160201-0ubuntu1) ...
  Removing webapp-container (0.23+16.04.20161028-0ubuntu2) ...
  Removing webbrowser-app (0.23+16.04.20161028-0ubuntu2) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    bamfdaemon -> gnome-menus
   packages' pending triggers which are or may be unresolvable:
    gnome-menus: /usr/share/applications
    bamfdaemon: /usr/share/applications
    libglib2.0-0:amd64: /usr/share/glib-2.0/schemas
    desktop-file-utils: /usr/share/applications
    mime-support: /usr/share/applications
  dpkg: error processing package gnome-menus (--remove):
   triggers looping, abandoned
  Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
  Processing triggers for mime-support (3.59ubuntu1) ...
  Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu1) ...
  Errors were encountered while processing:
   gnome-menus
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/gnome-menus.0.crash'
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
    S: Send report (376.4 KB)
    V: View report
    K: Keep report file for sending later or copying to somewhere else
    I: Cancel and ignore future crashes of this program version
    C: Cancel
  Please choose (S/V/K/I/C):

  .. (a lot of them)

   qml-module-qtquick-controls2:amd64
   qml-module-org-kde-kconfig:amd64
   libunity-control-center1
   libqt5quickcontrols2-5:amd64
   libglib2.0-bin
   libkf5plasma5:amd64
   locales
   qml-module-qtqml-models2:amd64
   libkf5coreaddons5:amd64
   gir1.2-goa-1.0:amd64
   libwebkit2gtk-4.0-37:amd64
  Processing was halted because there were too many errors.

  Upgrade complet

[Desktop-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.

[Sebastien Bacher]

https://launchpad.net/ubuntu/+source/cairo/1.16.0-3

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

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

Title:
  Unable to correctly print PDF file: Error: Ignoring spurious ET
  operator.

Status in cairo package in Ubuntu:
  Fix Released

Bug description:
  Upstream bug report https://github.com/OpenPrinting/cups-
  filters/issues/93.

  The university document
  [antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
  filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
  different printers.

  Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
  is first printed, and on the first page after _Email_ everything is
  missing. The second page is fine.

  ```
    Error: Ignoring spurious ET operator. Output may be inco 
  ```

  For that printer a special filter `sicgsfilter` has to be used, and is
  distributed by Canon. This also happens with their CQue 4.0-1 release
  from September 2018.

  ```
   *FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C 
-dPDFFitPage  -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u&user; 
-V"&title;" -n&copies; "
  ```

  On the Epson printer _WorkForce WF-2660_, no error page is printed,
  but on the first page everything after _Email_ _is missing_ too.

  Trying to use different pdftops renderers did not make any difference.
  For example,

  ```
   lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
  ```

  gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.

  Following `/usr/share/doc/cups-filters/README.gz` and
  https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
  exact same PDF is put into the CUPS spool directory, and I captured
  the data sent to the printer with the commands below.

  $ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P 
~/chipprinterpcl.ppd
  $ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf

  I get the attached Postscript file, which indeed contains the error
  messages.

  ```
  ESC%-12345X@PJL CQue4.0-1 x86_64
  @PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
  @PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
  @PJL SET RENDERMODE=COLOR
  @PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
  @PJL COMMENT CANPJL SET SORTERMODE=GENERICON
  @PJL COMMENT CANPJL SET STAPLE=GENERICOFF
  @PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
  @PJL SET DENSITY=0
  @PJL ENTER LANGUAGE=PCL
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: illegal nested BT operator detected.
 Output may be incorrect.
  Error: Ignoring spurious ET operator.
 Output may be incorrect.
  Error: Executing Do inside a text block, attempting to recover
 Output may be incorrect.
  Error: illegal nested BT operator detected.
 Output may be incorrect.
  […]
  ```

  Please find that file attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cups 2.2.8-5ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Thu Feb 21 10:23:08 2019
  InstallationDate: Installed on 2017-03-20 (702 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lpstat:
   device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
   device for DCP375CW: socket://141.14.220.198
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Papersize: a4
  PpdFiles:
   Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
   DCP375CW: Brother DCP-375CW CUPS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash initcall_debug log_buf_len=16M 
vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: Upgraded to cosmic on 2018-10-30 (113 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.boa

[Desktop-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.0.0-1ubuntu1

---
mesa (19.0.0-1ubuntu1) disco; urgency=medium

  * Merge from Debian. (LP: #1818516)
  * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889)

 -- Timo Aaltonen   Thu, 14 Mar 2019 18:48:18 +0200

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

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Confirmed
Status in QEMU:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Triaged
Status in mesa source package in Disco:
  Fix Released

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.0.0-1ubuntu1

---
mesa (19.0.0-1ubuntu1) disco; urgency=medium

  * Merge from Debian. (LP: #1818516)
  * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889)

 -- Timo Aaltonen   Thu, 14 Mar 2019 18:48:18 +0200

** Changed in: mesa (Ubuntu)
   Status: Fix Committed => 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/1815236

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME)

  ---

  I'm not sure, but this happened after updating to gstreamer 1.15.1, I
  have problems when I maximize totem.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1818516] Re: FFe: Mesa 19.0.x for disco

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.0.0-1ubuntu1

---
mesa (19.0.0-1ubuntu1) disco; urgency=medium

  * Merge from Debian. (LP: #1818516)
  * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889)

 -- Timo Aaltonen   Thu, 14 Mar 2019 18:48:18 +0200

** Changed in: mesa (Ubuntu)
   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/1818516

Title:
  FFe: Mesa 19.0.x for disco

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Mesa 19.0.0 will be soon released, and we should get that for disco,
  and then follow point-releases until the last one is released (roughly
  next July, will need an SRU).

  We'll also migrate it to use LLVM 8.

  New features according to upstream release notes:

  GL_AMD_texture_texture4 on all GL 4.0 drivers.
  GL_EXT_shader_implicit_conversions on all drivers (ES extension).
  GL_EXT_texture_compression_bptc on all GL 4.0 drivers (ES extension).
  GL_EXT_texture_compression_rgtc on all GL 3.0 drivers (ES extension).
  GL_EXT_render_snorm on gallium drivers (ES extension).
  GL_EXT_texture_view on drivers supporting texture views (ES extension).
  GL_OES_texture_view on drivers supporting texture views (ES extension).
  GL_NV_shader_atomic_float on nvc0 (Fermi/Kepler only).
  Shader-based software implementations of GL_ARB_gpu_shader_fp64, 
GL_ARB_gpu_shader_int64, GL_ARB_vertex_attrib_64bit, and GL_ARB_shader_ballot 
on i965.
  VK_ANDROID_external_memory_android_hardware_buffer on Intel
  Fixed and re-exposed VK_EXT_pci_bus_info on Intel and RADV
  VK_EXT_scalar_block_layout on Intel and RADV
  VK_KHR_depth_stencil_resolve on Intel
  VK_KHR_draw_indirect_count on Intel
  VK_EXT_conditional_rendering on Intel
  VK_EXT_memory_budget on RADV

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Daniel van Vugt]

You can safely install all three, but you only need two:  *.deb

You don't need *.ddeb

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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Disco:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/140

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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

[Desktop-packages] [Bug 1774957] Re: Network icons in status menu disappearing

[Andrei]

Daniel, how do I know which of the three deb-files

gnome-shell-common_3.28.3+git20190124-0ubuntu18.04.1_all.deb (179.2 KiB)
gnome-shell-dbgsym_3.28.3+git20190124-0ubuntu18.04.1_amd64.ddeb (1.1 MiB)
gnome-shell_3.28.3+git20190124-0ubuntu18.04.1_amd64.deb (650.2 KiB)

from that page I should install?

I tried to install the first one and it completely messed up my log in
procedure with the error "failed to start session" showing up at log in.
I spent half a day fixing that.

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

Title:
  Network icons in status menu disappearing

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Disco:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/140

  ---

  Ever since the update to Ubuntu 18.04 I'm having issues with the
  status menu at the top right of the screen.

  Normally you'd have a wired network connection icon displayed at the top 
without opening the menu. In my case it is not displayed half of the time. In 
the menu list no icon nor label is displayed for the wired connection menu item.
  When talking about half of the time it means that I can randomly make it 
display again when removing the USB network adapter and reconnecting it e.g.
  This does not work reliably though.

  When connecting to a VPN, normally you'd get an additional icon at the
  top. This is not the case any more, nor does the switch behind an
  activated VPN turns change to an active state. The result is that you
  can activate a VPN using the switch, but you can verify that it is
  activated, nor can you de-active the VPN through the menu. This does
  change in settings though.

  Wireless settings are no longer displayed in the menu at all. So no
  way to activate it or connect to a specific network.

  I tried reconfiguring (dpkg-reconfigure) gnome-shell as well as
  network-manager-gnome, to no avail.

  Attached you'll find a screenshot illustrating the issue. You'll see
  two icons missing to the left of the volume icon, as well as the
  wireless menu missing completely and no icon and text label for the
  wired connection menu item.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun  4 10:47:05 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-07 (604 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (3 days ago)

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

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