date:20170903

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

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

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

Title:
  GNOME Software is showing "No application found" when searching for
  new package and it shows only the installed ones

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Testing Ubuntu GNOME amd64 16.04 beta (build: 20160225.1) on Oracle
  VirtualBox. It happens with the Live Session and it is also happening
  after I install the system.

  To re-produce it:
  1- Open GNOME Software
  2- Type any package
  3- You should see "No application found" message.
  4- You're suppose to see only the installed packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.91~git20160225.dbf5b5d-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 25 23:28:02 2016
  InstallationDate: Installed on 2016-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160225.1)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1675024] Re: nouveau fails with orange screen with Quadro M2000 (Maxwell) in 16.04.2

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

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nouveau fails with orange screen with Quadro M2000 (Maxwell) in
  16.04.2

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Expired

Bug description:
  Steps to reproduce:
   1) Use a computer with an Nvidia Quadro M2000 GPU. (I used Lenovo 
ThinkStation P710 with Lenovo-bundled Quadro M2000.)
   2) Boot from Ubuntu 16.04.2 x86_64 live desktop / install USB stick.
   3) Choose try Ubuntu before installing from the boot scroon.

  Actual results:
  The screen goes orange and then no visible changes take place.

  Expected results:
  Expected to start Unity using nouveau-provided OpenGL functionality.

  Additional info:
  The 16.04.1 install media results in Unity starting up, but with OpenGL 
functionality (as reported by Unity and by Firefox) coming from llvmpipe on the 
CPU and not from nouveau on the GPU.

  With 17.04 install media, the screen goes black instead of orange.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1675024/+subscriptions

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

[Desktop-packages] [Bug 1702467] Re: software update indicator crashes and displays wrong error message

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

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

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

Title:
  software update indicator crashes and displays wrong error message

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  On a fresh Ubuntu 16.04.2 LTS install, the software update indicator
  indicator crashes (probably during startup) and reports the a mangled
  error.

  It states

  > The error message was 'ror in sitecustomize; set PYTHONVERBOSE
  > for traceback: AttributeError: module 'sys' has no attribute
  > 'setdefaultencoding' 0;0'.

  Please note the "ror" instead of "Error" at the beginning of the
  reported error message.

  The attached screenshot shows this error.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul  5 13:46:26 2017
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2017-06-24 (10 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1702502] Re: many messages

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

Title:
  many messages

Status in xorg package in Ubuntu:
  Expired

Bug description:
  there are many messages of sending errors report when ubuntu starts

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CasperVersion: 1.376.2
  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 Jul  5 15:07:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  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:1477]
 Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 740M] [1043:1477]
  LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
  MachineType: ASUSTeK COMPUTER INC. N46VB
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N46VB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N46VB
  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.:bvrN46VB.204:bd01/31/2013:svnASUSTeKCOMPUTERINC.:pnN46VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN46VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N46VB
  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.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Jul  5 15:02: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)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1714866] [NEW] Update libproxy to 0.4.15

Public bug reported:

https://github.com/libproxy/libproxy/releases

Big change here is updating the dependency from mozjs185 (from Firefox
4!) to mozjs38. libproxy1-plugin-mozjs is in universe and has no Ubuntu
reverse dependencies (Debian Edu uses it for something though.)

I don't have any proxies so I haven't tested this beyond making sure it
builds.

** Affects: libproxy (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: artful upgrade-software-version

** Description changed:

+ https://github.com/libproxy/libproxy/releases
+ 
  Big change here is updating the dependency from mozjs185 (from Firefox
- 4!) to mozjs38.
+ 4!) to mozjs38. libproxy1-plugin-mozjs is in universe and has no Ubuntu
+ reverse dependencies (Debian Edu uses it for something though.)
  
- https://github.com/libproxy/libproxy/releases
+ I don't have any proxies so I haven't tested this beyond making sure it
+ builds.

** Tags added: artful

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

Title:
  Update libproxy to 0.4.15

Status in libproxy package in Ubuntu:
  New

Bug description:
  https://github.com/libproxy/libproxy/releases

  Big change here is updating the dependency from mozjs185 (from Firefox
  4!) to mozjs38. libproxy1-plugin-mozjs is in universe and has no
  Ubuntu reverse dependencies (Debian Edu uses it for something though.)

  I don't have any proxies so I haven't tested this beyond making sure
  it builds.

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

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

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

2017-09-03 Thread Ubuntu Kernel Bot

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

apport-collect 1714783

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

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

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

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

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

Title:
  *beta 1 release* screen scrambling upon startup.

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714855] [NEW] Stucked in Airplane mode after suspend

2017-09-03 Thread Shu Hung (Koala)

Public bug reported:

I have updated to the latest version (as of 2017/9/4) of all my package
in my Artful.

Hardware Platform:

HP Spectre X360 (2015)


Software Version:

1.8.2-1ubuntu5


Steps to Reproduce on my Laptop:

1. Login to my account.
2. Connect to the wireless network as usual.
3. Suspend the machine by closing the lit.
4. Open up the lit and login again.


Expected:

The machine works normally.


Actually got:

The machine stucked at Airplane mode. I can neither disable the airplane mode
by the top right menu nor by the network settings UI. The airplane mode stays
on every time after I switch it off. I have to reboot to resume the network.

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

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

Title:
  Stucked in Airplane mode after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have updated to the latest version (as of 2017/9/4) of all my
  package in my Artful.

  Hardware Platform:

  HP Spectre X360 (2015)

  
  Software Version:

  1.8.2-1ubuntu5

  
  Steps to Reproduce on my Laptop:

  1. Login to my account.
  2. Connect to the wireless network as usual.
  3. Suspend the machine by closing the lit.
  4. Open up the lit and login again.

  
  Expected:

  The machine works normally.

  
  Actually got:

  The machine stucked at Airplane mode. I can neither disable the airplane mode
  by the top right menu nor by the network settings UI. The airplane mode stays
  on every time after I switch it off. I have to reboot to resume the network.

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

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

[Desktop-packages] [Bug 1580605] Re: gnome-shell crashes often

Everyone other than gnufied, please log your own separate bugs so we
don't get potentially different issues confused.

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

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

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

Title:
  gnome-shell crashes often

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I don't have full stacktrace right now unfortunately but gnome-shell
  appears to be crashing a lot for me.

  I am running it with multiple monitors and it crashes with following
  errors:

  [58566.199387] gnome-shell[11622]: segfault at e8 ip 7f577582c582
  sp 7ffc18448048 error 4 in
  libgdk-3.so.0.1800.9[7f57757ef000+d4000]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May 11 09:16:52 2016
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-04-17 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714783] Re: beta 1 release screen scrambling upon startup.

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

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

Title:
  *beta 1 release* screen scrambling upon startup.

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714826] Re: HiDPI scaling regression on Beta 1

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1714295, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1714295
   HiDPI scaling broken in Gnome 3.25

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

Title:
  HiDPI scaling regression on Beta 1

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After running today's updates, HiDPI scaling on my 4k 15,6" display
  stopped working. Ubuntu dock keeps correct scaling, but top bar,
  context menu, and other UI elements revert back to non-scaled
  dimensions. I can fix most of the UI with

  $ gsettings set org.gnome.desktop.interface scaling-factor 2

  but after reboot or logout it reverts back to wrong setting. I solved
  the topbar scaling by changing the size of the panel by one pixel
  (increase or decrease, doesn't matter. Perplexing, indeed), but can't
  find a way to fix context menu scaling.

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2017-09-03 Thread Bug Watch Updater

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

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

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714851] Re: /usr/bin/gnome-shell:11:g_type_check_instance_cast:shell_gtk_embed_window_created_cb:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

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

** This bug has been marked a duplicate of bug 1714745
   gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

Title:
  /usr/bin/gnome-
  
shell:11:g_type_check_instance_cast:shell_gtk_embed_window_created_cb:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

** Description changed:

+ https://errors.ubuntu.com/problem/7accb2ea7fd305736eb23cca5905e4b690a16cae
+ 
+ ---
+ 
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep  3 02:41:44 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (562 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
-  Segfault happened at: 0x7feb5dff7e26 :
mov(%rdi),%rdi
-  PC (0x7feb5dff7e26) ok
-  source "(%rdi)" (0x3fe0) not located in a known VMA region 
(needed readable region)!
-  destination "%rdi" ok
+  Segfault happened at: 0x7feb5dff7e26 :
mov(%rdi),%rdi
+  PC (0x7feb5dff7e26) ok
+  source "(%rdi)" (0x3fe0) not located in a known VMA region 
(needed readable region)!
+  destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  () at /usr/lib/gnome-shell/libgnome-shell.so
-  g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  () at /usr/lib/gnome-shell/libgnome-shell.so
+  g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to artful on 2017-05-02 (123 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin 
mock plugdev sambashare sbuild sudo wireshark

** Summary changed:

- gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
+ gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from 
shell_gtk_embed_window_created_cb() from g_closure_invoke() from 
signal_emit_unlocked_R()

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  shell_gtk_embed_window_created_cb() from g_closure_invoke() from
  signal_emit_unlocked_R()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/7accb2ea7fd305736eb23cca5905e4b690a16cae

  ---

  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep  3 02:41:44 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (562 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7feb5dff7e26 :
mov(%rdi),%rdi
   PC (0x7feb5dff7e26) ok
   source "(%rdi)" (0x3fe0) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/gnome-shell/libgnome-shell.so
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to artful on 2017-05-02 (123 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin 
mock plugdev sambashare sbuild sudo wireshark

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

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

[Desktop-packages] [Bug 1714851] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_cast:shell_gtk_embed_window_created_cb:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

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

Public bug reported:

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

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


** Tags: yakkety zesty

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

Title:
  /usr/bin/gnome-
  
shell:11:g_type_check_instance_cast:shell_gtk_embed_window_created_cb:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  :(

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Sep  2 16:47:32 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-10-16 (687 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fbe7998f296:mov0x1a0(%rax),%rax
   PC (0x7fbe7998f296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1479710] Re: /usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

2017-09-03 Thread pothos

Please comment on https://bugzilla.gnome.org/show_bug.cgi?id=756275#c6
if this happens with a UDisks version >= 2.7.2

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

Title:
  /usr/bin/gnome-
  
disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now

Status in GNOME Disks:
  Confirmed
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Triaged
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gnome-disk-utility.  This problem was most recently seen
  with version 3.16.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/9ec0e4eaf2490589696da7e6514c5fc0507946b0
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1479710/+subscriptions

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

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

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Unknown error when waking from sleep.  system appeared normal, but
  reported an error had occurred.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Sep  1 12:36:19 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-08-12 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170810)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f6ec1e6c296:mov0x1a0(%rax),%rax
   PC (0x7f6ec1e6c296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1714700] Re: VT output during restart/shutdown

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

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

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

Title:
  VT output visible during restart/shutdown

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

Bug description:
  When I restart or shutdown, I get a very unusual screen output like a
  terminal command had been ran. It's happened for the last few days and
  I just installed the beta 1 release yesterday for a fresh install.
  I'll upload a video after this comment to show you what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 08:51:49 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714656] Re: update from gnome-terminal crashes

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.


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

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

Title:
  update from gnome-terminal crashes

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  gnome-terminal crashed in gnome-shell wayland. I was updating and when
  it came to "unpacking  x11 common" the whole screen froze, mouse
  included and the update stopped and crashed the terminal. There was no
  report , no nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 05:58:28 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-08-22 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714700] Re: VT output during restart/shutdown

** Summary changed:

- Unusual screen output during restart/shutdown
+ VT output during restart/shutdown

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

Title:
  VT output visible during restart/shutdown

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

Bug description:
  When I restart or shutdown, I get a very unusual screen output like a
  terminal command had been ran. It's happened for the last few days and
  I just installed the beta 1 release yesterday for a fresh install.
  I'll upload a video after this comment to show you what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 08:51:49 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714700] Re: VT output visible during restart/shutdown

** Summary changed:

- VT output during restart/shutdown
+ VT output visible during restart/shutdown

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

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

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

Title:
  VT output visible during restart/shutdown

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

Bug description:
  When I restart or shutdown, I get a very unusual screen output like a
  terminal command had been ran. It's happened for the last few days and
  I just installed the beta 1 release yesterday for a fresh install.
  I'll upload a video after this comment to show you what's going on.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 08:51:49 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714849] [NEW] /usr/bin/gnome-shell:11:st_theme_node_reduce_border_radius:st_theme_node_paint_borders:st_theme_node_paint:st_widget_paint_background:st_label_paint

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

Public bug reported:

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

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


** Tags: artful xenial

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

Title:
  /usr/bin/gnome-
  
shell:11:st_theme_node_reduce_border_radius:st_theme_node_paint_borders:st_theme_node_paint:st_widget_paint_background:st_label_paint

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1714542] Re: gnome-shell crashed with SIGSEGV in overview

** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with SIGSEGV in overview
+ gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from 
st_theme_node_paint_borders() from st_theme_node_paint()

** Description changed:

+ https://errors.ubuntu.com/problem/23d376488259ea5f9fa6fb9843956cb6464f56e8
+ 
+ ---
+ 
  As of an upgrade to 3.25.91 (last session that did not exhibit this
  behavior was a 3.24.x session), I've experienced several crashes of the
  shell in the overview. journalctl shows the following output at the time
  of the crash:
  
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8792]: Window manager warning: 
Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54).
  Sep 01 08:14:41 spiny gnome-shell[8506]: 
meta_renderer_native_release_onscreen: assertion 
'onscreen_native->gbm.next_fb_id == 0' failed
  Sep 01 08:14:41 spiny gnome-shell[8506]: _cogl_onscreen_free: assertion 
'onscreen->winsys == ((void *)0)' failed
  Sep 01 08:14:41 spiny kernel: gnome-shell[8506]: segfault at 1a0 ip 
7fc6008dd296 sp 7fff2df360f0 error 4 in 
libmutter-1.so.0.0.0[7fc6007f9000+13e000]
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: Fatal server error:
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE) failed to read 
Wayland events: Connection reset by peer
  Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE)
  Sep 01 08:14:41 spiny gnome-session[8488]: gnome-session-binary[8488]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 01 08:14:41 spiny gnome-session-binary[8488]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 11
  Sep 01 08:14:41 spiny polkitd(authority=local)[1424]: Unregistered 
Authentication Agent for unix-session:c3 (system bus name :1.868, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disco
  Sep 01 08:14:41 spiny gsd-media-keys[8610]: gsd-media-keys: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-keyboard[8607]: gsd-keyboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-clipboard[8596]: gsd-clipboard: Fatal IO error 11 
(Resource temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-power[8613]: gsd-power: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny gsd-color[8599]: gsd-color: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :1024.
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: XIO: fatal IO error 11 
(Resource temporarily unavailable) on X server ":1024"
  Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: after 21 requests (21 
known processed) with 0 events remaining.
  Sep 01 08:14:41 spiny gdm-launch-environment][8400]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
  Sep 01 08:14:41 spiny systemd-logind[1376]: Removed session c3.
  Sep 01 08:14:41 spiny systemd[1]: Stopping User Manager for UID 121...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Accessibility services bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping Sound Service...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Default.
  Sep 01 08:14:41 spiny systemd[8432]: Stopping D-Bus User Message Bus...
  Sep 01 08:14:41 spiny systemd[8432]: Stopping sandboxed app permission 
store...
  Sep 01 08:14:41 spiny systemd[8432]: Stopped sandboxed app permission store.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped D-Bus User Message Bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Accessibility services bus.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped Sound Service.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Basic System.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Paths.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Timers.
  Sep 01 08:14:41 spiny systemd[8432]: Stopped target Sockets.
  Sep 01 08:14:41 spiny systemd[8432]: Closed D-Bus User Message Bus Socket.
  Sep 01 08:14:41 spiny systemd[8432]: Closed Sound System.
  Sep 01 08:14:41 spiny systemd[8432]: Reached target Shutdown.
  Sep 01 08:14:41 spiny systemd[8432]: Starting Exit the Session...
  Sep 01 08:14:41 spiny systemd[8432]: Received SIGRTMIN+24 from PID 8854 
(kill).
  Sep 01 08:14:41 spiny systemd[1]: Stopped User Manager for UID 121.
  Sep 01 08:14:41 spiny systemd[1]: Removed slice User Slice of gdm.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Sep  1 08:13:58 2017
  DisplayManager: gdm3

[Desktop-packages] [Bug 1714850] Re: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint() from st_widget_paint_backgro

This crash is close enough to bug 1714542 that I'll assume it's the same
for now.

** Summary changed:

- 
/usr/bin/gnome-shell:11:st_theme_node_reduce_border_radius:st_theme_node_paint_borders:st_theme_node_paint:st_widget_paint_background:shell_generic_container_paint
+ gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from 
st_theme_node_paint_borders() from st_theme_node_paint() from 
st_widget_paint_background() from shell_generic_container_paint()

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

Title:
  gnome-shell crashed with SIGSEGV in
  st_theme_node_reduce_border_radius() from
  st_theme_node_paint_borders() from st_theme_node_paint() from
  st_widget_paint_background() from shell_generic_container_paint()

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  normal login is failing. this error came during failsafe login but
  with regular x session from text based options

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Sep  1 19:08:16 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-02-25 (188 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7feab74da296:mov0x1a0(%rax),%rax
   PC (0x7feab74da296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to artful on 2017-08-13 (19 days ago)
  UserGroups:

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

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

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

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Gnome X or Wayland, also standard Ubuntu session, crash and loop back
  to login manager. Only logins via Unity possible.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Sep  1 08:45:25 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-04-01 (152 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170331)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f077a4bc296:mov0x1a0(%rax),%rax
   PC (0x7f077a4bc296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to artful on 2017-06-08 (84 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1714850] [NEW] gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint() from st_widget_paint_backg

Public bug reported:

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

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


** Tags: artful vivid wily xenial yakkety zesty

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

Title:
  gnome-shell crashed with SIGSEGV in
  st_theme_node_reduce_border_radius() from
  st_theme_node_paint_borders() from st_theme_node_paint() from
  st_widget_paint_background() from shell_generic_container_paint()

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1714849] Re: /usr/bin/gnome-shell:11:st_theme_node_reduce_border_radius:st_theme_node_paint_borders:st_theme_node_paint:st_widget_paint_background:st_label_paint

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

** This bug has been marked a duplicate of bug 1714542
   gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() 
from st_theme_node_paint_borders() from st_theme_node_paint()

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

Title:
  /usr/bin/gnome-
  
shell:11:st_theme_node_reduce_border_radius:st_theme_node_paint_borders:st_theme_node_paint:st_widget_paint_background:st_label_paint

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

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

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 #1714330, 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/1714847/+attachment/4943854/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1714330
   gnome-shell crashed with SIGSEGV in on_crtc_flipped() from 
g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from 
drmHandleEvent()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upon login, before anything else was done.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Sep  4 09:29:38 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-07-24 (41 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f18ba396836:mov0x1a0(%rax),%rax
   PC (0x7f18ba396836) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()

Yeah that changelog sounds confused. It doesn't sound like it's really 
mentioning a crash fix in:
  * New upstream git snapshot (LP: #1714330)

** Description changed:

+ https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99
+ 
+ ---
+ 
  Gnome shell crashes when trying to log in to the wayland ubuntu session.
  It works fine on Xorg.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
-  Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
-  PC (0x7fdee0bf9296) ok
-  source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
+  PC (0x7fdee0bf9296) ok
+  source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
+  destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
-  g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
-  drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
-  meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
+  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
+  g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
+  drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
+  meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

Title:
  gnome-shell crashed with SIGSEGV in on_crtc_flipped() from
  g_closure_invoke() from invoke_flip_closure() from page_flip_handler()
  from drmHandleEvent()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

  ---

  Gnome shell crashes when trying to log in to the wayland ubuntu
  session. It works fine on Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
   PC (0x7fdee0bf9296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  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/1714330/+subscriptions

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

[Desktop-packages] [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()

That said, the error tracker is showing this crash has stopped after 
3.25.91-0ubuntu2:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

So if you're still experiencing problems then please log a new bug.

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

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

Title:
  gnome-shell crashed with SIGSEGV in on_crtc_flipped() from
  g_closure_invoke() from invoke_flip_closure() from page_flip_handler()
  from drmHandleEvent()

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/196617236bfd49c847a208a8eda38e2bd701ca99

  ---

  Gnome shell crashes when trying to log in to the wayland ubuntu
  session. It works fine on Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
   PC (0x7fdee0bf9296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  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/1714330/+subscriptions

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

[Desktop-packages] [Bug 1714848] Re: /usr/bin/gnome-shell:11:on_crtc_flipped:g_closure_invoke:invoke_flip_closure:page_flip_handler:drmHandleEvent

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

** This bug has been marked a duplicate of bug 1714330
   gnome-shell crashed with SIGSEGV in on_crtc_flipped() from 
g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from 
drmHandleEvent()

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

Title:
  /usr/bin/gnome-
  
shell:11:on_crtc_flipped:g_closure_invoke:invoke_flip_closure:page_flip_handler:drmHandleEvent

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1714848] [NEW] /usr/bin/gnome-shell:11:on_crtc_flipped:g_closure_invoke:invoke_flip_closure:page_flip_handler:drmHandleEvent

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

Public bug reported:

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

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


** Tags: artful

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

Title:
  /usr/bin/gnome-
  
shell:11:on_crtc_flipped:g_closure_invoke:invoke_flip_closure:page_flip_handler:drmHandleEvent

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1713551] Re: System tray (notification area) icons are not shown on unity-session and gnome-classic

Sounds like it's fixed?

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

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

Title:
  System tray (notification area) icons are not shown on unity-session
  and gnome-classic

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install application which places its icon to the system tray (notification 
area) such as `hplip` or `transmission`
  3. Try to find application icon in the system tray (notification area)

  Expected results:
  Application icon is placed and shown in the system tray (notification area)

  Actual results:
  Application icon is not placed and not shown in the system tray (notification 
area)

  Info:
  $ export | grep "SESSION\|DESK"
  declare -x DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"
  declare -x 
DESKTOP_AUTOSTART_ID="1017f889114f44fd1415039439458098940102050008"
  declare -x DESKTOP_SESSION="ubuntu-xorg"
  declare -x GDMSESSION="ubuntu-xorg"
  declare -x GNOME_DESKTOP_SESSION_ID="this-is-deprecated"
  declare -x GNOME_SESSION_XDG_SESSION_PATH=""
  declare -x GNOME_SHELL_SESSION_MODE="ubuntu"
  declare -x 
SESSION_MANAGER="local/artful:@/tmp/.ICE-unix/10205,unix/artful:/tmp/.ICE-unix/10205"
  declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME"
  declare -x XDG_SESSION_DESKTOP="ubuntu-xorg"
  declare -x XDG_SESSION_ID="11"
  declare -x XDG_SESSION_TYPE="x11"


  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.25.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 21:13:32 2017
  InstallationDate: Installed on 2017-08-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714295] Re: HiDPI scaling broken in Gnome 3.25

** Summary changed:

- DPI scaling broken in Gnome 3.25
+ HiDPI scaling broken in Gnome 3.25

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

Title:
  HiDPI scaling broken in Gnome 3.25

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After applying the latest artful updates today and rebooting, the
  login screen is correctly scaled but after I login DPI scaling doesn't
  apply correctly. Everything is super tiny.

  If I launch gnome tweak tool then the screen snaps and then
  applications are correctly scaled. Even then, the top bar remains
  tiny. If I adjust the scaling factor, everything but the top bar
  changes.

  FWIW, I have scaling factor set to 1 in gnome tweak tool. I'm
  wondering if I have a preference somewhere that's sabotaging this but
  I've yet to find it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 10:59:17 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-07-23 (38 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1588150] Re: Remove webkitgtk from archive

gnome-web-photo has been removed from Debian and from Ubuntu 17.10

** Changed in: gnome-web-photo (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Remove webkitgtk from archive

Status in Bijiben:
  Fix Released
Status in Empathy:
  Fix Released
Status in Evolution:
  Fix Released
Status in Geary:
  Fix Released
Status in Liferea:
  Fix Released
Status in LightDM Webkit Greeter:
  Fix Committed
Status in bijiben package in Ubuntu:
  Fix Released
Status in birdfont package in Ubuntu:
  Fix Released
Status in cairo-dock-plugins package in Ubuntu:
  Fix Released
Status in empathy package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in geary package in Ubuntu:
  Fix Released
Status in gnome-web-photo package in Ubuntu:
  Fix Released
Status in gtkpod package in Ubuntu:
  Fix Released
Status in liferea package in Ubuntu:
  Fix Released
Status in lightdm-webkit-greeter package in Ubuntu:
  In Progress
Status in maildir-utils package in Ubuntu:
  Fix Released
Status in surf package in Ubuntu:
  Fix Released
Status in webkitgtk package in Ubuntu:
  Triaged
Status in xiphos package in Ubuntu:
  Triaged
Status in xombrero package in Ubuntu:
  Fix Released

Bug description:
  webkitgtk is obsolete and has been replaced by webkit2gtk. This
  requires things to be ported to the new API.

  Debian tracking:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-webkit-maintain...@lists.alioth.debian.org;tag=webkit1

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

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

[Desktop-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override

2017-09-03 Thread Jarod

It was only showing this core dump when installing package with apt before. but 
after upgrade to latest packages today (apt update && apt full-upgrade), I 
can't login to GDM (black screen).
The workaround is remove the package sogoupinyin, which provide this file 
/usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override
but now I can't use the best Chinese pinyin IME on linux...

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

Title:
  glib-compile-schemas invalid free in per session override

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  reinstall nautilus error with package sogoupinyin

  # sudo nautilus
  sys:1: PyGIWarning: Nautilus was imported without specifying a version 
  first. Use gi.require_version('Nautilus', '3.0') before import to 
  ensure that the right version gets loaded.
  ** Message: Init Stock Icons

  (nautilus:10235): GLib-GIO-ERROR **: Settings schema 
  'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'

  
  #sudo apt-get install --reinstall nautilus  nautilus-share nautilus-data 
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
  正在读取软件包列表... 完成
  正在分析软件包的依赖关系树
  正在读取状态信息... 完成
  升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
  需要下载 0 B/3,298 kB 的归档。
  解压缩后会消耗 0 B 的额外空间。
  您希望继续执行吗？ [Y/n] y
  (正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
  正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb  ...
  正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb  ...
  正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
  正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb  ...
  正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb  ...
  正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
  正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb  ...
  正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
  正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb  ...
  正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
  正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb  ...
  正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
  正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
  正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
  正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
  覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案 
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
  *** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double 
free or corruption (fasttop): 0x58242808 ***
  === Backtrace: =
  /lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
  /lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
  /lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
  /lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
  /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
  /usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
  === Memory map: 
  5659b000-565a5000 r-xp  08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a6000-565a7000 r--p a000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  565a7000-565a8000 rw-p b000 08:01 28049954   
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
  58113000-5829 rw-p  00:00 0  
[heap]
  f6e0-f6e21000 rw-p  00:00 0
  f6e21000-f6f0 ---p  00:00 0
  f6f75000-f712b000 r--p 002da000 08:01 25170585   
/usr/lib/locale/locale-archive
  f712b000-f732b000 r--p  08:01 25170585   
/usr/lib/locale/locale-archive
  f732b000-f732d000 rw-p  00:00 0
  f732d000-f7346000 r-xp  08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7346000-f7347000 r--p 00018000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7347000-f7348000 rw-p 00019000 08:01 50856428   
/lib/i386-linux-gnu/libpthread-2.24.so
  f7348000-f734a000 rw-p  00:00 0
  f734a000-f73c1000 r-xp  08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c1000-f73c2000 r--p 00076000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c2000-f73c3000 rw-p 00077000 08:01 50856034   
/lib/i386-linux-gnu/libpcre.so.3.13.3
  f73c3000-f7576000 r-xp  08:01 50856273   
/lib/i386-linux-gnu/libc-2.24.so
  f7576000-f7577000 ---p 001b3000 08:01 50856273

[Desktop-packages] [Bug 1419267] Re: libjpegturbo.so missing from -dev package

2017-09-03 Thread Matthias Klose

reopening.  What is the reason to have this package, when you can use
the standard jpeg8 headers?


** Changed in: libjpeg-turbo (Ubuntu)
   Status: Fix Released => Incomplete

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

Title:
  libjpegturbo.so missing from -dev package

Status in One Hundred Papercuts:
  Invalid
Status in libjpeg-turbo package in Ubuntu:
  Incomplete

Bug description:
  $ dpkg -L libjpeg-turbo8-dev
  /.
  /usr
  /usr/share
  /usr/share/doc
  /usr/share/doc/libjpeg-turbo8-dev
  /usr/share/doc/libjpeg-turbo8-dev/copyright
  /usr/share/doc/libjpeg-turbo8-dev/README.gz
  /usr/share/doc/libjpeg-turbo8-dev/structure.txt.gz
  /usr/share/doc/libjpeg-turbo8-dev/README-turbo.txt.gz
  /usr/share/doc/libjpeg-turbo8-dev/libjpeg.txt.gz
  /usr/lib
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libjpeg.a
  /usr/lib/x86_64-linux-gnu/libturbojpeg.a
  /usr/include
  /usr/include/jerror.h
  /usr/include/turbojpeg.h
  /usr/include/jmorecfg.h
  /usr/include/jpeglib.h
  /usr/include/jpegint.h
  /usr/include/x86_64-linux-gnu
  /usr/include/x86_64-linux-gnu/jconfig.h
  /usr/share/doc/libjpeg-turbo8-dev/changelog.Debian.gz
  /usr/lib/x86_64-linux-gnu/libjpeg.so


  See the libjpeg.so symlink. This is good.

  I also expect a libturbojpeg.so symlink. This is missing. Please add
  so that I can build software which depends on this dynamic library
  without manually creating this symlink.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libturbojpeg 1.3.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Sat Feb  7 08:41:19 2015
  Dependencies:
   gcc-4.9-base 4.9.1-16ubuntu6
   libc6 2.19-10ubuntu2.2
   libgcc1 1:4.9.1-16ubuntu6
   multiarch-support 2.19-10ubuntu2.2
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libjpeg-turbo
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (105 days ago)

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

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

[Desktop-packages] [Bug 1714839] Re: Xorg freezes on zesty default 4.10 kernel

2017-09-03 Thread Rob Ludwick

Workaround is to boot into the old 4.8 kernel.

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

Title:
  Xorg freezes on zesty default 4.10 kernel

Status in xorg package in Ubuntu:
  New

Bug description:
  When running the 4.10 kernel I get the following errors an a X lockup
  when trying to login as a user.

  kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
  kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Sep  3 18:33:15 2017
  DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-03-09 (178 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago)
  dmi.bios.date: 01/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

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

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

[Desktop-packages] [Bug 1714839] Re: Xorg freezes on zesty default 4.10 kernel

2017-09-03 Thread Rob Ludwick

** Attachment added: "Kernel log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839/+attachment/4943840/+files/kern.log

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

Title:
  Xorg freezes on zesty default 4.10 kernel

Status in xorg package in Ubuntu:
  New

Bug description:
  When running the 4.10 kernel I get the following errors an a X lockup
  when trying to login as a user.

  kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
  kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Sep  3 18:33:15 2017
  DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-03-09 (178 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago)
  dmi.bios.date: 01/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

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

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

[Desktop-packages] [Bug 1714839] [NEW] Xorg freezes on zesty default 4.10 kernel

2017-09-03 Thread Rob Ludwick

Public bug reported:

When running the 4.10 kernel I get the following errors an a X lockup
when trying to login as a user.

kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
Uname: Linux 4.8.0-59-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Sep  3 18:33:15 2017
DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
   Subsystem: Dell Device [1028:07be]
InstallationDate: Installed on 2017-03-09 (178 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago)
dmi.bios.date: 01/09/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.3
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1

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


** Tags: 4.10 amd64 apport-bug freeze ubuntu zesty

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

Title:
  Xorg freezes on zesty default 4.10 kernel

Status in xorg package in Ubuntu:
  New

Bug description:
  When running the 4.10 kernel I get the following errors an a X lockup
  when trying to login as a user.

  kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
  kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Sep  3 18:33:15 2017
  DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-03-09 (178 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed

[Desktop-packages] [Bug 1714654] Re: random blackscreen of death when switching tabs in firefox

2017-09-03 Thread amano

** Tags added: wayland

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

Title:
  random blackscreen of death when switching tabs in firefox

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  full update. screen will suddenly blackout for a few seconds when
  switching tabs in firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  2 05:30:59 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 
'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 
'com.canonical.launcher.amazon.desktop', 'gnome-control-center.desktop', 
'htop.desktop', 'etr.desktop', 'org.gnome.Screenshot.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-06-13 (80 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170611)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714833] Re: package fonts-noto-cjk (not installed) failed to install/upgrade: subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)

2017-09-03 Thread Gunnar Hjalmarsson

Thanks for your report. It sounds as a temporary glitch to me.

Can you please try to reinstall the package:

sudo apt install --reinstall fonts-noto-cjk

and let us know if it helped?

** Changed in: fonts-noto-cjk (Ubuntu)
   Status: New => Incomplete

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

Title:
  package fonts-noto-cjk (not installed) failed to install/upgrade:
  subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)

Status in fonts-noto-cjk package in Ubuntu:
  Incomplete

Bug description:
  Durante l'upgrade alla distro 16.06, è comparso l'errore in oggetto

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-noto-cjk (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Sep  3 22:55:03 2017
  DuplicateSignature:
   package:fonts-noto-cjk:(not installed)
   Unpacking fonts-noto-cjk (1:1.004+repack2-1~ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/fonts-noto-cjk_1%3a1.004+repack2-1~ubuntu1_all.deb 
(--unpack):
subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  ErrorMessage: subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  InstallationDate: Installed on 2012-08-19 (1841 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: fonts-noto-cjk
  Title: package fonts-noto-cjk (not installed) failed to install/upgrade: 
subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  UpgradeStatus: Upgraded to xenial on 2017-09-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1714833/+subscriptions

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

[Desktop-packages] [Bug 1714833] Re: package fonts-noto-cjk (not installed) failed to install/upgrade: subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)

** Tags removed: need-duplicate-check

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

Title:
  package fonts-noto-cjk (not installed) failed to install/upgrade:
  subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)

Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  Durante l'upgrade alla distro 16.06, è comparso l'errore in oggetto

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-noto-cjk (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Sep  3 22:55:03 2017
  DuplicateSignature:
   package:fonts-noto-cjk:(not installed)
   Unpacking fonts-noto-cjk (1:1.004+repack2-1~ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/fonts-noto-cjk_1%3a1.004+repack2-1~ubuntu1_all.deb 
(--unpack):
subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  ErrorMessage: subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  InstallationDate: Installed on 2012-08-19 (1841 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: fonts-noto-cjk
  Title: package fonts-noto-cjk (not installed) failed to install/upgrade: 
subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  UpgradeStatus: Upgraded to xenial on 2017-09-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1714833/+subscriptions

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

[Desktop-packages] [Bug 1714834] [NEW] display is detected on a non-connected DP port

2017-09-03 Thread Szilárd Páll

Public bug reported:

I have my screen connected to HDMI, and I also have a DP cable plugged
in. The single screen attached gets detected twice, xrands shows both
HDMI-1 as connected (primary) and DP-1 connected as well. If I
disconnect the DP cable xrandr does now show it as connected anymore.
xrandr output below:

$ xrandr 
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192
HDMI-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y 
axis) 553mm x 311mm
   2560x1440 59.95*+
   2048x1152 60.00  
   1920x1200 59.95  
   1920x1080 60.0060.0050.0059.9430.0025.0024.00
29.9723.98  
   1920x1080i60.0050.0059.94  
   1600x1200 60.00  
   1680x1050 59.88  
   1280x1024 75.0260.02  
   1200x960  59.99  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x576i  50.00  
   720x480   60.0059.94  
   720x480i  60.0059.94  
   640x480   75.0060.0059.94  
   720x400   70.08  
DP-1 connected (normal left inverted right x axis y axis)
   2560x1440 59.95 +
   2048x1152 60.00  
   1920x1200 59.88  
   1920x1080 60.0050.0059.9430.0025.0024.0029.97
23.98  
   1920x1080i60.0050.0059.94  
   1600x1200 60.00  
   1680x1050 59.95  
   1280x1024 75.0260.02  
   1200x960  59.99  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0360.00  
   800x600   75.0060.32  
   720x576   50.00  
   720x480   60.0059.94  
   640x480   75.0060.0059.94  
   720x400   70.08  
HDMI-2 disconnected (normal left inverted right x axis y axis)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg (not installed)
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-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: None
CurrentDesktop: Budgie:GNOME
Date: Mon Sep  4 00:45:37 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.40, 4.10.0-28-generic, x86_64: installed
 virtualbox, 5.0.40, 4.10.0-32-generic, x86_64: installed
 virtualbox, 5.0.40, 4.10.0-33-generic, x86_64: installed
 virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1926] (rev 0a) (prog-if 
00 [VGA controller])
   Subsystem: Intel Corporation Skylake Integrated Graphics [8086:2063]
InstallationDate: Installed on 2016-06-18 (441 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=04f11ff8-1726-4c69-9fec-69890c6d9f74 ro text
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.vendor: Intel Corp.
dmi.board.vendor: Intel corporation
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 Sep  4 00:25:20 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  display is detected on a non-connected DP port

Status in xorg package in Ubuntu:
  New

Bug description:
  I have my screen connected to HDMI, and I also have a DP cable plugged
  in. The single screen attached gets detected twice, xrands shows both
  HDMI-1 as connected (primary) and DP-1 connected as well. If I
  disconnect the DP cable xrandr does now show it as connected

[Desktop-packages] [Bug 1714833] [NEW] package fonts-noto-cjk (not installed) failed to install/upgrade: subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)

2017-09-03 Thread Vincenzo Valerio

Public bug reported:

Durante l'upgrade alla distro 16.06, è comparso l'errore in oggetto

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fonts-noto-cjk (not installed)
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Sun Sep  3 22:55:03 2017
DuplicateSignature:
 package:fonts-noto-cjk:(not installed)
 Unpacking fonts-noto-cjk (1:1.004+repack2-1~ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/fonts-noto-cjk_1%3a1.004+repack2-1~ubuntu1_all.deb 
(--unpack):
  subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
ErrorMessage: subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
InstallationDate: Installed on 2012-08-19 (1841 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: fonts-noto-cjk
Title: package fonts-noto-cjk (not installed) failed to install/upgrade: 
subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
UpgradeStatus: Upgraded to xenial on 2017-09-03 (0 days ago)

** Affects: fonts-noto-cjk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package fonts-noto-cjk (not installed) failed to install/upgrade:
  subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)

Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  Durante l'upgrade alla distro 16.06, è comparso l'errore in oggetto

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-noto-cjk (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Sep  3 22:55:03 2017
  DuplicateSignature:
   package:fonts-noto-cjk:(not installed)
   Unpacking fonts-noto-cjk (1:1.004+repack2-1~ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/fonts-noto-cjk_1%3a1.004+repack2-1~ubuntu1_all.deb 
(--unpack):
subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  ErrorMessage: subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  InstallationDate: Installed on 2012-08-19 (1841 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: fonts-noto-cjk
  Title: package fonts-noto-cjk (not installed) failed to install/upgrade: 
subprocess dpkg-deb --fsys-tarfile was killed by signal (Killed)
  UpgradeStatus: Upgraded to xenial on 2017-09-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1714833/+subscriptions

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

[Desktop-packages] [Bug 1714821] Re: FFe: Sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)

Well I guess the recommended package is not a fully functional Apache so
maybe Step 1.c. isn't that important and we can consider Step 2 for
artful.

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

Title:
  FFe: Sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)

Status in gnome-user-share package in Ubuntu:
  New

Bug description:
  Please sync gnome-user-share 3.18.3-2 (main) from Debian unstable
  (main)

  The version of gnome-user-share currently in Ubuntu has 2 features:
  Bluetooth and WebDav.

  Ubuntu has installed gnome-user-share by default for many years so
  that sending and receiving files over Bluetooth works. That feature is
  now  rovided by gnome-bluetooth and gnome-control-center. Therefore,
  the new version of gnome-user-share dropped the Bluetooth feature.

  Ubuntu has delayed packaging a newer version of gnome-user-share because it
  was using unity-control-center which did not support the new Bluetooth 
feature.

  Ubuntu has one long-standing diff from Debian. Ubuntu's gnome-user-share
  package does not actually include the apache dependencies needed for the
  WebDav feature to work (LP: #536766). Since that's now the only feature in
  gnome-user-share, dropping this diff makes sense.

  $ reverse-depends gnome-user-share
  Reverse-Recommends
  ==
  * cinnamon-desktop-environment
  * gnome-bluetooth
  * gnome-control-center

  Reverse-Depends
  ===
  * gnome-core [amd64 arm64 armhf i386 ppc64el]
  * ubuntu-budgie-desktop [amd64 arm64 armhf i386 ppc64el]
  * ubuntu-gnome-desktop [amd64 arm64 armhf i386 ppc64el]

  Step 1
  --
  Ubuntu and Ubuntu Budgie both use gnome-control-center so gnome-user-share is 
unused for Bluetooth.

  a. Drop the dependency on gnome-user-share from at least
  gnome-bluetooth
  gnome-control-center
  ubuntu-budgie-desktop

  But we might need to drop the dependency everywhere until after 18.04
  LTS for 1.c. to work.

  b. Demote gnome-user-share to universe.

  c. Have ubuntu-release-upgrader remove gnome-user-share on upgrades.

  Step 2
  --
  Sync gnome-user-share from Debian.

  I believe we want to do Step 1 for Ubuntu 17.10 "artful".

  The complication for Step 2 is that upgraders will get Apache
  installed unless they upgrade using update-manager/do-release-upgrade

  Therefore, I recommend delaying Step 2 until 18.04 development opens.

  Explanation of the Ubuntu delta and why it can be dropped:
    * Add git_add_systemd_service.patch:
  - Backport commit from 3.22 to add systemd user service file for
    compatibility with gnome-settings-daemon 3.22
    * debian/control.in:
  - Build-Depend on systemd
    * d/p/0004-revert-remove-help.patch: Bring back the help files
  for users of gnome-file-share-properties (LP: #1570230)
    * debian/patches: 0001-revert-remove-preferences-application.patch
  Fix launching of Prefences from nautilus share bar under unity and
  patch infobar color (LP: #1562515)
    * maintscript: remove old xdg autostart file (lp: #1526894)
    * New Upstream release (LP: #1518813)
    * Merge with Debian, Remaining changes:
  - Suggests the apache2.2-bin and libapache2-mod-dnssd binaries rather than
    depends on those, we want obex push to work out of the box but we don't
    really need webdav and the apache binaries on the default installation.
  - debian/patches:
    + 0001-revert-remove-preferences-application.patch
  0002-revert-data-get-started-by-gsd-sharing.patch
  0003-revert-webdav-fix-launching-server.patch:
   Bring back the preferences app for Unity and modify to allow g-s-d 
sharing
   panel to also work
    + 01_notification.patch: Display an alert box instead of a notification
  for files received.
  - debian/rules:
    + Don't change path to httpd
    + Remove apache 2.2 config

  Changelog entries since current artful version 3.14.2-2ubuntu5:

  gnome-user-share (3.18.3-2) unstable; urgency=medium

    * Fully drop Bluetooth from packaging, obsolete since 3.18.0.
    * Bump Standards-Version to 4.1.0

   -- Jeremy Bicha   Sun, 03 Sep 2017 10:28:16 -0400

  gnome-user-share (3.18.3-1) unstable; urgency=medium

    * New upstream release.
    * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged
  upstream.
    * Bump debhelper compat level to 10.
    * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir.

   -- Michael Biebl   Tue, 20 Sep 2016 12:48:27 +0200

  gnome-user-share (3.18.2-1) unstable; urgency=medium

    * New upstream release.
    * Add Build-Depends on systemd on Linux to get the correct path for the
  systemd user unit directory.
    * Add patch to ensure systemd is not mandatory so we can build on non-Linux
  architectures.

[Desktop-packages] [Bug 1683145] Re: Mouse pointer speed setting has no effect

2017-09-03 Thread Michael MacEachern

This is affecting me even on Kubuntu 17.04, on a fresh install.

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

Title:
  Mouse pointer speed setting has no effect

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

Bug description:
  In Setting, Mouse & Touchpad, changing the Mouse pointer speed has no effect 
after upgrading from 16.10 to 17.04.
  Same with Touchpad pointer speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 16 16:21:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-21 (664 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago)

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

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

[Desktop-packages] [Bug 48097] Re: gedit does not get focus when opening more than one document

2017-09-03 Thread Bug Watch Updater

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

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

Title:
  gedit does not get focus when opening more than one document

Status in gedit:
  Confirmed
Status in gedit package in Ubuntu:
  Invalid

Bug description:
  I already saw this behaviour during the dapper development phase, but
  it somehow got fixed with some updates. Now, some days before the
  dapper release, I've noticed it again.

  Basically, after having open a document, opening a new one will cause
  gedit to remain in the background, whereas it would be expected that
  gedit gets the focus and is brought to the foreground.

  Steps to reproduce:

  1.- Open a Nautilus window.

  2.- In this window, browse a folder that contains text documents.

  3.- Click on a text document. The document will be opened in gedit,
  which will appear on the foreground.

  4.- Go back to the Nautilus window and click on a second document. The
  document will be open in gedit, but this time in will remain in the
  background, while the window list bar is flashing.

  Expected: gedit opens the second document and gets focus (i.e. it
  appears in the foreground).

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

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

[Desktop-packages] [Bug 1714813] Re: No headphone sound with `nvidia-prime` installed.

2017-09-03 Thread Ryan P.C. McQuen

** Also affects: nvidia-prime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  No headphone sound with `nvidia-prime` installed.

Status in ubuntu-mate:
  New
Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Reproduces on:

  Ubuntu Mate: 16.04.3, 17.04, 17.10
  Kubuntu: 17.04, 17.10

  Probably not DE related since it is happening in KDE and Mate.

  Here's the output of `aplay -l` and `lspci`, let me know what other
  details I can provide:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: PCH [HDA Intel PCH], device 2: VT1802 Alt Analog [VT1802 Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2)
  03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 
(rev 01)
  04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)

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

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

[Desktop-packages] [Bug 1714826] [NEW] HiDPI scaling regression on Beta 1

2017-09-03 Thread tylnesh

Public bug reported:

After running today's updates, HiDPI scaling on my 4k 15,6" display
stopped working. Ubuntu dock keeps correct scaling, but top bar, context
menu, and other UI elements revert back to non-scaled dimensions. I can
fix most of the UI with

$ gsettings set org.gnome.desktop.interface scaling-factor 2

but after reboot or logout it reverts back to wrong setting. I solved
the topbar scaling by changing the size of the panel by one pixel
(increase or decrease, doesn't matter. Perplexing, indeed), but can't
find a way to fix context menu scaling.

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

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

Title:
  HiDPI scaling regression on Beta 1

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After running today's updates, HiDPI scaling on my 4k 15,6" display
  stopped working. Ubuntu dock keeps correct scaling, but top bar,
  context menu, and other UI elements revert back to non-scaled
  dimensions. I can fix most of the UI with

  $ gsettings set org.gnome.desktop.interface scaling-factor 2

  but after reboot or logout it reverts back to wrong setting. I solved
  the topbar scaling by changing the size of the panel by one pixel
  (increase or decrease, doesn't matter. Perplexing, indeed), but can't
  find a way to fix context menu scaling.

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

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

[Desktop-packages] [Bug 1419267] Re: libjpegturbo.so missing from -dev package

** Changed in: libjpeg-turbo (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  libjpegturbo.so missing from -dev package

Status in One Hundred Papercuts:
  Invalid
Status in libjpeg-turbo package in Ubuntu:
  Fix Released

Bug description:
  $ dpkg -L libjpeg-turbo8-dev
  /.
  /usr
  /usr/share
  /usr/share/doc
  /usr/share/doc/libjpeg-turbo8-dev
  /usr/share/doc/libjpeg-turbo8-dev/copyright
  /usr/share/doc/libjpeg-turbo8-dev/README.gz
  /usr/share/doc/libjpeg-turbo8-dev/structure.txt.gz
  /usr/share/doc/libjpeg-turbo8-dev/README-turbo.txt.gz
  /usr/share/doc/libjpeg-turbo8-dev/libjpeg.txt.gz
  /usr/lib
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libjpeg.a
  /usr/lib/x86_64-linux-gnu/libturbojpeg.a
  /usr/include
  /usr/include/jerror.h
  /usr/include/turbojpeg.h
  /usr/include/jmorecfg.h
  /usr/include/jpeglib.h
  /usr/include/jpegint.h
  /usr/include/x86_64-linux-gnu
  /usr/include/x86_64-linux-gnu/jconfig.h
  /usr/share/doc/libjpeg-turbo8-dev/changelog.Debian.gz
  /usr/lib/x86_64-linux-gnu/libjpeg.so


  See the libjpeg.so symlink. This is good.

  I also expect a libturbojpeg.so symlink. This is missing. Please add
  so that I can build software which depends on this dynamic library
  without manually creating this symlink.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libturbojpeg 1.3.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Sat Feb  7 08:41:19 2015
  Dependencies:
   gcc-4.9-base 4.9.1-16ubuntu6
   libc6 2.19-10ubuntu2.2
   libgcc1 1:4.9.1-16ubuntu6
   multiarch-support 2.19-10ubuntu2.2
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libjpeg-turbo
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (105 days ago)

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

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

[Desktop-packages] [Bug 1056566] Re: Missing pkgconfig file

** Changed in: libjpeg-turbo (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Missing pkgconfig file

Status in libjpeg-turbo package in Ubuntu:
  Fix Released

Bug description:
  Our packages do not contain a turbojpeg.pc file, meaning any
  pkgconfig-using build script that depends on it being in libjpeg-turbo
  may fail.

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

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

[Desktop-packages] [Bug 364091] Re: xrandr error with delmode

2017-09-03 Thread Elvis de Freitas Souza

Same problem


No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty


xrandr --delmode 'DVI-1' '"1368x768_60.00"'
X Error of failed request:  BadAccess (attempt to access private resource 
denied)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  19 (RRDeleteOutputMode)
  Serial number of failed request:  43
  Current serial number in output stream:  44

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

Title:
  xrandr error with delmode

Status in x11-xserver-utils package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: x11-xserver-utils

  Ubuntu 9.04 Realase Candidate, i386
  My setup:  Sapphire 2600 XT AGP + Compaq P1100 monitor (maximux resolution 
supported  1920x1440) connected via DVI port

  Output of xrandr
  Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 2048 x 1600
  DVI-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 
380mm x 290mm
 2048x1536  60.0  
 1920x1440  75.0 60.0  
 1856x1392  75.0 60.0  
 1792x1344  75.0 60.0  
 1600x1200  85.0*75.0 70.0 65.0 60.0  
 1680x1050  84.9 74.9 69.9 60.0  
 1600x1024  60.2  
 1400x1050  85.0 74.8 70.0 60.0  
 1280x1024  85.0 75.0 60.0  
 1440x900   59.9  
 1280x960   85.0 60.0  
 1360x768   59.8  
 1152x864  100.0 85.1 85.0 75.0 75.0 70.0 60.0  
 1024x768   85.0 75.0 70.1 60.0 43.5  
 832x62474.6  
 800x60085.1 85.1 72.2 75.0 60.3 56.2  
 640x48085.0 75.0 72.8 75.0 66.7 59.9  
 720x40087.8 85.0 70.1  
 640x40085.1  
 640x35085.1  
  VGA-0 disconnected (normal left inverted right x axis y axis)

  Maximum default resolution "2048 x 1600" reported, is wrong for Compaq
  P1100 monitor and i tried to delete with the command:

  $ xrandr --delmode DVI-0 2048x1536
  X Error of failed request:  BadAccess (attempt to access private resource 
denied)
Major opcode of failed request:  150 (RANDR)
Minor opcode of failed request:  19 ()
Serial number of failed request:  23
Current serial number in output stream:  24

  Note: GDM (Login Screen) Bad Screen Refresh Rate

  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM 
Controller/Host-Hub Interface [8086:2570] (rev 02)
Subsystem: ASRock Incorporation Device [1849:2570]
  01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV 630 XT AGP 
[Radeon HD 2600 XT AGP] [1002:9586]
Subsystem: PC Partner Limited Device [174b:0028]

  --- 
  Architecture: i386
  CurrentDmesg:
   [   24.596026] eth0: no IPv6 routers present
   [   26.752026] end_request: I/O error, dev fd0, sector 0
   [   26.784033] end_request: I/O error, dev fd0, sector 0
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  Package: x11-xserver-utils 7.5+1ubuntu2
  PackageArchitecture: i386
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic 
root=UUID=11fd8e9e-15b4-4eba-bb1d-434d4d5282b3 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Tags: lucid lucid
  Uname: Linux 2.6.32-21-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 11/07/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L1.72
  dmi.board.name: ConRoe865PE
  dmi.board.version: 3.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.72:bd11/07/2008:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00:
  dmi.product.name: ConRoe865PE
  dmi.product.version: 3.00
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-21-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/364091/+subscriptions

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

[Desktop-packages] [Bug 1056566] Re: Missing pkgconfig file

in new queue :)

** Changed in: libjpeg-turbo (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Missing pkgconfig file

Status in libjpeg-turbo package in Ubuntu:
  Fix Committed

Bug description:
  Our packages do not contain a turbojpeg.pc file, meaning any
  pkgconfig-using build script that depends on it being in libjpeg-turbo
  may fail.

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

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

[Desktop-packages] [Bug 1419267] Re: libjpegturbo.so missing from -dev package

in new queue :)

** Changed in: libjpeg-turbo (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  libjpegturbo.so missing from -dev package

Status in One Hundred Papercuts:
  Invalid
Status in libjpeg-turbo package in Ubuntu:
  Fix Committed

Bug description:
  $ dpkg -L libjpeg-turbo8-dev
  /.
  /usr
  /usr/share
  /usr/share/doc
  /usr/share/doc/libjpeg-turbo8-dev
  /usr/share/doc/libjpeg-turbo8-dev/copyright
  /usr/share/doc/libjpeg-turbo8-dev/README.gz
  /usr/share/doc/libjpeg-turbo8-dev/structure.txt.gz
  /usr/share/doc/libjpeg-turbo8-dev/README-turbo.txt.gz
  /usr/share/doc/libjpeg-turbo8-dev/libjpeg.txt.gz
  /usr/lib
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libjpeg.a
  /usr/lib/x86_64-linux-gnu/libturbojpeg.a
  /usr/include
  /usr/include/jerror.h
  /usr/include/turbojpeg.h
  /usr/include/jmorecfg.h
  /usr/include/jpeglib.h
  /usr/include/jpegint.h
  /usr/include/x86_64-linux-gnu
  /usr/include/x86_64-linux-gnu/jconfig.h
  /usr/share/doc/libjpeg-turbo8-dev/changelog.Debian.gz
  /usr/lib/x86_64-linux-gnu/libjpeg.so


  See the libjpeg.so symlink. This is good.

  I also expect a libturbojpeg.so symlink. This is missing. Please add
  so that I can build software which depends on this dynamic library
  without manually creating this symlink.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libturbojpeg 1.3.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  Date: Sat Feb  7 08:41:19 2015
  Dependencies:
   gcc-4.9-base 4.9.1-16ubuntu6
   libc6 2.19-10ubuntu2.2
   libgcc1 1:4.9.1-16ubuntu6
   multiarch-support 2.19-10ubuntu2.2
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libjpeg-turbo
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (105 days ago)

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

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

[Desktop-packages] [Bug 1714821] [NEW] FFe: Sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)

Public bug reported:

Please sync gnome-user-share 3.18.3-2 (main) from Debian unstable (main)

The version of gnome-user-share currently in Ubuntu has 2 features:
Bluetooth and WebDav.

Ubuntu has installed gnome-user-share by default for many years so that
sending and receiving files over Bluetooth works. That feature is now
rovided by gnome-bluetooth and gnome-control-center. Therefore, the new
version of gnome-user-share dropped the Bluetooth feature.

Ubuntu has delayed packaging a newer version of gnome-user-share because it
was using unity-control-center which did not support the new Bluetooth feature.

Ubuntu has one long-standing diff from Debian. Ubuntu's gnome-user-share
package does not actually include the apache dependencies needed for the
WebDav feature to work (LP: #536766). Since that's now the only feature in
gnome-user-share, dropping this diff makes sense.

$ reverse-depends gnome-user-share
Reverse-Recommends
==
* cinnamon-desktop-environment
* gnome-bluetooth
* gnome-control-center

Reverse-Depends
===
* gnome-core [amd64 arm64 armhf i386 ppc64el]
* ubuntu-budgie-desktop [amd64 arm64 armhf i386 ppc64el]
* ubuntu-gnome-desktop [amd64 arm64 armhf i386 ppc64el]

Step 1
--
Ubuntu and Ubuntu Budgie both use gnome-control-center so gnome-user-share is 
unused for Bluetooth.

a. Drop the dependency on gnome-user-share from at least
gnome-bluetooth
gnome-control-center
ubuntu-budgie-desktop

But we might need to drop the dependency everywhere until after 18.04
LTS for 1.c. to work.

b. Demote gnome-user-share to universe.

c. Have ubuntu-release-upgrader remove gnome-user-share on upgrades.

Step 2
--
Sync gnome-user-share from Debian.

I believe we want to do Step 1 for Ubuntu 17.10 "artful".

The complication for Step 2 is that upgraders will get Apache installed
unless they upgrade using update-manager/do-release-upgrade

Therefore, I recommend delaying Step 2 until 18.04 development opens.

Explanation of the Ubuntu delta and why it can be dropped:
  * Add git_add_systemd_service.patch:
- Backport commit from 3.22 to add systemd user service file for
  compatibility with gnome-settings-daemon 3.22
  * debian/control.in:
- Build-Depend on systemd
  * d/p/0004-revert-remove-help.patch: Bring back the help files
for users of gnome-file-share-properties (LP: #1570230)
  * debian/patches: 0001-revert-remove-preferences-application.patch
Fix launching of Prefences from nautilus share bar under unity and
patch infobar color (LP: #1562515)
  * maintscript: remove old xdg autostart file (lp: #1526894)
  * New Upstream release (LP: #1518813)
  * Merge with Debian, Remaining changes:
- Suggests the apache2.2-bin and libapache2-mod-dnssd binaries rather than
  depends on those, we want obex push to work out of the box but we don't
  really need webdav and the apache binaries on the default installation.
- debian/patches:
  + 0001-revert-remove-preferences-application.patch
0002-revert-data-get-started-by-gsd-sharing.patch
0003-revert-webdav-fix-launching-server.patch:
 Bring back the preferences app for Unity and modify to allow g-s-d 
sharing
 panel to also work
  + 01_notification.patch: Display an alert box instead of a notification
for files received.
- debian/rules:
  + Don't change path to httpd
  + Remove apache 2.2 config

Changelog entries since current artful version 3.14.2-2ubuntu5:

gnome-user-share (3.18.3-2) unstable; urgency=medium

  * Fully drop Bluetooth from packaging, obsolete since 3.18.0.
  * Bump Standards-Version to 4.1.0

 -- Jeremy Bicha   Sun, 03 Sep 2017 10:28:16 -0400

gnome-user-share (3.18.3-1) unstable; urgency=medium

  * New upstream release.
  * Drop 30-build-Properly-expand-paths-in-gnome-user-share-webd.patch, merged
upstream.
  * Bump debhelper compat level to 10.
  * Use non-multiarch path (/usr/lib/gnome-user-share) for libexecdir.

 -- Michael Biebl   Tue, 20 Sep 2016 12:48:27 +0200

gnome-user-share (3.18.2-1) unstable; urgency=medium

  * New upstream release.
  * Add Build-Depends on systemd on Linux to get the correct path for the
systemd user unit directory.
  * Add patch to ensure systemd is not mandatory so we can build on non-Linux
architectures.
  * Bump Standards-Version to 3.9.8.
  * Drop debian/dirs, no longer needed.
  * Convert from cdbs to dh.
  * Bump debhelper compatibility level to 9.
  * Add patch to properly expand paths in gnome-user-share-webdav.desktop.

 -- Michael Biebl   Fri, 02 Sep 2016 18:16:19 +0200

gnome-user-share (3.18.1-1) unstable; urgency=medium

  * New upstream release.
  * Bump Standards-Version to 3.9.7

 -- Andreas Henriksson   Thu, 24 Mar 2016 16:12:22
+0100

gnome-user-share (3.18.0-1) unstable; urgency=medium

  * New upstream release.
- drops ObexPush support which moved to gnome-bluetooth.
  *

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

2017-09-03 Thread Bug Watch Updater

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

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

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

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

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

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

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

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

  MM debug log output (full log attached):

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

  mmcli output:

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

[Desktop-packages] [Bug 1714818] [NEW] Display won't wake up , and some other problems

2017-09-03 Thread Mantas

Public bug reported:

Desktop pc ,ubuntu 17.04 ,Nvidia GTX1060 ,i7-6700K ,16gb RAM . Display 1 is a 
Philips 1920x1080 monitor ,connected via DVI-D cable , and LG TV 3840x2160 as 
display 2 ,connected via HDMI cable .When TV is turned on ,all icons on the 
desktop (on monitor) could dissapear ,if tv turned off ,they are again in place 
.
Also all active opened windows ( skype ,firefox ,transmission , everything else 
) are moved to TV when tv is turned on,i have to move mouse to tv screen and 
drag them back to monitor.
Also main problem is when TV turned on ,when monitor goes sleep after 10minutes 
of inactivity , it can't wake up ,if tv is turned off first . Monitor and TV 
then both have no in input signal ,moving mouse or pressing keyboard does not 
wake up neither display .Workaround is to move mouse to wake up pc monitor 
first ,then tv can be turned off .Or otherwise ,when no displays working , i 
have to press Alt-Ctrl-F1 , login , then type reboot ,press enter ,then pc 
reboots ,and pc monitor functions again .

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-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  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.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.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.5
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:Unity7
Date: Sun Sep  3 22:32:10 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP106 [GeForce GTX 1060 3GB] 
[1458:3724]
InstallationDate: Installed on 2017-05-21 (105 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=9d598b04-1c8d-4e74-86be-41205eda5f25 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3504
dmi.board.asset.tag: Default string
dmi.board.name: Z170-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Sun Sep  3 15:27:21 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1.1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty

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

Title:
  Display won't wake up ,and some

[Desktop-packages] [Bug 1714816] [NEW] firefox crashes when i want open the download folder caja

2017-09-03 Thread manu

Public bug reported:

hello,

if i download a file with Firefox, if i want opening the folder download
with firefox i have a crash of firefox the folder was never opening and
firefox stay in work.

i use ubuntu mate

thanks

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: firefox 55.0.2+build1-0ubuntu0.17.04.1
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic i686
AddonCompatCheckDisabled: False
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  manu   1504 F pulseaudio
BrokenPermissions: ffmpeg (0o363)
BuildID: 20170816204308
Channel: Unavailable
CurrentDesktop: MATE
Date: Sun Sep  3 21:29:41 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2017-07-27 (38 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release i386 (20170412)
IpRoute:
 default via 192.168.0.254 dev enp1s0 proto static metric 100 
 169.254.0.0/16 dev enp1s0 scope link metric 1000 
 192.168.0.0/24 dev enp1s0 proto kernel scope link src 192.168.0.10 metric 100
IwConfig:
 lono wireless extensions.
 
 enp1s0no wireless extensions.
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefErrors: 'utf-8' codec can't decode byte 0xe9 in position 7462: invalid 
continuation byte
PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816204308 (In use)
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F20
dmi.board.asset.tag: Default string
dmi.board.name: H110M-S2H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20:bd11/08/2016:svnGigabyteTechnologyCo.,Ltd.:pnH110M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: H110M-S2H
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: apport-bug i386 zesty

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

Title:
  firefox crashes when i want open the download folder caja

Status in firefox package in Ubuntu:
  New

Bug description:
  hello,

  if i download a file with Firefox, if i want opening the folder
  download with firefox i have a crash of firefox the folder was never
  opening and firefox stay in work.

  i use ubuntu mate

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 55.0.2+build1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manu   1504 F pulseaudio
  BrokenPermissions: ffmpeg (0o363)
  BuildID: 20170816204308
  Channel: Unavailable
  CurrentDesktop: MATE
  Date: Sun Sep  3 21:29:41 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-07-27 (38 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release i386 (20170412)
  IpRoute:
   default via 192.168.0.254 dev enp1s0 proto static metric 100 
   169.254.0.0/16 dev enp1s0 scope link metric 1000 
   192.168.0.0/24 dev enp1s0 proto kernel scope link src 192.168.0.10 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefErrors: 'utf-8' codec can't decode byte 0xe9 in position 7462: invalid 
continuation byte
  PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=

[Desktop-packages] [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()

2017-09-03 Thread Nicolás Abel Carbone

I am still having this bug even after updating mutter to the
aforementioned version. A update to gnome-shell is also needed?

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

Title:
  gnome-shell crashed with SIGSEGV in on_crtc_flipped() from
  g_closure_invoke() from invoke_flip_closure() from page_flip_handler()
  from drmHandleEvent()

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Gnome shell crashes when trying to log in to the wayland ubuntu
  session. It works fine on Xorg.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Aug 31 11:39:23 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-07-27 (35 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170723)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fdee0bf9296:mov0x1a0(%rax),%rax
   PC (0x7fdee0bf9296) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () at /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () at 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV
  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/1714330/+subscriptions

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

[Desktop-packages] [Bug 1714812] [NEW] XScreensaver crashes for a few seconds after restore from hibernation.

2017-09-03 Thread hritik

Public bug reported:

Hi

Whenever I restore my hibernated PC, I am greeted with the screen I left it 
with (No lock screen).
It remains that way for a while and input/output freezes. After a while (seems 
like eternity) the screen lock appears and then I am able to unlock it.

PS: I've tried disabling XScreensaver and without it the restore happens
like a charm and nothing freezes for a sec.

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

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

Title:
  XScreensaver crashes for a few seconds after restore from hibernation.

Status in xscreensaver package in Ubuntu:
  New

Bug description:
  Hi

  Whenever I restore my hibernated PC, I am greeted with the screen I left it 
with (No lock screen).
  It remains that way for a while and input/output freezes. After a while 
(seems like eternity) the screen lock appears and then I am able to unlock it.

  PS: I've tried disabling XScreensaver and without it the restore
  happens like a charm and nothing freezes for a sec.

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

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

[Desktop-packages] [Bug 1714810] [NEW] gnome-terminal shrinks window to nothing

2017-09-03 Thread Jon Watte

Public bug reported:

Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from the
desktop install, default Theme. The only change is the default window
size in the settings -- I have it at 149x48. This bug happens even with
the default 80x24 window size. The font is the default (not overridden)
Monospace Regular 12.

When running vim in gnome-terminal, there is an ugly margin of terminal-
background color on the right/bottom of the terminal window. My vim
background is gray, my terminal background is green, vim displays gray
background but there is a green border just slightly slimmer than one
character cell on the right/bottom. This also happens for other terminal
programs (including the shell) if they set the background color of
output.

In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints with
the background. I added the following to my gtk.css:

$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}

Now, when I open gnome-terminal, it keeps resizing itself to be shorter
in the Y axis, one line at a time, until it is only one line high. It's
almost like an animation of the window height, collapsing the window to
be very short. After it stops there, I can manually snap the terminal to
top/bottom edges of the screen, and it will stay there, but trying to
resize it will just keep shrinking the height.

This bug is about the resizing behavior. My totally uneducated guess is
that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the window,
measures contents, decides to attempt to "snap" to size of character
cell, rounds down, window gets shorter, terminal measures contents,
decides to attempt to "snap" to size of character cell, rounds down,
window gets shorter, ...

If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for that.

$ lsb_release -rd
Description:Ubuntu 17.04
Release:17.04

$ apt-cache policy gnome-terminal
gnome-terminal:
Installed: 3.20.2-1ubuntu8
Candidate: 3.20.2-1ubuntu8

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

** Attachment added: "screen capture showing the bug"

https://bugs.launchpad.net/bugs/1714810/+attachment/4943672/+files/2017-09-03-gnome-terminal-2017-09-03_10.44.05.mp4

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

Title:
gnome-terminal shrinks window to nothing

Status in gnome-terminal package in Ubuntu:
New

Bug description:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from
the desktop install, default Theme. The only change is the default
window size in the settings -- I have it at 149x48. This bug happens
even with the default 80x24 window size. The font is the default (not
overridden) Monospace Regular 12.

When running vim in gnome-terminal, there is an ugly margin of
terminal-background color on the right/bottom of the terminal window.
My vim background is gray, my terminal background is green, vim
displays gray background but there is a green border just slightly
slimmer than one character cell on the right/bottom. This also happens
for other terminal programs (including the shell) if they set the
background color of output.

In an attempt to at least make this less ugly, I tried to add some
padding to the terminal to center the drawable area that vim paints
with the background. I added the following to my gtk.css:

$ cat .config/gtk-3.0/gtk.css
vte-terminal {
padding: 8px 8px 5px 1px;
}

Now, when I open gnome-terminal, it keeps resizing itself to be
shorter in the Y axis, one line at a time, until it is only one line
high. It's almost like an animation of the window height, collapsing
the window to be very short. After it stops there, I can manually snap
the terminal to top/bottom edges of the screen, and it will stay
there, but trying to resize it will just keep shrinking the height.

This bug is about the resizing behavior. My totally uneducated guess
is that there's some off-by-one error when allocating space for the
terminal window contents. Terminal calculates contents, sets the
window, measures contents, decides to attempt to "snap" to size of
character cell, rounds down, window gets shorter, terminal measures
contents, decides to attempt to "snap" to size of character cell,
rounds down, window gets shorter, ...

If that is, indeed, the case, then the other bug (the ugly border) may
be caused by the same problem, but I will file a separate bug for
that.

$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04

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

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

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 #1714330, 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/1714795/+attachment/4943632/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1714330
   gnome-shell crashed with SIGSEGV in on_crtc_flipped() from 
g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from 
drmHandleEvent()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep  3 18:02:00 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f10fdbfa836:mov0x1a0(%rax),%rax
   PC (0x7f10fdbfa836) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1714797] [NEW] Pressing eject button in Gnome Files displays message that internal DVD-ROM drive can be removed

2017-09-03 Thread Alex Jones

Public bug reported:

Pressing the eject button (in the Gnome Files user interface, not the
physical button on the drive) for an internal SATA DVD-ROM drive causes
a message to appear that the drive can be removed. After this, the drive
is no longer accessible from within Gnome Files until the computer is
rebooted.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.25.92-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep  3 12:19:52 2017
InstallationDate: Installed on 2017-09-03 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Pressing eject button in Gnome Files displays message that internal
  DVD-ROM drive can be removed

Status in nautilus package in Ubuntu:
  New

Bug description:
  Pressing the eject button (in the Gnome Files user interface, not the
  physical button on the drive) for an internal SATA DVD-ROM drive
  causes a message to appear that the drive can be removed. After this,
  the drive is no longer accessible from within Gnome Files until the
  computer is rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.25.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 12:19:52 2017
  InstallationDate: Installed on 2017-09-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714793] Re: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it be

** Tags removed: need-duplicate-check

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

Title:
  package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed
  to install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in signon package in Ubuntu:
  New

Bug description:
  hp envy dv6 finerprint reader authentication error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-92.115-lowlatency 4.4.76
  Uname: Linux 4.4.0-92-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Sep  3 08:41:03 2017
  DuplicateSignature:
   package:libsignon-extension1:amd64:8.58+16.04.20151106-0ubuntu1
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libsignon-extension1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-02-17 (198 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: signon
  Title: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1711337] Re: Firefox crashes at start on armv7L after 55.0.1 update

2017-09-03 Thread Adam Smith

** Bug watch added: Mozilla Bugzilla #1391802
   https://bugzilla.mozilla.org/show_bug.cgi?id=1391802

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1391802
   Importance: Unknown
   Status: Unknown

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

Title:
  Firefox crashes at start on armv7L after 55.0.1 update

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Firefox always crashes when launched after the 55.0.1 update on an
  Orange Pi PC Plus (a single-board computer similar to a Raspberry Pi),
  even in safe mode.

  I did a fresh install of Armbian (a Ubuntu Xenial 16.04 re-spin for
  ARM single-board computer) on a similar board (Orange Pi Plus 2e),
  installed Firefox and experienced the same problem--it won't load
  without crashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.1+build2-0ubuntu0.16.04.2
  Uname: Linux 3.4.113-sun8i armv7l
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: armhf
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jim1138 F pulseaudio
   /dev/snd/controlC0:  jim1138 F pulseaudio
  BuildID: 20170814194718
  Card0.Amixer.info:
   Card hw:0 'audiocodec'/'audiocodec'
 Mixer name : ''
 Components : ''
 Controls  : 12
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'sndhdmi'/'sndhdmi'
 Mixer name : ''
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'hdmi audio format Function',0
 Capabilities: enum
 Items: 'null' 'pcm' 'AC3' 'MPEG1' 'MP3' 'MPEG2' 'AAC' 'DTS' 'ATRAC' 
'ONE_BIT_AUDIO' 'DOLBY_DIGITAL_PLUS' 'DTS_HD' 'MAT' 'WMAPRO'
 Item0: 'pcm'
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu Aug 17 05:37:00 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.10.1 dev eth0 
   default via 192.168.10.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.10.0/24 dev eth0  proto kernel  scope link  src 192.168.10.107 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.108  
metric 600
  Locales: extensions.sqlite corrupt or missing
  PciMultimedia:
   
  PciNetwork:
   
  Profiles: Profile0 (Default) - LastVersion=55.0.1/20170814194718
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714268] Re: Typo in german package description.

2017-09-03 Thread Hans Joachim Desserud

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

** Tags added: xenial

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

Title:
  Typo in german package description.

Status in Ubuntu Translations:
  New
Status in libreoffice package in Ubuntu:
  New

Bug description:
  The german package description shown with $ apt show libreoffice;
  starts with Libre0ffice; that is a zero instead of capital o.

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

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

[Desktop-packages] [Bug 1714793] [NEW] package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it

2017-09-03 Thread Adam Welchel

Public bug reported:

hp envy dv6 finerprint reader authentication error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-92.115-lowlatency 4.4.76
Uname: Linux 4.4.0-92-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Sun Sep  3 08:41:03 2017
DuplicateSignature:
 package:libsignon-extension1:amd64:8.58+16.04.20151106-0ubuntu1
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package libsignon-extension1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-02-17 (198 days ago)
InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: signon
Title: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed
  to install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in signon package in Ubuntu:
  New

Bug description:
  hp envy dv6 finerprint reader authentication error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-92.115-lowlatency 4.4.76
  Uname: Linux 4.4.0-92-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Sep  3 08:41:03 2017
  DuplicateSignature:
   package:libsignon-extension1:amd64:8.58+16.04.20151106-0ubuntu1
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libsignon-extension1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-02-17 (198 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: signon
  Title: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-09-03 Thread NJ

@terry69lawson and other frustrated users: perhaps you are in a position
to try *WireGuard* as a replacement for OpenVPN (or for other methods of
connecting to a VPN). Your VPN provider will need to have WireGuard
servers for this to work. If your provider does have such servers, then
you are in luck, for not only does Wireguard work with the latest
(unfixed) Network Manager, it's also fast and easy. Still, it's also
still in development and, though it has had some testing and had good
reviews, it is not guaranteed secure.

Still, I am amazed and boggled that Canonical has not fixed the problem.
Perhaps it's been fixed in a newer version of Ubuntu and not backported?
A bit of information, clearly presented, would not go amiss (@cyphermox)

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-09-03 Thread Seumas Finlayson

Now NONE of my Ubuntu machines, on Xenial or Zesty, will use my VPN for
even a brief time. I've tried several different versions of packages,
but nothing. This is absolutely intolerable. Fix this soon Canonical or
I will be forced to leave for a different Linux distro.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

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

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

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 #1714330, 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/1714784/+attachment/4943538/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1714330
   gnome-shell crashed with SIGSEGV in on_crtc_flipped() from 
g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from 
drmHandleEvent()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upgraded Artful to gnome-shell 3.25.91-0ubuntu2 and did a restart and
  this crash popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep  3 22:33:43 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-07-17 (48 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f34b0c56836:mov0x1a0(%rax),%rax
   PC (0x7f34b0c56836) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1714785] Re: package transmission-daemon 2.84-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package transmission-daemon 2.84-3ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in transmission package in Ubuntu:
  New

Bug description:
  Every time turn on PC, I get a error. But transmission-daemon run
  perfect.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: transmission-daemon 2.84-3ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Sep  3 16:39:01 2017
  DpkgHistoryLog:
   Start-Date: 2017-09-03  16:38:37
   Commandline: aptdaemon role='role-install-packages' sender=':1.64'
   Install: libportmidi0:i386 (1:200-0ubuntu3, automatic), liblapack3:i386 
(3.6.0-2ubuntu2, automatic), bubbros:i386 (1.6.2-1), libblas-common:i386 
(3.6.0-2ubuntu2, automatic), python-pygame:i386 (1.9.1release+dfsg-10, 
automatic), libgfortran3:i386 (5.4.0-6ubuntu1~16.04.4, automatic), 
libsdl1.2debian:i386 (1.2.15+dfsg1-3, automatic), libsdl-ttf2.0-0:i386 
(2.0.11-3, automatic), libsdl-mixer1.2:i386 (1.2.12-11build1, automatic), 
libmikmod3:i386 (3.3.8-2, automatic), libsdl-image1.2:i386 (1.2.12-5build2, 
automatic), libblas3:i386 (3.6.0-2ubuntu2, automatic), python-numpy:i386 
(1:1.11.0-1ubuntu1, automatic), libsmpeg0:i386 (0.4.5+cvs20030824-7.1, 
automatic)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-09 (542 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: transmission
  Title: package transmission-daemon 2.84-3ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-07-06 (58 days ago)
  mtime.conffile..etc.transmission-daemon.settings.json: 
2017-09-03T16:31:06.665438

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

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

[Desktop-packages] [Bug 1714785] [NEW] package transmission-daemon 2.84-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-09-03 Thread srsiempre

Public bug reported:

Every time turn on PC, I get a error. But transmission-daemon run
perfect.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: transmission-daemon 2.84-3ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Sun Sep  3 16:39:01 2017
DpkgHistoryLog:
 Start-Date: 2017-09-03  16:38:37
 Commandline: aptdaemon role='role-install-packages' sender=':1.64'
 Install: libportmidi0:i386 (1:200-0ubuntu3, automatic), liblapack3:i386 
(3.6.0-2ubuntu2, automatic), bubbros:i386 (1.6.2-1), libblas-common:i386 
(3.6.0-2ubuntu2, automatic), python-pygame:i386 (1.9.1release+dfsg-10, 
automatic), libgfortran3:i386 (5.4.0-6ubuntu1~16.04.4, automatic), 
libsdl1.2debian:i386 (1.2.15+dfsg1-3, automatic), libsdl-ttf2.0-0:i386 
(2.0.11-3, automatic), libsdl-mixer1.2:i386 (1.2.12-11build1, automatic), 
libmikmod3:i386 (3.3.8-2, automatic), libsdl-image1.2:i386 (1.2.12-5build2, 
automatic), libblas3:i386 (3.6.0-2ubuntu2, automatic), python-numpy:i386 
(1:1.11.0-1ubuntu1, automatic), libsmpeg0:i386 (0.4.5+cvs20030824-7.1, 
automatic)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-03-09 (542 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: transmission
Title: package transmission-daemon 2.84-3ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-07-06 (58 days ago)
mtime.conffile..etc.transmission-daemon.settings.json: 
2017-09-03T16:31:06.665438

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


** Tags: apport-package i386 xenial

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

Title:
  package transmission-daemon 2.84-3ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in transmission package in Ubuntu:
  New

Bug description:
  Every time turn on PC, I get a error. But transmission-daemon run
  perfect.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: transmission-daemon 2.84-3ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Sep  3 16:39:01 2017
  DpkgHistoryLog:
   Start-Date: 2017-09-03  16:38:37
   Commandline: aptdaemon role='role-install-packages' sender=':1.64'
   Install: libportmidi0:i386 (1:200-0ubuntu3, automatic), liblapack3:i386 
(3.6.0-2ubuntu2, automatic), bubbros:i386 (1.6.2-1), libblas-common:i386 
(3.6.0-2ubuntu2, automatic), python-pygame:i386 (1.9.1release+dfsg-10, 
automatic), libgfortran3:i386 (5.4.0-6ubuntu1~16.04.4, automatic), 
libsdl1.2debian:i386 (1.2.15+dfsg1-3, automatic), libsdl-ttf2.0-0:i386 
(2.0.11-3, automatic), libsdl-mixer1.2:i386 (1.2.12-11build1, automatic), 
libmikmod3:i386 (3.3.8-2, automatic), libsdl-image1.2:i386 (1.2.12-5build2, 
automatic), libblas3:i386 (3.6.0-2ubuntu2, automatic), python-numpy:i386 
(1:1.11.0-1ubuntu1, automatic), libsmpeg0:i386 (0.4.5+cvs20030824-7.1, 
automatic)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-03-09 (542 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: transmission
  Title: package transmission-daemon 2.84-3ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-07-06 (58 days ago)
  mtime.conffile..etc.transmission-daemon.settings.json: 
2017-09-03T16:31:06.665438

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

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

[Desktop-packages] [Bug 1714783] [NEW] beta 1 release screen scrambling upon startup.

2017-09-03 Thread Charlie Luna

Public bug reported:

This issue just happened with this beta 1 release. This was during a
cold startup. I'll retry a cold startup after this to see if the problem
is replicated and then I'll make comments in regards to that
investigation. I'm including a pic of what happened. I apologize for the
flash, it's automatic on my phone.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu2
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep  3 07:12:12 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-09-01 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Attachment added: "IMG_0042.JPG"
   
https://bugs.launchpad.net/bugs/1714783/+attachment/4943533/+files/IMG_0042.JPG

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

Title:
  *beta 1 release* screen scrambling upon startup.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1573206] Re: GNOME Software does not install third-party .deb packages

2017-09-03 Thread Andreas Alpha Frisandy

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

Same with ubuntu 16.04.3 LTS

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

Title:
  GNOME Software does not install third-party .deb packages

Status in gdebi:
  New
Status in GNOME Software:
  New
Status in GRadio:
  New
Status in SoundConverter:
  New
Status in Ubuntu GNOME:
  Triaged
Status in Ubuntu Studio:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 LTS (clean install). 64-bit. Final release.
  Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
    Version table:
   *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I intended to install MEGA Sync Client, Google Chrome and Dropbox by
  downloading the needed packages from their websites (respectively
  https://mega.nz/#sync and https://www.google.com/chrome/ and
  https://www.dropbox.com/install?os=lnx ). I opened the packages one by
  one with gnome-software and pressed Install - nothing, except for a
  super-quick progress bar animation, happened. No matter how many times
  I tried, same result. Also, an icon pops up on the panel saying
  "Waiting to install", but nothing seems to happen.

  This only seems to happen with third-party packages; installing a
  random deb from packages.ubuntu.com/xenial worked.

  I even tried to reinstall the system to make this work, but same
  problem.

  Gdebi, however, installs the packages as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  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 21 21:01:52 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nn_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1643183] Re: Natural scrolling is not working

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

** This bug is no longer a duplicate of bug 1683016
   Zesty: Touchpad natural scrolling doesn't work
** This bug has been marked a duplicate of bug 1686081
   If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

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

Title:
  Natural scrolling is not working

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

Bug description:
  Natural scrolling is not working even weather it's on or off nothing
  changed in Zesty Zapus with Budgie Desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-control-center 1:3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-1.2-generic 4.9.0-rc5
  Uname: Linux 4.9.0-1-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Nov 19 17:15:39 2016
  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/1643183/+subscriptions

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

[Desktop-packages] [Bug 1643183] Re: Natural scrolling is not working

2017-09-03 Thread Bernard Banko

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

#7 solution worked for me. Thanks.

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

Title:
  Natural scrolling is not working

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

Bug description:
  Natural scrolling is not working even weather it's on or off nothing
  changed in Zesty Zapus with Budgie Desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-control-center 1:3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-1.2-generic 4.9.0-rc5
  Uname: Linux 4.9.0-1-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Nov 19 17:15:39 2016
  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/1643183/+subscriptions

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

[Desktop-packages] [Bug 1714777] Re: GUI becomes irresponsive, eventually crashes

2017-09-03 Thread JPi

It might be useful to know that I am using nvidia drivers 
$ apt-cache policy nvidia-375
nvidia-375:
  Installed: 375.66-0ubuntu0.17.04.1
  Candidate: 375.66-0ubuntu0.17.04.1
  Version table:
 *** 375.66-0ubuntu0.17.04.1 500
500 http://ch.archive.ubuntu.com/ubuntu zesty-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/restricted amd64 
Packages
100 /var/lib/dpkg/status
 375.39-0ubuntu5 500
500 http://ch.archive.ubuntu.com/ubuntu zesty/restricted amd64 Packages

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

Title:
  GUI becomes irresponsive, eventually crashes

Status in inkscape package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Create a line with Bezier tool (Shift+F6)
  2. Add an arrow head to the end path using the Fill and Stroke properties.
  3. Clone the path
  4. Unselect everything by clicking in the drawing

  From there on I cannot select the orginal line, even if I select the clone 
and do Shift+D. 
  The menus do not render anymore. Eventually Inkscape crashes.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  $ uname -ra
  Linux poma 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  $ apt-cache policy inkscape
  inkscape:
Installed: 0.92.1-1
Candidate: 0.92.1-1
Version table:
   *** 0.92.1-1 500
  500 http://ch.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1714777] [NEW] GUI becomes irresponsive, eventually crashes

2017-09-03 Thread JPi

Public bug reported:

To reproduce:

1. Create a line with Bezier tool (Shift+F6)
2. Add an arrow head to the end path using the Fill and Stroke properties.
3. Clone the path
4. Unselect everything by clicking in the drawing

>From there on I cannot select the orginal line, even if I select the clone and 
>do Shift+D. 
The menus do not render anymore. Eventually Inkscape crashes.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty

$ uname -ra
Linux poma 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

$ apt-cache policy inkscape
inkscape:
  Installed: 0.92.1-1
  Candidate: 0.92.1-1
  Version table:
 *** 0.92.1-1 500
500 http://ch.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  GUI becomes irresponsive, eventually crashes

Status in inkscape package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Create a line with Bezier tool (Shift+F6)
  2. Add an arrow head to the end path using the Fill and Stroke properties.
  3. Clone the path
  4. Unselect everything by clicking in the drawing

  From there on I cannot select the orginal line, even if I select the clone 
and do Shift+D. 
  The menus do not render anymore. Eventually Inkscape crashes.

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  $ uname -ra
  Linux poma 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  $ apt-cache policy inkscape
  inkscape:
Installed: 0.92.1-1
Candidate: 0.92.1-1
Version table:
   *** 0.92.1-1 500
  500 http://ch.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

2017-09-03 Thread Joel Van Boxtel

this also affects 32bit systems

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1603324] Re: file-roller crashed with SIGSEGV in confirmation_dialog_response()

** Tags added: artful

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

Title:
  file-roller crashed with SIGSEGV in confirmation_dialog_response()

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Error after unzip a file. It seems to have unzipped it correctly
  though

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: file-roller 3.20.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 15 14:53:45 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2012-11-25 (1328 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627)
  ProcCmdline: file-roller --extract-here --notify 
file:///home/username/aaa/bbb/ccc/ddd.zip 
file:///home/username/aaa/bbb/ccc/eee.zip
  ProcEnviron:
   LANGUAGE=en_SG:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to yakkety on 2015-03-14 (488 days ago)
  UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo 
vboxusers

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

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

[Desktop-packages] [Bug 1714775] Re: file-roller crashed with SIGSEGV in g_closure_invoke()

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

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 #1603324, 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/1714775/+attachment/4943490/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1603324
   file-roller crashed with SIGSEGV in confirmation_dialog_response()

** 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 file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1714775

Title:
  file-roller crashed with SIGSEGV in g_closure_invoke()

Status in file-roller package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: file-roller 3.25.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep  3 13:25:43 2017
  ExecutablePath: /usr/bin/file-roller
  InstallationDate: Installed on 2017-06-18 (76 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170618)
  ProcCmdline: file-roller --extract-here --notify 
file:///home/username/%D0%A0%D0%B0%D0%B1%D0%BE%D1%87%D0%B8%D0%B9%20%D1%81%D1%82%D0%BE%D0%BB/NakScience312017.rar
 
file:///home/username/%D0%A0%D0%B0%D0%B1%D0%BE%D1%87%D0%B8%D0%B9%20%D1%81%D1%82%D0%BE%D0%BB/SE072016.rar
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb364e5c4c5:  mov0x1e0(%rax),%rbp
   PC (0xb364e5c4c5) ok
   source "0x1e0(%rax)" (0x01e0) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: file-roller
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: file-roller crashed with SIGSEGV in g_closure_invoke()
  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/file-roller/+bug/1714775/+subscriptions

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

[Desktop-packages] [Bug 1707393] Re: vlc no longer displays certain streams since update vdpau

2017-09-03 Thread Dimitri Papadopoulos

About the packages that were upgraded. This bug appeared a few days
before it was reported here on 2017-07-29. I can remember I tried to
investigate for a few days before finding and confirming this bug
report.

>From my file/var/log/apt/history.log.2.gz on my own computer I see that
I installed "vdpauinfo" on 2017-07-27, probably in order to investigate
this bug:

Start-Date: 2017-07-27  22:30:56
Commandline: apt install vdpauinfo
Requested-By: dimitri (1000)
Install: vdpauinfo:amd64 (1.0-1)
End-Date: 2017-07-27  22:31:01

So the updates responsible for this bug probably occurred hours to days
before that. I think this update is responsible:

Start-Date: 2017-07-27  21:32:51
Commandline: aptdaemon role='role-commit-packages' sender=':1.93'
Install: libllvm4.0:amd64 (1:4.0-1ubuntu1~16.04.1, automatic), libllvm4.0:i386 
(1:4.0-1ubuntu1~16.04.1, automatic), libwayland-bin:a
md64 (1.12.0-1~ubuntu16.04.1, automatic), libinput-bin:amd64 
(1.6.3-1ubuntu1~16.04.1, automatic), libsensors4:i386 (1:3.4.0-2, automatic)
Upgrade: libgles2-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 
17.0.7-0ubuntu0.16.04.1), libdrm-nouveau2:amd64 (2.4.70-1~ubuntu16.04.1, 
2.4.76-1~ubuntu16.04.1), libdrm-nouveau2:i386 (2.4.70-1~ubuntu16.04.1, 
2.4.76-1~ubuntu16.04.1), libwacom-common:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), 
libegl1-mesa-dev:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), 
libglapi-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), 
libglapi-mesa:i386 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), 
gnome-software:amd64 (3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1, 
3.20.5-0ubuntu0.16.04.5), xfonts-utils:amd64 (1:7.7+3, 1:7.7+3ubuntu0.16.04.2), 
libxatracker2:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), 
libwacom-bin:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), libegl1-mesa:amd64 
(12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgbm1:amd64 
(12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libwayland-client0:amd64 
(1.9.0-1, 1.12.0-1~ubuntu16.04.1), x11proto-core-dev:amd64 (7.0.28-
 2ubuntu1, 7.0.31-1~ubuntu16.04.1), libdrm-amdgpu1:amd64 
(2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-amdgpu1:i386 
(2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libwayland-dev:amd64 
(1.9.0-1, 1.12.0-1~ubuntu16.04.1), ubuntu-software:amd64 
(3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1, 3.20.5-0ubuntu0.16.04.5), 
libwayland-egl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), 
libxfont1:amd64 (1:1.5.1-1, 1:1.5.1-1ubuntu0.16.04.1), libdrm2:amd64 
(2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm2:i386 
(2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libgl1-mesa-dri:amd64 
(12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-dri:i386 
(12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-glx:amd64 
(12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-glx:i386 
(12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libdrm-intel1:amd64 
(2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-intel1:i386 
(2.4.70-1~ubuntu16.04.1,
  2.4.76-1~ubuntu16.04.1), libwacom2:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), 
libdrm-radeon1:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), 
libdrm-radeon1:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), 
mesa-vdpau-drivers:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), 
virtualbox-5.1:amd64 (5.1.24-117012~Ubuntu~xenial, 
5.1.26-117224~Ubuntu~xenial), gnome-software-common:amd64 
(3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1, 3.20.5-0ubuntu0.16.04.5), 
libdrm-dev:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), 
libwayland-server0:amd64 (1.9.0-1, 1.12.0-1~ubuntu16.04.1), libinput10:amd64 
(1.2.3-1ubuntu1, 1.6.3-1ubuntu1~16.04.1), libwayland-cursor0:amd64 (1.9.0-1, 
1.12.0-1~ubuntu16.04.1)
End-Date: 2017-07-27  21:35:59

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

Title:
  vlc no longer displays certain streams since update vdpau

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Display was fine until apdate of vdpau was applied.
  Vlc codec info from stream:
  Video
  MPEG-4 Video (mp4v)
  Resolution: 640x480
  Framerate: 1000
  Decode format: planar 4:2:0 YUV

  Previous recordings of this stream will also do not display anymore, while 
the standard Videos apllication does play them back fine.
  New recordings via vlc cannot be played back by both the vlc and Videos 
application.

  Console output while starting the stream:
  VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
  [01589088] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [7f86a9b8] core input error: ES_OUT_RESET_PCR called
  [7f86b00092d8] vdpau_avcodec generic error: decoder profile not 
supported: 12
  [7f86b0007ac8] vdpau_avcodec generic error: decoder profile not 
supported: 12

[Desktop-packages] [Bug 1707393] Re: vlc no longer displays certain streams since update vdpau

2017-09-03 Thread Dimitri Papadopoulos

As a workaround switching the "Output" parameter from "Automatic" to
"X11 video output (XCB)" restores video.

But then vlc keeps printing these error messages:

[7ff124060808] core blend error: blending YUVA to VDV0 failed
[7ff124060808] blend blend error: no matching alpha blending routine 
(chroma: YUVA -> VDV0)


** Attachment added: "Screen captur showing the parameter to change."
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707393/+attachment/4943466/+files/Output.png

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

Title:
  vlc no longer displays certain streams since update vdpau

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Display was fine until apdate of vdpau was applied.
  Vlc codec info from stream:
  Video
  MPEG-4 Video (mp4v)
  Resolution: 640x480
  Framerate: 1000
  Decode format: planar 4:2:0 YUV

  Previous recordings of this stream will also do not display anymore, while 
the standard Videos apllication does play them back fine.
  New recordings via vlc cannot be played back by both the vlc and Videos 
application.

  Console output while starting the stream:
  VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
  [01589088] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [7f86a9b8] core input error: ES_OUT_RESET_PCR called
  [7f86b00092d8] vdpau_avcodec generic error: decoder profile not 
supported: 12
  [7f86b0007ac8] vdpau_avcodec generic error: decoder profile not 
supported: 12
  [7f869c001d08] vdpau_display vout display error: output surface creation 
failure: A catch-all error, used when no other error code applies.
  [mpeg4 @ 0x7f869803dfa0] warning: first frame is no keyframe
  [7f869c001d08] vdpau_display vout display error: output surface creation 
failure: A catch-all error, used when no other error code applies.
  [7f869c001d08] vdpau_display vout display error: output surface creation 
failure: A catch-all error, used when no other error code applies.
  [7f869c001d08] vdpau_display vout display error: output surface creation 
failure: A catch-all error, used when no other error code applies.
  [7f869c001d08] vdpau_display vout display error: output surface creation 
failure: A catch-all error, used when no other error code applies.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-5ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 29 15:02:01 2017
  InstallationDate: Installed on 2017-06-17 (42 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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 #1714330, 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/1714770/+attachment/4943456/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1714330
   gnome-shell crashed with SIGSEGV in on_crtc_flipped() from 
g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from 
drmHandleEvent()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It's abug following bug 1713026.  There was a new update to day to get
  version 4.12.0-13 and dont matches. version 4.12.0-12 stay I force
  update buy looking for and install 4.12.0-13 with synaptic program
  Restart ok and all things get right. Except bug now with gnome-
  shellcrashed with Sigsegv... Colour, contrast, gamma, all parameters
  ok

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Sep  3 13:35:51 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-02-16 (198 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fa673537836:mov0x1a0(%rax),%rax
   PC (0x7fa673537836) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1714410] Re: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig

2017-09-03 Thread Shwan

If someone is impatioen like me (we are running a pre-releae) and needs
the monitors set up now

sudo add-apt-repository ppa:gnome3-team/gnome3-staging
sudo apt update 
sudo apt full-upgrade

and when this bug is closed or some time by next week,

sudo ppa-purge ppa:gnome3-team/gnome3-staging

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

Title:
  Can't change display configuration, Method ApplyConfiguration is not
  implemented on interface org.gnome.Mutter.DisplayConfig

Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Since last night's updates, I can no longer change screen resolution
  or monitor alignment in gnome-control-center anymore (in gnome-shell
  running under Wayland).

  gnome-control-center fails silently in the GUI but reports this from
  the command line:

  (gnome-control-center:5887): display-cc-panel-WARNING **: Error
  applying configuration:
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method
  ApplyConfiguration is not implemented on interface
  org.gnome.Mutter.DisplayConfig

  All the available display modes are listed in gnome-control-center
  (you just can't select them).

  On the initial login, xrandr only showed two screen resolutions, one
  for screen XWAYLAND0 of 3840x2160 and another for XWAYLAND1 of
  1920x1080, but after unplugging the external monitor and re-plugging
  it, now xrandr shows eDP-1 with all available modes and HDMI-1 with
  all available modes (you just can't select them from g-c-c).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu6
  Uname: Linux 4.13.0-041300rc7-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  1 11:47:50 2017
  InstallationDate: Installed on 2017-08-16 (15 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-08-17 (15 days ago)

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

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

[Desktop-packages] [Bug 1714766] [NEW] Software center apt failure at 15% when loading programs

2017-09-03 Thread Verner Cutter

Public bug reported:

I have just loaded the Ubuntu from LINUX format July 2017 edition, onto
my wifes computer. I tried to load a DVD player onto the computer (a
Lenovo ideapad 305) and every program that I try fails at 15% with an
error "apt exception failure", I have since gone to the room above the
room I was in (where the router is) and have managed to load VLC player
without a problem. Any ideas why and how I can make it easier to use
WiFi in all rooms in my semi-detached 3 bed house. I wondered if it was
the software or the computer (which has just been bought, pre-installed
with Windows 10. Widows 10 has been totally removed as it refused to
allow dual boot.

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

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

Title:
  Software center apt failure at 15% when loading programs

Status in software-center package in Ubuntu:
  New

Bug description:
  I have just loaded the Ubuntu from LINUX format July 2017 edition,
  onto my wifes computer. I tried to load a DVD player onto the computer
  (a Lenovo ideapad 305) and every program that I try fails at 15% with
  an error "apt exception failure", I have since gone to the room above
  the room I was in (where the router is) and have managed to load VLC
  player without a problem. Any ideas why and how I can make it easier
  to use WiFi in all rooms in my semi-detached 3 bed house. I wondered
  if it was the software or the computer (which has just been bought,
  pre-installed with Windows 10. Widows 10 has been totally removed as
  it refused to allow dual boot.

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep  3 02:41:44 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (562 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7feb5dff7e26 :
mov(%rdi),%rdi
   PC (0x7feb5dff7e26) ok
   source "(%rdi)" (0x3fe0) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/gnome-shell/libgnome-shell.so
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: Upgraded to artful on 2017-05-02 (123 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin 
mock plugdev sambashare sbuild sudo wireshark

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

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

[Desktop-packages] [Bug 1714763] [NEW] No way to disable system startup sound

2017-09-03 Thread George Shuklin

Public bug reported:

Package gnome-session-canberra contains
/usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop
file, which plays extremely annoying drum sound at every boot.

This is a problem (at least for me, but I think for many others), and
there is no way to disable this without changing package-provided files.
Moreover, this package (gnome-session-canberra) couldn't be removed
without breaking ubuntu-desktop package (I'll file separate bugreport
for this).

Propose: Create a way do disable those sounds in a user-available way.
The simplest way I can propose is to mark
/usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop as
conffile, which will keep user changes in this file during package
upgrade.

More user-friendly (visible) changes would be appreciated too, but
conffile should, at least, give some way to manage loud 'blam-blam' at
boot.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-session-canberra 0.30-3ubuntu1 [modified: 
usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop]
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Sun Sep  3 12:55:31 2017
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
InstallationDate: Installed on 2017-06-22 (73 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
SourcePackage: libcanberra
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  No way to disable system startup sound

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Package gnome-session-canberra contains
  /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop
  file, which plays extremely annoying drum sound at every boot.

  This is a problem (at least for me, but I think for many others), and
  there is no way to disable this without changing package-provided
  files. Moreover, this package (gnome-session-canberra) couldn't be
  removed without breaking ubuntu-desktop package (I'll file separate
  bugreport for this).

  Propose: Create a way do disable those sounds in a user-available way.
  The simplest way I can propose is to mark
  /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop
  as conffile, which will keep user changes in this file during package
  upgrade.

  More user-friendly (visible) changes would be appreciated too, but
  conffile should, at least, give some way to manage loud 'blam-blam' at
  boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session-canberra 0.30-3ubuntu1 [modified: 
usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop]
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sun Sep  3 12:55:31 2017
  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
  InstallationDate: Installed on 2017-06-22 (73 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  SourcePackage: libcanberra
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714762] Re: gvfsd-mtp crashed with SIGSEGV

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

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 #1706097, 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/1714762/+attachment/4943435/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  just plugged in android phone

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.33.91-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Sep  3 10:37:50 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2014-08-13 (1116 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.10 /org/gtk/gvfs/exec_spaw/1
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f7a40b7e5a9:mov0x18(%rax),%rax
   PC (0x7f7a40b7e5a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1275727] Re: [ENH] Add pt-BR spell & grammar check as full package

2017-09-03 Thread Adolfo Jayme

** Tags added: needs-packaging

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [ENH] Add pt-BR spell & grammar check as full package

Status in libreoffice package in Ubuntu:
  New

Bug description:
  As for English, Hungarian and Russian, add Brazilian Portuguese
  package for grammar and spell checks in Ubuntu/Debian.

  For en, hu, and ru, there ase the packages:

  libreoffice-lightproof-en
  libreoffice-lightproof-hu
  libreoffice-lightproof-ru-ru

  I am asking to add
  libreoffice-lightproof-pt-BR

  This will avoid many user question on "where is the grammar and spell
  checker of pt-BR in my linux?".

  Source code is in

  dictionary/pt-BR/

  Information on the spell check and grammar chek of LibreOffice for pt-
  BR are in (but in portuguese)

  http://pt-br.libreoffice.org/projetos/projeto-vero-verificador-
  ortografico/

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

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

[Desktop-packages] [Bug 1707110] Re: fwupd is consuming 100% of CPU in an upto date Ubuntu 16.04