[Desktop-packages] [Bug 1708977] Re: Cannot boot after update

[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/1708977

Title:
  Cannot boot after update

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Following minor linux update cannot boot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog: /dev/sda1: clean, 223961/121970688 files, 8834593/487854592 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Aug  6 20:15:50 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Pegatron GK107 [GeForce GT 640 OEM] [1b0a:90c5]
  MachineType: Hewlett-Packard 700-230qe
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic.efi.signed 
root=UUID=91d8e6ac-97d6-4068-a684-bc045f783fb5 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 80.15
  dmi.board.name: 2AF3
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 2MD3480GR8
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr80.15:bd09/19/2013:svnHewlett-Packard:pn700-230qe:pvr:rvnHewlett-Packard:rn2AF3:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: 700-230qe
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Aug  6 19:51:39 2017
  xserver.configfile: default
  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.3-1ubuntu2.2
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1709452] Re: Intell graphics

[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/1709452

Title:
  Intell graphics

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The HDMI stopped working suddenly. I tried re-install Intell Graphic drivers 
and still nothing.
  I have a Dell Insipiron 5010 64 bit.
  I ran de apport bug as the helped stated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug  8 20:33:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-83-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-89-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0447]
  InstallationDate: Installed on 2014-10-05 (1038 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=cbde2fc0-7e9c-48f9-b588-ea7014e028ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0WXY9J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd07/26/2010:svnDellInc.:pnInspironN5010:pvrA07:rvnDellInc.:rn0WXY9J:rvrA07:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug  8 20:28:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8940 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.3

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

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

[Desktop-packages] [Bug 1708983] Re: frozen screen

[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/1708983

Title:
  frozen screen

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Random freezing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Aug  6 16:51:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Dell Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[1028:0667]
  InstallationDate: Installed on 2017-08-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0c45:64ad Microdia 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3531
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=53de4d80-8cca-40f7-a458-af49bc522162 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 00FTTX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/30/2014:svnDellInc.:pnInspiron3531:pvrA03:rvnDellInc.:rn00FTTX:rvrA00:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Inspiron 3531
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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

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

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

[Desktop-packages] [Bug 1763885] Re: package libpoppler-glib8:amd64 0.41.0-0ubuntu1 failed to install/upgrade: package libpoppler-glib8:amd64 is not ready for configuration cannot configure (current s

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libpoppler-glib8:amd64 0.41.0-0ubuntu1 failed to
  install/upgrade: package libpoppler-glib8:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in poppler package in Ubuntu:
  New

Bug description:
  plz resolve

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpoppler-glib8:amd64 0.41.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Apr 14 10:22:59 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   package:libpoppler-glib8:amd64:0.41.0-0ubuntu1
   Processing triggers for libc-bin (2.23-0ubuntu10) ...
   dpkg: error processing package libpoppler-glib8:amd64 (--configure):
package libpoppler-glib8:amd64 is not ready for configuration
  ErrorMessage: package libpoppler-glib8:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-11-14 (150 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: poppler
  Title: package libpoppler-glib8:amd64 0.41.0-0ubuntu1 failed to 
install/upgrade: package libpoppler-glib8:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 491489] Re: Duplicate Entry for Samba Mounts in Places

[Bug Watch Updater]

** Changed in: nautilus
   Status: New => Expired

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

Title:
  Duplicate Entry for Samba Mounts in Places

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  I just upgraded from Jaunty to Karmic, and now in my Places it has one of my 
Shares listed twice.
  My share is setup via /etc/fstab like so:
  //192.168.1.103/RAID-storage /media/Unicorn-NAS   smbfs  
auto,credentials=/root/.credentials_Unicorn-NAS,uid=1000,umask=000,user,exec   
0 0

  Now "Unicorn-NAS" is listed twice:
  http://i4.photobucket.com/albums/y105/basskozz/Ubuntu/places-screenshot.png

  When I click on one of the shares (Unicorn-NAS), I get the following:
  
http://i4.photobucket.com/albums/y105/basskozz/Ubuntu/Screenshot-UntitledWindow.png

  But when I click on the other it opens up the share (as it should).
  So why now (after upgrading to Karmic) do I have a duplicate tab for 
Unicorn-NAS?

  See also: http://ubuntuforums.org/showthread.php?t=1342283

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Dec  2 12:49:48 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  NonfreeKernelModules: nvidia
  Package: nautilus 1:2.28.1-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-15-generic x86_64

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

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

[Desktop-packages] [Bug 412449] Re: Incorrect mount/umount/REMOVE behavior of USB drive

[Bug Watch Updater]

** Changed in: gvfs
   Status: New => Expired

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

Title:
  Incorrect mount/umount/REMOVE behavior of USB drive

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Host: Karmic, fully updated at time of posting.

1) When I insert an external USB drive, Karmic is automatically
  mounting all of the partitions.  This is NOT what I want, but please
  don't focus on this one issue.  Item #2 is arguably worse.

2) If I open Computer and right click a mounted partition, I can
  unmount the volume.  However, if I click the symbol next to the
  mounted volume, all of the partitions are unmounted, AND THE DRIVE IS
  REMOVED.

  So after connecting the drive via USB, and checking mounts, I see:

  /dev/sdb1 on /media/GRUB type ext3 (rw,nosuid,nodev,uhelper=devkit)
  /dev/sdb5 on /media/Fedora 10 type ext3 (rw,nosuid,nodev,uhelper=devkit)
  /dev/sdb6 on /media/Ubuntu 8.04.2 type ext3 (rw,nosuid,nodev,uhelper=devkit)
  /dev/sdb7 on /media/Ubuntu 8.10 type ext3 (rw,nosuid,nodev,uhelper=devkit)
  /dev/sdb8 on /media/Ubuntu 9.10 type ext3 (rw,nosuid,nodev,uhelper=devkit)
  /dev/sdb10 on /media/SHARED type xfs (rw,nosuid,nodev,uhelper=devkit)

  and after clicking the symbol, which USED to simply unmount
  undesirably mounted volumes, the entire drive is removed, e.g., there
  are no more entries under /dev for the drive.  udev log file attached.

  A few more notes:

A) the mounting behavior is inconsistent.  During testing to prepare
  the data for this report, I connected and disconnected the drive
  multiple times.  Each time a different set of partitions was mounted.

B) When I connect the same drive using eSATA instead of USB, I am
  prompted that authentication is required to mount volumes, whereas
  this is not required when the same drive is connected over USB.

C) The unmount versus remove behavior appears to be USB specific.
  If I use eSATA, the behavior is to simply unmount the partition, as
  expected.  I also have an SDHC card in the built-in reader.  It, too,
  is auto-mounted, but unlike the USB drive, clicking the icon next to
  the mounted volume only unmounts the volume.

  Unclear to me how much of this is nautilus, how much is DevceKit,
  etc., but I'll leave that for others to reassign.  I suspect that
  DeviceKit is to blame for at least some of the behavior, but want to
  focus on this newly introduced defect that removes the drive instead
  of unmounting the partition.

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

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

[Desktop-packages] [Bug 1763885] [NEW] package libpoppler-glib8:amd64 0.41.0-0ubuntu1 failed to install/upgrade: package libpoppler-glib8:amd64 is not ready for configuration cannot configure (current

[GURDEEP Male SINGH]

Public bug reported:

plz resolve

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpoppler-glib8:amd64 0.41.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sat Apr 14 10:22:59 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DuplicateSignature:
 package:libpoppler-glib8:amd64:0.41.0-0ubuntu1
 Processing triggers for libc-bin (2.23-0ubuntu10) ...
 dpkg: error processing package libpoppler-glib8:amd64 (--configure):
  package libpoppler-glib8:amd64 is not ready for configuration
ErrorMessage: package libpoppler-glib8:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
InstallationDate: Installed on 2017-11-14 (150 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: poppler
Title: package libpoppler-glib8:amd64 0.41.0-0ubuntu1 failed to 
install/upgrade: package libpoppler-glib8:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libpoppler-glib8:amd64 0.41.0-0ubuntu1 failed to
  install/upgrade: package libpoppler-glib8:amd64 is not ready for
  configuration  cannot configure (current status 'half-installed')

Status in poppler package in Ubuntu:
  New

Bug description:
  plz resolve

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpoppler-glib8:amd64 0.41.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Apr 14 10:22:59 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   package:libpoppler-glib8:amd64:0.41.0-0ubuntu1
   Processing triggers for libc-bin (2.23-0ubuntu10) ...
   dpkg: error processing package libpoppler-glib8:amd64 (--configure):
package libpoppler-glib8:amd64 is not ready for configuration
  ErrorMessage: package libpoppler-glib8:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-11-14 (150 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: poppler
  Title: package libpoppler-glib8:amd64 0.41.0-0ubuntu1 failed to 
install/upgrade: package libpoppler-glib8:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1251899] Re: every time I restart udisksd, the unity panel adds another "audio disc" icon

[Bug Watch Updater]

** Changed in: gvfs
   Status: Confirmed => Fix Released

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

Title:
  every time I restart udisksd, the unity panel adds another "audio
  disc" icon

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  I ended up restarting udisksd half a dozen times today while working
  on it and each time, unity added yet another duplicate icon for the
  cdrom.  Tried to restart unity by running unity --replace ( why isn't
  it an upstart job? ), and it just died so I had to alt-sysrq-k and
  login again, at which point all of the duplicates were gone.

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

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

[Desktop-packages] [Bug 1763888] [NEW] Display scale reverts to 1 every time screen locks. Ubuntu 16.04 after a recent update

[Peter Lavers]

Public bug reported:

Setting the display scale is not preserved after screen lock. Ubuntu 16.04 
(after a recent ?Feb 2018?) update.
This looks similar to previously reported bug #1689356.

This is very frustrating and makes it hard to justify using Ubuntu to
family members who just want things to work.

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

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

Title:
  Display scale reverts to 1 every time screen locks. Ubuntu 16.04 after
  a recent update

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

Bug description:
  Setting the display scale is not preserved after screen lock. Ubuntu 16.04 
(after a recent ?Feb 2018?) update.
  This looks similar to previously reported bug #1689356.

  This is very frustrating and makes it hard to justify using Ubuntu to
  family members who just want things to work.

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

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

[Desktop-packages] [Bug 1755023] Re: Restore ignores what I type into the folder box

[Vej]

** Also affects: deja-dup (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Restore ignores what I type into the folder box

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have my computer using Deja Dup to backup everything to a particular
  folder on a secondary drive. When I try to use Deja Dup to restore a
  backup from a different folder on that drive, it does not scan that
  folder.

  1. Open Deja Dup and click the Restore... button.
  2. In the Restore From Where? window, the Backup location is set to my 
external hard drive, and the Folder field is set to my current backup folder. 
From here, I try paths "a" and "b" below:
  3a. Change the text in the Folder field to be the name of the folder 
containing my previous computer's backup, and click Forward.
  4a. I am presented with a list of backups from my current backup folder, not 
from the other folder I tried to select.
  3b. Change the Backup location field to Local Folder, and now click the 
Choose Folder... button that has appeared next to the Folder field.
  4b. Browse to the mount point of my secondary drive, and select the backup 
folder that was used for my previous computer. Click OK, and then Forward.
  5b. I am presented with the message "Restore Failed" "No backups to restore"

  I'm on Ubuntu 17.10 with deja-dup 36.3-0ubuntu0.1 and duplicity
  0.7.12-1ubuntu1

  I have attached deja-dup.gsettings to this bug report. I will add debug 
outputs in comments below.
  In those logs, it should be noted that my secondary drive is named "Octonary" 
and is mounted at "/media/paul/Octonary". My current backup folder is 
"/media/paul/Octonary/Ubuntu Backup 3", and the backup folder of my previous 
computer is "/media/paul/Octonary/Ubuntu Backup 2".

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1755023/+subscriptions

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

I'm only on-site with these kiosks once a week, but the next time I'm
there I will run apport-collect on one of the affected systems, and see
if we can't capture the problem.  I'll also investigate whether there
are any messages in kernel log files, as best I can.

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

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 1755023] Re: Restore ignores what I type into the folder box

[Launchpad Bug Tracker]

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

** Changed in: deja-dup (Ubuntu)
   Status: New => Confirmed

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

Title:
  Restore ignores what I type into the folder box

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have my computer using Deja Dup to backup everything to a particular
  folder on a secondary drive. When I try to use Deja Dup to restore a
  backup from a different folder on that drive, it does not scan that
  folder.

  1. Open Deja Dup and click the Restore... button.
  2. In the Restore From Where? window, the Backup location is set to my 
external hard drive, and the Folder field is set to my current backup folder. 
From here, I try paths "a" and "b" below:
  3a. Change the text in the Folder field to be the name of the folder 
containing my previous computer's backup, and click Forward.
  4a. I am presented with a list of backups from my current backup folder, not 
from the other folder I tried to select.
  3b. Change the Backup location field to Local Folder, and now click the 
Choose Folder... button that has appeared next to the Folder field.
  4b. Browse to the mount point of my secondary drive, and select the backup 
folder that was used for my previous computer. Click OK, and then Forward.
  5b. I am presented with the message "Restore Failed" "No backups to restore"

  I'm on Ubuntu 17.10 with deja-dup 36.3-0ubuntu0.1 and duplicity
  0.7.12-1ubuntu1

  I have attached deja-dup.gsettings to this bug report. I will add debug 
outputs in comments below.
  In those logs, it should be noted that my secondary drive is named "Octonary" 
and is mounted at "/media/paul/Octonary". My current backup folder is 
"/media/paul/Octonary/Ubuntu Backup 3", and the backup folder of my previous 
computer is "/media/paul/Octonary/Ubuntu Backup 2".

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1755023/+subscriptions

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

[Desktop-packages] [Bug 1748000] Re: Remove from the archive: this legacy driver is unmaintained upstream

[Ingvass Silis]

I also think removing the nvidia-304 driver is a bad decision. I didn't
know that they removed this driver from the repositories before I
upgraded to Ubuntu 18.04 beta 2. I have a NVIDIA 7300 GT graphics card
that is rendered almost useless because of the removal of this driver,
on Ubuntu and its flavors (I use Xubuntu with this card). I have tried
building and installing the driver from NVIDIAs website, which failed. I
have finally tried installing this driver from the ppa "ppa:graphics-
drivers/ppa", which failed because of conflicting packages. Uninstalling
these conflicting packages uninstall very important packages, like the
Xubuntu desktop. This is also the only driver that works properly with
my card. Although it is unmaintained, it was still a very bad decision
to remove this driver, as old cards still use it. :(

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

Title:
  Remove from the archive: this legacy driver is unmaintained upstream

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Fix Released

Bug description:
  This driver branch is now dead upstream, so it should be removed from
  bionic.

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

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

[Desktop-packages] [Bug 1763488] Re: restore only does not use information from "folder" text field

[Vej]

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

Hello Dark Dragon,

thank for taking the time to report this bug.

Because your problem had been reported in bug #1755023, I am marking
this as a duplicate and Ubuntu as affected in bug #1755023.

If you want to give further informations or discuss about this problem
use bug bug #1755023 please.

Best Regards

Vej

** Also affects: deja-dup
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1755023
   Restore ignores what I type into the folder box

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

Title:
  restore only does not use information from "folder" text field

Status in Déjà Dup:
  New
Status in deja-dup package in Ubuntu:
  New

Bug description:
  I want to restore files from a server backup. I do not want to create
  a backup.

  So I click in the "Overview" tab the "Restore" button and then select
  my Nextcloud server and enter something in the "Folder" field. This
  does not work

  When I enter the information in "Storage location" and then start the
  restore, it works. When I click again on "Restore" and change the
  information in the "Folder" field, it still uses the old folder (the
  one in "Storage location").

  So my conclusion is that the "Folder" field in the "Restore" dialog is
  just ignored and the information from "Storage location" is used
  instead.

  Can someone confirm?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1763488/+subscriptions

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

[Desktop-packages] [Bug 1763819] [NEW] package thunderbird-gnome-support 1:52.6.0+build1-0ubuntu0.16.04.1 failed to install/upgrade: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't exist:

[Edison Zounar]

Public bug reported:

El instalador se estropeo y no puede completar la instalacion del SO

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: thunderbird-gnome-support 1:52.6.0+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 1922 F pulseaudio
BuildID: 20180124152824
CasperVersion: 1.376.2
Channel: Unavailable
Date: Fri Apr 13 14:02:33 2018
ErrorMessage: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't 
exist: Read-only file system
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
 192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.105  metric 
600
LiveMediaBuild: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
NoProfiles: True
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.3
 apt  1.2.25
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird-gnome-support 1:52.6.0+build1-0ubuntu0.16.04.1 
failed to install/upgrade: error ensuring '/target/var/lib/dpkg/reassemble.deb' 
doesn't exist: Read-only file system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE50_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.15
dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5750:pvrV1.15:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15:
dmi.product.name: Aspire 5750
dmi.product.version: V1.15
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package xenial

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

Title:
  package thunderbird-gnome-support 1:52.6.0+build1-0ubuntu0.16.04.1
  failed to install/upgrade: error ensuring
  '/target/var/lib/dpkg/reassemble.deb' doesn't exist: Read-only file
  system

Status in thunderbird package in Ubuntu:
  New

Bug description:
  El instalador se estropeo y no puede completar la instalacion del SO

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: thunderbird-gnome-support 1:52.6.0+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1922 F pulseaudio
  BuildID: 20180124152824
  CasperVersion: 1.376.2
  Channel: Unavailable
  Date: Fri Apr 13 14:02:33 2018
  ErrorMessage: error ensuring '/target/var/lib/dpkg/reassemble.deb' doesn't 
exist: Read-only file system
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.105  
metric 600
  LiveMediaBuild: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
  NoProfiles: True
  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.3
   apt  1.2.25
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird-gnome-support 1:52.6.0+build1-0ubuntu0.16.04.1 
failed to install/upgrade: error ensuring '/target/var/lib/dpkg/reassemble.deb' 
doesn't exist: Read-only file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE50_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5750:pvrV1.15:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15:
  dmi.product.name: Aspire 5750
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Bodie Solomon]

This also affected me on Bionic.  Note that I had the Nvidia native
drivers working in 17.10, but the bug only affected me in Bionic.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/1763774

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1763806] Re: Running breaks gnome-shell monitor configurations and vice-versa

[Launchpad Bug Tracker]

** Branch linked: lp:~3v1n0/unity-settings-daemon/use-and-migrate-unity-
monitors-xml

** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-bionic-3223

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

Title:
  Running breaks gnome-shell monitor configurations and vice-versa

Status in unity-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Mutter introduced a new format of monitors.xml (version 2), unity
  (-settings-daemon) still relies on the old format, so we need to
  separate the two files and migrate them if needed.

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

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

[Desktop-packages] [Bug 1763837] [NEW] Update apport hook

[Jeremy Bicha]

Public bug reported:

Ubuntu's yelp includes an apport hook that asks users whether they have
a problem with the help browser or need help performing a task. If the
user chooses "needs help", they are referred to "Launchpad Support":
https://answers.launchpad.net/

That feels to me like it is a bad place to send users. Could we update
that?

System Info
---
Ubuntu 18.04
yelp 3.26.0-1ubuntu2

/usr/share/apport/package-hooks/source_yelp.py

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


** Tags: bionic

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

Title:
  Update apport hook

Status in yelp package in Ubuntu:
  New

Bug description:
  Ubuntu's yelp includes an apport hook that asks users whether they
  have a problem with the help browser or need help performing a task.
  If the user chooses "needs help", they are referred to "Launchpad
  Support": https://answers.launchpad.net/

  That feels to me like it is a bad place to send users. Could we update
  that?

  System Info
  ---
  Ubuntu 18.04
  yelp 3.26.0-1ubuntu2

  /usr/share/apport/package-hooks/source_yelp.py

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

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

The following verbose log suggests that libsecret is missing from the
snap:

[8021:8236:0413/194753.217679:VERBOSE1:key_storage_util_linux.cc(53)] Password 
storage detected desktop environment: GNOME
[8021:8236:0413/194753.218064:VERBOSE1:libsecret_util_linux.cc(101)] Could not 
load libsecret-1.so.0: libsecret-1.so.0: cannot open shared object file: No 
such file or directory

I tested rebuilding the snap with libsecret-1-0 in the stage packages, and the 
message went away but still no window.
However after connecting the password-manager-service interface, the issue 
seemed to be resolved:

snap connect chromium:password-manager-service

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

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

** 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/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 1173787] Re: Delay selection in blender - ubuntu 13.04 - ati 4250

[Bug Watch Updater]

** Changed in: mesa
   Status: Confirmed => Won't Fix

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

Title:
  Delay selection in blender - ubuntu 13.04 - ati 4250

Status in Mesa:
  Won't Fix
Status in blender package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Delay selection in blender - ubuntu 13.04 - ati 4250

  When you select an object in Blender 2.66a, selection is slow. As if delay. 
No matter the complexity of the object, it is slow when selecting objects. 
(Blender installed from the ubuntu software center)
  My pc is an Acer Aspire 5552-6829 with integrated ATI HD4250 video with 
"Gallium 0.4 on AMD RS880" driver.

  This "error" occurs after installing Ubuntu 13.04 with Unity, but also
  occurs in Ubuntu GNOME 13.04. (all 64 bit) ... Previously not happen
  with Ubuntu 12.04 (kernel 3.2 / 5).

  Since there is an apparent problem or tangible and also am a newbie
  with this from the bugs, I would like to know what I have to analyze
  with "ubuntu-bug" I'm not sure it's the composer of windows or
  X.org.

  * Summary details:
  Ubuntu 13.04 64bit
  Blender 2.66a
  Ati HD4250
  Gallium 0.4 on AMD RS880

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

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

[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2

[Bill Miller]

I'd love to have it too. It controlled the heating on my laptop better
than any other version.

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

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

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

In chromium, in function os_crypt::SelectBackend()¹, when GNOME is
detected, the backend is SelectedLinuxBackend::GNOME_ANY, which is
documented as "GNOME_KEYRING or GNOME_LIBSECRET, whichever is
available". This piece of code doesn't seem to automatically fall back
to the basic (unencrypted) password store, like the regular
login/password storage functionality does.

This can be overridden on the command line though, with "--password-
store=basic" (and thus doesn't require the connection of the password-
manager-service interface).


¹ 
https://cs.chromium.org/chromium/src/components/os_crypt/key_storage_util_linux.cc?sq=package:chromium=30

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

[Olivier Tilloy]

Calling the following in the wrapper and checking for the return code
should do the trick:

dbus-send --session --dest=org.freedesktop.secrets
/org/freedesktop/secrets --print-reply
org.freedesktop.DBus.Properties.GetAll
string:'org.freedesktop.Secret.Service'

-- 
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 1763827] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()

[Apport retracing service]

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

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 #1724439, 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/1763827/+attachment/5114539/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724439
   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()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I can only describe the events leading up to the crash reporter
  popping up on my screen.

  I have a Intel NUC i5-7260U connected via a HDMI cable to a Samsung
  UE46D6515 TV set.  I turned off my TV using the remote control and
  when I turned it back on, the keyboard and mouse were unresponsive for
  a few seconds.  Moments later, all was well but the crash reporter
  appeared.

  I might add that I had difficulties with powering off the TV under
  17.10, leading me to switch to X11 (which worked better but had
  similar problems).

  All the best,  Gísli

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  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: Fri Apr 13 19:42:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-13 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f7f25cf0c24 :mov
0x18(%rax),%eax
   PC (0x7f7f25cf0c24) 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-2.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/ubuntu/+source/gnome-shell/+bug/1763827/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] [snap] chromium won't start after logging in to google account

[Olivier Tilloy]

Public bug reported:

(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

** Affects: chromium-browser (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: Confirmed


** Tags: snap

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

[Olivier Tilloy]

I wonder whether, as a workaround, the snap wrapper that launches
chromium could detect whether the password-manager-service interface is
connected, and if not add the --password-store=basic command-line
option.

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

[Olivier Tilloy]

Full wrapper:

#!/bin/sh
PASSWORD_STORE=gnome
dbus-send --session --dest=org.freedesktop.secrets /org/freedesktop/secrets 
--print-reply org.freedesktop.DBus.Properties.GetAll 
string:'org.freedesktop.Secret.Service' >/dev/null 2>&1
if [ "$?" -ne "0" ]; then
  PASSWORD_STORE=basic
fi
exec "$SNAP/usr/lib/chromium-browser/chromium-browser" 
--no-default-browser-check --no-first-run --password-store=$PASSWORD_STORE "$@"

This would require some testing on other desktop environments, e.g. KDE.

-- 
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 1672297] Re: gnome-shell uses lots of memory, and grows over time

[Amr Ibrahim]

Upstream has released new versions of accountsservice & polkit to fix some 
leaks.
https://cgit.freedesktop.org/accountsservice/tag/?h=0.6.46
https://cgit.freedesktop.org/polkit/tag/?h=0.114

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

Title:
  gnome-shell uses lots of memory, and grows over time

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

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

  ---

  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  

[Desktop-packages] [Bug 1755023] Re: Restore ignores what I type into the folder box

[Vej]

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Restore ignores what I type into the folder box

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  I have my computer using Deja Dup to backup everything to a particular
  folder on a secondary drive. When I try to use Deja Dup to restore a
  backup from a different folder on that drive, it does not scan that
  folder.

  1. Open Deja Dup and click the Restore... button.
  2. In the Restore From Where? window, the Backup location is set to my 
external hard drive, and the Folder field is set to my current backup folder. 
From here, I try paths "a" and "b" below:
  3a. Change the text in the Folder field to be the name of the folder 
containing my previous computer's backup, and click Forward.
  4a. I am presented with a list of backups from my current backup folder, not 
from the other folder I tried to select.
  3b. Change the Backup location field to Local Folder, and now click the 
Choose Folder... button that has appeared next to the Folder field.
  4b. Browse to the mount point of my secondary drive, and select the backup 
folder that was used for my previous computer. Click OK, and then Forward.
  5b. I am presented with the message "Restore Failed" "No backups to restore"

  I'm on Ubuntu 17.10 with deja-dup 36.3-0ubuntu0.1 and duplicity
  0.7.12-1ubuntu1

  I have attached deja-dup.gsettings to this bug report. I will add debug 
outputs in comments below.
  In those logs, it should be noted that my secondary drive is named "Octonary" 
and is mounted at "/media/paul/Octonary". My current backup folder is 
"/media/paul/Octonary/Ubuntu Backup 3", and the backup folder of my previous 
computer is "/media/paul/Octonary/Ubuntu Backup 2".

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1755023/+subscriptions

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

[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

[Yuriy Vidineev]

Hi Kai-Heng!
I still see this bug. I'll try to reproduce it with liveUSB

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1748000] Re: Remove from the archive: this legacy driver is unmaintained upstream

[Ricardo Almeida]

Although unmaintained, it's the only driver that works correctly with my
card... If there are ways to patch it so that it loads on Ubuntu 18.04,
I think it's a bad decision removing it :(

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

Title:
  Remove from the archive: this legacy driver is unmaintained upstream

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Fix Released

Bug description:
  This driver branch is now dead upstream, so it should be removed from
  bionic.

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

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

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[David Britton]

** Changed in: chrony (Ubuntu)
   Importance: Critical => High

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1763798] Re: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()

[Apport retracing service]

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

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 #1758651, 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/1763798/+attachment/5114357/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1763798

Title:
  Xwayland crashed with signal 7 in mieqProcessDeviceEvent()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Nothing to add, just browsing using Iridium Browser when the error
  came up.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 13 12:46:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2102]
  InstallationDate: Installed on 2017-11-30 (134 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=088c9d72-6e21-40ef-a173-aad179f6c233 ro
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   mieqProcessDeviceEvent ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x558fac48caa0, argc=12, argv=0x7ffdaed364f8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffdaed364e8) at ../csu/libc-start.c:310
  Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.406
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.406:bd11/08/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about 

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

[William F Hammond]

At the github site referenced here at the top it is said:

--
"On newer iOS version, ValidatePair is not mandatory to gain trusted host 
status. Starting with iOS 11, the ValidatePair request has been removed from 
lockdownd and will throw an error. This commit adds a version check so that 
ValidatePair is only called on devices prior iOS 7."
--

I'm looking for clarity here.  As I understand it, libimobiledevice
issues a formerly required ValidatePair call, and iOS 11 throws a
killing error.  Is that right?  Isn't it reasonable that iOS 11 could
just ignore it and keep going?

That is, isn't this something that one could ask Apple to fix?

Moreover, I still fail to understand why USB access to the iPhone file
system is so bizarre.  There is adequate authentication when (1) the
iPhone is unlocked by the user and (2) the user responds on the unlocked
phone to the question "Trust this computer?".  It should then be the
responsibility of iOS to show the unjailed part of the file system
transparently through the lightning port.  (In mentioning "jail", why
are the vcards behind "Contacts" not outside of jail?  There can be no
legitimate reason for that.)

One is left with the impression that Apple has little respect for inter-
operability with anything that is not Apple.  It would seem that the
only Apple-supported ways to move photos from an iPhone to a Linux
platform are (1) email (one photo at a time) or (2) iCloud via the web,
provided that the user allows iCloud backups from the phone.  (The
website at icloud.com is not itself fully inter-operable.  For example,
it says that it does not support Android mobile devices when it is
called from my Android tablet.)

-- 
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 1763648] [NEW] nvidia-304 (304.137) missing in Ubuntu 18.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

nvidia-304 is not available in the Ubuntu 18.04. Newer versions are
available but I have an old nVidia 7600 GT, so I need 304.137.

I searched online and found that at
https://answers.launchpad.net/ubuntu/bionic/amd64/nvidia-304/304.137-0ubuntu2
it has Status: Deleted :(

Could you please pack this for the new release of Ubuntu?

** Affects: nvidia-graphics-drivers-304 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: needs-packaging
-- 
nvidia-304 (304.137) missing in Ubuntu 18.04
https://bugs.launchpad.net/bugs/1763648
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.

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

[Desktop-packages] [Bug 1763780] Re: gnome-calendar crashed with SIGSEGV in g_str_equal()

[Apport retracing service]

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

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 #1755960, 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/1763780/+attachment/5114281/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1763780

Title:
  gnome-calendar crashed with SIGSEGV in g_str_equal()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Crashes when deleting 2nd of two day notes.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 09:49:36 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2018-04-06 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa3aed99d76 <__strcmp_ssse3+22>:movlpd 
(%rdi),%xmm1
   PC (0x7fa3aed99d76) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   g_str_equal () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__POINTERv () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in g_str_equal()
  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-calendar/+bug/1763780/+subscriptions

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

[Desktop-packages] [Bug 1763648] Re: nvidia-304 (304.137) missing in Ubuntu 18.04

[Hans Joachim Desserud]

Looks like it was removed from bionic due to bug 1748000. (Found via the
publishing history link in the upper right corner on the package
overview page, see https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-304/+publishinghistory for details)

** Package changed: ubuntu => nvidia-graphics-drivers-304 (Ubuntu)

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

Title:
  nvidia-304 (304.137) missing in Ubuntu 18.04

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

Bug description:
  nvidia-304 is not available in the Ubuntu 18.04. Newer versions are
  available but I have an old nVidia 7600 GT, so I need 304.137.

  I searched online and found that at
  https://answers.launchpad.net/ubuntu/bionic/amd64/nvidia-304/304.137-0ubuntu2
  it has Status: Deleted :(

  Could you please pack this for the new release of Ubuntu?

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

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

[Desktop-packages] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2

[Ricardo Almeida]

Could a ppa be created for the easy distribution of the patched version?

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

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

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

[Desktop-packages] [Bug 1761388] Re: Xorg crashed with signal 7 in _dl_fixup()

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xorg crashed with signal 7 in _dl_fixup()

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

Bug description:
  after login in session

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-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-13ubuntu1)
  .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-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Wed Apr  4 20:55:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-12-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd]
  InstallationDate: Installed on 2017-09-02 (214 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=1
  Signal: 7
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   _dl_fixup (l=0x55f44264f5b0, reloc_arg=) at 
../elf/dl-runtime.c:84
   _dl_runtime_resolve_xsavec () at ../sysdeps/x86_64/dl-trampoline.h:125
   wfbRasterizeTrapezoid () from /usr/lib/xorg/modules/libwfb.so
   ?? () from /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so
   ?? ()
  Title: Xorg crashed with signal 7 in _dl_fixup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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: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

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

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

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[David Britton]

** Changed in: chrony (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1763799] Re: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()

[Apport retracing service]

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

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 #1758651, 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/1763799/+attachment/5114378/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1763799

Title:
  Xwayland crashed with signal 7 in mieqProcessDeviceEvent()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Browsing with Iridium Browser, nothing else, bug came up.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 13 12:46:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  ExecutableTimestamp: 1520935141
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2102]
  InstallationDate: Installed on 2017-11-30 (134 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. K55A
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=088c9d72-6e21-40ef-a173-aad179f6c233 ro
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   mieqProcessDeviceEvent ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x558fac48caa0, argc=12, argv=0x7ffdaed364f8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffdaed364e8) at ../csu/libc-start.c:310
  Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/08/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K55A.406
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK55A.406:bd11/08/2012:svnASUSTeKCOMPUTERINC.:pnK55A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K55A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER 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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Desktop-packages] [Bug 1763806] [NEW] Running breaks gnome-shell monitor configurations and vice-versa

[Treviño]

Public bug reported:

Mutter introduced a new format of monitors.xml (version 2), unity
(-settings-daemon) still relies on the old format, so we need to
separate the two files and migrate them if needed.

** Affects: unity-settings-daemon (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

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

Title:
  Running breaks gnome-shell monitor configurations and vice-versa

Status in unity-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Mutter introduced a new format of monitors.xml (version 2), unity
  (-settings-daemon) still relies on the old format, so we need to
  separate the two files and migrate them if needed.

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

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

[Desktop-packages] [Bug 1606901] Re: Clicking "Show details" in AO for Nautilus produces "Could not find 'nautilus.desktop'" error from gnome-software

[Jeremy Bicha]

I looked at the status of this today in Ubuntu 18.04. GNOME Software has
been updated so that it shows better results in this case instead of an
error. (But it's still not perfect. Try gedit as the test case instead
of nautilus.)

Seb Bacher suggested that gnome-shell is probably wrong for sending the
old .desktop ID to gnome-software instead of the new one so I'm opening
a gnome-shell task here.

We also discussed this general issue in the Ubuntu Desktop team today.
We do not intend to drop the compatibility desktop files now for Ubuntu
18.04 LTS since they provide a useful service to upgrading Unity users.
It looks like we will probably drop them in 18.10 though since they
should no longer be needed then for GNOME or Unity.

** Changed in: nautilus (Ubuntu)
   Status: Triaged => Invalid

** Changed in: nautilus (Ubuntu Xenial)
   Status: Triaged => Invalid

** Changed in: gnome-pkg-tools (Ubuntu)
   Status: Triaged => Invalid

** Changed in: gnome-pkg-tools (Ubuntu Xenial)
   Status: Triaged => Invalid

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

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

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

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

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

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

Title:
  Clicking "Show details" in AO for Nautilus produces "Could not find
  'nautilus.desktop'" error from gnome-software

Status in Ubuntu GNOME:
  Triaged
Status in gnome-pkg-tools package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-software package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in gnome-pkg-tools source package in Xenial:
  Invalid
Status in gnome-shell source package in Xenial:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in nautilus source package in Xenial:
  Invalid

Bug description:
  In the Activities Overview applications list, if I right-click on
  "Files" (AKA Nautilus) and select the "Show details" option gnome-
  software is launched but with the error of "Could not find
  'nautilus.desktop'":

  gnome-software_Could_Not_Find_Nautilus-desktop.png

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Desktop-packages] [Bug 1763837] Re: Update apport hook

[Gunnar Hjalmarsson]

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

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

** Changed in: yelp (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Update apport hook

Status in yelp package in Ubuntu:
  In Progress

Bug description:
  Ubuntu's yelp includes an apport hook that asks users whether they
  have a problem with the help browser or need help performing a task.
  If the user chooses "needs help", they are referred to "Launchpad
  Support": https://answers.launchpad.net/

  That feels to me like it is a bad place to send users. Could we update
  that?

  System Info
  ---
  Ubuntu 18.04
  yelp 3.26.0-1ubuntu2

  /usr/share/apport/package-hooks/source_yelp.py

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

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

[Desktop-packages] [Bug 1756438] Re: Merge 0.62.0-2 from Debian

[Jeremy Bicha]

https://launchpad.net/ubuntu/+source/poppler/0.62.0-2ubuntu1

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

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

Title:
  Merge 0.62.0-2 from Debian

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Please merge poppler 0.62.0-2 from Debian. It contains packaging
  fixes.

  poppler (0.62.0-2) unstable; urgency=medium

* 01-new-gtk-doc.patch: patch from upstream git, fix FTBFS with new
  gtk-doc-tools. Closes: #887525.
* rules: don't hardcode CXXFLAGS when setting -g, instead append to it
  so that we also get dpkg's buildflags.
* rules: pass CFLAGS down to CMake. This should get x32 the required flags
  from dpkg to build with hardening=pie. This was lost during the switch
  to CMake as it doesn't use CFLAGS directly. Closes: #883881.
* debian/tests/test-qt4.cpp: drop, the qt4 build is gone.
* qt-visibility.diff: drop qt4 hunk.
* control: Switch Vcs to salsa.
* Upload to unstable.

   -- Emilio Pozuelo Monfort   Sun, 04 Mar 2018
  11:37:52 +0100

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

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

[Desktop-packages] [Bug 1763874] [NEW] Cherry-pick cairo good patch from 0.63 to improve performance

[Jeremy Bicha]

Public bug reported:

Bug filed for potential SRU purposes.

See Debian bug for details.

** Affects: poppler (Ubuntu)
 Importance: Medium
 Status: Fix Committed

** Affects: poppler (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: bionic

** Bug watch added: Debian Bug tracker #895487
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895487

** Also affects: poppler (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895487
   Importance: Unknown
   Status: Unknown

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

Title:
  Cherry-pick cairo good patch from 0.63 to improve performance

Status in poppler package in Ubuntu:
  Fix Committed
Status in poppler package in Debian:
  Unknown

Bug description:
  Bug filed for potential SRU purposes.

  See Debian bug for details.

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

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

[Desktop-packages] [Bug 1763874] Re: Cherry-pick cairo good patch from 0.63 to improve performance

[Jeremy Bicha]

This regression also affects Ubuntu 17.10 if someone wants to fix this
issue there.

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

Title:
  Cherry-pick cairo good patch from 0.63 to improve performance

Status in poppler package in Ubuntu:
  Fix Committed
Status in poppler package in Debian:
  Unknown

Bug description:
  Bug filed for potential SRU purposes.

  See Debian bug for details.

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

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

[Desktop-packages] [Bug 1525526] Re: evince/atril is excruciatingly slow

[Jeremy Bicha]

Please attach or link to a sample PDF as a test case so we can tell
whether this bug is fixed yet or not.

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

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

Title:
  evince/atril is excruciatingly slow

Status in poppler package in Ubuntu:
  Incomplete

Bug description:
  For image-heavy PDF files, both Atril and Evince are extremely slow
  when rendering the page. 'Slow' being in the region of 5-30s (timed),
  depending on the page, and depending on focus.

  Thumbnails take an equally long time to render.

  The same PDF files opened in muPDF render pages instantly.

  Currently version of libpoppler is 0.30.0-0ubuntu1.

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

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

[Desktop-packages] [Bug 1759625] Re: FFe: Sync gimp 2.10.0~RC1-1 (universe) from Debian experimental (main)

[Erich Eickmeyer]

Unfortunately updating gimp to 2.10 breaks mypaint. Until mypaint is
updated to a version that uses the newer version of libmypaint, we will
be unable to include gimp at this time as it will cause workflow
difficulties with some of our userbase. Releasing gimp 2.10 as an SRU
(so long as mypaint can be updated to 1.3 after its release) would be
the best route. Another option is to encourage the snap version of gimp
2.10 once released for those who want/need it.

At this time, on behalf of the Ubuntu Studio team, we recommend no FFe
for this case as it will break mypaint.

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

Title:
  FFe: Sync gimp 2.10.0~RC1-1 (universe) from Debian experimental (main)

Status in gimp package in Ubuntu:
  New

Bug description:
  Feature Freeze Justification
  
  gimp's last new stable series, 2.8, was released 6 years ago. The new series 
has years of work porting gimp to use gegl more completely, an integrated crash 
report tool, and many more improvements.

  The Gimp development team is so small that I do not expect there to be
  much support at all for gimp 2.8 any more.

  Future
  ==
  If the final gimp 2.10 is not released before Ubuntu 18.04 LTS is, then we 
should do an SRU to update it then.

  The Gimp developers have announced that they will add features to
  future 2.10 releases so that users won't have to wait several years
  like this again.

  Gimp 3.0 will switch to gtk3 (or gtk4).

  Affected Flavors
  
  Ubuntu Studio is the only flavor to include gimp by default.

  Changes
  ===
  This entire file!
  https://git.gnome.org/browse/gimp/tree/NEWS

  Features are described in several blog posts documenting the 2.9
  development releases at https://www.gimp.org/news/

  Changes in the new Debian version
  =
  Uploaded to experimental on request of the Debian maintainer Ari Pollack.

   gimp (2.10.0~RC1-1) experimental; urgency=medium
   .
     * New upstream release candidate (LP: #1759625)
   - Fixes screenshots in GNOME and KDE on Wayland (Closes: #880186)
     (LP: #1739684)
     * Bump dependencies per configure.ac
     * Add new Build-Depends: gegl, glib-networking, libgexiv2-dev,
   libmypaint-dev, libopenjp2-7-dev (Closes: #827083), libopenexr-dev,
   libwebp-dev, mypaint-brushes, python-cairo-dev
     * Depend on xdg-utils for email feature
     * Update debian/libgimp2.0.symbols
     * Drop all patches (except 01_hurd_ftbfs.patch) since they are obsolete
   with the new release

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

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

[Desktop-packages] [Bug 1738984] Re: slowness

[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/1738984

Title:
  slowness

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The boot sometimes fails.
  Many applications, such as Firefox, Chromium, Eclipse and even Nautilus crash 
the system for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.14
  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
  Date: Tue Dec 19 07:19:17 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 
270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Curacao XT [Radeon R7 370 / R9 
270X/370 OEM] [1458:2272]
  InstallationDate: Installed on 2017-08-15 (125 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=d065c847-7bd5-4dda-ad58-74db9d131eb7 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB:bd01/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Dec 19 05:45:23 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPixArt Microsoft USB Optical Mouse MOUSE, id 8
   inputMicrosoft Wired Keyboard 400 KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1714146] Re: Touchpad scrolling not working

[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/1714146

Title:
  Touchpad scrolling not working

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I expect the touchpad to allow to scroll up and down and side to side
  with two fingers, but it works like a mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 31 13:14:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics 
[1043:18fd]
  InstallationDate: Installed on 2017-08-21 (9 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. T300CHI
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9a7bb3ea-4a4d-4467-a0d1-d0f3d1cc7024 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T300CHI.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T300CHI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: T300CHI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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: Wed Aug 30 07:41:43 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1714282] Re: Sorry something went wrong GDBus:

[Launchpad Bug Tracker]

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

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

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

Title:
  Sorry something went wrong GDBus:

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  After applying the latest update the Software-center now opens but
  still has a problem.

  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
  interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell".

  Some of the links to the software doesn't work.
  Some of the buttons of categories doesn't work.
  Updates never show "software to be updated" anymore

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

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

[Desktop-packages] [Bug 1737618] Re: ibus not working in Ubuntu wayland session: traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd420440000+13

[Launchpad Bug Tracker]

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

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

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

Title:
  ibus not working in Ubuntu wayland session:  traps: ibus-ui-gtk3[1565]
  general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in
  libX11.so.6.3.0[7fd42044+134000]

Status in ibus package in Ubuntu:
  Expired

Bug description:
  Hi,

  ibus is not loading neither the applet appearing in Gnome Shell
  wayland session in Ubuntu 17.10. These are the error messages I can
  find:

  :~$ cat /var/log/kern.log |grep ibus*
  Dec 11 02:47:32 HP-LAPTOP kernel: [  356.188579] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
  Dec 11 05:26:54 HP-LAPTOP kernel: [   77.136259] traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]
  Dec 11 05:54:19 HP-LAPTOP kernel: [  138.126513] traps: ibus-ui-gtk3[2277] 
general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in 
libX11.so.6.3.0[7f4b79fce000+134000]
  Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled

  I tried changing input method using im-config to xim and it did not
  yield any positive results. Also, I remember one time, there was a
  segmentation fault happened with ibus which I cannot reproduce again
  on this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus-wayland 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: ndiswrapper
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 02:20:20 2017
  InstallationDate: Installed on 2017-11-22 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1748656] Re: Black Screen of Death after logging into Ubuntu Bionic: "Failed to acquire modesetting permission"

[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/1748656

Title:
  Black Screen of Death after logging into Ubuntu Bionic: "Failed to
  acquire modesetting permission"

Status in xorg package in Ubuntu:
  Expired

Bug description:
  **Specs:** Ubuntu Bionic; NVidia GTX 1070 w/`nvidia-387` drivers.

  **Problem:** After installing a new GTX 1070 and installing
  `nvidia-387`, I get a black screen of death AFTER logging into Ubuntu
  (i.e., the login screen shows up just fine). I'm not even able to
  access other TTYs (the error logs below were retrieved via SSH).

  **/var/log/Xorg.0.log** There doesn't seem to be anything problematic
  in this file.

  **/var/log/Xorg.1.log** The problematic message seems to be:

  [26.455] (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
  [26.455] (EE) NVIDIA(0): Failing initialization of X screen 0
  [26.455] (II) UnloadModule: "nvidia"
  [26.455] (II) UnloadSubModule: "wfb"
  [26.455] (II) UnloadSubModule: "fb"
  [26.455] (EE) Screen(s) found, but none have a usable configuration.
  [26.455] (EE) 
  Fatal server error:
  [26.455] (EE) no screens found(EE) 
  [26.455] (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  [26.455] (EE) Please also check the log file at "/var/log/Xorg.1.log" 
for additional information.
  [26.455] (EE) 
  [26.457] (EE) Server terminated with error (1). Closing log file.

  **Conf files.** Here are my conf files:

  $ cd /usr/share/X11
  $ find . -name "*.conf"
  ./xorg.conf.d/glamoregl.conf
  ./xorg.conf.d/10-amdgpu.conf
  ./xorg.conf.d/40-libinput.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm-outputclass.conf
  ./xorg.conf.d/10-quirks.conf
  ./xorg.conf.d/10-radeon.conf
  ./xorg.conf.d/70-wacom.conf

  I tried deleting all of these except for the nvidia one and rebooting,
  and the error persists. In addition, I tried deleting all of them and
  generating a new one via `sudo X -configure` but get

  $ cd /usr/share/X11$ 
  $ sudo pkill X && sudo X -configure  
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
  _XSERVTransMakeAllCOTSServerListeners: server already running
  (EE) 
  Fatal server error:
  (EE) Cannot establish any listening sockets - Make sure an X server isn't 
already running(EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.

  **kms.** Finally, in case relevant:

  $ lsmod | grep kms
  drm_kms_helper167936  1 nvidia_drm
  syscopyarea16384  1 drm_kms_helper
  sysfillrect16384  1 drm_kms_helper
  sysimgblt  16384  1 drm_kms_helper
  fb_sys_fops16384  1 drm_kms_helper
  drm   356352  6 nvidia_drm,drm_kms_helper

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm 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  387.34  Tue Nov 21 03:09:00 
PST 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)
  .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-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Feb 10 13:14:48 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-25-generic, x86_64: installed
   nvidia-387, 387.34, 4.13.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA 

[Desktop-packages] [Bug 1748660] Re: all bug

[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/1748660

Title:
  all bug

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm having an error when I start ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Feb 10 12:51:14 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 4.1.9, 4.13.0-32-generic, x86_64: installed
   evdi, 4.1.9, 4.4.0-112-generic, x86_64: installed
   openrazer-driver, 1.0.0, 4.13.0-32-generic, x86_64: installed
   openrazer-driver, 1.0.0, 4.4.0-112-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:806d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 930M] [103c:806d]
  InstallationDate: Installed on 2018-02-06 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0483:91d1 STMicroelectronics Sensor Hub
   Bus 001 Device 003: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP ENVY x360 m6 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=a33e7fed-003a-4efd-8fca-025d5fb03453 ro iommu=soft quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 806D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd06/09/2015:svnHewlett-Packard:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHewlett-Packard:rn806D:rvr72.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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

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

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

[Desktop-packages] [Bug 1576215] Re: Network Manager regularly thinks my wifi is a wired device

[tichaona tembo]

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

I have the same problem too I have ubuntu 16.04 on a duo boot with Windows 8. 
Updated my ubuntu on 13/04/18 and now am no longer able to connect to my 
phone's hotspot which would connect automatically before.
Anytime it tries to connect it keeps asking for the password.
Please help.

** Attachment added: "this is what I tried in the terminal but it gives same 
results no WiFi connection"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576215/+attachment/5114713/+files/IMG_20180414_034755.jpg

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

Title:
  Network Manager regularly thinks my wifi is a wired device

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When I boot up my network doesn't automatically connect.  I instead
  see when I click the network manager applet that it's got no Wifi
  devices listed.  It thinks my wireless card is an ethernet device.
  This isn't true and I have no ethernet devices in my system.

  When this situation happens if I issue /etc/init.d/network-manager
  restart it comes back up thinking it's a wireless device and happily
  associates with my saved SSID.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 09:03:13 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160406-0
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-13 (14 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160406-07:32
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID
  CON-PATH   
   wlp58s0  ethernet  connecting (getting IP configuration)  
/org/freedesktop/NetworkManager/Devices/1  Wired connection 1  
1c8c4cab-09d7-4a42-bfc4-aed14caf6a46  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo   loopback  unmanaged  
/org/freedesktop/NetworkManager/Devices/0  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1713564] Re: Repeated problem on login with damaged problem report.

[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/1713564

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Desktop-packages] [Bug 1712510] Re: Slow bootup

[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/1712510

Title:
  Slow bootup

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Could be a grub problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 23 18:51:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0708]
 Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
  InstallationDate: Installed on 2017-08-16 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1bcf:2b8c Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 187c:0528 Alienware Corporation 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware Alienware 15 R2
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=8e3659b0-7baf-41fc-af8b-0f93a2fac71a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.1.5
  dmi.board.name: Alienware 15 R2
  dmi.board.vendor: Alienware
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.1.5:bd09/18/2015:svnAlienware:pnAlienware15R2:pvr1.1.5:rvnAlienware:rnAlienware15R2:rvrX01:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 15 R2
  dmi.product.version: 1.1.5
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 23 18:49:52 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV124
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19528 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.3

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

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

[Desktop-packages] [Bug 1711766] Re: Apps keep crashing

[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/1711766

Title:
  Apps keep crashing

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Every new app i install, even some previously installed keep crashing
  and do not open.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Aug 19 01:37:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0262]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0262]
  InstallationDate: Installed on 2017-08-16 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude E5400
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0D693C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/05/2009:svnDellInc.:pnLatitudeE5400:pvr:rvnDellInc.:rn0D693C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E5400
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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

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

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

[Desktop-packages] [Bug 1709532] Re: Can't get the additional resolution

[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/1709532

Title:
  Can't get the additional resolution

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I only have one screen resolution in display (1024x768).

  I have kernel parameter nomodeset in use as I couldn't install Ubuntu
  without it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.14.1-0ubuntu3.25
  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: Wed Aug  9 10:29:21 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [8086:2a42]
     Subsystem: Intel Corporation Device [8086:2a42]
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=7dac48a4-be03-4308-9a7f-9e2e4231dcee ro nomodeset quiet splash 
vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: GM45+ICH9+775 Series
  dmi.board.vendor: LORD ELECTRONICS CO.,LTD.LORD
  dmi.board.version: I1T65 V0.5
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: bio...@163.com
  dmi.chassis.version: Any Question, Please send mail
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd12/10/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnLORDELECTRONICSCO.,LTD.LORD:rnGM45+ICH9+775Series:rvrI1T65V0.5:cvnbio...@163.com:ct3:cvrAnyQuestion,Pleasesendmail:
  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.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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: Wed Aug  9 10:27:05 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputCompx 2.4G Receiver  KEYBOARD, id 8
   inputCompx 2.4G Receiver  MOUSE, id 9
   inputCompx 2.4G Receiver  KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Desktop-packages] [Bug 1709918] Re: Freezes

[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/1709918

Title:
  Freezes

Status in xorg package in Ubuntu:
  Expired

Bug description:
  comp  freezes repeatedly

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-89-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Aug 10 18:19:20 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2017-06-27 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: 945GCMX-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GCMX-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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: Thu Aug 10 18:16:43 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSEMICCHIP Usb Mouse  MOUSE, id 8
   inputWebcam C170  KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12309 
   vendor DEL
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty2

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

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

[Desktop-packages] [Bug 1712416] Re: Inastalé Driver y el no funcionó

[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/1712416

Title:
  Inastalé Driver y el no funcionó

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Driver tarjeta gráfica no funciona: AMD-RADEON Dual-X R9 280X en
  ubuntu 17.10

  Gracias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Tue Aug 22 14:39:30 2017
  DistroCodename: artful
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713500] Re: installer

[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/1713500

Title:
  installer

Status in xorg package in Ubuntu:
  Expired

Bug description:
  In the installation of google chrome or other programs, the installer
  hangs on some vwersucht but it can not

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug 28 14:58:02 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7480D] [1002:0123]
  InstallationDate: Installed on 2017-08-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=fa5128ac-0b1b-49e5-a14b-b8d3c1b10b12 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XM-DS2
  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.:bvrF6:bd01/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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 Aug 28 14:47:58 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1711205] Re: Xorg freeze

[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/1711205

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Expired

Bug description:
  The screen freezes (with no corruption) when the PC enters standby or screen 
power saving.
  The event does not happen when the PC enters standby or screen power saving 
from the users selection screen.
  Once the problem happens the only way to recover normal operation is to 
switch to another VT (ctrl+alt+f*), login as any user and run "sudo service 
lightdm restart".

  Until some of the last updates, I was experiencing very serious
  episodes of screen corruptions that forced me to disable hardware
  acceleration. Now I can use acceleration with this residual problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.8-041008-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Aug 16 21:11:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GF116 [GeForce GTX 550 
Ti] [1462:809d]
  InstallationDate: Installed on 2016-04-23 (480 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.8-041008-lowlatency 
root=UUID=116cf640-f3d4-409e-bb36-c01299150422 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Aug 16 20:55:06 2017
  xserver.configfile: default
  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.3
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1710322] Re: Xorg freeze

[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/1710322

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Display was wedged but ssh worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 12 00:18:26 2017
  DistUpgraded: 2016-05-31 04:27:01,635 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/580] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb]
  InstallationDate: Installed on 2016-05-30 (438 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Supermicro X10DAi
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/vg--root-lvol0 ro quiet splash nomdmonddf nomdmonisw 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (437 days ago)
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10DAI
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  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.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: X10DAi
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 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: Sat Aug 12 00:07:34 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Trackball   MOUSE, id 8
   inputLITE-ON Technology USB NetVista Full Width Keyboard. KEYBOARD, 
id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1710080] Re: sysem is all of a sudden very slow

[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/1710080

Title:
  sysem is all of a sudden very slow

Status in xorg package in Ubuntu:
  Expired

Bug description:
  the system is all of a sudden  very slow and unresponsive

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   [  OK  ] Started WPA supplicant.
   [  OK  ] Started Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1).
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Restore mixer settings from saved values..
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  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 Aug 10 23:52:07 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.40, 4.4.0-89-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1650]
  InstallationDate: Installed on 2016-11-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=0ee545f7-07fb-4a5a-8d44-ba5697d6b189 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1650
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 07.26
  dmi.chassis.asset.tag: CNU1390R4H
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd03/21/2012:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr067F21242F1620100:rvnHewlett-Packard:rn1650:rvrKBCVersion07.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm4 Notebook PC
  dmi.product.version: 067F21242F1620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Aug 10 23:35:16 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5265 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.3

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

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

[Desktop-packages] [Bug 1606901] Re: Clicking "Show details" in AO for Nautilus produces "Could not find 'nautilus.desktop'" error from gnome-software

[Jeremy Bicha]

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

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

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

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

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

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

Title:
  Clicking "Show details" in AO for Nautilus produces "Could not find
  'nautilus.desktop'" error from gnome-software

Status in Ubuntu GNOME:
  Triaged
Status in gnome-pkg-tools package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-software package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in gnome-pkg-tools source package in Xenial:
  Invalid
Status in gnome-shell source package in Xenial:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in nautilus source package in Xenial:
  Invalid

Bug description:
  In the Activities Overview applications list, if I right-click on
  "Files" (AKA Nautilus) and select the "Show details" option gnome-
  software is launched but with the error of "Could not find
  'nautilus.desktop'":

  gnome-software_Could_Not_Find_Nautilus-desktop.png

  I am running Ubuntu GNOME 16.04 with GNOME 3.20.

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

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

[Desktop-packages] [Bug 1763846] 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/1763846/+attachment/5114577/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763846/+attachment/5114586/+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/1763846

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This was an automatically generated error report.  I didn't see
  anything that appeared wrong.

  This is an upgrade (done today) of 16.04.4 on a Lenovo T430s with 16
  GB RAM.

  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.13.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 13 14:59:05 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  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:
   ?? () 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: Upgraded to bionic on 2018-04-13 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1763848] Re: package texlive-fonts-extra-doc 2015.20160320-1 failed to install/upgrade: intentando sobreescribir `/usr/share/doc/texlive-doc/latex/mweights/README', que está ta

[Andres F. Caicedo]

Cuando intento solucionar las dependencia ocurre un error relacionado
con la ruptura de tuberías.

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

Title:
  package texlive-fonts-extra-doc 2015.20160320-1 failed to
  install/upgrade: intentando sobreescribir `/usr/share/doc/texlive-
  doc/latex/mweights/README', que está también en el paquete texlive-
  latex-extra-doc 2015.20160320-1

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  He intentado actualizar de 16.04 a 17.10 y ha ocurrido un error. Antes
  de actualizar hice algo relacionado con kubuntu. Hubo conflicto con
  las dependencias.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: texlive-fonts-extra-doc 2015.20160320-1
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr 13 15:25:56 2018
  DpkgTerminalLog:
   Preparando para desempaquetar 
.../texlive-fonts-extra-doc_2017.20170818-1_all.deb ...
   Desempaquetando texlive-fonts-extra-doc (2017.20170818-1) sobre 
(2015.20160320-1) ...
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/texlive-fonts-extra-doc_2017.20170818-1_all.deb 
(--unpack):
intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/mweights/README', que está también en el 
paquete texlive-latex-extra-doc 2015.20160320-1
  ErrorMessage: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/mweights/README', que está también en el 
paquete texlive-latex-extra-doc 2015.20160320-1
  InstallationDate: Installed on 2016-07-06 (646 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  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: texlive-extra
  Title: package texlive-fonts-extra-doc 2015.20160320-1 failed to 
install/upgrade: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/mweights/README', que está también en el 
paquete texlive-latex-extra-doc 2015.20160320-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760144] Re: Wrong size of icon, if launcher put on desktop

[Coeur Noir]

( sorry, postimg.org is now postimg.cc so here are new links to pictures
)

https://postimg.cc/image/6t98217zt/

https://postimg.cc/image/cu6wz42bt/

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

Title:
  Wrong size of icon, if launcher put on desktop

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  as off Firefox 59, if a launcher is put on desktop, its icon size is
  too large.

  The culprit may be a missing icons folder ?

  Testing on a liveUSB of Ubuntu 16.04.1 here I get :
  https://postimg.org/image/6t98217zt/
  left window is the liveUSB, right window is my actual 16.04 installation.

  Right after upgrading FF to newer version, I get :
  https://postimg.org/image/cu6wz42bt/
  left window is still the liveUSB.
  « icons » folder disappeared while upgrading FF
  and then instantly icon get much larger on desktop.

  It's not unity related : see
  https://bugzilla.mozilla.org/show_bug.cgi?id=1446262 or https
  ://ubuntu-mate.community/t/firefox-v59-has-a-ridiculously-large-
  static-desktop-icon/16205/3 or https://forum.ubuntu-
  fr.org/viewtopic.php?id=2023636

  The workarounds provided by those topics are not reliable fixes.

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

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

[Desktop-packages] [Bug 1763848] [NEW] package texlive-fonts-extra-doc 2015.20160320-1 failed to install/upgrade: intentando sobreescribir `/usr/share/doc/texlive-doc/latex/mweights/README', que está

[Andres F. Caicedo]

Public bug reported:

He intentado actualizar de 16.04 a 17.10 y ha ocurrido un error. Antes
de actualizar hice algo relacionado con kubuntu. Hubo conflicto con las
dependencias.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: texlive-fonts-extra-doc 2015.20160320-1
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Fri Apr 13 15:25:56 2018
DpkgTerminalLog:
 Preparando para desempaquetar 
.../texlive-fonts-extra-doc_2017.20170818-1_all.deb ...
 Desempaquetando texlive-fonts-extra-doc (2017.20170818-1) sobre 
(2015.20160320-1) ...
 dpkg: error al procesar el archivo 
/var/cache/apt/archives/texlive-fonts-extra-doc_2017.20170818-1_all.deb 
(--unpack):
  intentando sobreescribir `/usr/share/doc/texlive-doc/latex/mweights/README', 
que está también en el paquete texlive-latex-extra-doc 2015.20160320-1
ErrorMessage: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/mweights/README', que está también en el 
paquete texlive-latex-extra-doc 2015.20160320-1
InstallationDate: Installed on 2016-07-06 (646 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
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: texlive-extra
Title: package texlive-fonts-extra-doc 2015.20160320-1 failed to 
install/upgrade: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/mweights/README', que está también en el 
paquete texlive-latex-extra-doc 2015.20160320-1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package texlive-fonts-extra-doc 2015.20160320-1 failed to
  install/upgrade: intentando sobreescribir `/usr/share/doc/texlive-
  doc/latex/mweights/README', que está también en el paquete texlive-
  latex-extra-doc 2015.20160320-1

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  He intentado actualizar de 16.04 a 17.10 y ha ocurrido un error. Antes
  de actualizar hice algo relacionado con kubuntu. Hubo conflicto con
  las dependencias.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: texlive-fonts-extra-doc 2015.20160320-1
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Fri Apr 13 15:25:56 2018
  DpkgTerminalLog:
   Preparando para desempaquetar 
.../texlive-fonts-extra-doc_2017.20170818-1_all.deb ...
   Desempaquetando texlive-fonts-extra-doc (2017.20170818-1) sobre 
(2015.20160320-1) ...
   dpkg: error al procesar el archivo 
/var/cache/apt/archives/texlive-fonts-extra-doc_2017.20170818-1_all.deb 
(--unpack):
intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/mweights/README', que está también en el 
paquete texlive-latex-extra-doc 2015.20160320-1
  ErrorMessage: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/mweights/README', que está también en el 
paquete texlive-latex-extra-doc 2015.20160320-1
  InstallationDate: Installed on 2016-07-06 (646 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  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: texlive-extra
  Title: package texlive-fonts-extra-doc 2015.20160320-1 failed to 
install/upgrade: intentando sobreescribir 
`/usr/share/doc/texlive-doc/latex/mweights/README', que está también en el 
paquete texlive-latex-extra-doc 2015.20160320-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1763648] Re: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04

[Brian Murray]

*** This is an automated message ***

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

** Summary changed:

- nvidia-304 (304.137) missing in Ubuntu 18.04
+ [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04

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

Bug description:
  nvidia-304 is not available in the Ubuntu 18.04. Newer versions are
  available but I have an old nVidia 7600 GT, so I need 304.137.

  I searched online and found that at
  https://answers.launchpad.net/ubuntu/bionic/amd64/nvidia-304/304.137-0ubuntu2
  it has Status: Deleted :(

  Could you please pack this for the new release of Ubuntu?

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

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

[Desktop-packages] [Bug 1101134] Re: Incorrect delimiter on pt_BR

[Gunnar Hjalmarsson]

Nope. pt_BR refers to the Brazilian latin1 locale, and if that has not
been generated (it hasn't usually), the system falls back to the C
locale.

$ LC_TIME=C date +%x
04/14/18
$ LC_TIME=pt_BR.UTF-8 date +%x
14/04/2018

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

Title:
  Incorrect delimiter on pt_BR

Status in GLibC:
  Fix Released
Status in langpack-locales package in Ubuntu:
  Fix Released

Bug description:
  The delimiter is incorrect on pt_BR locale.

  $ export LANG=pt_BR
  $ date +%x
  17-01-2013

  According to Wikipedia
  (http://en.wikipedia.org/wiki/Date_format_by_country), the delimiter
  are slashes, and not hyphens.

  -- version info --
  $ lsb_release -rd
  Description:Ubuntu 12.04 LTS
  Release:12.04

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

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

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

[Apport retracing service]

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

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 #1754445, 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/1763850/+attachment/5114605/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754445
   gnome-shell crashed with SIGSEGV in cogl_object_unref() from 
iter_remove_or_steal() from g_hash_table_iter_remove() from 
st_texture_cache_evict_icons() from on_icon_theme_changed()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  No idea where this bug comes from. I was just browsing in Firefox for
  another bug, about the login screen graphics not being rendered
  properly, i.e. characters being skipped and other graphical items
  looking funky.

  Freshly installed 18.04 beta2 from 2018-04-06, today.

  The system was fully updated before I started searching for the other
  bug when the crash report appeared on the screen.

  I'm on a Acer Aspire V5 laptop with an i7-3517U CPU, 8 gb ram, ssd and nvidia 
optimus 620m.
  Using either the nouveau (not the closed nvidia) driver or intel graphics, 
depends on where I look in the GUI, not sure what commands to run to positively 
determine what's being used.

  If you need more info don't hesitate to ask, and if you don't mind,
  please point me in a direction as to how I can get that info for you
  (maybe a command to run, or some search engine terms).

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  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: GNOME-Greeter:GNOME
  Date: Fri Apr 13 22:11:33 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-13 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f9d56c2de00 :mov
(%rdi),%rax
   PC (0x7f9d56c2de00) 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:
   cogl_object_unref () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   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
  Title: gnome-shell crashed with SIGSEGV in cogl_object_unref()
  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/1763850/+subscriptions

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

[Desktop-packages] [Bug 1763806] Re: Running breaks gnome-shell monitor configurations and vice-versa

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-bionic-3223.1

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

Title:
  Running breaks gnome-shell monitor configurations and vice-versa

Status in unity-settings-daemon package in Ubuntu:
  In Progress

Bug description:
  Mutter introduced a new format of monitors.xml (version 2), unity
  (-settings-daemon) still relies on the old format, so we need to
  separate the two files and migrate them if needed.

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

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

[Desktop-packages] [Bug 1763580] [NEW] Xorg crash

[elcomandantetibi]

Public bug reported:

Crash occurs every time when booting from Xubuntu 18.04 installation
stick and choosing "Install Xubuntu". Shortly after selecting "Install
Xubuntu", the installer is started, the installation screen is visible
for a few seconds, then the display quickly blanks and drops the user
into a frozen view of the virtual terminal. Shortly thereafter, a
Xubuntu session is automatically started, similarly to having chosen
"Try Xubuntu without installing". Executing "Install Xubuntu" from the
desktop does successfully start the ubiquity installer.

Verifying the installation logs under /var/log/installer shows Xorg as
having crashed with error:

xf860OpenConsole: Switching VT failed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
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
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperVersion: 1.393
CompositorRunning: None
CurrentDesktop: XFCE
Date: Fri Apr 13 05:42:46 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2063]
LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180411)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
 Bus 001 Device 003: ID 04f2:0408 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corp.
dmi.board.vendor: Intel corporation
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 N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic crash ubuntu

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Crash occurs every time when booting from Xubuntu 18.04 installation
  stick and choosing "Install Xubuntu". Shortly after selecting "Install
  Xubuntu", the installer is started, the installation screen is visible
  for a few seconds, then the display quickly blanks and drops the user
  into a frozen view of the virtual terminal. Shortly thereafter, a
  Xubuntu session is automatically started, similarly to having chosen
  "Try Xubuntu without installing". Executing "Install Xubuntu" from the
  desktop does successfully start the ubiquity installer.

  Verifying the installation logs under /var/log/installer shows Xorg as
  having crashed with error:

  xf860OpenConsole: Switching VT failed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.393
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Apr 13 05:42:46 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2063]
  LiveMediaBuild: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180411)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 003: ID 04f2:0408 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   

[Desktop-packages] [Bug 1763589] Re: Tried to start Chromium

[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/1763589/+attachment/5113366/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763589/+attachment/5113375/+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/1763589

Title:
  Tried to start Chromium

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is what I get trying to start it from the console

  Gtk-Message: Failed to load module "canberra-gtk-module"
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ATTENTION: default value of option force_s3tc_enable overridden by 
environment.
  Gkr-Message: secret service operation failed: An AppArmor policy prevents 
this sender from sending this message to this recipient; type="method_call", 
sender=":1.81" (uid=1000 pid=4049 
comm="/snap/chromium/274/usr/lib/chromium-browser/chromi" 
label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" 
member="Ping" error name="(unset)" requested_reply="0" 
destination="org.freedesktop.secrets" (uid=1000 pid=1262 
comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined")

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  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: GNOME-Greeter:GNOME
  Date: Fri Apr 13 01:31:55 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-13 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /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/1763589/+subscriptions

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

[Desktop-packages] [Bug 1760073] Re: No network from suspend resume

[Kai-Heng Feng]

How did you suspend the machine?

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

Title:
  No network from suspend resume

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following a resume from suspend - no network available on machine.

  Originally reported when using 4.15.0-10-generic, recent update to
  kernel 4.15.0-15-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-0ubuntu1
  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: XFCE
  Date: Fri Mar 30 11:53:22 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  ---
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags: bionic third-party-packages
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  ---
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-08 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Tags:  bionic
  Uname: Linux 4.15.0-10-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/lightdm/+bug/1760073/+subscriptions

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

[Desktop-packages] [Bug 1762722] Re: Ubuntu 18.04 LTS Free Culture Showcase community wallpapers

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-wallpapers - 18.04.1-0ubuntu1

---
ubuntu-wallpapers (18.04.1-0ubuntu1) bionic; urgency=medium

  * debian/control: Remove daily-packaging / bileto comment; this is manually
uploaded.
  * Ubuntu Free Culture Showcase winners for 17.10 (LP: #1762722)
  * debian/rules: Use dh_missing --fail-missing - dh_install --fail-missing is
going to be removed in compat 12.
  * po/POTFILES.in, po/ubuntu-wallpapers.pot: Update .pot file, forgotten for
several cycles!

 -- Iain Lane   Thu, 12 Apr 2018 13:36:57 +0100

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 18.04 LTS Free Culture Showcase community wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released

Bug description:
  Attached are the winning entries from the FCS wallpaper competition
  for 18.04 LTS.

  These have been resized to n x 2160 pixels at 72x72 dpi.
  They are all named Image_Title_by_Author_Name.jpg and are all jpgs.
  JPG should result in smaller image sizes compared to PNG for this type of 
content.

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

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

[Desktop-packages] [Bug 1759699] Re: gnome-calendar crashed with SIGSEGV in gtk_image_clear()

[Wayne Stark]

Calendar crashed on me without doing anything, straight after login.

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

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  Steps:

  1. Start Calendar
  2. Add a Google account
  3. Notice that the newly-created Google account does not appear in Calendar
  4. Close Calendar
  5. It crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 23:56:13 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-10-02 (177 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x7fe0719fc517 :mov
0x28(%rdi),%rbp
   PC (0x7fe0719fc517) ok
   source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_image_clear () from /usr/lib/x86_64-linux-gnu/libgtk-3.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: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1763578] [NEW] gpu-manager syslog reported errors

[Dmitriy Geels]

Public bug reported:

syslog contains following error messages:

Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: /etc/modprobe.d is not a 
file
   Apr 13 10:31:36 dmig-Inspiron-5379 
gpu-manager[858]: Error: can't open /lib/modules/4.15.0-15-generic/updates/dkms
Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: Error: can't open 
/lib/modules/4.15.0-15-generic/updates/dkms

None of them represent a real error, gpu-manager shouldn't complain
about this

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-drivers-common 1:0.5
Uname: Linux 4.16.2-041602-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 13 12:36:47 2018
InstallationDate: Installed on 2018-03-27 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  gpu-manager syslog reported errors

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

Bug description:
  syslog contains following error messages:

  Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: /etc/modprobe.d is not a 
file
   Apr 13 10:31:36 dmig-Inspiron-5379 
gpu-manager[858]: Error: can't open /lib/modules/4.15.0-15-generic/updates/dkms
  Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: Error: can't open 
/lib/modules/4.15.0-15-generic/updates/dkms

  None of them represent a real error, gpu-manager shouldn't complain
  about this

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-drivers-common 1:0.5
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 12:36:47 2018
  InstallationDate: Installed on 2018-03-27 (16 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1698282] Re: Totem uses dramatically higher CPU than any other video player

[Daniel van Vugt]

Upstream bug (possibly related) attached:
https://github.com/intel/intel-vaapi-driver/issues/379

** Also affects: intel-vaapi-driver (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: github.com/intel/intel-vaapi-driver/issues #379
   https://github.com/intel/intel-vaapi-driver/issues/379

** Also affects: libva via
   https://github.com/intel/intel-vaapi-driver/issues/379
   Importance: Unknown
   Status: Unknown

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

Title:
  Totem uses dramatically higher CPU than any other video player

Status in Clutter GStreamer Bindings:
  Confirmed
Status in Clutter GTK:
  Confirmed
Status in Gstreamer1.0:
  Fix Released
Status in Libva:
  Unknown
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in intel-vaapi-driver package in Ubuntu:
  New
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem uses dramatically higher CPU than any other video player.

  Example 1: software playback under Gnome Shell Wayland:

  totem: 120% (but drops to 80% in Unity7)
  mplayer: 40%
  vlc: 40%
  [all are using ffmpeg for decoding]

  Example 2: hardware-accelerated playback under Gnome Shell Xorg:

  totem: 11%
  gst-play-1.0: 3%
  [both are using gstreamer-vaapi for decoding]

  Since the decoding libraries are theoretically the same it sounds like
  totem's performance problems might be in its rendering path.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/clutter-gst/+bug/1698282/+subscriptions

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

[Desktop-packages] [Bug 1763607] 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/1763607/+attachment/5113449/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763607/+attachment/5113458/+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/1763607

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

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

Bug description:
  Added Steam games librery

  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
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 13 09:55:32 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-04-05 (8 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  ProcCmdline: gnome-control-center background
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x56088a8ba311:mov0x90(%rbp),%rsi
   PC (0x56088a8ba311) 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 /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/1763607/+subscriptions

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

[Desktop-packages] [Bug 1763612] 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/1763612/+attachment/5113464/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763612/+attachment/5113474/+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/1763612

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This happened after I booted

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Apr 11 17:19:32 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-22 (202 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170922)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.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/1763612/+subscriptions

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

[Desktop-packages] [Bug 1763587] 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/1763587/+attachment/5113347/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763587/+attachment/5113356/+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/1763587

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  gnome-shell:
Installed: 3.28.0-0ubuntu5
Candidate: 3.28.0-0ubuntu5

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  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: GNOME-Greeter:GNOME
  Date: Thu Apr 12 09:36:54 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-28 (15 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /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/1763587/+subscriptions

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

[Desktop-packages] [Bug 1698282] Re: Totem uses dramatically higher CPU than any other video player

[Bug Watch Updater]

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

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

Title:
  Totem uses dramatically higher CPU than any other video player

Status in Clutter GStreamer Bindings:
  Confirmed
Status in Clutter GTK:
  Confirmed
Status in Gstreamer1.0:
  Fix Released
Status in Libva:
  New
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in intel-vaapi-driver package in Ubuntu:
  New
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem uses dramatically higher CPU than any other video player.

  Example 1: software playback under Gnome Shell Wayland:

  totem: 120% (but drops to 80% in Unity7)
  mplayer: 40%
  vlc: 40%
  [all are using ffmpeg for decoding]

  Example 2: hardware-accelerated playback under Gnome Shell Xorg:

  totem: 11%
  gst-play-1.0: 3%
  [both are using gstreamer-vaapi for decoding]

  Since the decoding libraries are theoretically the same it sounds like
  totem's performance problems might be in its rendering path.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/clutter-gst/+bug/1698282/+subscriptions

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

[Desktop-packages] [Bug 1763591] [NEW] dlmopen glib2.0 crashed in g_variant_lookup_value

[bin]

Public bug reported:

when dlmopen glib2.0 and the program is linked with pthread, glib2.0 crashed in 
g_variant_lookup_value when dlmopen with 
LM_ID_NEWLM

following is the poc:

#define _GNU_SOURCE
#include 
#include 
#include 
#include 


int main(int argc, char*argv[])
{
  char buf[4096] = {0};
  pthread_attr_t attr;

  pthread_attr_init();
  snprintf(buf, sizeof(buf), "/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2");
  dlmopen(-1, buf, RTLD_NOW|RTLD_LOCAL);
  return 0;
}

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  dlmopen glib2.0 crashed in g_variant_lookup_value

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  when dlmopen glib2.0 and the program is linked with pthread, glib2.0 crashed 
in g_variant_lookup_value when dlmopen with 
  LM_ID_NEWLM

  following is the poc:

  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 

  
  int main(int argc, char*argv[])
  {
char buf[4096] = {0};
pthread_attr_t attr;

pthread_attr_init();
snprintf(buf, sizeof(buf), "/lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2");
dlmopen(-1, buf, RTLD_NOW|RTLD_LOCAL);
return 0;
  }

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

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

[Desktop-packages] [Bug 1763632] 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/1763632/+attachment/5113522/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763632/+attachment/5113531/+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/1763632

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Yo no he percibido el error

  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
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 10:59:48 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-02-19 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6898e85fad:mov0x8(%rdi),%eax
   PC (0x7f6898e85fad) 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 lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1762360] Re: EVGA GeForce GTX 1060 - nouveau symbol lookup error causes X failure

[Ryan Hoover]

** Tags added: ubuntustudio-beta

** Tags added: bionic

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

Title:
  EVGA GeForce GTX 1060 - nouveau symbol lookup error causes X failure

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Fresh install of Ubuntu Studio 18.04 - xorg crashes just after login
  and returns to lightdm.  Moving to a TTY and attempting to startx
  returns the following:

  /usr/lib/Xorg: symbol lookup error:
  /usr/lib/xorg/modules/drivers/nouveau_drv.so: undefined symbol:
  exaGetPixmapDriverPrivate

  Installing nvidia-driver-390 and rebooting resolves the issue.

  apt update && apt full-upgrade performed @ 03:54 EDT (I didn't think
  to check which versions the updates were at, as there were something
  like 145 of them)

  GPU:EVGA Nvidia GeForce GTX 1060 6GB
  Kernel: 4.15.0-13-lowlatency
  OS: Ubuntu Studio 18.04 Bionic
  CPU:Intel Core i5-4690K @ 3.5GHz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1762360/+subscriptions

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

Re: [Desktop-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate

[Iain Lane]

On Thu, Apr 12, 2018 at 12:41:30PM -, Jeremy Bicha wrote:
> Resetting to New since the g-s-d commits have been accepted upstream.
> They are the first 4 commits for 12 Apr, 2018.
> 
> https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commits/master

The new version is to automatically select this policy if systemd
supports it, right?

What makes systemd answer yes to that question? Is there a chance that
existing machines could start using this and it could be broken for
them?

Cheers,

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

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

Title:
  FFe: Support suspend-then-hibernate

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Suspend to hibernate is a new feature that will put the system into
  hibernate after a period of time spent in the system's supported sleep
  state.  This mode will be used on some systems that take suspend to
  idle in the future with Ubuntu 18.04.

  This feature is available in upstream systemd from these two commits.
  
https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703
  
https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5
  This is accepted upstream.

  The policy needs to be made available to gnome from this commit:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9
  As of 3/15/2018 this is not yet accepted or rejected.

  The new mode is not selected by default, but that can be changed from a 
separate policy package.
  The policy for the amount of time spent in S3/S2I can be configured by a 
separate package.

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

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

[Desktop-packages] [Bug 1762292] Re: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main)

[Jeremy Bicha]

This bug was fixed in the package appstream - 0.12.0-3
Sponsored for Matthias Klumpp (ximion)

---
appstream (0.12.0-3) unstable; urgency=medium

  * load-desktop-data.patch: Load desktop file data properly again

 -- Matthias Klumpp   Fri, 06 Apr 2018 21:30:08 +0200

appstream (0.12.0-2) unstable; urgency=medium

  * Make autopkgtest work again
  * Update d/copyright (Closes: #894856)
  * icon config: Pull in non-HiDPI config for large icons
if large-icon HiDPI config is installed

 -- Matthias Klumpp   Fri, 06 Apr 2018 14:12:26 +0200

appstream (0.12.0-1) unstable; urgency=medium

  * New upstream version: 0.12.0
  * Drop all patches: Applied upstream
  * Update .symbols file
  * d/rules: Drop obsolete --parallel flag
  * Add APT config snippet packages for an easy way of enabling
icon downloads for different sizes and HiDPI.

 -- Matthias Klumpp   Wed, 04 Apr 2018 18:36:26 +0200

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

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

Title:
  FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main)

Status in appstream package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Please sync appstream 0.12.0-3 (main) from Debian unstable (main)

  This introduces a new feature release pretty late in the cycle, so it
  is something to more carefully consider. Even if it's very late, I do
  think upgrading this package in Bionic is a good idea though.

  First of all, it makes upgrading the appstream-generator package to version 
0.7.1-3 possible, allowing people to generate much better and smaller metadata 
for Debian and Ubuntu repositories (and this is what sparked the creation of 
this sync request).
  But there are also many other good reasons.

  This is the NEWS file for the new release, with explanations on why we
  want the respective changes (I shuffled some entries around to form
  logical groups) :

  Version 0.12.0
  ~~
  Released: 2018-04-04

  Features:
   * Implement release types
   * qt: Support release types

  This adds a new feature to the AppStream specification and
  libappstream that allows release metadata to be tagged as
  "development" or "stable" releases. Nothing in Ubuntu uses this, so
  adding will not break anything, but having this in the LTS release
  means upstream projects can use this feature more easily, and Ubuntu
  will understand metadata containing it.

   * Update static data lists
   * spdx: Add some compatibility workarounds for SPDX 3.0
   * validator: Validate SPDX license expressions for metadata_license

  This updates the SPDX[1] license lists to version 3.0 and adds some 
compatibility glue to libappstream to parse the new license strings introduced 
in SPDX 3.0. This is very useful to have, because many projects will start 
using the new identifier, and it makes sense for AppStream in Ubuntu to be 
ready for that.
  Furthermore, it prevents errors from people using the new IDs with older 
AppStream versions (unfortunately, SPDX 3.0 broke the format, AppStream speaks 
all flavors of SPDX now, though)

  [1]: https://spdx.org/licenses/

   * apt: Add config snippets to enable icon downloads

  This results in an easy way for users as well as software centers to
  enable the download of application icon tarballs via APT just by
  installing a sepecific package (apt-icons-*). This is quite neat to
  make icon downloads configurable easily, and also have a central place
  for the APT configuration. The new packages are used in Debian already
  by GNOME Software and Plasma Dicover. All existing solutions to enable
  icons work though, this is an optional change.

   * Implement support for requires/recommends
   * Add recommends/requires data to the cache
   * Add a quick way to check if a version satisfies an AsRelation requirement
   * yaml: Make Requires/Recommends data more compact and easier to emit
   * Default to format version 0.12
   * validator: Validate requires/recommends tags

  This adds a new feature to allow AppStream components to require other
  components or system resources (e.g. minimal memory sizes). Nothing
  uses this yet, due to that this feature also can't break anything.
  Having it in the LTS means that upstream projects can already add the
  metadata easily though and have it validated.

   * ascli: Properly document the --no-net flag
   * ascli: Allow to disable network access via an environment variable

  This is useful in a package build environment where AppStream metadata is 
validated and the distributor wants to make sure appstreamcli doesn't try to 
access the network without changing upstream's code and passing the --no-net 
flag explicitly somewhere.
  Nice feature to have, no risk potential to break 

[Desktop-packages] [Bug 1763628] [NEW] autopkgtests are failing on valgrind

[Iain Lane]

Public bug reported:

This happens now

autopkgtest [07:42:07]: test make-check: ---]
autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - results - - - - - 
- - - - -
make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368
autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - stderr - - - - - 
- - - - -
==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
==9257==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==9257==by 0x18EF2D: xmalloc (in /bin/bash)
==9257==by 0x18898A: set_default_locale (in /bin/bash)
==9257==by 0x137E66: main (in /bin/bash)
==9257== 
==9505== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
==9505==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==9505==by 0x18EF2D: xmalloc (in /bin/bash)
==9505==by 0x18898A: set_default_locale (in /bin/bash)
==9505==by 0x137E66: main (in /bin/bash)
==9505== 
autopkgtest [07:42:08]:  summary
make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368

>From http://autopkgtest.ubuntu.com/packages/c/colord/bionic/amd64 it
looks like it's cause by the new glib2.0, but I just tried on my machine
without that package and it still happened.

Could you have a look please? Looks like it might not actually be
colord's fault here, but maybe we want to reconsider running under
valgrind at least for the autopktests?

** Affects: colord (Ubuntu)
 Importance: Undecided
 Assignee: Chris Halse Rogers (raof)
 Status: New

** Changed in: colord (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

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

Title:
  autopkgtests are failing on valgrind

Status in colord package in Ubuntu:
  New

Bug description:
  This happens now

  autopkgtest [07:42:07]: test make-check: ---]
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - results - - - - 
- - - - - -
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368
  autopkgtest [07:42:08]: test make-check:  - - - - - - - - - - stderr - - - - 
- - - - - -
  ==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9257==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9257==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9257==by 0x18898A: set_default_locale (in /bin/bash)
  ==9257==by 0x137E66: main (in /bin/bash)
  ==9257== 
  ==9505== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368
  ==9505==at 0x4C2FB0F: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==9505==by 0x18EF2D: xmalloc (in /bin/bash)
  ==9505==by 0x18898A: set_default_locale (in /bin/bash)
  ==9505==by 0x137E66: main (in /bin/bash)
  ==9505== 
  autopkgtest [07:42:08]:  summary
  make-check   FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely 
lost in loss record 67 of 368

  From http://autopkgtest.ubuntu.com/packages/c/colord/bionic/amd64 it
  looks like it's cause by the new glib2.0, but I just tried on my
  machine without that package and it still happened.

  Could you have a look please? Looks like it might not actually be
  colord's fault here, but maybe we want to reconsider running under
  valgrind at least for the autopktests?

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

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

[Desktop-packages] [Bug 1763645] ThreadStacktrace.txt

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1763645/+attachment/5113633/+files/ThreadStacktrace.txt

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Invalid

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

Title:
  Xorg crashed with signal 7

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

Bug description:
  after turn on system...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-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-15ubuntu2)
  .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-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Apr 13 12:56:41 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd]
  InstallationDate: Installed on 2017-09-02 (222 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=1
  Signal: 7
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: Xorg crashed with signal 7
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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: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

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

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

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

[Launchpad Bug Tracker]

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

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

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

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

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

Bug description:
  Occurred when trying to turn on Mobile broadband connection. I think
  this is the first of these kind of bug reported in Ubuntu 17.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 13:50:45 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-09 (12 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center network
  SegvAnalysis:
   Segfault happened at: 0x55dd0bf3ed13 : 
jmpq   *0xb8(%rax)
   PC (0x55dd0bf3ed13) ok
   source "*0xb8(%rax)" ok
   SP (0x7ffed7f73968) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   net_device_get_find_connection ()
   ?? ()
   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: gnome-control-center crashed with SIGSEGV in 
net_device_get_find_connection()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)
  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/1725604/+subscriptions

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

[Desktop-packages] [Bug 1763171] Re: graphic card driver packages cant be installed

[Timo Aaltonen]

intel drivers are installed by default, you shouldn't need to install
any external packages

and we don't support doing that, anyway

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

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

Title:
  graphic card driver packages cant be installed

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  i used intel graphics update tool for linux, couldnt install packages,
  i also tried lots of command lines from various guides but still the
  problem cant be solved. What i could understand is that maybe intel
  doesnt support this old drivers for linux? because i had windows on
  this laptop (Lenovo Thinkpad T410)earlier and everything was fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Thu Apr 12 00:29:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2018-03-19 (23 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: LENOVO 25184HU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=566b3489-a039-4407-a87c-e4ee4bbb0565 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET65WW (1.25 )
  dmi.board.name: 25184HU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET65WW(1.25):bd06/07/2010:svnLENOVO:pn25184HU:pvrThinkPadT410:rvnLENOVO:rn25184HU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 25184HU
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91+git1804061830.cb850c~oibaf~x
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1804111930.bd9539~oibaf~x
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1804111930.bd9539~oibaf~x
  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: Thu Apr 12 00:23: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

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

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

[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button to Right (left-handed) in Settings

[Timo Aaltonen]

x-x-i-libinput 0.27.1 should fix that, it's on the upload queue

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

Title:
  Cannot switch mouse primary button to Right (left-handed) in Settings

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured 
for left handed use. That is the mouse primary button being switched to the 
right. GCC doesn't seem to work for this now. I don't know if it's related to 
evdev or what.
  Held back reporting this in case it was fixed by changes overnight. Updated 
this morning and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 23 07:07:02 2018
  InstallationDate: Installed on 2018-01-19 (62 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1763645] Xorg crashed with signal 7

[Apport retracing service]

StacktraceTop:
 ?? () from 
/tmp/apport_sandbox_blobpndl/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so
 ?? ()
 ?? ()
 ?? ()
 CMapEnterVT (pScrn=0x55ae7c8a5ce0) at 
../../../../../../hw/xfree86/common/xf86cmap.c:475

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

Title:
  Xorg crashed with signal 7

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

Bug description:
  after turn on system...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-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-15ubuntu2)
  .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-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Apr 13 12:56:41 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
   virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85cd]
  InstallationDate: Installed on 2017-09-02 (222 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=a5d262b4-1b0f-4856-9935-f6a7f6d6d406 ro quiet splash vt.handoff=1
  Signal: 7
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: Xorg crashed with signal 7
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2003
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2003:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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: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

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

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

[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.

[Adrian]

Since the older bug (1685502) was marked duplicate in favor of this one,
I'll just copy a few related links (aside from the listed duplicates)
that might be of interest:

https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/938380
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1652454
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1675580
https://ubuntu-mate.community/t/17-04-nm-applet-works-fine-but-shows-2-icons-in-the-system-tray/12020/22
https://github.com/mate-desktop/mate-panel/issues/539

Would be nice to finally see this fixed across all Ubuntu flavors, but
maybe that's not possible due to different approaches (panels).

** Bug watch added: github.com/mate-desktop/mate-panel/issues #539
   https://github.com/mate-desktop/mate-panel/issues/539

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

Title:
  Two Wi-Fi network applets appear after logging back into live-usb
  Lubuntu 18.04 session.

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

Bug description:
  Lubuntu 18.04 ISO version: 20180404
  network-manager-applet version: 1.8.10-2ubuntu1
  After logging into my Wi-Fi network then logging out then logging back into 
the Live-USB session Two Wi-Fi network applets appeared where One would be the 
expected outcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.392
  CurrentDesktop: LXDE
  Date: Thu Apr  5 21:06:24 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 
600
  LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  wifi  
1522962221  Thu Apr  5 21:03:41 2018  yes  0 no 
   /org/freedesktop/NetworkManager/Settings/2  yes wlp3s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Wired connection 1  472b45a7-c95b-3638-b452-3f6720688df8  ethernet  
1522961321  Thu Apr  5 20:48:41 2018  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  no  --  -- --
  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1756226] Re: nvidia-driver-390 fails to start GUI

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-390 -
390.48-0ubuntu2

---
nvidia-graphics-drivers-390 (390.48-0ubuntu2) bionic; urgency=medium

  [ Alberto Milone ]
  * debian/templates/10-nvidia.conf.in,
debian/templates/xserver-xorg-video-nvidia-flavour.install.in:
- Rename xorg.conf.d file.
- Drop the PrimaryGpu option from the xorg.conf.d file, as it
  has a bad interaction with systems with multiple NVIDIA GPUs
  (LP: #1756226).

  [ Graham Inggs ]
  * debian/templates/control.in:
- Make sure that libnvidia-compute does not conflict with or
  replace opencl-icd, so that other OpenCL ICDs can be installed
  at the same time.

 -- Alberto Milone   Thu, 12 Apr 2018
16:45:37 +0200

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  nvidia-driver-390 fails to start GUI

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress

Bug description:
  I was the original person who posted Ubuntu [Bug 1752053] nvidia-390
  fails to boot graphical display.  I was able to use the fix on my
  laptop successfully.  However, my desktop computer has 2 GTX1080 Ti
  cards and the fix does not work.  After I boot my desktop computer, I
  do not get a login screen.  I get a blank screen with a flickering
  text cursor in the top left corner.  I am running Bionic.

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] H264 missing from WebRTC (regression)

[Ben]

Public bug reported:

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

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

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