[Desktop-packages] [Bug 899013] Re: Firefox: Not using localized Google Search

[Launchpad Bug Tracker]

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  Firefox: Not using localized Google Search

Status in One Hundred Papercuts:
  Expired
Status in Ubuntu Translations:
  Expired
Status in firefox package in Ubuntu:
  Expired

Bug description:
  Hello,

  on a fresh Precise Alpha1 installation search results through the
  Google search bar (right beside the URL bar) are English during the
  first run of Firefox, allthough the system's locale (and the one in
  Firefox too) is German.

  You can reproduce it the following way:

  - Boot a fresh installation of Precise, whose locale has been set to German 
on installation (or perhaps also other languages different from English).
  - Start Firefox.
  - Enter "Tonne" in the Google search bar on the right top.
  - Google displays the English Wikipedia page for "Tonne" as the first result.
  - Close Firefox.
  - Start Firefox again and do the same search again.
  - Now Google displays correctly the German Wikipedia page for "Tonne" as the 
first result.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 9.0~b3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
  Uname: Linux 3.2.0-2-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jan1488 F pulseaudio
   /dev/snd/controlC0:  jan1488 F pulseaudio
  BuildID: 2024173847
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf910 irq 45'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,1458a002,00100101'
 Controls  : 41
 Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf600 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 20
 Simple ctrls  : 4
  Channel: beta
  Date: Fri Dec  2 09:31:52 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  IpRoute:
   default via 192.168.178.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.21  
metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Plugins:
   Windows Media Player Plug-in 10 (compatible; Totem) - 
Lib=libtotem-gmp-plugin.so, Location=/usr/lib/mozilla/plugins
   QuickTime Plug-in 7.6.6 - Lib=libtotem-narrowspace-plugin.so, 
Location=/usr/lib/mozilla/plugins
   DivX® Web Player - Lib=libtotem-mully-plugin.so, 
Location=/usr/lib/mozilla/plugins
   VLC Multimedia Plugin (compatible Totem 3.0.1) - 
Lib=libtotem-cone-plugin.so, Location=/usr/lib/mozilla/plugins
   iTunes Application Detector - Lib=librhythmbox-itms-detection-plugin.so, 
Location=/usr/lib/mozilla/plugins
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=9.0/2024173847
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 899013] Re: Firefox: Not using localized Google Search

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox: Not using localized Google Search

Status in One Hundred Papercuts:
  Expired
Status in Ubuntu Translations:
  Expired
Status in firefox package in Ubuntu:
  Expired

Bug description:
  Hello,

  on a fresh Precise Alpha1 installation search results through the
  Google search bar (right beside the URL bar) are English during the
  first run of Firefox, allthough the system's locale (and the one in
  Firefox too) is German.

  You can reproduce it the following way:

  - Boot a fresh installation of Precise, whose locale has been set to German 
on installation (or perhaps also other languages different from English).
  - Start Firefox.
  - Enter "Tonne" in the Google search bar on the right top.
  - Google displays the English Wikipedia page for "Tonne" as the first result.
  - Close Firefox.
  - Start Firefox again and do the same search again.
  - Now Google displays correctly the German Wikipedia page for "Tonne" as the 
first result.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 9.0~b3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
  Uname: Linux 3.2.0-2-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jan1488 F pulseaudio
   /dev/snd/controlC0:  jan1488 F pulseaudio
  BuildID: 2024173847
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf910 irq 45'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,1458a002,00100101'
 Controls  : 41
 Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf600 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 20
 Simple ctrls  : 4
  Channel: beta
  Date: Fri Dec  2 09:31:52 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  IpRoute:
   default via 192.168.178.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.21  
metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Plugins:
   Windows Media Player Plug-in 10 (compatible; Totem) - 
Lib=libtotem-gmp-plugin.so, Location=/usr/lib/mozilla/plugins
   QuickTime Plug-in 7.6.6 - Lib=libtotem-narrowspace-plugin.so, 
Location=/usr/lib/mozilla/plugins
   DivX® Web Player - Lib=libtotem-mully-plugin.so, 
Location=/usr/lib/mozilla/plugins
   VLC Multimedia Plugin (compatible Totem 3.0.1) - 
Lib=libtotem-cone-plugin.so, Location=/usr/lib/mozilla/plugins
   iTunes Application Detector - Lib=librhythmbox-itms-detection-plugin.so, 
Location=/usr/lib/mozilla/plugins
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=9.0/2024173847
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 827354] Re: Items in "Draft" are notified

[Launchpad Bug Tracker]

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

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

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

Title:
  Items in "Draft" are notified

Status in thunderbird package in Ubuntu:
  Expired

Bug description:
  I was just writing an email, when the subject of that email showed up
  as I was having a new message (when in fact I was writing that very
  message to someone else).

  Part of the problem might be related to that this message is saved as
  "Unread" in the Drafts folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 6.0~b3+build1+nobinonly-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
  Uname: Linux 3.0.0-8-generic x86_64
  Architecture: amd64
  Date: Tue Aug 16 15:25:27 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110802.1)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 899013] Re: Firefox: Not using localized Google Search

[Launchpad Bug Tracker]

[Expired for Ubuntu Translations because there has been no activity for
60 days.]

** Changed in: ubuntu-translations
   Status: Incomplete => Expired

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

Title:
  Firefox: Not using localized Google Search

Status in One Hundred Papercuts:
  Expired
Status in Ubuntu Translations:
  Expired
Status in firefox package in Ubuntu:
  Expired

Bug description:
  Hello,

  on a fresh Precise Alpha1 installation search results through the
  Google search bar (right beside the URL bar) are English during the
  first run of Firefox, allthough the system's locale (and the one in
  Firefox too) is German.

  You can reproduce it the following way:

  - Boot a fresh installation of Precise, whose locale has been set to German 
on installation (or perhaps also other languages different from English).
  - Start Firefox.
  - Enter "Tonne" in the Google search bar on the right top.
  - Google displays the English Wikipedia page for "Tonne" as the first result.
  - Close Firefox.
  - Start Firefox again and do the same search again.
  - Now Google displays correctly the German Wikipedia page for "Tonne" as the 
first result.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 9.0~b3+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
  Uname: Linux 3.2.0-2-generic x86_64
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jan1488 F pulseaudio
   /dev/snd/controlC0:  jan1488 F pulseaudio
  BuildID: 2024173847
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf910 irq 45'
 Mixer name : 'Realtek ALC889A'
 Components : 'HDA:10ec0885,1458a002,00100101'
 Controls  : 41
 Simple ctrls  : 23
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf600 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 20
 Simple ctrls  : 4
  Channel: beta
  Date: Fri Dec  2 09:31:52 2011
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  IpRoute:
   default via 192.168.178.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.21  
metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Plugins:
   Windows Media Player Plug-in 10 (compatible; Totem) - 
Lib=libtotem-gmp-plugin.so, Location=/usr/lib/mozilla/plugins
   QuickTime Plug-in 7.6.6 - Lib=libtotem-narrowspace-plugin.so, 
Location=/usr/lib/mozilla/plugins
   DivX® Web Player - Lib=libtotem-mully-plugin.so, 
Location=/usr/lib/mozilla/plugins
   VLC Multimedia Plugin (compatible Totem 3.0.1) - 
Lib=libtotem-cone-plugin.so, Location=/usr/lib/mozilla/plugins
   iTunes Application Detector - Lib=librhythmbox-itms-detection-plugin.so, 
Location=/usr/lib/mozilla/plugins
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=9.0/2024173847
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F13
  dmi.board.name: P35-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1

[Launchpad Bug Tracker]

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

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

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

Title:
  oem-config fails on Nvidia GPU machine on 18.04.1

Status in OEM Priority Project:
  Expired
Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  More an nvidia driver fail but happens in a oem-config scenario :

  - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) 
  - full-upgrade
  - ubuntu-drivers autoinstall ( To get nvidia drivers) 
  - Reboot and confirm nvidia driver work great

  
  - oem-config-prepare

  - Send machine to client

  - client goes through oem-config wizard normally

  - instead of going to the new desktop , client gets a blackscreen

  - After reboot he always get a black screen.

  - If he logs into TTY1 , he can login and startx to get a gnome3
  desktop.

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

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

[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1

[Launchpad Bug Tracker]

[Expired for OEM Priority Project because there has been no activity for
60 days.]

** Changed in: oem-priority
   Status: Incomplete => Expired

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

Title:
  oem-config fails on Nvidia GPU machine on 18.04.1

Status in OEM Priority Project:
  Expired
Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  More an nvidia driver fail but happens in a oem-config scenario :

  - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) 
  - full-upgrade
  - ubuntu-drivers autoinstall ( To get nvidia drivers) 
  - Reboot and confirm nvidia driver work great

  
  - oem-config-prepare

  - Send machine to client

  - client goes through oem-config wizard normally

  - instead of going to the new desktop , client gets a blackscreen

  - After reboot he always get a black screen.

  - If he logs into TTY1 , he can login and startx to get a gnome3
  desktop.

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

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

[Desktop-packages] [Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1

[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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1811668

Title:
  oem-config fails on Nvidia GPU machine on 18.04.1

Status in OEM Priority Project:
  Expired
Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  More an nvidia driver fail but happens in a oem-config scenario :

  - Install 18.04.1 on an Nvidia GPU machine ( desktop or laptop) 
  - full-upgrade
  - ubuntu-drivers autoinstall ( To get nvidia drivers) 
  - Reboot and confirm nvidia driver work great

  
  - oem-config-prepare

  - Send machine to client

  - client goes through oem-config wizard normally

  - instead of going to the new desktop , client gets a blackscreen

  - After reboot he always get a black screen.

  - If he logs into TTY1 , he can login and startx to get a gnome3
  desktop.

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

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

[Desktop-packages] [Bug 1820490] [NEW] i find them while xdiagnose

[Amit Kumar]

Public bug reported:

these bugs must be cleans and further bugs should be reported

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 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: Sun Mar 17 09:20:02 2019
DistUpgraded: 2019-03-15 15:41:59,975 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
InstallationDate: Installed on 2019-02-26 (18 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 3542
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=35f08810-0153-46db-9a01-b9159f8cb46e ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-03-15 (1 days ago)
dmi.bios.date: 05/23/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0FKWR5
dmi.board.vendor: Dell Inc.
dmi.board.version: A14
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0FKWR5:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3542
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.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 10:45:31 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1110 
 vendor LGD
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  i find them while xdiagnose

Status in xorg package in Ubuntu:
  New

Bug description:
  these bugs must be cleans and further bugs should be reported

  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 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: Sun Mar 17 09:20:02 2019
  DistUpgraded: 2019-03-15 15:41:59,975 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2019-02-26 (18 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=35f08810-0153-46db-9a01-b9159f8cb46e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-03-15 (1 days ago)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0FKWR5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0FKWR5:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.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
  

[Desktop-packages] [Bug 1820489] [NEW] nautilus search bar showing up when window with is expanded

[shemgp]

Public bug reported:

When nautilus is expanded horizontally the search bar shows up behind
the path bar.  This can be seen when it's maximized.

I've attached a screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.31.90-1ubuntu2
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: Sun Mar 17 11:52:30 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-09-28 (1265 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: nautilus
UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
usr_lib_nautilus:

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


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

** Attachment added: "Screenshot from 2019-03-17 11-48-53.png"
   
https://bugs.launchpad.net/bugs/1820489/+attachment/5246903/+files/Screenshot%20from%202019-03-17%2011-48-53.png

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

Title:
  nautilus search bar showing up when window with is expanded

Status in nautilus package in Ubuntu:
  New

Bug description:
  When nautilus is expanded horizontally the search bar shows up behind
  the path bar.  This can be seen when it's maximized.

  I've attached a screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.31.90-1ubuntu2
  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: Sun Mar 17 11:52:30 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (1265 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-02-16 (29 days ago)
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

[Charles Green]

I cant speak to other peoples issues - I trigger the message in the
system journal, by booting my system.  I understand gdm3 starts the
spice-vdagent program?  I have not noted any ill effects, and I've been
simply ignoring it.

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

Title:
  spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

  oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent
  virtio channel /dev/virtio-ports/com.redhat.spice.0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: spice-vdagent 0.17.0-1ubuntu2
  Uname: Linux 4.19.0-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 14:34:00 2018
  InstallationDate: Installed on 2017-10-13 (378 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820446] Re: ModemManager crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  ModemManager crashed with SIGSEGV in g_closure_invoke()

Status in modemmanager package in Ubuntu:
  New

Bug description:
  I'm not certain if this is related to
  https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1755006 ,
  which I also attached a comment & report to.  The error I experienced
  this time around was different; it's the one listed in the summary.

  I cannot say precisely what circumstances surrounded or caused this
  crash report.  It happened when the machine was idle and I was away
  from it.  The one thing that hasn't changed between this and my other
  report is that there are _no_ modems attached to this machine, so I
  don't know why modemmanager was running, or trying to run, to begin
  with.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: modemmanager 1.6.4-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sat Mar 16 20:54:50 2019
  ExecutablePath: /usr/sbin/ModemManager
  InstallationDate: Installed on 2018-02-13 (396 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/sbin/ModemManager
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x43986e:  mov0x40(%rax),%rbp
   PC (0x0043986e) ok
   source "0x40(%rax)" (0x0001013f) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: modemmanager
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ModemManager crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://launchpad.net/~desktop-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]

[Jeremy LaCroix]

On my end, I haven't been able to reproduce this so far with Ubuntu
Appindicators disabled. It's very stable for me now. I am not 100% sure
this is the fix for me, time will tell. But it's definitely more stable
and possibly even fixed now.

-- 
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 1820331] Re: gnome-shell crashed with SIGABRT

[Bug Watch Updater]

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

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

Title:
  gnome-shell crashed with SIGABRT

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Confirmed

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/mutter/+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 1820331] Re: gnome-shell crashed with SIGABRT

[El jinete sin cabeza]

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

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

** Description changed:

- https://gitlab.gnome.org/GNOME/mutter/issues/506
- 
- ---
- 
  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:

** Project changed: gnome-shell => mutter

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

Title:
  gnome-shell crashed with SIGABRT

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Confirmed

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/mutter/+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 1820331] Re: gnome-shell crashed with SIGABRT

[El jinete sin cabeza]

Of:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1070

To:
https://gitlab.gnome.org/GNOME/mutter/issues/506

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

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

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #506
   https://gitlab.gnome.org/GNOME/mutter/issues/506

** Description changed:

- https://gitlab.gnome.org/GNOME/gnome-shell/issues/1070
+ https://gitlab.gnome.org/GNOME/mutter/issues/506
  
  ---
  
  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:

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

Title:
  gnome-shell crashed with SIGABRT

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

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/506

  ---

  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 1820435] Re: gnome-shell crashed with SIGABRT in g_assertion_message_expr()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1820331
   gnome-shell crashed with SIGABRT

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message_expr()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Returning hibernating.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 20:15:43 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano', 
'system-moni...@paradoxxx.zero.gmail.com', 'ubuntu-appindicat...@ubuntu.com', 
'ubuntu-d...@ubuntu.com', 'dash-to-pa...@jderose9.github.com']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
   b'org.gnome.desktop.interface' b'clock-show-weekday' b'true'
  InstallationDate: Installed on 2018-12-02 (104 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2018-12-02 (104 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[El jinete sin cabeza]

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/1070
+ 
+ ---
+ 
  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
+  () 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:

-- 
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:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1070

  ---

  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 1820331] Re: gnome-shell crashed with SIGABRT

[Launchpad Bug Tracker]

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

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

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/1070

  ---

  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 1820430] Re: failed to install in latest 03-16-2019 disco-dingo xubuntu-desktop-amd64.iso

[Ubuntu QA Website]

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

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

** Tags added: iso-testing

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

Title:
  failed to install in latest 03-16-2019 disco-dingo xubuntu-desktop-
  amd64.iso

Status in xorg package in Ubuntu:
  New

Bug description:
  install proceeded normally (manual partitioning) on reboot failed to
  start X session .. rebooted to grub selection screen chose rescue mode
  .. from the choices menu ran some checks then did updates install ..
  all of the xorg-server files were installed automaticly .. then
  selected the "boot resume " (not sure on wording) which then allowed
  normal login to proceed (lightdm) into xfce/xubuntu evironment..

  
  seems the xorg packages were not installed initially .. this appears to be a 
recent "change" as earlier images did install these files normally.. early 
march?, but February and earlier for sure..

  
  this is a older machine lenovo SL500 with Intel GM45 Express Chipset video .. 

  This machine runs dicso fine normally .. has been running disco since first 
CD install images were available .. daily updates from proposed .. but has only 
run xorg-server ..
  not sure if chipset is wayland capable..

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  march 16, 2019 daily iso tested

  earlier feb 8 and 15 iso's were ok

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Mar 16 17:42:14 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-16 (0 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=119a6b43-9936-4b5d-ab5b-814f531ed9b7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1818053] Re: /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:____lambda22__gasync_ready_callback:g_simple_async_result_complete

[Launchpad Bug Tracker]

This bug was fixed in the package seahorse - 3.32-1

---
seahorse (3.32-1) experimental; urgency=medium

  * New upstream release
- Fix crash when changing login password (LP: #1818053) 

 -- Jeremy Bicha   Sat, 16 Mar 2019 08:24:50 -0400

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

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

Title:
  
/usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:lambda22__gasync_ready_callback:g_simple_async_result_complete

Status in seahorse package in Ubuntu:
  Fix Released

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

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

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

[Stephen Turley]

I'm having the save error with the Epson V550. Happy to help with a fix
if someone could show me where to start looking.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820430] [NEW] failed to install in latest 03-16-2019 disco-dingo xubuntu-desktop-amd64.iso

[Derk Willem te Bokkel]

Public bug reported:

install proceeded normally (manual partitioning) on reboot failed to
start X session .. rebooted to grub selection screen chose rescue mode
.. from the choices menu ran some checks then did updates install .. all
of the xorg-server files were installed automaticly .. then selected the
"boot resume " (not sure on wording) which then allowed normal login to
proceed (lightdm) into xfce/xubuntu evironment..


seems the xorg packages were not installed initially .. this appears to be a 
recent "change" as earlier images did install these files normally.. early 
march?, but February and earlier for sure..


this is a older machine lenovo SL500 with Intel GM45 Express Chipset video .. 

This machine runs dicso fine normally .. has been running disco since first CD 
install images were available .. daily updates from proposed .. but has only 
run xorg-server ..
not sure if chipset is wayland capable..

Description:Ubuntu Disco Dingo (development branch)
Release:19.04

march 16, 2019 daily iso tested

earlier feb 8 and 15 iso's were ok

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu11
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Sat Mar 16 17:42:14 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
InstallationDate: Installed on 2019-03-16 (0 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
MachineType: LENOVO 2746CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=119a6b43-9936-4b5d-ab5b-814f531ed9b7 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET64WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 2746CTO
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET64WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET64WW
dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
dmi.product.name: 2746CTO
dmi.product.version: ThinkPad SL500
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco has-workaround regression reproducible 
single-occurrence 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/1820430

Title:
  failed to install in latest 03-16-2019 disco-dingo xubuntu-desktop-
  amd64.iso

Status in xorg package in Ubuntu:
  New

Bug description:
  install proceeded normally (manual partitioning) on reboot failed to
  start X session .. rebooted to grub selection screen chose rescue mode
  .. from the choices menu ran some checks then did updates install ..
  all of the xorg-server files were installed automaticly .. then
  selected the "boot resume " (not sure on wording) which then allowed
  normal login to proceed (lightdm) into xfce/xubuntu evironment..

  
  seems the xorg packages were not installed initially .. this appears to be a 
recent "change" as earlier images did install these files normally.. early 
march?, but February and earlier for sure..

  
  this is a older machine lenovo SL500 with Intel GM45 Express Chipset video .. 

  This machine runs dicso fine normally .. has been running disco since first 
CD install images were available .. daily updates from proposed .. but has only 
run xorg-server ..
  not sure if chipset is wayland capable..

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  march 16, 2019 daily iso tested

  earlier feb 8 and 15 iso's were ok

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu1

[Desktop-packages] [Bug 1760849] Re: Login screen appears on only one monitor and it's not the one I want

[Chris Rainey]

WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
screensaver + numlockx(optionally)

Greeter will auto-appear on whichever screen your mouse is on or moves
to, dynamically.


See: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423

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

Title:
  Login screen appears on only one monitor and it's not the one I want

Status in gdm:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/372

  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-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 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another

[Chris Rainey]

WORKAROUND FOR UBUNTU 18.10(clean install):


Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + 
numlockx(optionally)


See: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820423

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

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

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

[Desktop-packages] [Bug 1820428] Re: gnome-logs cannot open display: :0

[Simon]

** Description changed:

** Changed in: gnome-logs (Ubuntu)
   Status: New => Invalid

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

Title:
  gnome-logs cannot open display: :0

Status in gnome-logs package in Ubuntu:
  Invalid

Bug description:
  simon@pc ~> gnome-logs

  (gnome-logs:16346): Gtk-WARNING **: 23:28:19.106: cannot open display:
  :0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-logs (not installed)
  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: Sat Mar 16 23:32:08 2019
  InstallationDate: Installed on 2019-03-13 (3 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-logs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1304351] Re: firefox 200% CPU usage while idle/shutdown: mpegaudioparse0 and mpegaudioparse1 processes

[Mathew Hodson]

A of totem (3.13.90-1) the totem-mozilla (browser plugin) package is no
longer shipped.

** Changed in: totem (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  firefox 200% CPU usage while idle/shutdown: mpegaudioparse0 and
  mpegaudioparse1 processes

Status in totem package in Ubuntu:
  Won't Fix

Bug description:
  Firefox regularly eats up 100% or 200% CPU usage while just gmail and
  google calendar pages are opened.

  Shutting down firefox does not really shut it down, only the window
  disappears, the processes that eat CPU stay, so restarting firefox
  does not work until I manually kill these processes.

  While they show up as "firefox" in $ top, I now managed to activate
  the "thread view" where these processes show up as "mpegaudioparse0"
  and "mpegaudioparse1" processes.

  Actually this might not be a bug in firefox but in one of the
  extensions, e.g., flashplugin, but I am not sure. Firefox should kill
  these harshly when exiting, so that restarting firefox is a possible
  solution to CPU-eating buggy plugins and extensions.

  I am using ubuntu 12.4.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 28.0+build2-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-19-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: 92HD90BXX Analog [92HD90BXX Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ps 2607 F pulseaudio
   /dev/snd/controlC0:  ps 2607 F pulseaudio
  BuildID: 20140317233623
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xe676 irq 46'
 Mixer name : 'IDT 92HD90BXX'
 Components : 'HDA:111d76e7,10280494,00100102'
 Controls  : 28
 Simple ctrls  : 13
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xe508 irq 17'
 Mixer name : 'Nvidia GPU 1c HDMI/DP'
 Components : 'HDA:10de001c,10280494,00100100'
 Controls  : 21
 Simple ctrls  : 3
  Channel: Unavailable
  Date: Tue Apr  8 14:25:11 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IpRoute:
   default via 193.255.160.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   193.255.160.0/23 dev eth0  proto kernel  scope link  src 193.255.160.48  
metric 1
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  MostRecentCrashID: bp-e838124b-7e27-4001-bba3-7c4442140319
  PrefSources:
   prefs.js
   
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140317233623 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.2.4.0-1
   icedtea-7-plugin  1.2.3-0ubuntu0.12.04.4
   rhythmbox-mozilla 2.96-0ubuntu4.3
   totem-mozilla 3.0.1-0ubuntu21.1
   gnome-shell   3.4.1-0ubuntu2
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0692FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0692FT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1820428] [NEW] gnome-logs cannot open display: :0

[Simon]

Public bug reported:

simon@pc ~> gnome-logs

(gnome-logs:16346): Gtk-WARNING **: 23:28:19.106: cannot open display:
:0

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-logs (not installed)
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: Sat Mar 16 23:32:08 2019
InstallationDate: Installed on 2019-03-13 (3 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: gnome-logs
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-logs cannot open display: :0

Status in gnome-logs package in Ubuntu:
  New

Bug description:
  simon@pc ~> gnome-logs

  (gnome-logs:16346): Gtk-WARNING **: 23:28:19.106: cannot open display:
  :0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-logs (not installed)
  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: Sat Mar 16 23:32:08 2019
  InstallationDate: Installed on 2019-03-13 (3 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  SourcePackage: gnome-logs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820355] Re: Firefox icon missing

[Launchpad Bug Tracker]

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

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

Title:
  Firefox icon missing

Status in gnome-shell package in Ubuntu:
  Confirmed

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 1810176] Re: libmtp error could not get object handles

[Ricardo Gentil de Araújo Pereira]

Similar error here.
Can copy file from Phone folder, but if I try to access Camera folder (inside 
DCIM folder), Nemo shows this error after some time processing.

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

Title:
  libmtp error could not get object handles

Status in libmtp package in Ubuntu:
  Confirmed

Bug description:
  When connecting my android galaxy s7 phone via usb, I am unable to
  access my Music folder, which contains 380 subfolders.  The file
  manager is inactive for a long time, and finally displays the error:

  Sorry, could not display all the contents of "Music": libmtp error:
  could not get object handles.

  Adding one more subfolder on the android side seems to work around the
  issue, so the issue is related to the number of items.

  Given this, my issue appears to be a specific example of the issue described 
in the link below.
  https://sourceforge.net/p/libmtp/bugs/1808/

  Observed in linux mint 18.3 64 bit / ubuntu 16.04

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

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

[Desktop-packages] [Bug 1810176] Re: libmtp error could not get object handles

[Launchpad Bug Tracker]

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

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

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

Title:
  libmtp error could not get object handles

Status in libmtp package in Ubuntu:
  Confirmed

Bug description:
  When connecting my android galaxy s7 phone via usb, I am unable to
  access my Music folder, which contains 380 subfolders.  The file
  manager is inactive for a long time, and finally displays the error:

  Sorry, could not display all the contents of "Music": libmtp error:
  could not get object handles.

  Adding one more subfolder on the android side seems to work around the
  issue, so the issue is related to the number of items.

  Given this, my issue appears to be a specific example of the issue described 
in the link below.
  https://sourceforge.net/p/libmtp/bugs/1808/

  Observed in linux mint 18.3 64 bit / ubuntu 16.04

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [gradle/bionic] possible regression found

[Brian Murray]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of gradle from bionic-proposed
was performed and bug 1820389 was found.  Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed-
bionic" tag from this bug report and add the tag "bot-stop-nagging" to
bug 1820389 (not this bug). Thanks!

** Tags added: verification-failed-bionic

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

[Desktop-packages] [Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

[Kenneth Loafman]

** Changed in: duplicity
   Status: In Progress => Fix Committed

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

Status in Duplicity:
  Fix Committed
Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820423] [NEW] monitors.xml is not parsed or applied correctly after reboot or shutdown

[Chris Rainey]

Public bug reported:

WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings + gnome-
screensaver

ERROR(syslog) = "Failed to get current display configuration state:
GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
"org.gnome.Mutter.DisplayConfig" does not exist"

gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
TypeError: monitor is
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17


CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri Feb 
8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary 
monitor and HDMI(wireless Tx) as secondary to projector and then apply custom 
monitor positioning using g-c-c "Displays" panel.


RESULT = correct positioning and working of multiple displays until reboot or 
shutdown, then--problems until HDMI cable is unseated and rebooted again.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gdm3 3.30.1-1ubuntu5.1
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 16 13:50:52 2019
InstallationDate: Installed on 2019-03-07 (8 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

** Attachment added: "monitors.xml"
   
https://bugs.launchpad.net/bugs/1820423/+attachment/5246801/+files/monitors.xml

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

Title:
  monitors.xml is not parsed or applied correctly after reboot or
  shutdown

Status in gdm3 package in Ubuntu:
  New

Bug description:
  WORKAROUND: replace gdm3 with slick-greeter + lightdm-settings +
  gnome-screensaver

  ERROR(syslog) = "Failed to get current display configuration state:
  GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
  "org.gnome.Mutter.DisplayConfig" does not exist"

  gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded:
  TypeError: monitor is
  
null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17

  
  CAUSE = clean install of Ubuntu 18.10(4.18.0-16-generic #17-Ubuntu SMP Fri 
Feb 8 00:06:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux), attach VGA as primary 
monitor and HDMI(wireless Tx) as secondary to projector and then apply custom 
monitor positioning using g-c-c "Displays" panel.

  
  RESULT = correct positioning and working of multiple displays until reboot or 
shutdown, then--problems until HDMI cable is unseated and rebooted again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gdm3 3.30.1-1ubuntu5.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 16 13:50:52 2019
  InstallationDate: Installed on 2019-03-07 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1820377] Re: Headerbars not respecting window control button layout

[Roland (Rolandixor) Taylor]

Turns out the problem was using SDDM as opposed to GDM.

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

Title:
  Headerbars not respecting window control button layout

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 18.10.

  Full details here: https://askubuntu.com/questions/1125401/how-to-
  restore-correct-window-control-behaviour-in-gnome

  Basically: after installing, then later removing (purging) pantheon, I
  found that window controls on CSD windows no longer respect the
  gsettings value. Clearing dconf settings completely made no
  difference.

  Only this account is affect.

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

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

[Desktop-packages] [Bug 1820413] [NEW] Firefox 66 can't open new tab

[Joe Barnett]

Public bug reported:

With the disco upgrade to firefox 66, I can't open new tabs, and the
browser doesn't cleanly exit on closing windows.  Disabling all
extensions does not fix, downgrading to firefox 65 does.  Safe mode also
appears to fix, but weird that disabling extensions doesn't?

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 66.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jbarnett   2363 F pulseaudio
BuildID: 20190315094614
Channel: Unavailable
CurrentDesktop: GNOME
Date: Sat Mar 16 10:09:11 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2018-09-26 (171 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
 default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
PrefSources:
 /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
 prefs.js
Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago)
dmi.bios.date: 10/10/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.0
dmi.board.name: 0N338G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9575
dmi.product.sku: 080D
dmi.sys.vendor: Dell Inc.

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

Title:
  Firefox 66 can't open new tab

Status in firefox package in Ubuntu:
  New

Bug description:
  With the disco upgrade to firefox 66, I can't open new tabs, and the
  browser doesn't cleanly exit on closing windows.  Disabling all
  extensions does not fix, downgrading to firefox 65 does.  Safe mode
  also appears to fix, but weird that disabling extensions doesn't?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 66.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jbarnett   2363 F pulseaudio
  BuildID: 20190315094614
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Sat Mar 16 10:09:11 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-09-26 (171 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago)
  dmi.bios.date: 10/10/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 0N338G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
  

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

[Andreas Schildbach]

4) Android builds are entirely broken with OpenJDK 11.

Apparently, you'd be forced to upgrade Android Gradle plugin to at least
3.1.0 to be compatible to OpenJDK 11. Ubuntu/Debian still has version
2.2.2 [1]!

But even if you upgrade to 3.1.0 manually (bypassing apt), you'd break
reproducable builds. Versions 3.1 to 3.4 are dependent on file system
sort order. According to Google, that bug has recently been fixed in 3.5
[2] and will be backported to 3.4, but anyway these versions require
newer Gradle versions that have yet to appear in Ubuntu/Debian. So we
have a dependency deadlock that is currently unresolvable.

[1] 
https://packages.ubuntu.com/search?keywords=libgradle-android-plugin-java=names
[2] https://issuetracker.google.com/issues/110237303

** Bug watch added: issuetracker.google.com/issues #110237303
   https://issuetracker.google.com/issues/110237303

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

[Desktop-packages] [Bug 1815354] Re: BCM 43142 driver not installed - no WiFi

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  BCM 43142 driver not installed - no WiFi

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  Disco daily Lubuntu 09.02.2019 and Disco daily Kubuntu 10.02.2019

  BCM 43142 drivers not installed resulting in no WiFi during and after
  installation.

  I was able to attach ethernet cable and use the command line "ubuntu-
  drivers" command to install the drivers and all worked well after
  that.

  Of course if running a machine with no ethernet then this is a huge
  problem for the user.

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

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

[Desktop-packages] [Bug 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login

[Kai-Heng Feng]

The next step is to test v4.18-rc5.

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

Title:
  [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer
  freezes after login

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

Bug description:
  I can boot to login, but if I input correct information it freezes. If
  I boot in recovery mode and choose to resume boot, I can login. But my
  external display doesn't register. If I choose the failsafeX version
  there is an error text related to xorg.

  I have not had any problems before on this terminal. It came when I
  let the system update and reboot.

  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.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 20:26:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:119b]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1197]
  InstallationDate: Installed on 2018-11-26 (100 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
   Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A715-71G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmeleon_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA715-71G:pvrV1.10:rvnKBL:rnCharmeleon_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-71G
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  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: Wed Mar  6 20:16:01 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:119b]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1197]
  InstallationDate: Installed on 2018-11-26 (100 days ago)
  InstallationMedia: Ubuntu 16.04.5 

[Desktop-packages] [Bug 1820323] Re: xorg crash

[Timo Aaltonen]

This bugreport was filed with the stock 16.04(.1) stack though, with
kernel 4.4 and xserver 1.18 but with an updated mesa. The failure here
is that some symlinks to amdgpu-pro got overwritten (since they were
owned by mesa, not amdgpu-pro..), and those need to be fixed manually.

To do that I think this should be enough:
apt --reinstall install libgl1-amdgpu-mesa-dri

That should restore the symlinks. AMD has fixed this bug in newer
releases, so that if the system mesa is upgraded, the symlinks
restoration is triggered after the upgrade.

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

-- 
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:
  Incomplete

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+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

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

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

[Desktop-packages] [Bug 1803681] Re: osmesa doesn't suport core contexts but could

[Timo Aaltonen]

indeed, it was enabled fairly recently:

mesa (18.3.0~rc5-1) experimental; urgency=medium

  * New upstream release candidate.
  * rules: Fix a typo in list of dri drivers.
  * rules, meson-add-glx-direct-toggle.diff: Fix build on hurd.
  * rules: Drop extra -Dosmesa from confflags.
  * rules: Don't build gallium nouveau on s390x.
  * rules: Classic osmesa needs classic swrast, and since it's not enabled
where llvmpipe is enabled, enable gallium osmesa there.

 -- Timo Aaltonen   Fri, 30 Nov 2018 11:45:45 +0200

so, disco has it, and it's also on ppa:ubuntu-x-swat/updates

bionic will get it with 19.0.x backport for 18.04.3

** Changed in: mesa (Ubuntu)
   Status: Incomplete => 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/1803681

Title:
  osmesa doesn't suport core contexts but could

Status in mesa package in Ubuntu:
  Fix Released

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 1801151] Re: firefox scrollbar in ubuntu mate

[Paul White]

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

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

Title:
  firefox scrollbar in ubuntu mate

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

Bug description:
  I want to report 3 bugs related to Firefox browser in Ubuntu Mate
  18.04 and 18.10:

  1- The scrollbar width is so small. And I do not know how to increase
  it.

  2- When I click in empty scrollbar in firefox, the bar goes directly
  to the place instead of goes down screen by screen.

  3- the scale display in firefox and in the whole Ubuntu Mate is so
  bad. all sentences are so small. Could you make the scale display and
  firefox work like in Kubuntu because in Kubuntu the firefox and scale
  display work great.

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

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

[Desktop-packages] [Bug 1819193] Re: Document search does not work

[Mordi]

I am able to make this work by first stopping and then restarting the
"gnome-documents" process. Search results from GNOME Shell will then be
opened in Documents as expected. Unfortunately, after a few searches,
Documents will crash and searching from g-s will no longer work.

I suspect that this is a Gnome Documents bug. However, Gnome Documents
in itself will not crash unless it is accessed from GNOME Shell search
results.

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

Title:
  Document search does not work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  1. Description: Ubuntu 18.04.2 LTS
  2. 3.28.3-0ubuntu0.18.04.4
  3. I expect to be able to search document by content from the gnome shell 
("Type to search..."). The option is enabled from settings.
  4. Nothing happens. No documents are retrieved. 

  I get the following error message in logs repeatedly:

  "Wrong number of result metas returned by search provider
  org.gnome.Documents.desktop: expected 5 but got 0"

  gnome-documents also gives this:
  "JS ERROR: GLib.Error g-invoke-error-quark: Could not locate 
gd_filename_strip_extension: (null)"

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

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

[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen

[Douglas H. Silva]

How long until the fix arrives for Cosmic?

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

Title:
  XFCE window buttons are not clickable at the top of the screen

Status in X.Org X server:
  New
Status in greybird-gtk-theme package in Ubuntu:
  Fix Released
Status in xfce4-panel package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in greybird-gtk-theme source package in Cosmic:
  Triaged
Status in xfce4-panel source package in Cosmic:
  Triaged
Status in xorg-server source package in Cosmic:
  New
Status in greybird-gtk-theme source package in Disco:
  Fix Released
Status in xfce4-panel source package in Disco:
  Fix Released
Status in xorg-server source package in Disco:
  Confirmed

Bug description:
  This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic.

  With Cosmic, it is not possible to click on the window buttons after
  moving the mouse cursor to the top of the screen. Unlike similar bugs,
  no amount of moving left or right triggers the hover event or the
  ability to click on the window button.

  With Adwaita and Numix, we see the same issues we see elsewhere, where
  the buttons can sometimes be clicked, but also have issue with the
  topmost part of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: greybird-gtk-theme 3.22.9-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Sep 29 09:05:24 2018
  InstallationDate: Installed on 2018-09-29 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929)
  PackageArchitecture: all
  SourcePackage: greybird-gtk-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Pat Clash]

This hapend after today xenial update (32bits)

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Pat Clash]

Same issue too :

firefox -p
XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
/usr/lib/i386-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found 
(required by /usr/lib/firefox/libxul.so)
Couldn't load XPCOM.

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Goonie]

3) Even when I revert back to OpenJDK 8, my build is broken
(java.lang.ExceptionInInitializerError). See

https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1820389

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

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

[Goonie]

I just tried updating my 18.04 LTS to the Gradle 4.4.1-5~18.04 that just
arrived via ubuntu-proposed, but I think the package still needs more
work.

1) It should not switch to Java 11 by force. For a LTS, this is way too
intrusive. It breaks many parts of my build system which I specifically
built on an LTS because it's supposed to be stable. I think this can be
fixed by still allowing a dependency to OpenJDK 8 and making sure
update-alternatives isn't run durig the upgrade.

2) Even if you use OpenJDK 11, it spams with WARNING messages. This is a
long standing bug:

https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1803855

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

[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Adrian S.]

After seeing Alex's post, I tried installing 410.104-0ubuntu0~18.10.1 from 
ppa:graphics-drivers.
Using 4.18.0-16-generic kernel.

I find that when I use Intel profile, powertop reports the nvidia card as 0% 
active, and the setting in Tunables shows up as Good.
However, /proc/acpi/bbswitch reports as :01:00.0 ON, and the *fans* are 
spinning.

Turning the graphics card OFF with bbswitch, the fans stop spinning.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Ftarkin]

BTW, teh bug is in X84_64 for me

$ strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_3.4.14
GLIBCXX_3.4.15
GLIBCXX_3.4.16
GLIBCXX_3.4.17
GLIBCXX_3.4.18
GLIBCXX_3.4.19
GLIBCXX_3.4.20
GLIBCXX_3.4.21
GLIBCXX_DEBUG_MESSAGE_LENGTH

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Ftarkin]

I have the same issue

f@xxx:~$ firefox
XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not found 
(required by /usr/lib/firefox/libxul.so)
Couldn't load XPCOM.

Firefox is the last version from Ubuntu 16.O4, firefox
65.0.1+build2-0ubuntu0.16.04.1

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 1819013] Re: Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

[Launchpad Bug Tracker]

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

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

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

Title:
  Hard dependency on libstdc++ 6.1.0 at runtime on ppc64el on xenial

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  $ firefox 
  XPCOMGlueLoad error for file /usr/lib/firefox/libxul.so:
  /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.22' not 
found (required by /usr/lib/firefox/libxul.so)
  Couldn't load XPCOM.
  $ ldd /usr/lib/firefox/libxul.so | head -1
  /usr/lib/firefox/libxul.so: /usr/lib/powerpc64le-linux-gnu/libstdc++.so.6: 
version `GLIBCXX_3.4.22' not found (required by /usr/lib/firefox/libxul.so)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 65.0.1+build2-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-29-generic ppc64le
  AddonCompatCheckDisabled: False
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  7 10:00 seq
   crw-rw 1 root audio 116, 33 Mar  7 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20190215002040
  Channel: Unavailable
  Date: Thu Mar  7 10:02:49 2019
  ForcedLayersAccel: False
  InstallationDate: Installed on 2018-01-11 (419 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release ppc64el 
(20170801)
  IpRoute:
   default via 10.128.60.1 dev enP2p1s0f0 
   10.128.60.0/25 dev enP2p1s0f0  proto kernel  scope link  src 10.128.60.99
  NoProfiles: True
  PciMultimedia:
   
  ProcLoadAvg: 2.46 2.48 2.23 3/1329 109239
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /dev/sda3   partition379411841110016 
-2
  ProcVersion: Linux version 4.15.0-29-generic (buildd@bos02-ppc64el-002) (gcc 
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu 
SMP Wed Jul 18 08:50:43 UTC 2018
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 16
  cpu_coreson: Number of cores online = 16
  cpu_smt: SMT=8

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

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

[Desktop-packages] [Bug 998087] Re: printer ERROR: invalidaccess OFFENDING COMMAND: filter

[Ray]

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

I had the same problem with Lenovo when I'm running Ubuntu 14.04 and I
also faced some issue whenever I tried to set up a printer with the
laptop I tried to solve this problem from the help of various post but
no result came than I finally got a solution from this site:
https://uaewebsitedevelopment.com/digital-marketing-services/

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

Title:
  printer ERROR:  invalidaccess  OFFENDING COMMAND: filter

Status in cups-filters package in Ubuntu:
  Fix Released
Status in cups-filters source package in Precise:
  Fix Released
Status in cups-filters source package in Quantal:
  Fix Released

Bug description:
  This is probably related to bug #960666  but is when trying to print to an HP 
LaserJet 4050. 
  When trying to print graphics (I have tried both from Geany and from Document 
Viewer (viewing a PDF), the printer prints a blank page and then a page with 
the text:

  ERROR:
  invalidaccess
  OFFENDING COMMAND:
  filter
  STACK:
  /SubFileDecode
  endstream
  0
  --nostringval--
  --nostringval--
  11
  false

  (above was when trying to print from geany) but I think the PDF printed the 
same text.
  This printer worked perfectly in the previous 3 versions of Xubuntu but I get 
this error in Xubuntu 12.04, so I know it's not a printer problem.
  Interestingly, the Ubuntu test page prints perfectly.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Marco Ferretti]

p.s.: restarting gnome-shell (with SIGQUIT) works as a temporary patch.

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

[Marco Ferretti]

I am still experiencing the issue on ubuntu 18.04.4 :

dpkg -s gnome-shell
Package: gnome-shell
Status: install ok installed
Priority: optional
Section: universe/gnome
Installed-Size: 7350
Maintainer: Ubuntu Developers 
Architecture: amd64
Version: 3.28.3-0ubuntu0.18.04.4
Provides: notification-daemon, polkit-1-auth-agent
Depends: libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 (>= 1.12.4), libc6 (>= 
2.14), libcairo2 (>= 1.14.0), libcanberra-gtk3-0 (>= 0.25), libcanberra0 (>= 
0.2), libcroco3 (>= 0.6.2), libecal-1.2-19 (>= 3.17), libedataserver-1.2-23 (>= 
3.17.2), libgcr-base-3-1 (>= 3.8.0), libgdk-pixbuf2.0-0 (>= 2.22.0), 
libgirepository-1.0-1 (>= 1.35.9), libgjs0-libmozjs-52-0, libgjs0g (>= 1.52.1), 
libglib2.0-0 (>= 2.53.0), libgstreamer1.0-0 (>= 1.4.0), libgtk-3-0 (>= 3.21.6), 
libical3 (>= 3.0.0), libjson-glib-1.0-0 (>= 0.13.2), libmutter-2-0 (>= 3.28.3), 
libnm0 (>= 1.0.0), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), 
libpolkit-agent-1-0 (>= 0.99), libpolkit-gobject-1-0 (>= 0.94), 
libpulse-mainloop-glib0 (>= 0.99.1), libpulse0 (>= 0.99.1), libsecret-1-0 (>= 
0.7), libstartup-notification0 (>= 0.11), libsystemd0, libx11-6, libxfixes3, 
evolution-data-server (>= 3.17.2), gir1.2-accountsservice-1.0, gir1.2-atspi-2.0 
(>= 2.9.91), gir1.2-freedesktop, gir1.2-gdesktopenums-3.0 (>= 3.12), 
gir1.2-geoclue-2.0, gir1.2-gcr-3 (>= 3.7.5), gir1.2-gdm-1.0 (>= 3.18.2), 
gir1.2-glib-2.0 (>= 1.45.3), gir1.2-gnomebluetooth-1.0 (>= 3.12.0), 
gir1.2-gnomedesktop-3.0 (>= 3.12.0), gir1.2-gtk-3.0 (>= 3.16), 
gir1.2-gweather-3.0, gir1.2-ibus-1.0 (>= 1.5.2), gir1.2-mutter-2 (>= 3.27.91), 
gir1.2-nm-1.0, gir1.2-nma-1.0, gir1.2-pango-1.0, gir1.2-polkit-1.0, 
gir1.2-rsvg-2.0, gir1.2-soup-2.4 (>= 2.40.1), gir1.2-upowerglib-1.0 (>= 0.99), 
gjs (>= 1.47.90), gnome-settings-daemon (>= 3.16.0), gnome-shell-common (= 
3.28.3-0ubuntu0.18.04.4), ubuntu-wallpapers, gsettings-desktop-schemas (>= 
3.21.3), mutter (>= 3.27.91), python3, libglib2.0-bin (>= 2.53.0)
Recommends: xserver-xorg-legacy, bolt (>= 0.2), gkbd-capplet, 
gnome-control-center, gnome-user-guide, iio-sensor-proxy, unzip, ubuntu-session 
| gnome-session
Suggests: gir1.2-telepathyglib-0.12, gir1.2-telepathylogger-0.2 (>= 0.8.0), 
chrome-gnome-shell, gdm3 (>= 3.10.0.1-3~), gnome-themes-standard-data, 
switcheroo-control
Breaks: gdm3 (<< 3.19.92), gnome-session (<< 3.19)
Conflicts: gnome-screensaver (<< 3.6)
Description: graphical shell for the GNOME desktop
 The GNOME Shell provides core interface functions like switching
 windows, launching applications or see your notifications. It takes
 advantage of the capabilities of modern graphics hardware and
 introduces innovative user interface concepts to provide a
 delightful and easy to use experience. GNOME Shell is the defining
 technology of the GNOME 3 user experience.
Homepage: https://wiki.gnome.org/Projects/GnomeShell
Original-Maintainer: Debian GNOME Maintainers 


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

[Desktop-packages] [Bug 1814964] Re: No audio when logging in as second user. Only dummy audio device seen

[Chris]

ah, sadly not.  added my user to audio group, logged in/out and still
dont get sound (my wife's session is running in the background)

I'll try a reboot and see if that works.

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

Title:
  No audio when logging in as second user.  Only dummy audio device seen

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Laptop with multiple user accounts.

  Logging in as any user has working audio, but if that session is
  locked and a second user logs in, the second user gets no sound.

  Workaround is for both users to log out and 2nd user to log in a fresh
  session.  Obviously a problem if you cant log in as the first user.

  No sound hardware is shown in the MATE sound preferences, output pane
  only shows "dummy output".

  Looking at 'top' or system monitor shows that 1st user pulseaudio is
  running, but 2nd user pulseaudio is sleeping.

  $ lspci -nnk | grep -A2 Audio
  00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset 
High Definition Audio [8086:3b57] (rev 05)
Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio 
[1028:0410]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Wed Feb  6 21:19:25 2019
  InstallationDate: Installed on 2018-11-12 (86 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Symptom_Jack: Speaker, Internal
  Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails 
to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0T6M8G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E4310
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1803810] Re: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card

[Mutatina Charles Mwombeki]

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

thank you for your reply


On Mon, 19 Nov 2018 at 06:15, Daniel van Vugt 
wrote:

> Can you please try headphones, to see if the problem is just with the
> speakers?
>
> Please also run this command:
>
>   dpkg -l > allpackages.txt
>
> and send us the resulting 'allpackages.txt'.
>
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> ** Summary changed:
>
> - [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card
> + [chtmax98090 - chtmax98090, playback] Cannot get sound at all
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1803810
>
> Title:
>   [chtmax98090 - chtmax98090, playback] Cannot get sound at all
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   just downloaded and upgraded to ubuntu 18.04 and now i cannot get
>   sound at all im using acer chromebook cb3-111 bay trail with intel
>   processor
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: pulseaudio 1:11.1-1ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
>   Uname: Linux 4.15.0-39-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  mutta255   1262 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Nov 17 11:39:20 2018
>   InstallationDate: Installed on 2018-11-16 (0 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   SourcePackage: pulseaudio
>   Symptom: audio
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect
> card
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/03/2017
>   dmi.bios.vendor: coreboot
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: GOOGLE
>   dmi.modalias:
> dmi:bvncoreboot:bvr:bd12/03/2017:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
>   dmi.product.name: Gnawty
>   dmi.product.version: 1.0
>   dmi.sys.vendor: GOOGLE
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803810/+subscriptions
>

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

Title:
  [chtmax98090 - chtmax98090, playback] Cannot get sound at all

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  just downloaded and upgraded to ubuntu 18.04 and now i cannot get
  sound at all im using acer chromebook cb3-111 bay trail with intel
  processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mutta255   1262 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 11:39:20 2018
  InstallationDate: Installed on 2018-11-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2017
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd12/03/2017:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1814964] Re: No audio when logging in as second user. Only dummy audio device seen

[Chris]

I was reading more about pulseaudio and saw this on one of the Arch pages:
https://wiki.archlinux.org/index.php/PulseAudio#Configuration_files
"PulseAudio uses udev and logind to give access dynamically to the currently 
"active" user"

could it be this which is not happening correctly?  I started looking at
udev and logind documentation and dont know where to start.

The previous line quoted above, was about not needing to have a user
being member of the "audio" group.  Thought I would check, and strange!
my account is the only one NOT in the audio group.

Ive added my user in and will report back if that fixes it.  (my user
was the default admin one created on ubuntu install).

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

Title:
  No audio when logging in as second user.  Only dummy audio device seen

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Laptop with multiple user accounts.

  Logging in as any user has working audio, but if that session is
  locked and a second user logs in, the second user gets no sound.

  Workaround is for both users to log out and 2nd user to log in a fresh
  session.  Obviously a problem if you cant log in as the first user.

  No sound hardware is shown in the MATE sound preferences, output pane
  only shows "dummy output".

  Looking at 'top' or system monitor shows that 1st user pulseaudio is
  running, but 2nd user pulseaudio is sleeping.

  $ lspci -nnk | grep -A2 Audio
  00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset 
High Definition Audio [8086:3b57] (rev 05)
Subsystem: Dell 5 Series/3400 Series Chipset High Definition Audio 
[1028:0410]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: MATE
  Date: Wed Feb  6 21:19:25 2019
  InstallationDate: Installed on 2018-11-12 (86 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Symptom_Jack: Speaker, Internal
  Title: [Latitude E4310, IDT 92HD81B1X5, Speaker, Internal] Pulseaudio fails 
to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0T6M8G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0T6M8G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E4310
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1820377] [NEW] Headerbars not respecting window control button layout

[Roland (Rolandixor) Taylor]

Public bug reported:

I'm running Ubuntu 18.10.

Full details here: https://askubuntu.com/questions/1125401/how-to-
restore-correct-window-control-behaviour-in-gnome

Basically: after installing, then later removing (purging) pantheon, I
found that window controls on CSD windows no longer respect the
gsettings value. Clearing dconf settings completely made no difference.

Only this account is affect.

** Affects: unity-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Headerbars not respecting window control button layout

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 18.10.

  Full details here: https://askubuntu.com/questions/1125401/how-to-
  restore-correct-window-control-behaviour-in-gnome

  Basically: after installing, then later removing (purging) pantheon, I
  found that window controls on CSD windows no longer respect the
  gsettings value. Clearing dconf settings completely made no
  difference.

  Only this account is affect.

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

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

[Desktop-packages] [Bug 1819368] Re: unity-control-center crashed with SIGSEGV in free()

[Khurshid Alam]

** Branch linked: lp:~khurshid-alam/unity-control-center/info-panel-fix

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

Title:
  unity-control-center crashed with SIGSEGV in free()

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

Bug description:
  Happens when trying to open the info (details) panel

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: unity-control-center 15.04.0+19.04.20190209-0ubuntu2
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Mar 10 15:09:20 2019
  ExecutablePath: /usr/bin/unity-control-center
  ExecutableTimestamp: 1551456572
  InstallationDate: Installed on 2019-03-09 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  ProcCmdline: unity-control-center info --verbose
  ProcCwd: /home/doug
  SegvAnalysis:
   Segfault happened at: 0x7f17f1c1f25d <__GI___libc_free+29>:  mov
-0x8(%rdi),%rax
   PC (0x7f17f1c1f25d) ok
   source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   __GI___libc_free (mem=0x1) at malloc.c:3109
   g_unix_mount_free () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so
   () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so
   g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in __GI___libc_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[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