[Desktop-packages] [Bug 1764515] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1764515

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: xenial

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When 
I installed afresh, wifi was alright until recently, everyone time I connect, 
it pops the dialog that the wifi key is needed for authentication over and 
again, so it never gets connected to the internet.i have tried reinstalling 
network manager, service restart, boot and reboot, adding [device] 
wifi.scan nothing worked
  What do I need? I barely use windows now 'Cause linux is just dope...‎

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

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

[Desktop-packages] [Bug 1758067] Re: OpenType font variation not working correctly

[Olivier Tilloy]

Adolfo, can you please elaborate on what you mean by not implemented yet?
I don't see any indication that opentype support is not implemented in 
libreoffice (it seems that there's no UI to select specific opentype features, 
but fonts should definitely be listed at the very least).

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

Title:
  OpenType font variation not working correctly

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I tried to open an OpenDocument presentation with text formatted in Adobe 
Source Sans (OpenType version installed). But LibreOffice did not recognise the 
latest version of this font despite refreshing font cache several times.
  ---
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: 
  InstallationMedia: 
  Package: libreoffice 1:6.0.2-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1764515] Re: wifi crashes in ubuntu 16.04 lts xenial

[Kai-Heng Feng]

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

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  
  ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When 
I installed afresh, wifi was alright until recently, everyone time I connect, 
it pops the dialog that the wifi key is needed for authentication over and 
again, so it never gets connected to the internet.i have tried reinstalling 
network manager, service restart, boot and reboot, adding [device] 
wifi.scan nothing worked
  What do I need? I barely use windows now 'Cause linux is just dope...‎

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

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

[Desktop-packages] [Bug 1504404] Re: Imported image got black

[Olivier Tilloy]

Sorry for the lack of feedback in almost three years…

Is this bug still present in more recent versions of libreoffice?

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

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

Title:
  Imported image got black

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Mint 17.2
  LibO 5.0.2 from PPA

  When I try to Insert -> Image, select a file, (if activated Preview it
  shows correctly) and then Insert, I only get a Black Box in big images
  (2.9 mb)

  It also happens if I try to Copy & Paste or Dragging

  I tried with LibO 4.4.3 rc2 from Mint 17.2 and I got the same results
  inserting, copying or dragging: a Black Box.

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

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

[Desktop-packages] [Bug 1574746] Re: Enable support for libsoxr

[Daniel van Vugt]

That's mostly because fixing bug 1702558 is a prerequisite.

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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

[Desktop-packages] [Bug 1764202] Re: chromium-browser not drawing change when tab change after resume

[Olivier Tilloy]

It looks like this could be a problem with the NVIDIA proprietary
driver.

Did this work correctly with previous versions of chromium and/or the
driver?

Are there any crash files in /var/crash ?

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

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

Title:
  chromium-browser not drawing change when tab change after resume

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  # reploduce
  chromium open multi tab.
  suspend and resume ubuntu.
  chromium tab change.

  # issue
  Drawing of the contents of the tab is not updated even when tab switching is 
done. (Even in this state, the Chromium Web page title display switches 
normally.)

  # workaround
  After waiting for a while after switching the tab, the tab switch will 
operate normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 09:14:10 2018
  DetectedPlugins:
   
  InstallationDate: Installed on 2018-03-04 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1574746] Re: Enable support for libsoxr

[Neo]

Still not included in 18.04 delivery ...

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

Title:
  Enable support for libsoxr

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'd like to ask to enable support for libsoxr-based resamplers in the 
official Ubuntu packages for pulseaudio. The upstream already supports libsoxr 
and automatically detects its availability, so the only change really needed is 
to add the build dependency to debian/control.
   
  The resamplers based in libsoxr offer better quality and better performace 
while introducing more delay compared to the speex resamplers that are used by 
default. The resamplers are documented in the man pages of pulseaudio in Ubuntu 
16.04 but unfortunately are not enabled at build time ('pulseaudio 
--dump-resample-methods' doesn't list them). I've built local packages with 
libsoxr and verified that the resampler works as expected.

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

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

[Desktop-packages] [Bug 1704250] Re: ERROR

[Launchpad Bug Tracker]

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

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

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

Title:
  ERROR

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The system has a breakdown problem since the new update from ubuntu
  15.04, I would like to know how to repair it. From already thank you
  very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul 13 22:20:10 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-62-generic, i686: installed
   bbswitch, 0.8, 4.4.0-66-generic, i686: installed
   bbswitch, 0.8, 4.4.0-75-generic, i686: installed
   bbswitch, 0.8, 4.4.0-83-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] NX8600GT-T2D256EZ 
[1462:0910]
  InstallationDate: Installed on 2017-02-09 (154 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lsusb:
   Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard
   Bus 002 Device 002: ID 04f3:0230 Elan Microelectronics Corp. 3D Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. GA-73VM-S2
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=73161ce2-6cf4-4d9d-8c08-a11a9e14405b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4c
  dmi.board.name: GA-73VM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd10/07/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-73VM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-73VM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-73VM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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: Thu Jul 13 22:17:49 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB+PS/2 Optical Mouse MOUSE, id 8
   inputHID 0b38:0010KEYBOARD, id 9
   inputHID 0b38:0010KEYBOARD, id 10
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1704409] Re: Flickering screen on ubuntu 16.04.2 Lenovo B70

[Launchpad Bug Tracker]

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

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

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

Title:
  Flickering screen on ubuntu 16.04.2 Lenovo B70

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Tested both unity & ubuntu-gnome on 16.04.2
  and both are constantly flickering from login to desktop and on LIVEusb on a 
product: 

  Haswell-ULT Integrated Graphics Controller and driver=i915

  and kernel: Linux fernand-Lenovo-B70-80 4.8.0-58-generic
  #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 UTC 2017 x86_64 x86_64
  x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jul 14 17:18:12 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3987]
  InstallationDate: Installed on 2017-07-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp.
   Bus 001 Device 003: ID 0bda:579a Realtek Semiconductor Corp.
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=c471367f-a9a5-4e15-a987-f7b614634a1d ro quiet splash 
"acpi_osi=Windows 2013" vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D1CN06WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrD1CN06WW:bd05/18/2015:svnLENOVO:pn80MR:pvrLenovoB70-80:rvnLENOVO:rnLenovoB70-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB70-80:
  dmi.product.name: 80MR
  dmi.product.version: Lenovo B70-80
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jul 14 17:06:37 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5921
   vendor CMN
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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

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

[Desktop-packages] [Bug 1749692] Re: My Resolution is verry Low

[Launchpad Bug Tracker]

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

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

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

Title:
  My Resolution is verry Low

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My monitor is HD but the system only shows low resolution.The highest is 
1024x768.
  What can I do to get more resolution options?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:04:20 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4th Generation Core Processor Family 
Integrated Graphics Controller [103c:0266]
  InstallationDate: Installed on 2018-02-06 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Hewlett-Packard HP 402 G1 SFF Business PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=a8d31c50-2e57-46fd-bbfb-a8f11d427e0a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: BRJ448DM7Q
  dmi.board.name: 0266
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: BRJ448DM7Q
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: 1.02
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd04/03/2014:svnHewlett-Packard:pnHP402G1SFFBusinessPC:pvr1.02:rvnHewlett-Packard:rn0266:rvr1.02:cvnHewlett-Packard:ct3:cvr1.02:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP 402 G1 SFF Business PC
  dmi.product.version: 1.02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices

[William F Hammond]

My last sentence in #9 should be:

It's certainly less than transparent usb access through the lightning
port to the file system on the iPhone.

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

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

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

[Desktop-packages] [Bug 1759540] Re: [MIR] ubuntu-report: send telemetry data to ubuntu server

[Michael Hudson-Doyle]

The package looks fine to me now.

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

Title:
  [MIR] ubuntu-report: send telemetry data to ubuntu server

Status in ubuntu-report package in Ubuntu:
  New

Bug description:
  Note that only the C library ("libsysmetrics1") and the command line
  ("ubuntu-report") packages are needed in main (we should also promote
  "libsysmetrics-dev" package, even if not necessary). We don't need the
  Go API "golang-github-ubuntu-ubuntu-report-dev" which has many go
  package dependencies in universe.

  [Availability]
  Available and built on all archs.

  [Rationale]
  We want to provide telemetry upload features, collected by ubiquity, 
do-release-upgrader and that package in ubnutu 18.04. see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1755456 for more 
rationales and details.

  [Security]
  No security issue reported, as brand new package.
  The package do a POST message over https to an ubuntu server, data being sent 
are really limited to garantee anynomous informations.
  See example of what is sent on https://github.com/ubuntu/ubuntu-report README.

  [Quality assurance]
  The canonical desktop team is the upstream maintainer and will continue 
maintening it.
  Upstream has CI built-in on every commit + coverage report. The package build 
and runs (currently) 243 tests from unit to integration tests. Autopkgtests 
ensuring that building works and tests still pass is also provided.

  In addition the documentation and C API are continously strongly
  tested (with examples extracted from the documentation, built, linked
  against a on-demand generated C library, and tests ran against it).

  [Dependencies]
  Upstream is using a vendor/ directory, but the ubuntu package remove it on 
build and use the distribution packaged build-deps equivalent.
  No runtime dep in the 3 packages that needs to be promoted.

  [Standards compliance]
  Package follow latest debian packaging standard compliant. No lintian 
override files, and binaries/packages follows Debian standard FHS. Note that 
there is no .symbols file as the generated C API export internal symbols 
(starting with _) which names contains a hash dependant of the source file, and 
per arch specific. The exported symbols from the public API have a stable name 
though: https://godoc.org/github.com/ubuntu/ubuntu-report/pkg/sysmetrics/C

  [Maintenance]
  Canonical desktop team being the usptream and downstream maintainer, strongly 
backed by tests, will follow bugs and maintenance.

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

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

[Desktop-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices

[William F Hammond]

I could not replicate for my latest photos this evening what I reported
in #8.

Yet by fiddling in various ways, after a reboot I was able to coax
shotwell to import the photos on the iPhone. I then had command line
access to those photos in the location where shotwell dropped them.

As for /run/user/1000/gvfs: the robotic gphoto name appeared there on
and off, but when it was there it appeared to be empty from the command
line.

As a comment on my #8, it would seem that the appearance of the robotic
gphoto name in /run/user/1000/gvfs has something to do with a prior
running of shotwell.  (The shotwell executable in Xenial links to two
gphoto runtime libraries.)

I don't know what is going on.

It's certainly less than transparent access through the lightning port
to the usb file system on the iPhone.

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

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

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

[Desktop-packages] [Bug 1764611] Re: gnome-shell crashed with signal 5

[Apport retracing service]

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

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 #1748450, 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/1764611/+attachment/5118759/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This appeared shortly after I logged into the GNOME desktop. Cannot
  trace it back to a specific cause, though, unfortunately.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr 16 17:05:46 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-07 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1641284] Re: libatk-adaptor breaks down the LibreOffice TexMaths extension

[Bug Watch Updater]

** Changed in: at-spi2-atk (Debian)
   Status: New => Fix Released

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

Title:
  libatk-adaptor breaks down the LibreOffice TexMaths extension

Status in at-spi2-atk package in Ubuntu:
  Confirmed
Status in at-spi2-atk package in Debian:
  Fix Released

Bug description:
  Package: libatk-adaptor 2.18.1-2ubuntu1
  System: Ubuntu 16.04.1 LTS (Xenial Xerus)

  If the package libatk-adaptor is installed on Ubuntu (as a depency of
  gnome-orca for example), it breaks down the LibreOffice TexMaths
  extension. TexMaths is a popular extension used to enter / edit LaTeX
  equations on LibreOffice (see http://roland65.free.fr/texmaths).

  Step to reproduce the bug:

  1. It is assumed that LibreOffice 5.1.4 (with at least the Writer and
  Draw components) is installed on Ubuntu. It is also assumed that
  libatk-adaptor is installed.

  2. Install texlive:
  sudo apt-get install texlive

  3. Download and install the TexMaths extension (version 0.42) from
  there: https://sourceforge.net/projects/texmaths/files/0.42/

  4. Create a new empty Writer document, then click on the Pi icon (this
  is the TexMaths icon) and in the window that opens, type: 'x(t)+y(t)'
  (without the quotes), then click on the LaTeX button. This generates
  an SVG image of the 'x(t)+y(t)' equation.

  5. Select the SVG image of the equation by left clicking on it. Then
  click on the Pi icon. Now, instead of editing the equation, an error
  message is displayed: "The selected object is not a TexMaths
  equation... Please unselect it and call the macro again...".

  6. Now, right click on the SVG image and select the 'Description' menu
  voice. In the window that opens, the description is empty and does not
  contain the equation text, as it should.

  7. Now purge (and not just remove) the libatk-adaptor package:

  sudo apt-get purge libatk-adaptor

  then logout and login and repeat the steps 4, 5, and 6: everything is
  OK and the equation can be edited as usual.

  Another way to remove the bug instead of purging libatk-adaptor is to
  rename the file: /etc/X11/Xsession.d/90atk-adaptor to
  /etc/X11/Xsession.d/90atk-adaptor.orig . Then logout and login.

  Note there is another bug #1584795 that relates libatk-adaptor and
  LibreOffice, see there https://bugs.launchpad.net/ubuntu/+source/at-
  spi2-atk/+bug/1584795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1641284/+subscriptions

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

[Desktop-packages] [Bug 1762307] Re: Cannot access enctypted volume

[Glyn Davies]

I have the same error occurring when trying to decrypt a removable USB
drive. Though the same machine is running on a LUKS+LVM encrypted system
disk without having any issues at all.

The actual error is:
Unable to access "64 GB Encrypted"
Error unlocking /dev/sdb1: The function 'bd_crypto_luks_open_blob' called, but 
not implemented

I have also confirmed that the USB drive in question is able to be
unencrypted and read successfully on my 16.04 machine.

Current setup info:

 ./+o+-glyndavies@riss
  y- -yy+  OS: Ubuntu 18.04 bionic
   ://+//-yyo  Kernel: x86_64 Linux 4.15.0-15-generic
   .++ .:/++/-.+sss/`  Uptime: 12m
 .:++o:  //:--:/-  Packages: 1941
o:+o+:++.`..```.-/oo+/ Shell: bash 4.4.19
   .:+o:+o/.  `+sssoo+/Resolution: 3840x2520
  .++/+:+oo+o:` /sssooo.   DE: Budgie
 /+++//+:`oo+o   /::--:.   WM: BudgieWM
 \+/+o+++`o++o   ++.   WM Theme: Adapta
  .++.o+++oo+:` /dddhhh.   GTK Theme: Adapta [GTK2/3]
   .+.o+oo:.  `odd+Icon Theme: Papirus-Adapta
\+.++o+o``-.:ohdh+ Font: Noto Sans UI 11
 `:o+++ `oyo++os:  CPU: Intel Core i7-5600U @ 4x 3.2GHz 
[77.0°C]
   .o:`.syhhh/.oo++o`  GPU: intel
   /osyyo++ooo+++/ RAM: 1978MiB / 7661MiB
   ` +oo+++o\:
  `oo++.

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

Title:
  Cannot access enctypted volume

Status in udisks2 package in Ubuntu:
  New

Bug description:
  At the screen preparing to install Kubuntu, I selected the button
  "Guided - use entire disk and set up encrypted LVM". System has two
  hard drives, sda with both Mint 18.3 and Bionic 18.04; sdb with Bionic
  18.04. The installer graphic showed it would use all of sda for
  Kubuntu.

  In Dolphin, trying to access the encrypted volume on sda returns:
  An error occurred while accessing '58.9 GiB Encrypted Drive', the system 
responded: The requested operation has failed: Error unlocking /dev/sda5: The 
function 'bd_crypto_luks_open_blob' called, but not implemented!

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

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

[Desktop-packages] [Bug 1762307] Re: Cannot access enctypted volume

[Glyn Davies]

Apologies, let's try that again.

Current setup info:
OS: Ubuntu 18.04 bionic
Kernel: x86_64 Linux 4.15.0-15-generic
Uptime: 12m
Packages: 1941
Shell: bash 4.4.19
Resolution: 3840x2520
DE: Budgie
WM: BudgieWM
WM Theme: Adapta
GTK Theme: Adapta [GTK2/3]
Icon Theme: Papirus-Adapta
Font: Noto Sans UI 11
CPU: Intel Core i7-5600U @ 4x 3.2GHz [77.0°C]
GPU: intel
RAM: 1978MiB / 7661MiB

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

Title:
  Cannot access enctypted volume

Status in udisks2 package in Ubuntu:
  New

Bug description:
  At the screen preparing to install Kubuntu, I selected the button
  "Guided - use entire disk and set up encrypted LVM". System has two
  hard drives, sda with both Mint 18.3 and Bionic 18.04; sdb with Bionic
  18.04. The installer graphic showed it would use all of sda for
  Kubuntu.

  In Dolphin, trying to access the encrypted volume on sda returns:
  An error occurred while accessing '58.9 GiB Encrypted Drive', the system 
responded: The requested operation has failed: Error unlocking /dev/sda5: The 
function 'bd_crypto_luks_open_blob' called, but not implemented!

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

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

[Desktop-packages] [Bug 1764539] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto

[dino99]

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

** This bug has been marked a duplicate of bug 1762827
   package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different 
from other instances of package libsane1:i386

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: intentando sobreescribir el compartido
  `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias
  del paquetes libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  es un informe de fallo interno, en ubuntu mate Versión 17.10 (Artful
  Aardvark) de 64-bit. Toshiba Satellite-A215 AMD Athlon(tm) 64 X2 Dual-
  Core Processor TK-57 × 2

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sat Apr 14 21:07:45 2018
  ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  InstallationDate: Installed on 2018-04-14 (2 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  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/1764539/+subscriptions

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

[Desktop-packages] [Bug 1703668] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()

[Treviño]

ACK, I missed your comment before... That's fine.

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

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

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from
  meta_input_settings_find_logical_monitor()

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/bfdb8ffc57978ae7c23f78fdf44266fa56985fe9

  ---

  The only thing i recognize from the crash is the crash report.
  everything works as expected

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.12.0-6.7-generic 4.12.0
  Uname: Linux 4.12.0-6-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Jul  9 21:56:54 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-07 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170630)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd10dc9e103 :   
jmpq   *0x88(%rax)
   PC (0x7fd10dc9e103) ok
   source "*0x88(%rax)" ok
   SP (0x7ffe42d50508) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1764518] Re: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] failed to install/upgrade: problemas com dependências - a deixar por configurar [The libpam-s

[Daniel van Vugt]

** Summary changed:

- package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] failed 
to install/upgrade: problemas com dependências - a deixar por configurar
+ package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] failed 
to install/upgrade: problemas com dependências - a deixar por configurar [The 
libpam-systemd: amd64 package is not yet configured.]

** Tags added: xenial

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

Title:
  package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
  failed to install/upgrade: problemas com dependências - a deixar por
  configurar [The libpam-systemd: amd64 package is not yet configured.]

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On system startup

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antonio1431 F pulseaudio
  Date: Mon Apr 16 00:50:52 2018
  ErrorMessage: problemas com dependências - a deixar por configurar
  InstallationDate: Installed on 2018-04-15 (0 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: pulseaudio
  Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] 
failed to install/upgrade: problemas com dependências - a deixar por configurar
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V5.10
  dmi.board.name: Satellite U300-130
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300-130:pvrPSU30E-03D013PT:rvnTOSHIBA:rnSatelliteU300-130:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite U300-130
  dmi.product.version: PSU30E-03D013PT
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1764414] Re: + and - buttons are not themed in LibreOffice

[Daniel van Vugt]

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Low

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-themes
   Status: New => Confirmed

** Changed in: ubuntu-themes
   Importance: Undecided => Low

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

Title:
  + and - buttons are not themed in LibreOffice

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Start Writer
  2. Go to Tools -> Options -> LibreOffice -> General
  3. You will see an input field with + and - buttons

  The buttons are not properly themed in Ambiance:
  1. The - button has no left border
  2. The + button has an extra right border
  3. There is no hover effect (only touching without pressing the button)

  All those three issues do not exist in Adwaita.

  See the attached screencast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 15:37:38 2018
  InstallationDate: Installed on 2017-10-02 (195 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (19 days ago)

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

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

[Desktop-packages] [Bug 1703668] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()

[Treviño]

** No longer affects: gnome-shell (Ubuntu)

** Changed in: mutter (Ubuntu)
   Importance: Medium => High

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from
  meta_input_settings_find_logical_monitor()

Status in Mutter:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/bfdb8ffc57978ae7c23f78fdf44266fa56985fe9

  ---

  The only thing i recognize from the crash is the crash report.
  everything works as expected

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.12.0-6.7-generic 4.12.0
  Uname: Linux 4.12.0-6-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Jul  9 21:56:54 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-07 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170630)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd10dc9e103 :   
jmpq   *0x88(%rax)
   PC (0x7fd10dc9e103) ok
   source "*0x88(%rax)" ok
   SP (0x7ffe42d50508) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1764591] [NEW] update gnome-control-center to 3.28.1

[Jeremy Bicha]

Public bug reported:

placeholder bug for 3.28.1 upgrade

bugfix release:
https://gitlab.gnome.org/GNOME/gnome-control-center/commits/gnome-3-28

plus a cherry-picked patch for a file permissions issue

** Affects: gnome-control-center (Ubuntu)
 Importance: Medium
 Status: In Progress


** Tags: bionic upgrade-software-version

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

Title:
  update gnome-control-center to 3.28.1

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  placeholder bug for 3.28.1 upgrade

  bugfix release:
  https://gitlab.gnome.org/GNOME/gnome-control-center/commits/gnome-3-28

  plus a cherry-picked patch for a file permissions issue

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

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

[Desktop-packages] [Bug 1757321] Re: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic]

[GizmoChicken]

I just want to reiterate that, as mentioned by Stuart Bishop in Comment
#8 above, this bug also affects the Ubuntu Live USB/CD.

I've been using an Ubuntu Live USB for accessing LUKS volumes on my
systems for years.  I hope that the Ubuntu 18.04 Live USB continues to
provide this functionality.

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

Title:
  udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2
  instead of suggests [Can't mount encrypted USB drive after upgrade to
  bionic]

Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  after upgrading to bionic, attempts to mount an encrypted USB drive
  fail with the error "function bd_crypto_luks_open_blob called but not
  implemented"

  Installing libblockdev-crypto2 and libblockdev-crypto-dev and
  rebooting appears to have fixed it, but should that be necessary?  or
  at least better documented?
  (https://www.distrowatch.com/weekly.php?issue=20171113 is the only
  reference I could find on the error)

  [Workaround]
  1. Install libblockdev-crypto2
  2. Restart udisks:
$ systemctl restart udisks2

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udisks2 2.7.6-2ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules
  Date: Tue Mar 20 20:28:39 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (942 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  MachineType: Apple Inc. MacBookPro11,4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1
  SourcePackage: udisks2
  UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP114.88Z.0172.B04.1506051511
  dmi.board.name: Mac-06F11FD93F0323C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,4
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11FD93F0323C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen

[Daniel van Vugt]

Thanks. The common factor then in both reports of this bug is that
nouveau is in use. And historically, this isn't surprising. Nouveau has
occasionally had such missing textures bugs like this over the years.

Please try installing the Nvidia proprietary driver if you haven't
already:

  sudo apt install nvidia-driver-390

Another fix which may be required at the same time, or as an alternative
is to tell gdm3 to not try to use Wayland. You can do that by editing
/etc/gdm3/custom.conf and uncommenting:

  #WaylandEnable=false

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen

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

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1764589] Re: Switch to using apt-config-icons

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  Switch to using apt-config-icons

Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  For Ubuntu 18.04 LTS, we'd like to have gnome-software depend on apt-
  config-icons instead of including the apt snippet in gnome-software
  itself. The change is virtually harmless as apt-config-icons includes
  the same apt snippet that gnome-software did but adds an icon size
  parameter.

  apt-config-icons is part of appstream 0.12 (so these apt snippets are
  now upstream and can be shared among other appstream clients).
  appstream 0.12 is in bionic because of recent FFe LP: #1762292. This
  upload is just clean up basically from that FFe. apt-config-icons is
  already in main.

  A major advantage of the new apt snippets is that users can easily get
  higher resolution icons by installing one of the other apt-config-
  icons-* packages. Some of those don't work yet because
  https://appstream.ubuntu.com/ will need to get a newer version of the
  appstream-generator software installed first.

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

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

[Desktop-packages] [Bug 1764589] [NEW] Switch to using apt-config-icons

[Jeremy Bicha]

Public bug reported:

For Ubuntu 18.04 LTS, we'd like to have gnome-software depend on apt-
config-icons instead of including the apt snippet in gnome-software
itself. The change is virtually harmless as apt-config-icons includes
the same apt snippet that gnome-software did but adds an icon size
parameter.

apt-config-icons is part of appstream 0.12 (so these apt snippets are
now upstream and can be shared among other appstream clients). appstream
0.12 is in bionic because of recent FFe LP: #1762292. This upload is
just clean up basically from that FFe. apt-config-icons is already in
main.

A major advantage of the new apt snippets is that users can easily get
higher resolution icons by installing one of the other apt-config-
icons-* packages. Some of those don't work yet because
https://appstream.ubuntu.com/ will need to get a newer version of the
appstream-generator software installed first.

** Affects: gnome-software (Ubuntu)
 Importance: Low
 Status: In Progress


** Tags: bionic

** Description changed:

  For Ubuntu 18.04 LTS, we'd like to have gnome-software depend on apt-
  config-icons instead of including the apt snippet in gnome-software
  itself. The change is virtually harmless as apt-config-icons includes
  the same apt snippet that gnome-software did but adds an icon size
  parameter.
  
- apt-config-icons is part of appstream 0.12 which got recent FFe LP:
+ apt-config-icons is part of appstream 0.12 (so these apt snippets are
+ now upstream). appstream 0.12 is in bionic because of recent FFe LP:
  #1762292. This upload is just clean up basically from that FFe. apt-
  config-icons is already in main.
  
  A major advantage of the new apt snippets is that users can easily get
  higher resolution icons by installing one of the other apt-config-
  icons-* packages. Some of those don't work yet because
  https://appstream.ubuntu.com/ will need to get a newer version of the
  appstream-generator software installed first.

** Description changed:

  For Ubuntu 18.04 LTS, we'd like to have gnome-software depend on apt-
  config-icons instead of including the apt snippet in gnome-software
  itself. The change is virtually harmless as apt-config-icons includes
  the same apt snippet that gnome-software did but adds an icon size
  parameter.
  
  apt-config-icons is part of appstream 0.12 (so these apt snippets are
- now upstream). appstream 0.12 is in bionic because of recent FFe LP:
- #1762292. This upload is just clean up basically from that FFe. apt-
- config-icons is already in main.
+ now upstream and can be shared among other appstream clients). appstream
+ 0.12 is in bionic because of recent FFe LP: #1762292. This upload is
+ just clean up basically from that FFe. apt-config-icons is already in
+ main.
  
  A major advantage of the new apt snippets is that users can easily get
  higher resolution icons by installing one of the other apt-config-
  icons-* packages. Some of those don't work yet because
  https://appstream.ubuntu.com/ will need to get a newer version of the
  appstream-generator software installed first.

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

Title:
  Switch to using apt-config-icons

Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  For Ubuntu 18.04 LTS, we'd like to have gnome-software depend on apt-
  config-icons instead of including the apt snippet in gnome-software
  itself. The change is virtually harmless as apt-config-icons includes
  the same apt snippet that gnome-software did but adds an icon size
  parameter.

  apt-config-icons is part of appstream 0.12 (so these apt snippets are
  now upstream and can be shared among other appstream clients).
  appstream 0.12 is in bionic because of recent FFe LP: #1762292. This
  upload is just clean up basically from that FFe. apt-config-icons is
  already in main.

  A major advantage of the new apt snippets is that users can easily get
  higher resolution icons by installing one of the other apt-config-
  icons-* packages. Some of those don't work yet because
  https://appstream.ubuntu.com/ will need to get a newer version of the
  appstream-generator software installed first.

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

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

[Desktop-packages] [Bug 1764486] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Проверочное утверждение «hash

[Daniel van Vugt]

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

** This bug is no longer a duplicate of private bug 1764376
** This bug has been marked a duplicate of bug 1763878
   [regression] Many programs crashing at exit with assert failure: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed. Called from 
cairo_debug_reset_static_data()

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Проверочное утверждение «hash_table->live_entries == 0» не выполнено.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Проверочное 
утверждение «hash_table->live_entries == 0» не выполнено.
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 21:25:36 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['restart-entry@atomant', 
'axemenu@wheezy', 'dash-to-d...@micxgx.gmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   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 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell-extension-prefs 
extension:///dash-to-d...@micxgx.gmail.com
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff8e8138622 , assertion=assertion@entry=0x7ff8f0687d05 
"hash_table->live_entries == 0", file=file@entry=0x7ff8f0687ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7ff8f0687e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7ff8f0687d05 "hash_table->live_entries == 
0", file=0x7ff8f0687ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7ff8f0687e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Проверочное утверждение «hash_table->live_entries == 
0» не выполнено.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_c

[Jeremy Bicha]

I am unsubscribing ubuntu-sponsors since this has been uploaded to the
bionic queue.

Actually, the GTK devs just released 3.22.30 which I have also uploaded
to the queue so this fix is in the queue twice now!

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 237721] Re: Secure attention key

[Bug Watch Updater]

** Changed in: kde-baseapps
   Status: Confirmed => Unknown

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

Title:
  Secure attention key

Status in gdm:
  New
Status in KDE Base:
  Unknown
Status in Light Display Manager:
  Won't Fix
Status in Unity System Compositor:
  New
Status in gdm package in Ubuntu:
  Confirmed
Status in kdebase-workspace package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Won't Fix
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  New
Status in xdm package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: gdm

  In many environments computers are left unattended (e.g. schools,
  libraries, etc) and people can launch applications which mimic the
  look-and-feel of the login application (GDM) in order to get the users
  username and password.

  This is called login spoofing.
  * http://en.wikipedia.org/wiki/Login_spoofing

  Login spoofing can be prevented by using a secure attention key which is a 
key combination pressed before the user login to launch the password request 
dialog. This key can only be seen by the kernel, and not sniffed by any 
application.
  * http://en.wikipedia.org/wiki/Secure_attention_key

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

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

[Desktop-packages] [Bug 473650] Re: file-roller assert failure: *** glibc detected *** file-roller: free(): invalid pointer: 0x08b2da68 ***

[pqwoerituytrueiwoq]

Zip file I was using trying to check for other bugs
Here is my apport.log file:
ERROR: apport (pid 2343) Mon Apr 16 23:07:43 2018: called for pid 2335, signal 
6, core limit 0, dump mode 1
ERROR: apport (pid 2343) Mon Apr 16 23:07:43 2018: executable: 
/usr/bin/file-roller (command line "file-roller 
/home/xubuntu/Desktop/Adwaita.zip")
ERROR: apport (pid 2343) Mon Apr 16 23:07:43 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 2343) Mon Apr 16 23:07:43 2018: debug: session gdbus call: 
ERROR: apport (pid 2343) Mon Apr 16 23:07:47 2018: wrote report 
/var/crash/_usr_bin_file-roller.999.crash
ERROR: apport (pid 3812) Mon Apr 16 23:14:53 2018: called for pid 3805, signal 
11, core limit 0, dump mode 1
ERROR: apport (pid 3812) Mon Apr 16 23:14:53 2018: executable: 
/usr/bin/file-roller (command line "file-roller 
/home/xubuntu/Desktop/Adwaita.zip")
ERROR: apport (pid 3812) Mon Apr 16 23:14:53 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 3812) Mon Apr 16 23:14:53 2018: debug: session gdbus call: 
ERROR: apport (pid 3812) Mon Apr 16 23:14:57 2018: wrote report 
/var/crash/_usr_bin_file-roller.999.crash
ERROR: apport (pid 4815) Mon Apr 16 23:18:39 2018: called for pid 3857, signal 
11, core limit 0, dump mode 1
ERROR: apport (pid 4815) Mon Apr 16 23:18:39 2018: executable: 
/usr/lib/valgrind/memcheck-amd64-linux (command line "/usr/bin/valgrind.bin -v 
--tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log 
/usr/bin/file-roller /home/xubuntu/Desktop/Adwaita.zip")
ERROR: apport (pid 4815) Mon Apr 16 23:18:39 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 4815) Mon Apr 16 23:18:39 2018: debug: session gdbus call: 
ERROR: apport (pid 4815) Mon Apr 16 23:19:26 2018: wrote report 
/var/crash/_usr_lib_valgrind_memcheck-amd64-linux.999.crash


** Attachment added: "Adwaita.zip"
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/473650/+attachment/5118673/+files/Adwaita.zip

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

Title:
  file-roller assert failure: *** glibc detected *** file-roller:
  free(): invalid pointer: 0x08b2da68 ***

Status in file-roller package in Ubuntu:
  New

Bug description:
  Binary package hint: file-roller

  trying to drag and drop file from File Roller 2.28.1 to Desktop after
  tried to drag & drop to smb: folder.

  ProblemType: Crash
  Architecture: i386
  AssertionMessage: *** glibc detected *** file-roller: free(): invalid 
pointer: 0x08b2da68 ***
  Date: Wed Nov  4 02:02:11 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  Package: file-roller 2.28.1-0ubuntu1
  ProcCmdline: file-roller /home/username/Desktop/Scooters.zip
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  Signal: 6
  SourcePackage: file-roller
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libc.so.6
   abort () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /lib/tls/i686/cmov/libc.so.6
  Title: file-roller assert failure: *** glibc detected *** file-roller: 
free(): invalid pointer: 0x08b2da68 ***
  Uname: Linux 2.6.31-14-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

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

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

[Desktop-packages] [Bug 1764563] Re: Xorg crashed with SIGABRT in OsAbort()

[Apport retracing service]

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

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 #1543192, 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/1764563/+attachment/5118642/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1543192
   Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

** 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 nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1764563

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in nvidia-graphics-drivers package in Ubuntu:
  New

Bug description:
  Nvidiasewttings

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CrashCounter: 1
  Date: Tue Apr 17 01:18:18 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 
1060 6GB] [1462:3283]
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=d0f89eb8-8c5c-4919-8ecb-bcca1091806a ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x55b106efcb50, argc=11, argv=0x7ffda5086778, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffda5086768) at ../csu/libc-start.c:310
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77N-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/29/2013:s

[Desktop-packages] [Bug 473650] Re: file-roller assert failure: *** glibc detected *** file-roller: free(): invalid pointer: 0x08b2da68 ***

[pqwoerituytrueiwoq]

I was able to get this issue in xubuntu 18.04 64bit Live (April 15 daily ISO)
Apport gave me this summary: file-roller assert failure: free(): invalid pointer

I made a .zip file of a system theme Adwaita
attempted to drag/drop the containing file to the desktop
It seems to be reproducible with a rate of about 1 in 3 or 1 in 2

** Attachment added: "valgrind.log.zip"
   
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/473650/+attachment/5118638/+files/valgrind.log.zip

** Changed in: file-roller (Ubuntu)
   Status: Invalid => New

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

Title:
  file-roller assert failure: *** glibc detected *** file-roller:
  free(): invalid pointer: 0x08b2da68 ***

Status in file-roller package in Ubuntu:
  New

Bug description:
  Binary package hint: file-roller

  trying to drag and drop file from File Roller 2.28.1 to Desktop after
  tried to drag & drop to smb: folder.

  ProblemType: Crash
  Architecture: i386
  AssertionMessage: *** glibc detected *** file-roller: free(): invalid 
pointer: 0x08b2da68 ***
  Date: Wed Nov  4 02:02:11 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/file-roller
  Package: file-roller 2.28.1-0ubuntu1
  ProcCmdline: file-roller /home/username/Desktop/Scooters.zip
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  Signal: 6
  SourcePackage: file-roller
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/tls/i686/cmov/libc.so.6
   abort () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /lib/tls/i686/cmov/libc.so.6
   ?? () from /lib/tls/i686/cmov/libc.so.6
  Title: file-roller assert failure: *** glibc detected *** file-roller: 
free(): invalid pointer: 0x08b2da68 ***
  Uname: Linux 2.6.31-14-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users

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

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

[Desktop-packages] [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

[Treviño]

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

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

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

** Changed in: mutter (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: mutter (Ubuntu Bionic)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from
  ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from
  function_call()

Status in Mutter:
  In Progress
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  In Progress
Status in mutter source package in Bionic:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854

  ---

  left virtual box to update win10 came back and got error message

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:37:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-18 (182 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7feb2ed42d94 :mov
0x18(%rax),%eax
   PC (0x7feb2ed42d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

[Treviño]

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

** This bug is no longer a duplicate of bug 1761131
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from logical_monitor_find_monitor() from 
meta_input_settings_find_monitor() from update_device_display()
** This bug has been marked a duplicate of bug 1703668
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  changing resolutions

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Oct 23 16:50:20 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f915fd97543 :   
jmpq   *0x88(%rax)
   PC (0x7f915fd97543) ok
   source "*0x88(%rax)" ok
   SP (0x7ffe40674f38) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_get_vendor () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1724102] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from logical_monitor_has_monitor()

[Treviño]

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

** This bug is no longer a duplicate of bug 1761131
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from logical_monitor_find_monitor() from 
meta_input_settings_find_monitor() from update_device_display()
** This bug has been marked a duplicate of bug 1703668
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from logical_monitor_has_monitor()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  17.10 Beta Fully Updated and re-installed in a fresh partition for
  best results.

  When screen went blank at time out, returning it from "its'
  hibernation state" screws up "workspace to Dock"

  So Alt+F2 and "r" brought it back but other things like terminal
  stopped working.

  Trying to help, Mark

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Oct 16 16:12:44 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fbbde5c8543 :   
jmpq   *0x88(%rax)
   PC (0x7fbbde5c8543) ok
   source "*0x88(%rax)" ok
   SP (0x7fff9bbdef08) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1761358] Re: /usr/bin/gnome-shell:11:meta_monitor_get_main_output:meta_monitor_get_vendor:logical_monitor_find_monitor:meta_input_settings_find_monitor:update_device_display

[Treviño]

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

** This bug is no longer a duplicate of bug 1761131
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from logical_monitor_find_monitor() from 
meta_input_settings_find_monitor() from update_device_display()
** This bug has been marked a duplicate of bug 1703668
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_monitor_get_main_output:meta_monitor_get_vendor:logical_monitor_find_monitor:meta_input_settings_find_monitor:update_device_display

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1761131] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from logical_monitor_find_monitor() from meta_input_settings_find

[Treviño]

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

** This bug has been marked a duplicate of bug 1703668
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from logical_monitor_find_monitor()
  from meta_input_settings_find_monitor() from update_device_display()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/dd87180eee24f496777a479c52715703596eb268

  ---

  happened on screensaver activation

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  4 11:13:09 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Software.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'firefox.desktop', 
'org.gnome.Terminal.desktop', 'jetbrains-phpstorm.desktop', 
'skypeforlinux.desktop', 'gnome-control-center.desktop', 
'org.gnome.gedit.desktop', 'dbeaver.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-03-13 (21 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fecaee5fe53 :   
jmpq   *0x88(%rax)
   PC (0x7fecaee5fe53) ok
   source "*0x88(%rax)" ok
   SP (0x7ffd4e598cd8) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1764548] [NEW] Update gtk+3.0 to 3.22.30 for bionic

[Jeremy Bicha]

Public bug reported:

New upstream bugfix release in the stable 3.22.x series.

gtk3 is part of the GNOME microrelease exception and we did an SRU with
it for Ubuntu 17.10.

https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
https://gitlab.gnome.org/GNOME/gtk/compare/3.22.30...3.22.29

Testing Done

Pending

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: bionic upgrade-software-version

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

Title:
  Update gtk+3.0 to 3.22.30 for bionic

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  New upstream bugfix release in the stable 3.22.x series.

  gtk3 is part of the GNOME microrelease exception and we did an SRU
  with it for Ubuntu 17.10.

  https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-22/NEWS
  https://gitlab.gnome.org/GNOME/gtk/commits/gtk-3-22
  https://gitlab.gnome.org/GNOME/gtk/compare/3.22.30...3.22.29

  Testing Done
  
  Pending

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

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

[Desktop-packages] [Bug 1724102] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from logical_monitor_has_monitor()

[Treviño]

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

** This bug has been marked a duplicate of bug 1761131
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from logical_monitor_find_monitor() from 
meta_input_settings_find_monitor() from update_device_display()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  from meta_monitor_get_vendor() from logical_monitor_has_monitor()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  17.10 Beta Fully Updated and re-installed in a fresh partition for
  best results.

  When screen went blank at time out, returning it from "its'
  hibernation state" screws up "workspace to Dock"

  So Alt+F2 and "r" brought it back but other things like terminal
  stopped working.

  Trying to help, Mark

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Oct 16 16:12:44 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fbbde5c8543 :   
jmpq   *0x88(%rax)
   PC (0x7fbbde5c8543) ok
   source "*0x88(%rax)" ok
   SP (0x7fff9bbdef08) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_get_vendor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

[Treviño]

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

** This bug is no longer a duplicate of bug 1724102
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from logical_monitor_has_monitor()
** This bug has been marked a duplicate of bug 1761131
   gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from 
meta_monitor_get_vendor() from logical_monitor_find_monitor() from 
meta_input_settings_find_monitor() from update_device_display()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  changing resolutions

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Oct 23 16:50:20 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f915fd97543 :   
jmpq   *0x88(%rax)
   PC (0x7f915fd97543) ok
   source "*0x88(%rax)" ok
   SP (0x7ffe40674f38) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_get_main_output () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_monitor_get_vendor () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1759483] Re: Inkscape doesn't render formulas with the Latex extension

[Bug Watch Updater]

** Changed in: pstoedit (Debian)
   Status: New => Fix Released

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

Title:
  Inkscape doesn't render formulas with the Latex extension

Status in inkscape package in Ubuntu:
  Confirmed
Status in pstoedit package in Debian:
  Fix Released

Bug description:
  Affects inkscape 0.92.3-1 on Bionic Beaver development version

  
  On hitting 'Extensions -> Render -> Latex' the usual interface to insert a 
latex formula appears, but on hitting 'Apply' stops with the following error:

  
  PostScript/PDF Interpreter finished. Return status 65280 executed command : 
/usr/bin/gs -I/home/till/.fonts -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY 
-dNOEPS "/tmp/psinVP0LD1"

  The interpreter seems to have failed, cannot proceed !

  Full output (including a ghostscript warning) given below:

   *** WARNING - the DELAYBIND command has been deprecated, and will be

     removed in the next version. For now you can restore

     the behaviour by using -dREALLYDEALYBIND but if you

     require continued use of this command you should
  contact

     the Ghostscript developers. Commercial customers of

     Artifex should email their support contact, free users

     are encouraged to talk to us on the #ghostscript IRC

     channel on irc.freenode.net.

  Unrecoverable error: undefined in DELAYBIND

  PostScript/PDF Interpreter finished. Return status 65280 executed
  command : /usr/bin/gs -I/home/till/.fonts -q -dDELAYBIND
  -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS "/tmp/psinVP0LD1"

  The interpreter seems to have failed, cannot proceed !

  Traceback (most recent call last):
    File "eqtexsvg.py", line 160, in 
  e.affect()
    File "/usr/share/inkscape/extensions/inkex.py", line 283, in affect
  self.effect()
    File "eqtexsvg.py", line 154, in effect
  svg_open(self, svg_file)
    File "eqtexsvg.py", line 81, in svg_open
  doc = inkex.etree.parse(filename)
    File "src/lxml/etree.pyx", line 3425, in lxml.etree.parse
    File "src/lxml/parser.pxi", line 1839, in lxml.etree._parseDocument
    File "src/lxml/parser.pxi", line 1865, in lxml.etree._parseDocumentFromURL
    File "src/lxml/parser.pxi", line 1769, in lxml.etree._parseDocFromFile
    File "src/lxml/parser.pxi", line 1162, in 
lxml.etree._BaseParser._parseDocFromFile
    File "src/lxml/parser.pxi", line 600, in 
lxml.etree._ParserContext._handleParseResultDoc
    File "src/lxml/parser.pxi", line 710, in lxml.etree._handleParseResult
    File "src/lxml/parser.pxi", line 639, in lxml.etree._raiseParseError
    File "/tmp/inkscape-cf8rEb/eq.svg", line 1
  lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1

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

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

[Desktop-packages] [Bug 1764539] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distin

[paqueagua]

Public bug reported:

es un informe de fallo interno, en ubuntu mate Versión 17.10 (Artful
Aardvark) de 64-bit. Toshiba Satellite-A215 AMD Athlon(tm) 64 X2 Dual-
Core Processor TK-57 × 2

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Sat Apr 14 21:07:45 2018
ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
InstallationDate: Installed on 2018-04-14 (2 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: intentando sobreescribir el compartido
  `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias
  del paquetes libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  es un informe de fallo interno, en ubuntu mate Versión 17.10 (Artful
  Aardvark) de 64-bit. Toshiba Satellite-A215 AMD Athlon(tm) 64 X2 Dual-
  Core Processor TK-57 × 2

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sat Apr 14 21:07:45 2018
  ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  InstallationDate: Installed on 2018-04-14 (2 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  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/1764539/+subscriptions

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

[Desktop-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

[Chris Darroch]

One further historical detail: when these machines were running 14.04.3
and we made the mistake of accepting the HardWare Enablement (HWE)
upgrade:

https://wiki.ubuntu.com/1404_HWE_EOL

which replaced the old fglrx driver with the radeon one, that's when we
first encountered this unable-to-unblank problem.

Fortunately, at that time we were able to roll back Xorg to 1.16 and
keep things sort-of working:

https://askubuntu.com/questions/815591/ubuntu-14-04-5-16-04-and-newer-on-amd-graphics
https://askubuntu.com/questions/676216/downgrade-xorg-server

When we performed a clean, full re-install with 16.04 we were hoping
this problem would be resolved, but as I've documented here it continues
to affect the systems.

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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

[Desktop-packages] [Bug 1764517] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

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 #1754924, 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/1764517/+attachment/5118417/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1764517

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 22:29:37 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-14 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: gnome-control-center bluetooth
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5616297fb311:mov0x90(%rbp),%rsi
   PC (0x5616297fb311) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1764523] [NEW] xorg

[Steve]

Public bug reported:

display problems

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-35-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Mon Apr 16 16:46:13 2018
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2018-02-17 (58 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  display problems

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Mon Apr 16 16:46:13 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (58 days ago)

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

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

[Desktop-packages] [Bug 1480387] Re: Clicking a date to go back or forward a month causes repeated jumps between two dates

[Bug Watch Updater]

** Changed in: gtk
   Status: Expired => Confirmed

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

Title:
  Clicking a date to go back or forward a month causes repeated jumps
  between two dates

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  I asked in #ubuntu-desktop and people couldn't reproduce this in vivid
  or trusty. It happened for me in the most recent wily iso.

  Open the indicator, click one of the greyed dates at the start or end
  of the month (sometimes requires more than one go). The active date
  starts to repeatedly jump between this date and another one. I ran
  with G_MESSAGES_DEBUG=all and when it's happening this is spammed (I
  clicked a date in 2015-05).

  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 31 17:09:43 2015
  InstallationDate: Installed on 2012-10-07 (1026 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2013-05-07 (815 days ago)

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

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

[Desktop-packages] [Bug 1326954] Re: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate

[Bug Watch Updater]

** Changed in: modemmanager
   Status: Incomplete => Confirmed

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Confirmed
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0'
 |  ports: 'cdc-wdm0 (mbim), wwan0 (net)'
-
Numbers  |   own : 'unknown'

[Desktop-packages] [Bug 1764515] [NEW] wifi crashes in ubuntu 16.04 lts xenial

[israel oluwole]

Public bug reported:


‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When I 
installed afresh, wifi was alright until recently, everyone time I connect, it 
pops the dialog that the wifi key is needed for authentication over and again, 
so it never gets connected to the internet.i have tried reinstalling network 
manager, service restart, boot and reboot, adding [device] wifi.scan 
nothing worked
What do I need? I barely use windows now 'Cause linux is just dope...‎

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: manager network

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  
  ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When 
I installed afresh, wifi was alright until recently, everyone time I connect, 
it pops the dialog that the wifi key is needed for authentication over and 
again, so it never gets connected to the internet.i have tried reinstalling 
network manager, service restart, boot and reboot, adding [device] 
wifi.scan nothing worked
  What do I need? I barely use windows now 'Cause linux is just dope...‎

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

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

[Desktop-packages] [Bug 1764518] [NEW] package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] failed to install/upgrade: problemas com dependências - a deixar por configurar

[Antonio Marues Pereira]

Public bug reported:

On system startup

ProblemType: Package
DistroRelease: elementary 0.4.1
Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  antonio1431 F pulseaudio
Date: Mon Apr 16 00:50:52 2018
ErrorMessage: problemas com dependências - a deixar por configurar
InstallationDate: Installed on 2018-04-15 (0 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: pulseaudio
Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] 
failed to install/upgrade: problemas com dependências - a deixar por configurar
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/15/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V5.10
dmi.board.name: Satellite U300-130
dmi.board.vendor: TOSHIBA
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300-130:pvrPSU30E-03D013PT:rvnTOSHIBA:rnSatelliteU300-130:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: Satellite U300-130
dmi.product.version: PSU30E-03D013PT
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-package loki third-party-packages

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

Title:
  package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
  failed to install/upgrade: problemas com dependências - a deixar por
  configurar

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On system startup

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antonio1431 F pulseaudio
  Date: Mon Apr 16 00:50:52 2018
  ErrorMessage: problemas com dependências - a deixar por configurar
  InstallationDate: Installed on 2018-04-15 (0 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: pulseaudio
  Title: package pulseaudio-module-bluetooth 1:8.0-0ubuntu3.8 [origin: Ubuntu] 
failed to install/upgrade: problemas com dependências - a deixar por configurar
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V5.10
  dmi.board.name: Satellite U300-130
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV5.10:bd01/15/2009:svnTOSHIBA:pnSatelliteU300-130:pvrPSU30E-03D013PT:rvnTOSHIBA:rnSatelliteU300-130:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite U300-130
  dmi.product.version: PSU30E-03D013PT
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_c

[Ubuntu Foundations Team Bug Bot]

The attachment "gtk3.debdiff" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 1763978] Re: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

[Ubuntu Foundations Team Bug Bot]

The attachment "Modified service file" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  nvidia-prime-boot.service: Main process exited, code=exited,
  status=2/INVALIDARGUMENT

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Since this week (i believe April 9th) Nvidia-prime isn't working for
  me.

  Running:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  Nvidia-prime version:

  Nvidia-prime version:
Installed: 0.8.7
Candidate: 0.8.7
Version table:
   *** 0.8.7 500

  Error code:
  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main 
process exited, code=exited, status=2/INVALIDARGUMENT

  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service:
  Failed with result 'exit-code'.

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

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

[Desktop-packages] [Bug 1764510] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

[Apport retracing service]

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

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 #1748450, 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/1764510/+attachment/5118374/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr 16 21:38:56 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop

[Luke Williams]

It could be a backlight issue. I tried with the latest daily-build
(April 16, 2018) and I boot up with the nouveau.modeset=0 kernel param
and it shows the splash screen, and then I hear the login sound, and if
I turn off the lights in my office and look closely, I can see the
display, but it looks like the backlight for the screen is not lit. I
tried adjusting the brightness using the FN+F7/F8 (Which adjust
brightness) and they don't work (They don't work on any other
distribution/Release as well. Only things that work are volume control
and Projector options).

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

Title:
  nouveau/nvidia drivers do not work with display in Bionic on Asus
  GL703VD Laptop

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with
  NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not
  using 3D) and the installer does not display. I have tried
  nouveau.modeset=0 and nomodeset boot options to no avail. I was able
  to finally install Bionic by hooking up the laptop to a projector, but
  after a reboot, the laptop display still did not work and I had to set
  the account to autologin otherwise I could not login to the laptop. I
  then install openssh-server so that I could ssh into the laptop and I
  installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which
  installed, but still no local display.

  In Artful, I could install with the nouveau.modeset=0 and then
  installing the proprietary NVIDIA drivers and everything (except
  touchpad, LP: 1738263) worked.

  lspci shows the graphics card and NVIDIA card, and lsmod does show
  that before NVIDIA drivers install, it is using nouveau, asus_wmi, and
  i915 for graphcis, and once NVIDIA drivers are install, lsmod only
  shows i915 and asus_wmi for graphics while nvidia is used for gpu and
  3D, but still no display on the laptop.

  lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline
  lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline
  lspci.txt shows the detected hardware
  lshw.txt shows the hardware in the laptop.

  Please let me know if you need any other information.

  Thanks,
  Luke

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

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

[Desktop-packages] [Bug 1750253] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear()

[Launchpad Bug Tracker]

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

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

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

Title:
  ibus-daemon crashed with SIGABRT in g_mutex_clear()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  With sddm Displaymanger. gdm3 goes automatic to Ubuntu Wayland. No
  change possible.

  No Mouse click possibele but mouse moved. Can't change the
  Displaymanger.

  SDDM Change possible. Ubuntu or Gnome not started.

  Scroll Lock flashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Feb 18 15:20:13 2018
  ExecutablePath: /usr/bin/ibus-daemon
  ProcCmdline: ibus-daemon --xim --panel disable
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   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
  Title: ibus-daemon crashed with SIGABRT in g_mutex_clear()
  UpgradeStatus: Upgraded to bionic on 2017-12-04 (76 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1763662] Re: H264 missing from WebRTC (regression)

[Launchpad Bug Tracker]

** Branch linked: lp:~chromium-team/chromium-browser/bionic-beta

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

Title:
  H264 missing from WebRTC (regression)

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  H264 is missing from WebRTC in Chromium 65.0.3325.181.
  This is a regression. It worked in Chromium 64.0.3282.167.
  According to the webrtc team it might be because of a missing flag [1].

  Steps to reproduce:
  1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser 
chromium-codecs-ffmpeg-extra
  2. open a tab with chrome://webrtc-internals
  3. Create a room in https://appr.tc and join the room.
  3. Check the SDP offer in webrtc-internals. Select the 
https://appr.tc/r/ tab and click on the createOfferOnSuccess event.

  We should have H264 in the SDP offer but it's missing:
  a=rtpmap:100 H264/9

  [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096

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

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

[Desktop-packages] [Bug 1763662] Re: H264 missing from WebRTC (regression)

[Olivier Tilloy]

chromium-browser 66.0.3359.106-0ubuntu1 currently building in
https://launchpad.net/~chromium-team/+archive/ubuntu/beta/+packages with
rtc_use_h264=true. Once built, let's see if this fixes the problem.

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  H264 missing from WebRTC (regression)

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  H264 is missing from WebRTC in Chromium 65.0.3325.181.
  This is a regression. It worked in Chromium 64.0.3282.167.
  According to the webrtc team it might be because of a missing flag [1].

  Steps to reproduce:
  1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser 
chromium-codecs-ffmpeg-extra
  2. open a tab with chrome://webrtc-internals
  3. Create a room in https://appr.tc and join the room.
  3. Check the SDP offer in webrtc-internals. Select the 
https://appr.tc/r/ tab and click on the createOfferOnSuccess event.

  We should have H264 in the SDP offer but it's missing:
  a=rtpmap:100 H264/9

  [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096

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

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

[Desktop-packages] [Bug 472450] Re: gnome-keyring crashes for no apparent reason

[Niels Erik Jensen]

?

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

Title:
  gnome-keyring crashes for no apparent reason

Status in gnome-keyring package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-keyring

  doing nothing related to the keyring. entering keyring password at
  startup succeeded.

  applications in use: evolution, firefox, tasque, empathy

  possibly unrelated observations:
  a jabber account used in empathy regularly goes offline (about every 11 
minutes) - reason unknown.

  might be related to: #405667

  ProblemType: Crash
  Architecture: i386
  AssertionMessage: ERROR:gck-file-tracker.c:97:update_file: assertion failed: 
(old_mtime)
  CheckboxSubmission: 0b44424daa2eeb8fdbb5cd71b44a076d
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  CrashCounter: 1
  Date: Tue Nov  3 10:44:48 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-keyring-daemon
  Package: gnome-keyring 2.28.1-0ubuntu1
  ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login
  ProcEnviron: LANG=de_DE.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
  Signal: 6
  SourcePackage: gnome-keyring
  StacktraceTop:
   __kernel_vsyscall ()
   *__GI_raise (sig=6)
   *__GI_abort () at abort.c:92
   IA__g_assertion_message (domain=0x0, 
   IA__g_assertion_message_expr (domain=0x0,
  Title: gnome-keyring-daemon assert failure: 
ERROR:gck-file-tracker.c:97:update_file: assertion failed: (old_mtime)
  Uname: Linux 2.6.31-14-generic-pae i686
  UserGroups: adm admin audio cdrom dialout dip floppy libvirtd lpadmin netdev 
plugdev powerdev sambashare scanner users video www-data

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

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

[Desktop-packages] [Bug 1763978] Re: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

[Giraffe]

@op3ntrap 
Thanks for responding, since this problem also affects you would you mind 
clicking "this bug also affects me (top left). This will give the bug a higher 
priority.

Thanks

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

Title:
  nvidia-prime-boot.service: Main process exited, code=exited,
  status=2/INVALIDARGUMENT

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Since this week (i believe April 9th) Nvidia-prime isn't working for
  me.

  Running:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  Nvidia-prime version:

  Nvidia-prime version:
Installed: 0.8.7
Candidate: 0.8.7
Version table:
   *** 0.8.7 500

  Error code:
  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main 
process exited, code=exited, status=2/INVALIDARGUMENT

  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service:
  Failed with result 'exit-code'.

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

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

[Desktop-packages] [Bug 1764494] Re: X fails to start upon boot

[yannek]

** Attachment added: "X after the manual start"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764494/+attachment/5118364/+files/Xorg.0.log.second_time

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

Title:
  X fails to start upon boot

Status in xorg package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy xorg
  xorg:
Installed:   1:7.7+19ubuntu6

  
  The system is an upgrade from 17.10 to 18.04. The X-server fails to start 
initially, on each boot. After switching to tty2 I can start the login daemon 
via

  $ systemctl start sddm

  and X and sddm work as expected. (i.e. X starts, the login daemon
  starts, I can login to an X session)

  The system in question is a Lenovo X220 Thinkpad with integrated
  graphics. As lspci puts it:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  This behaviour started as a result of the upgrade.

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

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

[Desktop-packages] [Bug 1764494] [NEW] X fails to start upon boot

[yannek]

Public bug reported:

$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

$ apt-cache policy xorg
xorg:
  Installed:   1:7.7+19ubuntu6


The system is an upgrade from 17.10 to 18.04. The X-server fails to start 
initially, on each boot. After switching to tty2 I can start the login daemon 
via

$ systemctl start sddm

and X and sddm work as expected. (i.e. X starts, the login daemon
starts, I can login to an X session)

The system in question is a Lenovo X220 Thinkpad with integrated
graphics. As lspci puts it:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)

This behaviour started as a result of the upgrade.

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

** Attachment added: "Xorg.0.log.failed"
   
https://bugs.launchpad.net/bugs/1764494/+attachment/5118363/+files/Xorg.0.log.failed

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

Title:
  X fails to start upon boot

Status in xorg package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu Bionic Beaver (development branch)
  Release:18.04

  $ apt-cache policy xorg
  xorg:
Installed:   1:7.7+19ubuntu6

  
  The system is an upgrade from 17.10 to 18.04. The X-server fails to start 
initially, on each boot. After switching to tty2 I can start the login daemon 
via

  $ systemctl start sddm

  and X and sddm work as expected. (i.e. X starts, the login daemon
  starts, I can login to an X session)

  The system in question is a Lenovo X220 Thinkpad with integrated
  graphics. As lspci puts it:

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  This behaviour started as a result of the upgrade.

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

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

[Desktop-packages] [Bug 1763978] Re: nvidia-prime-boot.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

[op3ntrap]

Hi,
I too had the same problem and after some digging I found out that the file 
from which the service runs is:
/etc/systemd/system/display-manager.service.wants/nvidia-prime-boot.service

the service used vgaswitcheroo module to switch off the dGPU. However I
think most of use i915 or modesetting driver which doesn't give the
"vgaswitcheroo" module.

I changed my file to the attached copy.

Basically instead of using vgaswitcheroo, you can use 
   "echo 'auto' > '/sys/bus/pci/devices/:01:00.0/power/control'" to switch 
off your dGPU.


** Attachment added: "Modified service file"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1763978/+attachment/5118361/+files/nvidia-prime-boot.service

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

Title:
  nvidia-prime-boot.service: Main process exited, code=exited,
  status=2/INVALIDARGUMENT

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Since this week (i believe April 9th) Nvidia-prime isn't working for
  me.

  Running:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  Nvidia-prime version:

  Nvidia-prime version:
Installed: 0.8.7
Candidate: 0.8.7
Version table:
   *** 0.8.7 500

  Error code:
  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service: Main 
process exited, code=exited, status=2/INVALIDARGUMENT

  apr 14 11:56:33 Precision-7510 systemd[1]: nvidia-prime-boot.service:
  Failed with result 'exit-code'.

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

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

[Desktop-packages] [Bug 1764486] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Проверочное утверждение «hash

[Apport retracing service]

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

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 #1764376, 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/1764486/+attachment/5118348/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Проверочное утверждение «hash_table->live_entries == 0» не выполнено.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Проверочное 
утверждение «hash_table->live_entries == 0» не выполнено.
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 21:25:36 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['restart-entry@atomant', 
'axemenu@wheezy', 'dash-to-d...@micxgx.gmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   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 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell-extension-prefs 
extension:///dash-to-d...@micxgx.gmail.com
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff8e8138622 , assertion=assertion@entry=0x7ff8f0687d05 
"hash_table->live_entries == 0", file=file@entry=0x7ff8f0687ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7ff8f0687e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7ff8f0687d05 "hash_table->live_entries == 
0", file=0x7ff8f0687ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7ff8f0687e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Проверочное утверждение «hash_table->live_entries == 
0» не выполнено.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1764482] Re: unity-control-center crashed with signal 5 in g_settings_bind_with_mapping()

[Apport retracing service]

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

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 #1756233, 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/1764482/+attachment/5118325/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1764482

Title:
  unity-control-center crashed with signal 5 in
  g_settings_bind_with_mapping()

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

Bug description:
  when updating to Ubuntu 18.01

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr 16 14:12:54 2018
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2018-04-05 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: unity-control-center info
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  Signal: 5
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_bind_with_mapping () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libscreen-sharing.so
   g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with signal 5 in 
g_settings_bind_with_mapping()
  UpgradeStatus: Upgraded to bionic on 2018-04-16 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1740618] Re: Remove gksu from Ubuntu

[Jeremy Bicha]

** Description changed:

  Debian has removed gksu. I recommend that we remove gksu and libgksu for
  Ubuntu 18.04 LTS also.
  
  It has recommended that developers use PolicyKit to only use elevated
  privileges for the specific actions where it is needed.
  
  It is recommended that users use the gvfs admin backend available in
  Ubuntu 17.10 and 18.04 LTS. You can do this with the admin:// prefix.
  For instance, instead of running gksu gedit or gksu nautilus to edit say
  /etc/default/grub, navigate to admin:///etc/default/ and open the grub
  file.
  
  Ubuntu 17.10's default session (a themed GNOME on Wayland) does not
  support gksu. Ubuntu 18.04 switched back to using X instead of Wayland
  as default but it is expected that Wayland will once again be the
  default in 18.10.
  
  $ reverse-depends src:gksu
  Reverse-Recommends
  ==
  * macchanger-gtk(for gksu)
  * wicd-gtk  (for gksu)
- * zenmap(for gksu)
  
  Reverse-Depends
  ===
  * edubuntu-netboot  (for gksu)
  * peony-gksu(for gksu)
  * umit  (for gksu)
  
  List of packages to remove and commentary
  -
  * macchanger-gtk: Removed from Debian Testing in January 2017 for a security 
bug
  * libui-dialog-perl: no other rdepends but macchanger-gtk. This is the 
security bug that got macchanger-gtk removed from Testing. Debian bug 496448
  * edubuntu-netboot: never in Debian. Edubuntu is "on hold" since 2016.
  * umit: never in Debian, appears unmaintained upstream since at least 2014 
(maybe 2012?)
  * gksu
  * libgksu
  
  Blocker bug
  ---
  peony-gksu (source peony-extensions) was accepted into Ubuntu in April 2018. 
See LP: #1764201
  
  References
  --
  https://jeremy.bicha.net/2018/03/21/gksu-is-dead/
  https://bugs.debian.org/892768

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

Title:
  Remove gksu from Ubuntu

Status in edubuntu-netboot package in Ubuntu:
  New
Status in gksu package in Ubuntu:
  New
Status in libgksu package in Ubuntu:
  New
Status in libui-dialog-perl package in Ubuntu:
  New
Status in macchanger-gtk package in Ubuntu:
  New
Status in network-config package in Ubuntu:
  Fix Released
Status in sbackup package in Ubuntu:
  Fix Released
Status in umit package in Ubuntu:
  New

Bug description:
  Debian has removed gksu. I recommend that we remove gksu and libgksu
  for Ubuntu 18.04 LTS also.

  It has recommended that developers use PolicyKit to only use elevated
  privileges for the specific actions where it is needed.

  It is recommended that users use the gvfs admin backend available in
  Ubuntu 17.10 and 18.04 LTS. You can do this with the admin:// prefix.
  For instance, instead of running gksu gedit or gksu nautilus to edit
  say /etc/default/grub, navigate to admin:///etc/default/ and open the
  grub file.

  Ubuntu 17.10's default session (a themed GNOME on Wayland) does not
  support gksu. Ubuntu 18.04 switched back to using X instead of Wayland
  as default but it is expected that Wayland will once again be the
  default in 18.10.

  $ reverse-depends src:gksu
  Reverse-Recommends
  ==
  * macchanger-gtk(for gksu)
  * wicd-gtk  (for gksu)

  Reverse-Depends
  ===
  * edubuntu-netboot  (for gksu)
  * peony-gksu(for gksu)
  * umit  (for gksu)

  List of packages to remove and commentary
  -
  * macchanger-gtk: Removed from Debian Testing in January 2017 for a security 
bug
  * libui-dialog-perl: no other rdepends but macchanger-gtk. This is the 
security bug that got macchanger-gtk removed from Testing. Debian bug 496448
  * edubuntu-netboot: never in Debian. Edubuntu is "on hold" since 2016.
  * umit: never in Debian, appears unmaintained upstream since at least 2014 
(maybe 2012?)
  * gksu
  * libgksu

  Blocker bug
  ---
  peony-gksu (source peony-extensions) was accepted into Ubuntu in April 2018. 
See LP: #1764201

  References
  --
  https://jeremy.bicha.net/2018/03/21/gksu-is-dead/
  https://bugs.debian.org/892768

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

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

[Desktop-packages] [Bug 1754422] Re: [MIR] volume-key

[Iain Lane]

volume-key_0.3.9-4 is uploaded to unstable. Although I forgot to say it
in the changelog, it runs the tests fatally.

I'd still like some confirmation that my patch is OK, but assuming it is
- it could be synced.

cyphermox - any chance you could review it pre-upload and approve the
MIR on the basis that it is this version that is promoted?

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

Title:
  [MIR] volume-key

Status in volume-key package in Ubuntu:
  In Progress
Status in volume-key source package in Bionic:
  In Progress

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  GNOME Disks uses udisks2. Debian's udisks2 recommends libblockdev-crypto2 
which depends on libvolume-key1.

  The package description for libblockdev-crypto2 is:
   "The libblockdev library plugin (and in the same time a standalone library)
    providing the functionality related to encrypted devices (LUKS)."

  This sounds like a very useful feature for Ubuntu since we offer full
  disk encryption using LUKS.

  Security
  
  No known security issues. Presumably should get a Security review.

  https://security-tracker.debian.org/tracker/source-package/volume-key
  https://launchpad.net/ubuntu/+source/volume-key/+cve

  Quality assurance
  =
  - Please subscribe Ubuntu Desktop bugs (although the Desktop Team thinks that 
Foundations should be responsible for udisks and friends)

  https://bugs.launchpad.net/ubuntu/+source/volume-key
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=volume-key
  https://pagure.io/volume_key/issues

  dh_auto_test is run but tests are failing and ignored.

  No autopkgtests

  Dependencies
  
  No universe dependencies

  Standards compliance
  
  4.1.3, debhelper compat 11, simple dh7 style rules

  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.

  https://salsa.debian.org/utopia-team/volume-key

  upstream:
  https://pagure.io/volume_key

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

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

[Michael Steenbeek]

I can't seem to edit my previous post, but after running ldd on the .so
file I noticed that libusb-0.1-4 was missing. Installing that package
(on top of the workaround in #80) made the scanner work for me.

-- 
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 1547135] Re: Support purchasing software

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.28.1-0ubuntu2

---
gnome-software (3.28.1-0ubuntu2) bionic; urgency=medium

  * debian/patches/0017-snap-Use-default-icon-if-none-provided.patch:
- Fix snaps without icons not showing (LP: #1763736)
  * debian/patches/0018-snap-Make-snaps-purchasable.patch:
- Support purchasable snaps (LP: #1547135)
  * debian/patches/0001-snap-Scale-embedded-snap-icons-to-64x64.patch:
  * debian/patches/0001-snap-Only-load-icons-once.patch:
- Fix snap icon sizes and stop duplicate loading

 -- Robert Ancell   Mon, 16 Apr 2018
15:32:27 +1200

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

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

Title:
  Support purchasing software

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

Bug description:
  Eventually people will be able to buy software with money.  This means
  that the prices will need to be displayed in the UI.

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

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

[Desktop-packages] [Bug 1763662] Re: H264 missing from WebRTC (regression)

[Olivier Tilloy]

https://webrtc.googlesource.com/src.git/+/d3070f43b19f503246be4ebad425d87568a71ce0
appears to be the cause of the regression. It was later reverted
(https://webrtc.googlesource.com/src.git/+/3bb1194fff251bb63062aa1a807ee7107779f36b),
but I guess that wasn't backported to branches 65 and 66.

Forcing rtc_use_h264 to true in the build flags should do the trick.

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  H264 missing from WebRTC (regression)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  H264 is missing from WebRTC in Chromium 65.0.3325.181.
  This is a regression. It worked in Chromium 64.0.3282.167.
  According to the webrtc team it might be because of a missing flag [1].

  Steps to reproduce:
  1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser 
chromium-codecs-ffmpeg-extra
  2. open a tab with chrome://webrtc-internals
  3. Create a room in https://appr.tc and join the room.
  3. Check the SDP offer in webrtc-internals. Select the 
https://appr.tc/r/ tab and click on the createOfferOnSuccess event.

  We should have H264 in the SDP offer but it's missing:
  a=rtpmap:100 H264/9

  [1] https://bugs.chromium.org/p/webrtc/issues/detail?id=9096

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

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

[Desktop-packages] [Bug 1763736] Re: communitheme snap not present in gnome software on bionic, but it is on 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.28.1-0ubuntu2

---
gnome-software (3.28.1-0ubuntu2) bionic; urgency=medium

  * debian/patches/0017-snap-Use-default-icon-if-none-provided.patch:
- Fix snaps without icons not showing (LP: #1763736)
  * debian/patches/0018-snap-Make-snaps-purchasable.patch:
- Support purchasable snaps (LP: #1547135)
  * debian/patches/0001-snap-Scale-embedded-snap-icons-to-64x64.patch:
  * debian/patches/0001-snap-Only-load-icons-once.patch:
- Fix snap icon sizes and stop duplicate loading

 -- Robert Ancell   Mon, 16 Apr 2018
15:32:27 +1200

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

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

Title:
  communitheme snap not present in gnome software on bionic, but it is
  on 16.04

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  In ubuntu 18.04, communitheme is not present in the logitheque. We can't find 
it in the available applications.
  snap search can find it

  on the other side, we can notice its presence in the logitheque of
  ubuntu 16.04

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

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

[Michael Steenbeek]

I have a Samsung M2070W. I have tried the workaround in #80, but
unfortunately it did not work for me, even after restarting.

-- 
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 1763829] Re: [snap] chromium won't start after logging in to google account

[Olivier Tilloy]

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  [snap] chromium won't start after logging in to google account

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  (issue initially reported on the forum: https://forum.snapcraft.io/t
  /call-for-testing-chromium-65-0-3325-146/4390/20)

  $ snap info core chromium | egrep "name|installed"
  name:  core
  installed:   16-2.32.3(4407) 90MB core
  name:  chromium
  installed:   65.0.3325.181 (274)  144MB -

  Steps to reproduce:
  1) Install the chromium snap: snap install chromium
  2) Launch it: /snap/bin/chromium
  3) Click the account button on the right side of the tabs bar, and log into a 
google account
  4) Close the browser window
  5) Launch chromium again

  Expected result: chromium launches, a window is shown and the user is
  logged into their google account

  Current result: the executable seemingly hangs, no window is shown

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

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

[Desktop-packages] [Bug 1764161] Re: Translation template for ibus is missing some strings

[Gunnar Hjalmarsson]

Thanks for your report!

Right, the LP template was almost three years old. I created and
uploaded a new template for now. That ought to help a bit. But it
resulted in 64 untranslated strings, which indicates that the upstream
PO files were created with an old template.

3 days before deadline. Some translators will hate me...

Looking at the build log, dh_translations isn't mentioned and -
consequently - the latest translation tarball is without a POT file.

@Sebastien: What determines whether dh_translations should be run when
building?

** Changed in: ubuntu-translations
   Importance: Undecided => Medium

** Changed in: ubuntu-translations
   Status: New => In Progress

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Translation template for ibus is missing some strings

Status in Ubuntu Translations:
  In Progress
Status in ibus package in Ubuntu:
  New

Bug description:
  There are some strings missing in the translation template for ibus,
  at least in my (Czech) language. For example these strings:

  #: ../setup/setup.ui.h:50
  msgid "Emoji choice:"
  msgstr "Výběr emoji:"

  #: ../setup/setup.ui.h:51
  msgid "Set a font of emoji candidates on the emoji dialog"
  msgstr "Nastavit písmo kandidátů emoji v dialogu emoji"

  #: ../setup/setup.ui.h:52
  msgid "Emoji font:"
  msgstr "Font emoji:"

  #: ../setup/setup.ui.h:53
  msgid "Set a language of emoji annotations on the emoji dialog"
  msgstr "Nastavit jazyk anotací emoji v dialogu emoji"

  #: ../setup/setup.ui.h:54
  msgid "Emoji annotation language:"
  msgstr "Jazyk anotací emoji:"

  They are fully translated upstream, but are missing on Launchpad and
  are untranslated in Ubuntu 18.04 (see the attached screenshot).

  But there are more strings missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1764161/+subscriptions

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

[Desktop-packages] [Bug 1757058] Re: gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R

[Ubuntu Foundations Team Bug Bot]

The attachment "gnome-calendar.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather
  → g_closure_invoke → signal_emit_unlocked_R

Status in gnome-calendar package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2

[Mario Vukelic]

** Description changed:

  Report created by following 
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_the_Touchpad_features_work.2C_but_does_not_work_correctly_and_as_expected
  Let me know if anything is wrong or if I can give more info
  
  Touchpad worked perfectly in Ubuntu 17.10 when using one and two fingers
  clicks, two finger scrolling, and tapping. (I don't know if multitouch
  worked, but IIRC it did in the past with Unity)
  
  After upgrading to Bionic Beaver it frequently becomes unresponsive,
- during which I can neither move the mouse cursor or scroll. There seem
- to be two slightly different kinds of unresponsiveness, one provoked by
- one-finger movement, the other provoked by two-finger scrolling:
+ during which I can neither move the mouse cursor or scroll. I can repro
+ it most of the time, even directly after rebooting, but not in 100% of
+ tries. Sometimes, without anything obvious happening (e.g., no reboot or
+ logging out), the problem may not occur for an hour or two and I cannot
+ repro it on purpose. Then after a while it is back. Checking the CPU
+ when it occurs does not show high load. Also repro on gdm screen and
+ logging in as a different user account and with a an alternative non-
+ gnome-shell session.
+ 
+ There seem to be two slightly different kinds of unresponsiveness, one
+ provoked by one-finger movement, the other provoked by two-finger
+ scrolling:
  
  One-finger movement:
  
  Triggered by:
  Giving continuous input to touchpad for a second or two. E.g., move one 
finger in a small circle. After 1-3 circles the touchpad becomes unresponsive. 
(Making long straight left-right movements also tends to trigger it, but less 
clearly)
  
  Results in:
  Stays unresponsive until the finger is lifted from and lowered on touchpad 
again. However, lifting+lowering only restores responsiveness briefly, then it 
stops again. Waiting a few seconds makes it work again, like for two-finger 
scrolling.
  
  Two-finger scrolling:
  
  Scroll up and down a few times. Does not seem to matter what the
  application is.
  
  Results in:
  Scrolling stops after a few movements. Lifting and re-lowering both fingers 
does not seem to make it go again, but it works after waiting a few seconds. 
However scrolling is jumpy most of the time and rarely as smooth as it was in 
17.10
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-synaptics (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog:
   Gave up waiting for suspend/resume device
   /dev/sda4: clean, 1015626/39428096 files, 55279634/157701376 blocks
   Gave up waiting for suspend/resume device
   /dev/sda4: clean, 1026169/39428096 files, 54683366/157701376 blocks
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 12:07:31 2018
  DistUpgraded: 2018-04-08 10:29:35,542 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-15 (2037 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: Apple Inc. MacBookPro5,4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=1f4ef214-a70d-44ac-8515-2d4234f32e38 ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: Upgraded to bionic on 2018-04-08 (7 days ago)
  dmi.bios.date: 06/15/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP53.88Z.00AC.B03.0906151647
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22587A1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro5,4
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22587A1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,4:pvr1.0:rvnAppleInc.:rnMac-F22587A1:rvrMacBookPro5,4:cvnAppleInc.:ct10:cvrMac-F22587A1:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro5,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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: Sun Apr 15 

[Desktop-packages] [Bug 1757280] Re: Night Light only works on one Monitor

[Digital Spinner]

Yes the issue is annoying.. To have the second screen Night Light
enabled, change the default screen to the other screen and back to first
one - the second screen should have Night Light enabled. The same thing
you have to do when disabling Night Light. - at least it works for me
like this.

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

Title:
  Night Light only works on one Monitor

Status in gnome-control-center:
  Expired
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  
  Hi

  If I activate the Night Light mode with an external monitor connected,
  the mode is only on the external monitor activated.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Mar 20 23:12:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2018-03-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319)
  MachineType: LENOVO 20HF0016MZ
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET45W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF0016MZ
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF0016MZ
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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

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

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

[Desktop-packages] [Bug 1755885] Re: Night Light won't turn on after start on display #1

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Night Light won't turn on after start on display #1

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have two displays and have Night Light mode enabled with Sunset to
  Sunrise setting (tried to change it into Manual, but this didn't make
  any difference).

  It was perfectly OK some time before, but now only display #2 is
  started with the Night Light mode switched on.

  I can work around it: go to the Display Settings, try to switch into
  non-native mode for Display #1 and it switched into it with Night
  Light enabled. Then choose not to keep settings and it returns into
  native resolution with Night Light on.

  Not all changes help to switch the mode on though. For instance,
  mirroring screen doesn't switch it on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.42  Sat Mar  3 04:10:22 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar 14 21:31:45 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-10-generic, x86_64: installed
   nvidia, 390.42, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e5]
  InstallationDate: Installed on 2018-02-05 (37 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=68661197-00b4-4652-9c8f-2ef606012d2d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-K/USB 3.1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd03/17/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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

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

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

[Desktop-packages] [Bug 1754186] Re: Night Light only affects a single monitor now

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Night Light only affects a single monitor now

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The Display settings have a "Night Light" option which allows reducing blue 
light at night.
  In Ubuntu 17.10, this worked great, and the setting took effect on all 3 of 
my monitors.
  In Bionic, only the 1st monitor is affected; the other 2 remain at the 
default color temperature.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Mar  7 17:51:02 2018
  DistUpgraded: 2018-03-07 12:52:16,474 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Double D HD 7970 Black Edition [1682:3211]
  InstallationDate: Installed on 2014-08-21 (1294 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=98fea0b5-8fa6-4625-bae5-b85a70783a13 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-07 (0 days ago)
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1208
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1208:bd04/18/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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: Sat Oct  7 12:18:20 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1761995] Re: Error Formatting luks device

[Jesse]

I have an installation of Xenial (16.04 LTS) which doesn't have this bug
(gnome-disk-utility version 3.18). After upgrading to 18.04 (gnome disk
version 3.28) I start seeing this bug. It's not a showstopper as I know
my way through the command line, but still, I spend 60% of my time on
macOS and having a common task such as LUKS + ext4 done through a
graphical interface is much appreciated

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

Title:
  Error Formatting luks device

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in meta-gnome3 package in Ubuntu:
  Confirmed

Bug description:
  Application Gnome Disks

  When trying to format an encrypted drive I get this error:

  Error formatting volume

  Error creating the luks device:The function
  'bd_crypto_luks_format_blob' called, but not implemented! (udisks-
  error-quark,0)

  1. Description:   Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. GNOME Disks 3.28.0-1ubuntu1

  3. LUKS formatting disk should work

  4. error message when opting for password protect volume (LUKS)
  utilizing format volume

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 09:46:19 2018
  InstallationDate: Installed on 2018-03-12 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1763829] Re: [snap] chromium won't start after logging in to google account

[Olivier Tilloy]

Unfortunately bug #1763641 is blocking publication in the store, I'm
working with store people to try and resolve this.

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

Title:
  [snap] chromium won't start after logging in to google account

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (issue initially reported on the forum: https://forum.snapcraft.io/t
  /call-for-testing-chromium-65-0-3325-146/4390/20)

  $ snap info core chromium | egrep "name|installed"
  name:  core
  installed:   16-2.32.3(4407) 90MB core
  name:  chromium
  installed:   65.0.3325.181 (274)  144MB -

  Steps to reproduce:
  1) Install the chromium snap: snap install chromium
  2) Launch it: /snap/bin/chromium
  3) Click the account button on the right side of the tabs bar, and log into a 
google account
  4) Close the browser window
  5) Launch chromium again

  Expected result: chromium launches, a window is shown and the user is
  logged into their google account

  Current result: the executable seemingly hangs, no window is shown

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

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

[Desktop-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_c

[Andrea Azzarone]

Plese find attached a debdiff with the fix cherry-fixed from upstream.

** Patch added: "gtk3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1759468/+attachment/5118260/+files/gtk3.debdiff

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 1761995] Re: Error Formatting luks device

[Launchpad Bug Tracker]

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

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

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

Title:
  Error Formatting luks device

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in meta-gnome3 package in Ubuntu:
  Confirmed

Bug description:
  Application Gnome Disks

  When trying to format an encrypted drive I get this error:

  Error formatting volume

  Error creating the luks device:The function
  'bd_crypto_luks_format_blob' called, but not implemented! (udisks-
  error-quark,0)

  1. Description:   Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. GNOME Disks 3.28.0-1ubuntu1

  3. LUKS formatting disk should work

  4. error message when opting for password protect volume (LUKS)
  utilizing format volume

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 09:46:19 2018
  InstallationDate: Installed on 2018-03-12 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761995] Re: Error Formatting luks device

[Jesse]

** Also affects: gnome-disk-utility (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Error Formatting luks device

Status in gnome-disk-utility package in Ubuntu:
  Confirmed
Status in meta-gnome3 package in Ubuntu:
  Confirmed

Bug description:
  Application Gnome Disks

  When trying to format an encrypted drive I get this error:

  Error formatting volume

  Error creating the luks device:The function
  'bd_crypto_luks_format_blob' called, but not implemented! (udisks-
  error-quark,0)

  1. Description:   Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. GNOME Disks 3.28.0-1ubuntu1

  3. LUKS formatting disk should work

  4. error message when opting for password protect volume (LUKS)
  utilizing format volume

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 09:46:19 2018
  InstallationDate: Installed on 2018-03-12 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: meta-gnome3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754422] Re: [MIR] volume-key

[Iain Lane]

umm, that's nonsense, try "just needed to have a writable home
directory"

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

Title:
  [MIR] volume-key

Status in volume-key package in Ubuntu:
  In Progress
Status in volume-key source package in Bionic:
  In Progress

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  GNOME Disks uses udisks2. Debian's udisks2 recommends libblockdev-crypto2 
which depends on libvolume-key1.

  The package description for libblockdev-crypto2 is:
   "The libblockdev library plugin (and in the same time a standalone library)
    providing the functionality related to encrypted devices (LUKS)."

  This sounds like a very useful feature for Ubuntu since we offer full
  disk encryption using LUKS.

  Security
  
  No known security issues. Presumably should get a Security review.

  https://security-tracker.debian.org/tracker/source-package/volume-key
  https://launchpad.net/ubuntu/+source/volume-key/+cve

  Quality assurance
  =
  - Please subscribe Ubuntu Desktop bugs (although the Desktop Team thinks that 
Foundations should be responsible for udisks and friends)

  https://bugs.launchpad.net/ubuntu/+source/volume-key
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=volume-key
  https://pagure.io/volume_key/issues

  dh_auto_test is run but tests are failing and ignored.

  No autopkgtests

  Dependencies
  
  No universe dependencies

  Standards compliance
  
  4.1.3, debhelper compat 11, simple dh7 style rules

  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.

  https://salsa.debian.org/utopia-team/volume-key

  upstream:
  https://pagure.io/volume_key

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

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

[Desktop-packages] [Bug 1764355] Re: XDG_CONFIG_DIRS keeps getting expanded every login

[Tony Arnold]

This issue also applies to version 17.10. In my case, I am using gnome
desktop and the path /etx/xdg/xdg-gnome-xorg gets prepended to
$XDG_CONFIG_DIRS on every login.

Once the $XDG_CONFIG_DIRS gets beyond a certain length, applications
such as slack-desktop fails with a segmentation violation on start up.

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

Title:
  XDG_CONFIG_DIRS keeps getting expanded every login

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Version: 18.04
  gnome-session-common Version: 3.28.1-0ubuntu1

  What's expected to happen: $XDG_CONFIG_DIRS is the same on every login
  What happens instead: $XDG_CONFIG_DIRS gets expanded on every login

  It seems that $XDG_CONFIG_DIRS gets expanded by two entries on every
  login.

  On first login it looks like this:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  On second login it gets expanded by the same two entries in front:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg

  On third login, two more entries get added:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  At this point Visual Studio Code, which lead me to this, no longer
  starts and just throw a Segmentation fault/Core Dump.

  I suspect this behaviour is triggered by
  /etc/profile.d/xdg_dirs_desktop_session.sh adding more stuff to
  $XDG_CONFIG_DIRS on every login.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-common 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 11:30:09 2018
  Dependencies:

  InstallationDate: Installed on 2018-04-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754422] Re: [MIR] volume-key

[Iain Lane]

ok, just needed to be run as root, I asked jibel if he could test my
proposed package in ppa:laney/ppa, just waiting to hear back

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

Title:
  [MIR] volume-key

Status in volume-key package in Ubuntu:
  In Progress
Status in volume-key source package in Bionic:
  In Progress

Bug description:
  Availability
  
  Built for all supported architectures. In sync with Debian.

  Rationale
  =
  GNOME Disks uses udisks2. Debian's udisks2 recommends libblockdev-crypto2 
which depends on libvolume-key1.

  The package description for libblockdev-crypto2 is:
   "The libblockdev library plugin (and in the same time a standalone library)
    providing the functionality related to encrypted devices (LUKS)."

  This sounds like a very useful feature for Ubuntu since we offer full
  disk encryption using LUKS.

  Security
  
  No known security issues. Presumably should get a Security review.

  https://security-tracker.debian.org/tracker/source-package/volume-key
  https://launchpad.net/ubuntu/+source/volume-key/+cve

  Quality assurance
  =
  - Please subscribe Ubuntu Desktop bugs (although the Desktop Team thinks that 
Foundations should be responsible for udisks and friends)

  https://bugs.launchpad.net/ubuntu/+source/volume-key
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=volume-key
  https://pagure.io/volume_key/issues

  dh_auto_test is run but tests are failing and ignored.

  No autopkgtests

  Dependencies
  
  No universe dependencies

  Standards compliance
  
  4.1.3, debhelper compat 11, simple dh7 style rules

  Maintenance
  ===
  Maintained in Debian by the Debian Utopia team, which is a small team focused 
on cross-desktop freedesktop.org stuff.

  https://salsa.debian.org/utopia-team/volume-key

  upstream:
  https://pagure.io/volume_key

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

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

[Desktop-packages] [Bug 1764355] Re: XDG_CONFIG_DIRS keeps getting expanded every login

[Launchpad Bug Tracker]

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

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

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

Title:
  XDG_CONFIG_DIRS keeps getting expanded every login

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Version: 18.04
  gnome-session-common Version: 3.28.1-0ubuntu1

  What's expected to happen: $XDG_CONFIG_DIRS is the same on every login
  What happens instead: $XDG_CONFIG_DIRS gets expanded on every login

  It seems that $XDG_CONFIG_DIRS gets expanded by two entries on every
  login.

  On first login it looks like this:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  On second login it gets expanded by the same two entries in front:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg

  On third login, two more entries get added:

  /etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  /xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg

  At this point Visual Studio Code, which lead me to this, no longer
  starts and just throw a Segmentation fault/Core Dump.

  I suspect this behaviour is triggered by
  /etc/profile.d/xdg_dirs_desktop_session.sh adding more stuff to
  $XDG_CONFIG_DIRS on every login.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session-common 3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 11:30:09 2018
  Dependencies:

  InstallationDate: Installed on 2018-04-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1764453] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

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 #1754924, 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/1764453/+attachment/5118250/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1764453

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Bug description:
  Crash while installing printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Apr 16 18:08:29 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x55937dc6c311:mov0x90(%rbp),%rsi
   PC (0x55937dc6c311) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1764448] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

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 #1754924, 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/1764448/+attachment/5118236/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1764448

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  
  gnome-control-center *** 1:3.28.0-0ubuntu6 500

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 18:42:42 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-07 (40 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x55d873ceb311:mov0x90(%rbp),%rsi
   PC (0x55d873ceb311) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1764436] Re: gnome-control-center crashed with SIGSEGV

[Raphael Ouazana]

** This bug is no longer a duplicate of private bug 1754954

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crashed after clicking on back button.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 16:21:01 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-05 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe279411fad:mov0x8(%rdi),%eax
   PC (0x7fe279411fad) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_c

[Andrea Azzarone]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 1757058] Re: gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R

[Andrea Azzarone]

** Patch added: "gnome-calendar.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1757058/+attachment/5118206/+files/gnome-calendar.debdiff

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

Title:
  gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather
  → g_closure_invoke → signal_emit_unlocked_R

Status in gnome-calendar package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 1764436] Re: gnome-control-center crashed with SIGSEGV

[Apport retracing service]

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

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 #1754954, 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/1764436/+attachment/5118177/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1764436

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Crashed after clicking on back button.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 16:21:01 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-05 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fe279411fad:mov0x8(%rdi),%eax
   PC (0x7fe279411fad) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1757058] Re: gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R

[Andrea Azzarone]

Please find attached a proposed debdiff with the fix cherry-picked from
upstream.

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

Title:
  gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather
  → g_closure_invoke → signal_emit_unlocked_R

Status in gnome-calendar package in Ubuntu:
  In Progress

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

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

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

[Desktop-packages] [Bug 1764445] [NEW] the system is running in low-graphics mode

[damiano]

Public bug reported:

Ubuntu probably not recognizing installed Intel graphics driver

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Apr 16 17:38:17 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
InstallationDate: Installed on 2016-06-01 (684 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=108b2d66-e751-447b-8aed-a462e8ece73b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX2 R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd09/02/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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: Mon Apr 16 16:59:16 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  the system is running in low-graphics mode

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu probably not recognizing installed Intel graphics driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 16 17:38:17 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [1043:844d]
  InstallationDate: Installed on 2016-06-01 (684 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=108b2d66-e751-447b-8aed-a462e8ece73b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: To be filled by O.E.M.
  

[Desktop-packages] [Bug 1764434] Re: nome-shell crashed with SIGSEGV ign gbm_bo_get_plane_count()

[Apport retracing service]

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

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 #1758528, 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/1764434/+attachment/5118160/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1758528
   gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count() from 
gbm_get_next_fb_id()

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

Title:
  nome-shell crashed with SIGSEGV ign gbm_bo_get_plane_count()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I upgraded from 16.04 -> 17.10 -> 18.04 using the standard system
  update, and then upgrade via the GUI.

  After the upgrade I started experiencing issues. First with logging in
  (log in loop). Had to click on the gear icon and switch from Xorg to
  Unity (17.10).

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr 16 22:58:12 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-13 (2 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fd09ac4ec90 :   mov
(%rdi),%rax
   PC (0x7fd09ac4ec90) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   gbm_bo_get_plane_count () from /usr/lib/x86_64-linux-gnu/libgbm.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   cogl_onscreen_swap_buffers_with_damage () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
  Title: gnome-shell crashed with SIGSEGV in gbm_bo_get_plane_count()
  UpgradeStatus: Upgraded to bionic on 2018-04-16 (0 days ago)
  UserGroups:

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

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

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

[Baljaa]

Public bug reported:

x

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Apr 16 23:21:59 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:183e]
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=7f424bd3-4785-4184-ab31-dd3870c7c934 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.27
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 183E
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 56.32
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd09/07/2016:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 07911020561620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Apr 16 15:51:23 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  x

Status in xorg package in Ubuntu:
  New

Bug description:
  x

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 16 23:21:59 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:183e]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=7f424bd3-4785-4184-ab31-dd3870c7c934 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Desktop-packages] [Bug 1758070] Re: Switching users takes excessive time

[John Rose]

Over 3 weeks and nobody has posted a reply/comment/solution.

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

Title:
  Switching users takes excessive time

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  I'm not sure if this is the correct package on which to report this
  problem. Everything fine (took a few seconds) on switching users until
  a couple of days ago. Now it takes approx 30 econds to do so with lots
  of flashing on screen. Also, when user goes away from PC for a while
  and Ubuntu suspends, it displays login screen with Password box
  replaced by "Switch to Greeter". Thus, no obvious way to enter
  password. Clicking on "Switch to Greeter" gives (after a delay) login
  screen with password box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-greeter 16.04.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 22 13:58:18 2018
  InstallationDate: Installed on 2016-12-08 (469 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: unity-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1764435] Re: "Software is up to date" even after refresh, but "apt update && apt upgrade" shows updates

[Nathaniel W. Turner]

Note: same behavior even after dealing with the "kept back packages":

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-4.15.0-15 linux-headers-4.15.0-15-generic 
linux-image-4.15.0-15-generic linux-image-extra-4.15.0-15-generic 
linux-tools-4.15.0-15
  linux-tools-4.15.0-15-generic networkd-dispatcher
The following packages will be upgraded:
  adwaita-icon-theme adwaita-icon-theme-full appstream autofs autofs5 
ca-certificates cloud-image-utils command-not-found command-not-found-data cpp-7
  evolution evolution-common evolution-plugin-bogofilter 
evolution-plugin-pstimport evolution-plugins g++-7 gcc-7 gcc-7-base gcc-8-base 
gcc-8-base:i386
  gedit gedit-common gir1.2-gdesktopenums-3.0 gir1.2-goa-1.0 
gir1.2-harfbuzz-0.0 gjs gnome-calendar gnome-contacts gnome-keyring 
gnome-keyring-pkcs11
  gnome-online-accounts gnome-settings-daemon gnome-settings-daemon-schemas 
gnome-todo gnome-todo-common gsettings-desktop-schemas language-pack-en
  language-pack-gnome-en language-selector-common language-selector-gnome 
lib32gcc1 lib32stdc++6 libappstream4 libasan4 libatomic1 libcc1-0 libcilkrts5
  libevolution libfreetype6 libgcc-7-dev libgcc1 libgcc1:i386 libgfortran4 
libgjs0g libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev
  libglib2.0-dev-bin libgnome-todo libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgomp1 libharfbuzz-dev libharfbuzz-gobject0 
libharfbuzz-icu0
  libharfbuzz0b libitm1 liblsan0 libmpx2 libnautilus-extension1a libnghttp2-14 
libnss-myhostname libnss-mymachines libnss-systemd libobjc-7-dev libobjc4
  libpam-gnome-keyring libpam-systemd libpoppler-glib8 libpoppler-qt5-1 
libpoppler73 libpython2.7 libpython2.7-dev libpython2.7-minimal 
libpython2.7-stdlib
  libqpdf21 libquadmath0 libsonic0 libstdc++-7-dev libstdc++6 libsystemd-dev 
libsystemd0 libtsan0 libubsan0 libudev-dev libudev1 libxen-4.9 libxen-dev
  libxenstore3.0 libyelp0 linux-generic linux-headers-generic 
linux-image-generic linux-libc-dev linux-tools-common linux-tools-generic 
nautilus
  nautilus-data ndiff nmap poppler-utils python2.7 python2.7-dev 
python2.7-minimal python3-commandnotfound python3-distupgrade 
python3-software-properties
  python3-update-manager qpdf snapd software-properties-common 
software-properties-gtk strace systemd systemd-container systemd-sysv 
ubuntu-docs
  ubuntu-drivers-common ubuntu-release-upgrader-core 
ubuntu-release-upgrader-gtk ubuntu-settings ubuntu-wallpapers 
ubuntu-wallpapers-artful
  ubuntu-wallpapers-bionic ubuntu-wallpapers-zesty ubuntu-web-launchers udev 
update-manager update-manager-core xserver-xorg-input-libinput yelp
143 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/244 MB of archives.
After this operation, 379 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.

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

Title:
  "Software is up to date" even after refresh, but "apt update && apt
  upgrade" shows updates

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The Updates tab shows "Software is up to date". Pressing the reload
  button on the button bar shows it looking for new updates, the
  "Software is up to date".

  Running "sudo apt update && sudo apt upgrade" however shows 143
  upgraded packages:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
linux-headers-4.15.0-15 linux-headers-4.15.0-15-generic 
linux-image-4.15.0-15-generic linux-image-extra-4.15.0-15-generic 
linux-tools-4.15.0-15
linux-tools-4.15.0-15-generic networkd-dispatcher
  The following packages have been kept back:
nodejs nodejs-dev
  The following packages will be upgraded:
adwaita-icon-theme adwaita-icon-theme-full appstream autofs autofs5 
ca-certificates cloud-image-utils command-not-found command-not-found-data cpp-7
evolution evolution-common evolution-plugin-bogofilter 
evolution-plugin-pstimport evolution-plugins g++-7 gcc-7 gcc-7-base gcc-8-base 
gcc-8-base:i386
gedit gedit-common gir1.2-gdesktopenums-3.0 gir1.2-goa-1.0 
gir1.2-harfbuzz-0.0 gjs gnome-calendar gnome-contacts gnome-keyring 
gnome-keyring-pkcs11
gnome-online-accounts gnome-settings-daemon gnome-settings-daemon-schemas 
gnome-todo gnome-todo-common gsettings-desktop-schemas language-pack-en
language-pack-gnome-en language-selector-common language-selector-gnome 
lib32gcc1 lib32stdc++6 libappstream4 libasan4 libatomic1 libcc1-0 libcilkrts5
libevolution libfreetype6 libgcc-7-dev libgcc1 libgcc1:i386 libgfortran4 
libgjs0g libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev
libglib2.0-dev-bin libgnome-todo 

[Desktop-packages] [Bug 1764430] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

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 #1754924, 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/1764430/+attachment/5118138/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1764430

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Bug description:
  Changed from xorg to wayland and logged in.  When I loaded the
  Settings app, this error occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 09:51:33 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-11 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5600cf3e7311:mov0x90(%rbp),%rsi
   PC (0x5600cf3e7311) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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