date:20180316

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  This error occurred without an apparent cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 00:43:50 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-11-12 (124 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7fc208137a1d:mov0x8(%rdi),%eax
   PC (0x7fc208137a1d) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1743063] Re: package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo ante

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

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

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

Title:
  package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  trying to install nestopia

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
  Uname: Linux 4.13.0-19-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  AptOrdering:
   nestopia:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jan 12 22:20:26 2018
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-12-12 (31 days ago)
  InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: libreoffice
  Title: package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1682233] Re: 10de:1c8c [MSI] Module nouveau seems to MISS GeForce GTX 1050 Ti Mobile

2018-03-16 Thread Etienne URBAH

In fact, Linux kernel 4.14.0-041400rc7 caused Xorg to crash :
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1732574

With Linux kernel 4.16.0-041600rc5 from http://kernel.ubuntu.com
/~kernel-ppa/mainline and kernel option 'acpi_osi=! acpi_osi="Windows
2009"', XORG seems to work correctly :

$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x66 cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 4 
associated providers: 1 name:modesetting
Provider 1: id: 0x3f cap: 0x4, Source Offload crtcs: 0 outputs: 0 associated 
providers: 1 name:nouveau

Therefore, this issue seems to be solved.

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

Title:
  10de:1c8c [MSI] Module nouveau seems to MISS GeForce GTX 1050 Ti
  Mobile

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

Bug description:
  I have a laptop computer with hybrid graphics :  'Intel Onboard IGD'
  and 'Nvidia GeForce GTX 1050 Ti Mobile'.

  The 'Intel Onboard IGD' correctly manages the onboard monitor with
  resolution 1920 x 1080.

  But I need the Nvidia card to manage an external monitor with
  resolution 4K2K connected to DisplayPort.

  At the beginning, the 'nouveau' module of the Linux kernel seems to be 
correctly loaded :
  $ lsmod  |  grep  '^nouveau'
  nouveau  1601536  0

  But XORG does NOT load its 'nouveau' module.  So, I force it with following 
file :
  $ cat  /usr/share/X11/xorg.conf.d/20-module-nouveau.conf
  Section "Module"
  Load   "nouveau"
  EndSection

  In the attached 'Xorg-with-nouveau.0.log' file, you can see :

  -  Lines 58-59 :XORG correctly finds both Intel and Nvidia
  graphics hardware.

  -  Lines 61-66 :XORG loads its 'nouveau' module.

  -  Lines 94-108 :   The list of the Nvidia chipsets known by the
  'nouveau' module does NOT contain 'GTX 1050'.  Is this meaningful ?

  -  Line  123 :  Message ending with 'cannot open kernel arbiter, no 
multi-card support'.
  Is  this meaningful ?  If yes, is it possible to activate 
the 'kernel arbiter' ?

  -  Lines 124-226 :  The 'modesetting' module of XORG (perhaps with the
  help of the 'glamoregl' submodule) correctly reports the 4 available
  graphics outputs, in particular 'eDP-1' connected to the onboard
  monitor.

  -  Lines 233-234 :  XORG unloads its 'nouveau' module, which has NOT
  reported any graphics hardware or outputs

  
  If necessary, I am able to test :
  -  the latest version of the 'xserver-xorg-video-nouveau' package from a PPA
  -  the latest upstream kernel from 
http://kernel.ubuntu.com/~kernel-ppa/mainline

  
  Finally, I wonder where this issue has to be solved :

  -  inside configuration files in '/usr/share/X11/xorg.conf.d',

  -  inside the 'xserver-xorg-video-nouveau' package,

  -  inside the 'nouveau' module of the Linux kernel,

  -  inside the 'kernel arbiter'.

  Thank you in advance for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Apr 12 22:01:15 2017
  InstallationDate: Installed on 2017-03-28 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-16 Thread Doug McMahon

18.04 should really get the new driver, whether it's easier to do before or 
after release I don't know but it should be done.
For some reason Debian hasn't added it yet but that shouldn't stop Ubuntu from 
doing so.
In addition to bug symptoms there are other advantages to going to 2.1. For 
example there is a new interface for EGL interop, vaAcquireSurfaceHandle() in 
libva 2.1 but you need the 2.1 driver to implement.
So while the 2.1.x driver will certainly be available via ppa's before too long 
Ubuntu should plan on providing in 18.04 as best achieved.

** Changed in: libva (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Invalid

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  This error occurred while I was trying to solve the problem of the
  printer icon that disappeared. (Control-center/devices)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 17 00:17:46 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-11-12 (124 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x55a5bc9985f1:mov0x90(%rbp),%rsi
   PC (0x55a5bc9985f1) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1756484] Re: Screen flickers and small moving artifacts

2018-03-16 Thread Scott Palmer

I believe I have corrected this by changing my refresh rate from 59.99
Hz to 59.86 Hz.

Is this a requirement for 2560x1600 resolution on DL-DVI?  Should this
perhaps be communicated upstream to someone who knows better?

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

Title:
  Screen flickers and small moving artifacts

Status in xorg package in Ubuntu:
  New

Bug description:
  This is likely a wayland issue.  I can't bear the tearing if I don't
  use wayland.

  I get screen flickering (approximately every 5 seconds) and some
  windows seem to bring up some mis-colored moving artifacts that clear
  when the window is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 20:07:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1732574] Re: 10de:1c8c [MSI] nouveau fails to manage GP107M [GeForce GTX 1050 Ti Mobile]

2018-03-16 Thread Etienne URBAH

The cause of this issue seems to be in fact Linux kernel
4.14.0-041400rc7 :

With Linux kernel 4.16.0-041600rc5 from http://kernel.ubuntu.com
/~kernel-ppa/mainline and kernel option 'acpi_osi=! acpi_osi="Windows
2009"', Xorg works correctly.

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

Title:
  10de:1c8c [MSI] nouveau  fails to manage GP107M [GeForce GTX 1050 Ti
  Mobile]

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

Bug description:
  I am trying to use my Nvidia GP107M [GeForce GTX 1050 Ti Mobile] with
  Linux kernels from Ubuntu 17.10 (Artful) and http://kernel.ubuntu.com
  /~kernel-ppa/mainline

  At this day, when I issue 'lspci', the only 'nouveau' module of the
  kernel which succeeds comes from Linux kernel Linux kernel
  4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-ppa/mainline

  Even with this Linux kernel 4.14.0-041400rc7, Xorg systematically
  crashes as soon as I try to really use Nvidia GP107M [GeForce GTX 1050
  Ti Mobile] with the attached '20-onboard-monitor-nvidia-nouveau.conf'
  file :

  [  2114.194] (EE) Backtrace:
  [  2114.194] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x559e3139537d]
  [  2114.194] (EE) 1: /usr/lib/xorg/Xorg (0x559e311dd000+0x1bc119) 
[0x559e31399119]
  [  2114.194] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fefd8ed8000+0x13150) [0x7fefd8eeb150]
  [  2114.194] (EE) 3: /usr/lib/xorg/Xorg 
(xf86RandR12CreateScreenResources+0x501) [0x559e312b0651]
  [  2114.194] (EE) 4: /usr/lib/xorg/Xorg (0x559e311dd000+0xc61d0) 
[0x559e312a31d0]
  [  2114.194] (EE) 5: /usr/lib/xorg/Xorg (0x559e311dd000+0x56d14) 
[0x559e31233d14]
  [  2114.194] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) 
[0x7fefd8b191c1]
  [  2114.194] (EE) 7: /usr/lib/xorg/Xorg (_start+0x2a) [0x559e3121db2a]
  [  2114.194] (EE) 
  [  2114.194] (EE) Segmentation fault at address 0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  Uname: Linux 4.14.0-041400rc7-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 02:41:25 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11c8]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
  InstallationDate: Installed on 2017-10-31 (15 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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.
  MachineType: Micro-Star International Co., Ltd. GE62 7RE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-041400rc7-generic 
root=UUID=2ae0c332-8ab4-4946-adcc-7c9c4a7b8a1d ro quiet splash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J9IMS.309
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J9
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.309:bd11/28/2016:svnMicro-StarInternationalCo.,Ltd.:pnGE627RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: G
  dmi.product.name: GE62 7RE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

--

[Desktop-packages] [Bug 1710752] Re: Intel HDA Audio doesn't work

2018-03-16 Thread Scott Palmer

I just installed the 18.04 daily and formatted a fresh partition (no
prior home directory or any existing data used) and this is still an
issue in 4.15.0-12-generic.

Can I run a command to manually turn on this jack at startup or force it
to recheck that input to see if something is plugged in?

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

Title:
  Intel HDA Audio doesn't work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I get no sound on most boots.  In Sound settings the default Output device is 
HDMI / DisplayPort -
   Built-in Audio and there is no option to select anything else.  If I unplug 
my line out and plug it in again it shows up in the list, automatically sets 
itself as default and sound works fine. In Windows 10 this unplug and replug is 
not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

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

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

[Desktop-packages] [Bug 1756484] [NEW] Screen flickers and small moving artifacts

2018-03-16 Thread Scott Palmer

Public bug reported:

This is likely a wayland issue.  I can't bear the tearing if I don't use
wayland.

I get screen flickering (approximately every 5 seconds) and some windows
seem to bring up some mis-colored moving artifacts that clear when the
window is closed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 20:07:47 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] 
(prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
InstallationDate: Installed on 2018-03-17 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1807
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic reproducible ubuntu wayland-session

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

Title:
  Screen flickers and small moving artifacts

Status in xorg package in Ubuntu:
  New

Bug description:
  This is likely a wayland issue.  I can't bear the tearing if I don't
  use wayland.

  I get screen flickering (approximately every 5 seconds) and some
  windows seem to bring up some mis-colored moving artifacts that clear
  when the window is closed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 20:07:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Barts PRO [Radeon HD 6850] [1682:3112]
  InstallationDate: Installed on 2018-03-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=7cf929d1-3748-4cac-bd67-e25c2fdf0038 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Desktop-packages] [Bug 170049] Re: Inverted ruler co-ordinate system

2018-03-16 Thread Brenda Collins

I too LOVE all the new features and the stability of Inkscape 62.2
but... but I use Inkscape for label design and the wonky design and
inversion of the x-y coordinates makes trying to mentally invert all the
label alignments makes my head explode... just sayin!

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

Title:
  Inverted ruler co-ordinate system

Status in Inkscape:
  Confirmed
Status in inkscape package in Ubuntu:
  Triaged

Bug description:
  The y-axis of the rulers' co-ordinate system is
  inverted (increasing upwards), and places the origin on
  the bottom left of the viewport. The SVG spec places the
  default origin on the top left of the viewport, and has
  the co-ordinate system increasing to the right and
  downwards.

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

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

[Desktop-packages] [Bug 1756475] Re: gnome-software crashed with signal 5 in g_main_context_new()

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

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 #1756339, 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/1756475/+attachment/5081905/+files/CoreDump.gz

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

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

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

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

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

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

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

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  After fresh install of 18.04 beta, after software updater, ran
  synaptic to install all my software.

  During synaptic software installation, got this message.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 21:37:39 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-10 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_list_one_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

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

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 #1750138, 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/1756477/+attachment/5081916/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xwayland crashed with signal 7 in __libc_start_main()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Mar 17 06:42:43 2018
  DistUpgraded: 2018-03-11 13:34:23,267 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0623]
  InstallationDate: Installed on 2018-03-09 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Acer Aspire 5749Z
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=c959b491-11e9-4811-a983-3876c24c1ca3 ro quiet splash vt.handoff=1
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x564545ed2ac0, argc=12, argv=0x7ffe88ec0578, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffe88ec0568) at ../csu/libc-start.c:310
  Title: Xwayland crashed with signal 7 in __libc_start_main()
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 09/29/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: HMA51_HR
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrV1.06:bd09/29/2011:svnAcer:pnAspire5749Z:pvrV1.06:rvnAcer:rnHMA51_HR:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5749Z
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list:

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

This bug was fixed in the package deja-dup - 37.1-2fakesync1

---
deja-dup (37.1-2fakesync1) bionic-proposed; urgency=medium

  * Fake sync due to mismatching orig tarball.

deja-dup (37.1-2) experimental; urgency=medium

  * Add 0002-don-t-use-ulimit.patch:
- Stop using ulimit since it is incompatible with webkit2gtk 2.20
  (LP: #1751460)

 -- Jeremy Bicha   Fri, 16 Mar 2018 19:31:21 -0400

** Changed in: deja-dup (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Triaged
Status in deja-dup source package in Xenial:
  Triaged
Status in webkit2gtk source package in Xenial:
  New
Status in deja-dup source package in Artful:
  Triaged
Status in webkit2gtk source package in Artful:
  New
Status in deja-dup source package in Bionic:
  Fix Released
Status in webkit2gtk source package in Bionic:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::<lambda()>::operator()

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

** Also affects: webkit2gtk (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: webkit2gtk (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: deja-dup (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  [regression] deja-dup-monitor crashed with SIGSEGV in
  Gigacage::::operator()

Status in Déjà Dup:
  New
Status in WebKit:
  Confirmed
Status in deja-dup package in Ubuntu:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Triaged
Status in deja-dup source package in Xenial:
  Triaged
Status in webkit2gtk source package in Xenial:
  New
Status in deja-dup source package in Artful:
  Triaged
Status in webkit2gtk source package in Artful:
  New
Status in deja-dup source package in Bionic:
  Fix Released
Status in webkit2gtk source package in Bionic:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-1fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat Feb 24 14:30:47 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-12-27 (59 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff1c3dda588:movl   $0x0,(%rax)
   PC (0x7ff1c3dda588) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7ff1c404202c, 
init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1755675] Re: Ubuntu 17.10 OpenVPN DNS Leaks

2018-03-16 Thread LPNow

Sorry I left out a package name.

I am a Linux Geek and I've spent a huge amount of time on this, to the
extent that no one should ever have to spend, and I'm not coming up with
a simple solution to this.

I'd greatly appreciate it if someone can tell me a simple way to this,
without having to install several things like openresolv, unbound,
etc...

Thanks

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

Title:
  Ubuntu 17.10 OpenVPN DNS Leaks

Status in network-manager package in Ubuntu:
  New

Bug description:
  On Ubuntu 17.10 x64 I have noticed that when using the NetworkManager
  and OpenVPN, that DNS leaks from the Router or ISP, instead of only
  being tunneled from the VPN...

  I have spent hours playing with this, it's beyond absurd, the amount
  of time and effort needed to try and resolve something that should be
  working out the box!

  This is not LFS, or Slackware, in fact Slackware is simpler and easier
  to make this work in less then 5 mins!

  Seriously this has been an ongoing issue for ages/years in Ubuntu, and
  the end-users typically for Ubuntu are inexperienced users, again, the
  only thing end-users should have to do is install the correct OpenVPN
  packages, configure OpenVPN in the NetworkManager and it works, but it
  doesn't!

  While Canonical works on trying to resolve this, can someone PLEASE
  tell me a simple way in which to prevent DNS leaks while using OpenVPN
  through the NetworkManager?

  THANKS

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

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

[Desktop-packages] [Bug 1740804] Re: Remove old vte package from Ubuntu

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

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

Title:
  Remove old vte package from Ubuntu

Status in genius package in Ubuntu:
  New
Status in rasmol package in Ubuntu:
  New
Status in vte package in Ubuntu:
  Incomplete

Bug description:
  NOTE
  
  Debian's debian-installer (specifically cdebconf-gtk-terminal I believe) uses 
a udeb from the old vte package. See https://bugs.debian.org/887649

  Original Bug Report
  ===
  The old vte source hasn't been maintained upstream since 2011 (when GNOME 3 
was released). vte will be dropped from Debian Testing soon. We should not ship 
it in Ubuntu 18.04 LTS. The replacement is provided by source vte2.91 (which 
requires gtk3).

  sjterm was already requested for removal in LP: #1728241

  $ reverse-depends src:vte
  Reverse-Depends
  ===
  * gnome-genius  (for libvte9)
  * pypar2(for python-vte)
  * rasmol [amd64 arm64 armhf i386 s390x]  (for libvte9)
  * stjerm(for libvte9)

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

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

[Desktop-packages] [Bug 1751797] Re: NetworkManager incorrectly uses resolved' route-only DNS setting, resulting in dns resolution only working for domains in 'search'.

This bug was fixed in the package network-manager - 1.10.4-1ubuntu3

---
network-manager (1.10.4-1ubuntu3) bionic; urgency=medium

  * Cherry-pick a partial patch from 1.11 branch, to stop agressively
setting route_only flag on nameservers in the systemd-resolved dns
plugin. LP: #1751797

 -- Dimitri John Ledkov   Thu, 15 Mar 2018 15:24:01
+

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  NetworkManager incorrectly uses resolved' route-only DNS setting,
  resulting in dns resolution only working for domains in 'search'.

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  After reboot, dns was broken.
  This is a very simple Network Manager managed interface that has dhcp.

  $ nmcli device show enp0s25  | pastebinit
  http://paste.ubuntu.com/p/sMVTdrMBxJ/

  
  I've attached systemd-resolve --status output.

  In order to file the bug I just modified /etc/resolv.conf to put the
  dns server in directly.

  Other information, it seems like it just will only look for dns under
  my search domains from the dhcp server:

  $ systemd-resolve home.mosers.us
  home.mosers.us: 23.28.108.176

  -- Information acquired via protocol DNS in 1.5ms.
  -- Data is authenticated: no

  $ systemd-resolve google.com
  google.com: resolve call failed: No appropriate name servers or networks for 
name found

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:35:32 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

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

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

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  Memory: 14.7 GiB
  Processor: AMD Ryzen 3 2200g with radeon vega graphics x 4
  Graphics: AMD Raven
  GNOME: 3.28.0
  OS type: 64-bit
  Disk: 983.4 GB

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Mar 16 18:48:38 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-16 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x564f8c9145f1:mov0x90(%rbp),%rsi
   PC (0x564f8c9145f1) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1756461] Re: Breeze theme makes menus in menubar unselectable in several applications

2018-03-16 Thread Daniel Visser

Hello again,

What kind of specs or information do you might need additionally?
I use a Tuxedo BX1505 with an Intel grafics card.
Some ppa's are included (see attachment) which should not affect the usabilitiy 
according to the tuxedo support team. They couldn't help me with this problem.

Best wishes and Thank you so far
Daniel Leander

** Attachment added: "package sources"
   
https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1756461/+attachment/5081856/+files/noMenuPPAs.png

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

Title:
  Breeze theme makes menus in menubar unselectable in several
  applications

Status in amarok package in Ubuntu:
  New

Bug description:
  In Kubuntu 16.04 I cannot access the menus in the menu bar in several 
applications if the Breeze theme is selected. If I click on any menu, the menu 
is highlighted but no submenus/menu items appear.
   
  Affected applications:
  dolphin4, kile, Amarok, okular, speedcrunch, digikam, soundkonverter,

  Other applications menus of the menubar work well:
  dolphin, kate, synaptic, libreoffice writer, konsole, gimp, audacity, 
tuxhuitar

  
  If the oxygen theme is selected the problem does not exist anymore.

  Do you need any logs?
  I am glad if I can help out.

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

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

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

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

** Changed in: intel-vaapi-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

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

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

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  Confirmed
Status in libva package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice

[Desktop-packages] [Bug 1756461] [NEW] Breeze theme makes menus in menubar unselectable in several applications

2018-03-16 Thread Daniel Visser

Public bug reported:

In Kubuntu 16.04 I cannot access the menus in the menu bar in several 
applications if the Breeze theme is selected. If I click on any menu, the menu 
is highlighted but no submenus/menu items appear.
 
Affected applications:
dolphin4, kile, Amarok, okular, speedcrunch, digikam, soundkonverter,

Other applications menus of the menubar work well:
dolphin, kate, synaptic, libreoffice writer, konsole, gimp, audacity, tuxhuitar


If the oxygen theme is selected the problem does not exist anymore.

Do you need any logs?
I am glad if I can help out.

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

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

Title:
  Breeze theme makes menus in menubar unselectable in several
  applications

Status in amarok package in Ubuntu:
  New

Bug description:
  In Kubuntu 16.04 I cannot access the menus in the menu bar in several 
applications if the Breeze theme is selected. If I click on any menu, the menu 
is highlighted but no submenus/menu items appear.
   
  Affected applications:
  dolphin4, kile, Amarok, okular, speedcrunch, digikam, soundkonverter,

  Other applications menus of the menubar work well:
  dolphin, kate, synaptic, libreoffice writer, konsole, gimp, audacity, 
tuxhuitar

  
  If the oxygen theme is selected the problem does not exist anymore.

  Do you need any logs?
  I am glad if I can help out.

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

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

[Desktop-packages] [Bug 1743183] Re: Mouse left button not being noticed when clicked under Wayland - works under x11

2018-03-16 Thread Mark Rogers

Update:

I was running the: paulo-miguel-dias/mesa   build
and the: oibaf/graphics-driversbuild

I uninstalled both and reverted to the standard ubuntu drivers/setup. This 
fixed the mouse issue.
As both of the above adons have some popularity one of them may have been the 
cause of the issue - though cant confirm which one. Perhaps it was because I 
was running both that caused a configuration issue after an update - all just 
conjecture, however I now have a working Wayland session now.

Hope this sheds some light on what might have happened.

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

Title:
  Mouse left button not being noticed when clicked under Wayland - works
  under x11

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Connected other mice, unplugging/rebooting/replugging  in mouse has no
  affect.

  However booting into X11 from the login screen fixes the mouse issue!
  If I try to login with Wayland then the problem reemerges.

  Ive even enabled "Pre-Release Updates and downloaded all the updated
  files in the hope of fixing the issue - it didnt.

  So HELP!

  Even though I have a working system I would prefer to be working under
  Wayland.

  Cheers in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-release-upgrader-core 1:17.10.8
  Uname: Linux 4.13.0-041300-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 14 15:57:30 2018
  InstallationDate: Installed on 2017-09-06 (129 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170905)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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

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

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-16 Thread Prasad Murthy

I can confirm this bug exists.

OS version: Ubuntu 18.04 beta rc
Hardware: Intel core i5 7400 (Kaby lake processor)
with Intel HD graphics 630 supporting VP9 10-bit and 8-bit video decoding.


In version 1.8.x of the driver the VP9 decoding is broken, the corresponding 
upstream patch got into 2.0.0. But since VP9 profiles are missing in 2.0.0 
driver in Ubuntu, hardware acceleration is absent, so high cpu and power usage. 
The buggy driver 1.8.x is used in the vlc snap too and snap developers doubt 
the driver version in snap will be upgraded. 

* VP9 decoding broken in 17.10
* VP9 decoding broken in snap packages
* VP9 decoding broken in 18.04 beta rc

Either driver version has to be updated to 2.1.0 or at-least cherry pick
a one line patch to current Ubuntu core snap, a link for which I will
mention below.

Upstream driver patch: https://github.com/intel/intel-vaapi-
driver/commit/9d66570032fb02b1e79a883af7697b035d700a8e

Upstream bug report: https://github.com/intel/intel-vaapi-
driver/issues/297

In any way kindly support VP9 hardware decoding via supported Intel
hardwares in 18.04 or in 17.10(by backporting/cherry picking) or atleast
via updated snap core/apps.


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

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in libva package in Ubuntu:
  New

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:

[Desktop-packages] [Bug 1756451] [NEW] gnome-terminal and gedit do not open remote windoes

2018-03-16 Thread Bill Morita

Public bug reported:

ssh'ing in from a remote host:

Ubuntu 17.10 gnome-terminal and gedit do not open remote windows.

On 17.10.1 windows are opened on localhost if logged in, not on remote
host as expected.

These actions successfully opened windows on remote hosts for 16.10

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

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

Title:
  gnome-terminal and gedit do not open remote windoes

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  ssh'ing in from a remote host:

  Ubuntu 17.10 gnome-terminal and gedit do not open remote windows.

  On 17.10.1 windows are opened on localhost if logged in, not on remote
  host as expected.

  These actions successfully opened windows on remote hosts for 16.10

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

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

[Desktop-packages] [Bug 1756448] [NEW] Aw Snap problem after some hours, V56 Raspberry PI 3

2018-03-16 Thread Ricardo Ferreira

Public bug reported:

Hi,

I have a solution of Digital Signage using raspberry for each screen, we 
currently display our content using the chromium-browser and our code is 
developed in Angular 2.
After about 8 hours of operation the display shows the Aw Snap error.

As a solution we restarted raspiberry, although the browser content
again works, it has the same error "Aw Snap !!" again. However, more
frequently it occurs every 2 hours of operation.

Our devices use Raspibian, based on Debian 8 version 4.4.38-v7 + # 938

Att Ricardo Ferreira

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Aw Snap problem after some hours, V56 Raspberry PI 3

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi,

  I have a solution of Digital Signage using raspberry for each screen, we 
currently display our content using the chromium-browser and our code is 
developed in Angular 2.
  After about 8 hours of operation the display shows the Aw Snap error.

  As a solution we restarted raspiberry, although the browser content
  again works, it has the same error "Aw Snap !!" again. However, more
  frequently it occurs every 2 hours of operation.

  Our devices use Raspibian, based on Debian 8 version 4.4.38-v7 + # 938

  Att Ricardo Ferreira

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

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

[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service

Just for clarity, was your test done on a computer with a traditional
hard drive or solid state drive?

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

Title:
  Delay start of gnome-software service

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
  With gnome-software delayed gnome-shell starts 2 seconds faster.

  
  gnome-software service startup should be delayed if it cannot be stop 
completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

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

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

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 #1723249, 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/1756445/+attachment/5081804/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  Ubuntu experienced an internal error

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:07:40 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x55e3a3ab9925:cmpb   $0x0,(%rbx)
   PC (0x55e3a3ab9925) ok
   source "$0x0" ok
   destination "(%rbx)" (0x4002) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  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: gnome-control-center 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/gnome-control-center/+bug/1756445/+subscriptions

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

[Desktop-packages] [Bug 1756442] Re: gnome-shell crashed with SIGSEGV in cogl_object_unref() Tried to install application from Software center

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_object_unref() Tried to
  install application from Software center

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Tried to install few application in Software Center. Tried to install
  few apps by pressing install buttons.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 16 20:26:32 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-13 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f8b28417510 :mov
(%rdi),%rax
   PC (0x7f8b28417510) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   cogl_object_unref () from 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-cogl-2.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in cogl_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service

Yes, this is the desktop file I used:
"""
[Desktop Entry]
Type=Application
Name=GNOME Software
X-GNOME-Autostart-Delay=60
Exec=/usr/bin/gnome-software --gapplication-service
OnlyShowIn=GNOME;Unity;
NoDisplay=true
"""

I tried with 60s but it can probably be more. The drawback is that
gnome-software is used as a search provider and package search won't be
available until it's running.

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

Title:
  Delay start of gnome-software service

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
  With gnome-software delayed gnome-shell starts 2 seconds faster.

  
  gnome-software service startup should be delayed if it cannot be stop 
completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1756439] [NEW] gnome-shell causes high CPU load with dual monitors

2018-03-16 Thread Klaus

Public bug reported:

I have ubuntu 10.10 with Xorg Gnome desktop, intel i915 driver and two monitors 
attached.
gnome-shell causes a very high CPU load which seems to make the system unusable 
sluggish.
When moving a window the CPU usage of gnome-shell raises to over 90 %.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 21:30:31 2018
DisplayManager: gdm3
GsettingsChanges:
 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', 
'gnome-control-center.desktop', 'thunderbird.desktop', 'jameica_2_6_6.desktop', 
'org.gnome.Calculator.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-08-18 (210 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-11-05 (131 days ago)

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

Title:
  gnome-shell causes high CPU load with dual monitors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have ubuntu 10.10 with Xorg Gnome desktop, intel i915 driver and two 
monitors attached.
  gnome-shell causes a very high CPU load which seems to make the system 
unusable sluggish.
  When moving a window the CPU usage of gnome-shell raises to over 90 %.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 21:30:31 2018
  DisplayManager: gdm3
  GsettingsChanges:
   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', 
'gnome-control-center.desktop', 'thunderbird.desktop', 'jameica_2_6_6.desktop', 
'org.gnome.Calculator.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-08-18 (210 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-05 (131 days ago)

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

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

[Desktop-packages] [Bug 1713098] Re: Frequent DEP8 test failures related to ftp

2018-03-16 Thread Andreas Hasenack

I don't know if the timeout is borderline short, but the unmount definitely 
failed. Logs further down (sorry, these logs are interleaved and have no 
timestamp) show that unmount failed because the filesystem was busy:
ftp: Queued new job 0x1002d932210 (GVfsJobCloseRead)
ftp: <- 0 --  226 Transfer Complete.
ftp: send_reply(0x1002d932210), failed=0 ()
ftp: backend_dbus_handler org.gtk.vfs.Mount:Unmount (pid=7819)
ftp: g_vfs_job_unmount_new request: 0x789a5002adf0
ftp: Queued new job 0x1002d93f740 (GVfsJobUnmount)
ftp: send_reply(0x1002d93f740), failed=1 (File system is busy)
ftp: send_reply(0x1002d93f740), failed=1 (File system is busy)


That "transfer complete" was about self.do_mount_check_api(gfile, True) which, 
among other things, downloads "myfile.txt" and asserts its contents. That's the 
last thing that method does, and the "finally:\nself.unmount_api(gfile)" call 
comes right after that.

I don't know why there are two "file system is busy" messages in the
logs. And I also don't know if it would have worked had we waited a bit
more, or if the myfile.txt retrieval somehow left that file open and
that's why unmount failed.

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

Title:
  Frequent DEP8 test failures related to ftp

Status in gvfs package in Ubuntu:
  New

Bug description:
  There are somewhat constant, but intermittent, DEP8 test failures in the gvfs 
package. They seem to always be around ftp:
  tp:// anonymous (API with flag) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_api_user (__main__.Ftp)
  ftp:// anonymous (API with user) ... ok
  test_anonymous_cli_option (__main__.Ftp)
  ftp:// anonymous (CLI with option) ... Error mounting location: Location is 
already mounted
  ERROR

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_cli_user (__main__.Ftp)
  ftp:// anonymous (CLI with user) ... ok
  test_authenticated_api (__main__.Ftp)
  ftp:// authenticated (API) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_authenticated_cli (__main__.Ftp)
  ftp:// authenticated (CLI) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  Here is a link: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/g/gvfs/20170825_135452_c32a9@/log.gz

  This bug is to investigate these ftp tests, determine why they are
  flaky, and fix them if possible.

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

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

[Desktop-packages] [Bug 1756440] [NEW] Android Studio snap does not appear in search results

2018-03-16 Thread Omer Akram

Public bug reported:

We have the snap 'android-studio' published in the stable channel, its a
classic snap but it does not appear in search results in gnome-software.

Steps to reproduce
1. Open gnome-software
2. Search for Android, Android Studio or android-studio

What happens:
Android studio is not found.

Now in terminal type below command and android-studio will be installed 
correctly.
$ snap install android-studio --classic

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

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

Title:
  Android Studio snap does not appear in search results

Status in gnome-software package in Ubuntu:
  New

Bug description:
  We have the snap 'android-studio' published in the stable channel, its
  a classic snap but it does not appear in search results in gnome-
  software.

  Steps to reproduce
  1. Open gnome-software
  2. Search for Android, Android Studio or android-studio

  What happens:
  Android studio is not found.

  Now in terminal type below command and android-studio will be installed 
correctly.
  $ snap install android-studio --classic

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

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

[Desktop-packages] [Bug 1750197] Re: Activities overview causes heavy CPU spikes in Wayland & Xorg

2018-03-16 Thread Luke B.

What I did was profile gnome-shell using sysprof, and I found that file
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.5502.0 uses 25.06% of CPU
time by itself. My guess is that it's called/utilized very frequently.
Attached is part of the output that should explain what I'm stating.

Let me know if any more information is necessary.

** Attachment added: "My sysprof findings"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1750197/+attachment/5081778/+files/ProfileOutput_LukeB.txt

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

Title:
  Activities overview causes heavy CPU spikes in Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   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/1750197/+subscriptions

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

[Desktop-packages] [Bug 1756372] Re: Merge 2.24.32-1 from Debian

2018-03-16 Thread Simon Quigley

I can take this merge.

** Changed in: gtk+2.0 (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => In Progress

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

Title:
  Merge 2.24.32-1 from Debian

Status in gtk+2.0 package in Ubuntu:
  In Progress

Bug description:
  Please merge gtk+2.0 (2.24.32-1) from Debian. It's a bug-fix release.

  Overview of Changes from GTK+ 2.24.31 to 2.24.32
  

  * Build:
   - Support Visual Studio 2017

  * Bug fixes:
   136059 Ctrl-navigation works in opposite direction in right-to-left text
   165385 Win32 keyboard handling still incomplete
   358970 gtk_scale_set_digits does not cause value to be rounded if 
draw-value...
   468868 Popup of "appears-as-list" ComboBox does not change screen with its 
t...
   554057 Calling gtk_menu_shell_select_item() on GtkMenuBar can break grabs 
(a...
   569581 Using the US-Intl keyboard layout causes unexpected character 
combina...
   618160 Documentation for gtk_combo_box_get_active_iter is unclear
   658111 gtk_label_set_pattern() is reset by a call to gtk_box_pack_start()
   676550 Adding underlines to Label with gtk_label_set_pattern() does not work
   696624 Japanese (Korean/Chinese) XIM input mode indicator has not been 
worki...
   701296 gtkfixed accepts toplevel windows into its children list after 
gtk_wi...
   729651 Crash in GtkFileChooserButton with appears-as-list
   734946 Implement GContentType on OSX
   768722 Keyboard shortcuts for russian characters doesn't work
   769214 keyval field not filled correctly for Pause key
   772389 Appending a character to a GtkEntry control in overwrite mode rings 
t...
   772794 segfault when on unchecked XListInputDevices return value
   773587 recent-manager: Add a limit to the list's size
   776909 gtk_adjustment_clamp_page: Conditional jump or move depends on 
uninit...
   777683 SIGBUS due to gdk_x11_window_set_opacity
   778542 Use UTF-8 encoding for tooltips on files in the "recently used" list
   778811 Enter submenus when activating their parent item
   779009 Missing property-change::accessible-description events when the 
toolt...
   779081 GtkTextView: expose API to get Pango line direction
   779605 GLib-CRITICAL Source ID xxx was not found when attempting to remove it
   781020 GIMP UI vector icons are drawn way too small
   781605 GtkVolumeButton limited to 10 values
   785165 Set translation domain for parameter_string in gtk_init_with_args
   785672 Entry: Setting icon tooltip to empty disables tooltip on whole widget
   786771 Critical about mismatched GdkDisplays when opening Inspector combobox
   787158 gtk_widget_get_preferred_width on GtkToolbar gives wrong minimum width
   787195 gtk_toolbar_set_show_arrow does not show an arrow
   787410 entry: fix memory leak
   788577 Global -GtkComboBox-appears-as-list breaks opening menu-mode CBs by 
k...

  * Translation updates:
   Hungarian
   Indonesian
   Polish
  

  gtk+2.0 (2.24.32-1) unstable; urgency=medium

* New upstream release
* debian/libgtk2.0-0.symbols: Add symbols
* Update Vcs fields for migration to https://salsa.debian.org/
* Drop patches applied in new release:
  - 0001-Don-t-use-guint32-with-XChangeProperty.patch
  - 0002-GtkMenuShell-always-activate-menu-shells.patch

   -- Jeremy Bicha   Sat, 20 Jan 2018 07:46:38 -0500

  gtk+2.0 (2.24.31-5) unstable; urgency=medium

* Update Vcs fields for conversion to git
* Add debian/gbp.conf
* Bump Standards-Version to 4.1.2

   -- Jeremy Bicha   Thu, 21 Dec 2017 14:05:20 -0500

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

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

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

2018-03-16 Thread Amr Ibrahim

Public bug reported:

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

poppler (0.62.0-2) unstable; urgency=medium

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

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

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

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

Title:
  Merge 0.62.0-2 from Debian

Status in poppler package in Ubuntu:
  New

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

  poppler (0.62.0-2) unstable; urgency=medium

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

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

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

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

[Desktop-packages] [Bug 1713098] Re: Frequent DEP8 test failures related to ftp

2018-03-16 Thread Andreas Hasenack

Oh, look at that unmount_api() docstring:

def unmount_api(self, gfile):
'''Umount a mounted Gio.File using the Gio API

This times out after 5 seconds.
'''

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

Title:
  Frequent DEP8 test failures related to ftp

Status in gvfs package in Ubuntu:
  New

Bug description:
  There are somewhat constant, but intermittent, DEP8 test failures in the gvfs 
package. They seem to always be around ftp:
  tp:// anonymous (API with flag) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_api_user (__main__.Ftp)
  ftp:// anonymous (API with user) ... ok
  test_anonymous_cli_option (__main__.Ftp)
  ftp:// anonymous (CLI with option) ... Error mounting location: Location is 
already mounted
  ERROR

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_cli_user (__main__.Ftp)
  ftp:// anonymous (CLI with user) ... ok
  test_authenticated_api (__main__.Ftp)
  ftp:// authenticated (API) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_authenticated_cli (__main__.Ftp)
  ftp:// authenticated (CLI) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  Here is a link: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/g/gvfs/20170825_135452_c32a9@/log.gz

  This bug is to investigate these ftp tests, determine why they are
  flaky, and fix them if possible.

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

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

[Desktop-packages] [Bug 1713098] Re: Frequent DEP8 test failures related to ftp

2018-03-16 Thread Andreas Hasenack

This is the first test that fails:
==
FAIL: test_anonymous_api_user (__main__.Ftp)
ftp:// anonymous (API with user)
--
Traceback (most recent call last):
  File "/home/gvfs-testbed-script", line 676, in test_anonymous_api_user
self.unmount_api(gfile)
  File "/home/gvfs-testbed-script", line 287, in unmount_api
self.assertNotEqual(self.cb_result, None, 'operation timed out')
AssertionError: None == None : operation timed out

The code does:
def test_anonymous_api_user(self):
'''ftp:// anonymous (API with user)'''

uri = 'ftp://anonymous@localhost:2121'
gfile = Gio.File.new_for_uri(uri)
self.assertEqual(self.mount_api(gfile), True)
try:
self.do_mount_check_api(gfile, True)
finally:
self.unmount_api(gfile)

It's failing in the "finally" clause, with a timeout. It's never
unmounted.

Then the next test comes along, and fails because the thing is still
mounted:

test_anonymous_cli_user (__main__.Ftp)
ftp:// anonymous (CLI with user) ... gio: ftp://anonymous@localhost:2121/: 
Location is already mounted
(...)
ERROR: test_anonymous_cli_user (__main__.Ftp)
ftp:// anonymous (CLI with user)
--
Traceback (most recent call last):
  File "/home/gvfs-testbed-script", line 601, in test_anonymous_cli_user
subprocess.check_call(['gio', 'mount', uri])
  File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['gio', 'mount', 
'ftp://anonymous@localhost:2121']' returned non-zero exit status 2.

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

Title:
  Frequent DEP8 test failures related to ftp

Status in gvfs package in Ubuntu:
  New

Bug description:
  There are somewhat constant, but intermittent, DEP8 test failures in the gvfs 
package. They seem to always be around ftp:
  tp:// anonymous (API with flag) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_api_user (__main__.Ftp)
  ftp:// anonymous (API with user) ... ok
  test_anonymous_cli_option (__main__.Ftp)
  ftp:// anonymous (CLI with option) ... Error mounting location: Location is 
already mounted
  ERROR

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_cli_user (__main__.Ftp)
  ftp:// anonymous (CLI with user) ... ok
  test_authenticated_api (__main__.Ftp)
  ftp:// authenticated (API) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_authenticated_cli (__main__.Ftp)
  ftp:// authenticated (CLI) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  Here is a link: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/g/gvfs/20170825_135452_c32a9@/log.gz

  This bug is to investigate these ftp tests, determine why they are
  flaky, and fix them if possible.

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

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

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

2018-03-16 Thread Cliff Carson

Seen this problem twice when going to Settings-Devices-Printer.  The
Settings window and the apport error is displayed.  The second time
Settings-Devices-Printer is selected the Printer selection window
appears.

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

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

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

Bug description:
  Crash occurred while editing the custom keyboard shortcuts.

  4.15.0-12-generic #13-Ubuntu SMP Thu Mar 8 06:24:47 UTC 2018

  Description:Ubuntu Bionic Beaver (development branch) 

 
  Release:18.04

  gnome-control-center: 

 
Installed: 1:3.27.92-1ubuntu1
Candidate: 1:3.27.92-1ubuntu1
Version table:
   *** 1:3.27.92-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 10 22:33:39 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-03 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x562f4ba335f1:mov0x90(%rbp),%rsi
   PC (0x562f4ba335f1) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1756336] Re: cupsd crashed with SIGSEGV in finalize_job()

Can you please activate the CUPS debug mode following the instructions
of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems and leave it
activated. As soon as the problem occurs again, please attach your
error_log to this bug report.

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

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

Title:
  cupsd crashed with SIGSEGV in finalize_job()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I tried to print to an HP P1102w printer. I don't have more detailed
  information.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 16 12:31:49 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2018-03-02 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  Lpstat: device for HP-LaserJet-Professional-P-1102w: 
hp:/usb/HP_LaserJet_Professional_P_1102w?serial=0W473S3TPR1a
  MachineType: LENOVO 20HR006CMX
  Papersize: a4
  PpdFiles: HP-LaserJet-Professional-P-1102w: HP LaserJet Professional P 1102w, 
hpcups 3.17.10, requires proprietary plugin
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x5563faec0ee9:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x5563faec0ee9) ok
   source "%es:(%rdi)" (0x5563faee0898) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5563fae9f2b0, argc=2, argv=0x7ffd075f3808, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd075f37f8) at ../csu/libc-start.c:310
  Title: cupsd crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR006CMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HR006CMX:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR006CMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR006CMX
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1754356] Re: xdg-user-dirs-update does not take care of $HOME

** Also affects: xdg-user-dirs (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: xdg-user-dirs (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  xdg-user-dirs-update does not take care of $HOME

Status in xdg-user-dirs package in Ubuntu:
  In Progress
Status in xdg-user-dirs source package in Xenial:
  Triaged

Bug description:
  [ Impact ]

  When setting an user dir to a folder that is subfolder of $HOME (and
  when $HOME does not match the /etc/passwd defined home for the user),
  the ~/.config/user-dirs.dirs is wrongly generated.

  [ Test case ]

   1) env HOME=/tmp/temp-home xdg-user-dirs-update
   2) find /tmp/temp-home/
   3) should list generated XDG user directories
   4) /tmp/temp-home/.config/user-dirs.dirs should mention them

  Launching something like:
   - env HOME=/tmp/temp-home ./xdg-user-dirs-update --set DOWNLOADS 
"/tmp/temp-home/sub/folder/of/it/Downloads"

  Should modify /tmp/temp-home/.config/user-dirs.dirs so that it contains:
XDG_DOWNLOADS_DIR="$HOME/sub/folder/of/it/Downloads"

  [ Regression potential ]

  Xdg folders could be generated in wrong locations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1754356/+subscriptions

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

[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

2018-03-16 Thread Jim Campbell

Include associated patch to fix this for Trusty.  Please update package
after associated packages for Artful and Xenial.

** Patch added: "One-line fix and associated changelog - Trusty"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachment/5081722/+files/ubuntu_geoip_url_https_trusty.patch

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Triaged
Status in ubuntu-geoip source package in Artful:
  Triaged

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  
  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

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

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

[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

2018-03-16 Thread Jim Campbell

Include patch to set https geoip url for Xenial. Package should be
updated after the related Artful package, but before the associated
Trusty package.

** Patch added: "One-line fix and associated changelog - Xenial"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachment/5081721/+files/ubuntu_geoip_url_https_xenial.patch

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Triaged
Status in ubuntu-geoip source package in Artful:
  Triaged

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  
  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

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

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

[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

2018-03-16 Thread Jim Campbell

Include associated patch for Artful. This package should be updated
before packages for Trusty and Xenial, although I'm attaching all three
patches at more or less the same time.

** Patch added: "One-line fix and associated changelog"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-geoip/+bug/1617535/+attachment/5081720/+files/ubuntu_geoip_url_https_artful.patch

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Fix Released
Status in ubuntu-geoip source package in Trusty:
  Triaged
Status in ubuntu-geoip source package in Xenial:
  Triaged
Status in ubuntu-geoip source package in Artful:
  Triaged

Bug description:
  Impact
  --
  It's better to use https where we can. There were concerns about location 
leakage for users using a proxy (such as Tor).

  Test Case
  -

  Regression Potential
  
  As long as Canonical maintains https://geoip.ubuntu.com, things should be 
fine here. Minimal fix.

  
  Original Bug Report
  ---
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over HTTP. This 
can potentially be utilized by nation state adversaries to compromise user 
privacy. This service is called multiple times per day by the OS in order to 
track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

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

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

[Desktop-packages] [Bug 1263355] Re: Unable to directly access files of any smartphone from Ubuntu

2018-03-16 Thread Uwe Jugel

I can confirm the problem on Xubuntu 17.10. I think the problem is caused by
braces "()" in file names. [1]
The MTP backend does not seem to like them.

It can be reproduced as follows:

1. Check that mtp works in general
2. create a regular file with only "a-z0-9" chars in a dir on your MTP device
3. mount and access it from Linux. This should work in most cases.

4. Now try the error case
5. create file with braces "()" in a dir on your MTP device.
6. mount and access it from Linux using `thunar`, `nautilus`, or even using
`ls` or `cd` on the command line. This should produce the file manager (or
console) to hang and no longer respond to user input, etc.

I also suspect this bug to be the cause for other bugs, e.g. in `gvfs`
[2]

[1] related error report at askubuntu
https://askubuntu.com/questions/995383/nautilus-hangs-on-accessing-dcim-camera-on-android/1013351
[2] maybe related gvfs bug
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556

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

Title:
Unable to directly access files of any smartphone from Ubuntu

Status in libmtp package in Ubuntu:
Confirmed

Bug description:
Unable to access files of Samsung Trend from Nautilus, when you
connect device a problem happens: "Unable to mound Android, Unable to
open MTP device '[usb:003,003]' "

If i try to access files such music or pictures in Android device, i
get some errors.

I can copy files from Android device, and paste to a home folder, like
Pictures or Documents, and it's possible to see images or listen
musics in this way, for example.

The expected behavior is to see an ask window, and I could choose what
I do with the device (open with Nautilus, Rhythmbox, Image viewer,
Gthumb...).

lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 04f2:b3aa Chicony Electronics Co., Ltd
Bus 001 Device 023: ID 0489:e062 Foxconn / Hon Hai
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly
Feiya Technology Corp.) Flash Drive
Bus 003 Device 004: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone
[Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libmtp-runtime 1.1.6-20-g1b9f164-1ubuntu2
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.336ubuntu1
Date: Sat Dec 21 17:09:49 2013
LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
ProcEnviron:
LANGUAGE=en_US
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: libmtp
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1754843] Re: gdk-pixbuf version in artful > version in bionic

2018-03-16 Thread Colin Watson

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
   gdk-pixbuf version in artful > version in bionic

Status in gdk-pixbuf package in Ubuntu:
  Fix Released

Bug description:
  gdk-pixbuf in artful is 2.36.11-1ubuntu0.1 which is greater than
  2.36.11-1 in bionic

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

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

[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service

2018-03-16 Thread Sebastien Bacher

Thanks, that makes sense I think, you tested adding an X-GNOME-
Autostart-Delay key to the autostart desktop right and that worked?

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

Title:
  Delay start of gnome-software service

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
  With gnome-software delayed gnome-shell starts 2 seconds faster.

  
  gnome-software service startup should be delayed if it cannot be stop 
completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1706488] Re: Snaps without icons not showing

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

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

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

Title:
  Snaps without icons not showing

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Confirmed
Status in gnome-software source package in Zesty:
  Confirmed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Snaps without an icon (i.e. not provided in snap or in the store) are not 
shown in GNOME Software. This is because GNOME Software fails to get the
  "package-x-generic" default icon.

  [Test Case]
  1. Install a snap without an icon, e.g:
  $ sudo snap install openscad-plars
  2. Start GNOME Software
  3. Click on installed tab

  Expected result:
  The installed snap is show in the list of apps.

  Observed result:
  The snap is not shown.

  [Regression Potential]

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

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

[Desktop-packages] [Bug 1706488] Re: Snaps without icons not showing

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

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

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

Title:
  Snaps without icons not showing

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Confirmed
Status in gnome-software source package in Zesty:
  Confirmed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Snaps without an icon (i.e. not provided in snap or in the store) are not 
shown in GNOME Software. This is because GNOME Software fails to get the
  "package-x-generic" default icon.

  [Test Case]
  1. Install a snap without an icon, e.g:
  $ sudo snap install openscad-plars
  2. Start GNOME Software
  3. Click on installed tab

  Expected result:
  The installed snap is show in the list of apps.

  Observed result:
  The snap is not shown.

  [Regression Potential]

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

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

[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic

2018-03-16 Thread Sebastian Stark

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

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

Title:
  vaapi VP9 hardware decoding not working anymore in bionic

Status in intel-vaapi-driver package in Ubuntu:
  New
Status in libva package in Ubuntu:
  New

Bug description:
  Hardware: Dell XPS13 9365, i7-7Y75
  System: Ubuntu Bionic Beaver (development branch)

  
  vainfo output on bionic is:

  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.1 (libva 2.1.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSliceLP
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointEncSliceLP
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointEncPicture
VAProfileVP8Version0_3  :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain   :   VAEntrypointEncSlice
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointEncSlice

  As you can see, VP9 entrypoints are missing.

  vainfo output on 17.10 was:

  libva info: VA-API version 0.40.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_40
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.40 (libva )
  vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:VAEntrypointVLD
VAProfileMPEG2Simple:VAEntrypointEncSlice
VAProfileMPEG2Main  :VAEntrypointVLD
VAProfileMPEG2Main  :VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointVLD
VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP
VAProfileH264Main   :VAEntrypointVLD
VAProfileH264Main   :VAEntrypointEncSlice
VAProfileH264Main   :VAEntrypointEncSliceLP
VAProfileH264High   :VAEntrypointVLD
VAProfileH264High   :VAEntrypointEncSlice
VAProfileH264High   :VAEntrypointEncSliceLP
VAProfileH264MultiviewHigh  :VAEntrypointVLD
VAProfileH264MultiviewHigh  :VAEntrypointEncSlice
VAProfileH264StereoHigh :VAEntrypointVLD
VAProfileH264StereoHigh :VAEntrypointEncSlice
VAProfileVC1Simple  :VAEntrypointVLD
VAProfileVC1Main:VAEntrypointVLD
VAProfileVC1Advanced:VAEntrypointVLD
VAProfileNone   :VAEntrypointVideoProc
VAProfileJPEGBaseline   :VAEntrypointVLD
VAProfileJPEGBaseline   :VAEntrypointEncPicture
VAProfileVP8Version0_3  :VAEntrypointVLD
VAProfileVP8Version0_3  :VAEntrypointEncSlice
VAProfileHEVCMain   :VAEntrypointVLD

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

2018-03-16 Thread Kenneth Loafman

Try this then:

sh -c "ulimit -v 100; ulimit -n 8192; exec /usr/lib/x86_64-linux-gnu
/deja-dup/deja-dup-monitor"

It adds the ulimit -n call and may do what you need now that the systemd
settings are in place.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Triaged
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1751892] Re: Unable to set different Scale on different Monitors

It looks like this bug may be a duplicate of the 1735986

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

Title:
  Unable to set different Scale on different Monitors

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  My laptop screen is 3840x2160 while my external monitor is only
  1680x1050. In order for the laptop monitor to be usable I have the
  scaling set at 200 (this works wonderful). However, when I plug in my
  external monitor it is scaled up to 200% as well making it unusable.

  Attempting to scale one to 100 and the other 200 looks to be possible;
  however, the Apply button keeps appearing and disappearing randomly
  with no actual effect.

  It looks like practically you can only set one scale for both monitors
  even though the UI looks to be letting you do it.

  I have tried this on Wayland and Xorg with similar results.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 15:12:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:83b9]
  InstallationDate: Installed on 2018-02-21 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd01/23/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1756073] Re: Display scaling doesn't work properly on second display

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

It looks like this is also a duplicate of the bug 1735986

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

Title:
  Display scaling doesn't work properly on second display

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu version 17.10

  I have a laptop with 2560x1440 display and a 1920x1080 BenQ display.
  The scale is set to 200% on the built-in display, but some windows are also 
getting scaled on the second display.

  Attached screenshot demonstrates it. One terminal window I opened
  right on the second display, and one window I dragged from the first
  display.

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

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

[Desktop-packages] [Bug 1751892] Re: Unable to set different Scale on different Monitors

correct notation:  bug 1735986

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

Title:
  Unable to set different Scale on different Monitors

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  My laptop screen is 3840x2160 while my external monitor is only
  1680x1050. In order for the laptop monitor to be usable I have the
  scaling set at 200 (this works wonderful). However, when I plug in my
  external monitor it is scaled up to 200% as well making it unusable.

  Attempting to scale one to 100 and the other 200 looks to be possible;
  however, the Apply button keeps appearing and disappearing randomly
  with no actual effect.

  It looks like practically you can only set one scale for both monitors
  even though the UI looks to be letting you do it.

  I have tried this on Wayland and Xorg with similar results.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 15:12:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:83b9]
  InstallationDate: Installed on 2018-02-21 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd01/23/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  got this after logging in

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 16 08:00:06 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-12-15 (91 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171214)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1750197] Re: Activities overview causes heavy CPU spikes in Wayland & Xorg

2018-03-16 Thread Luke B.

Forgive me, but what method did you use to profile the resource usage of
gnome-shell? I would like to see if the root cause you discovered
matches what affects my system.

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

Title:
  Activities overview causes heavy CPU spikes in Wayland & Xorg

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Release: 17.10 and 18.04
  gnome-shell version: 3.26.2
  System Theme: CommuniTheme Beta

  Upon navigating through various areas of the system, GUI animations
  are very stuttery. This heavily affects the CPU usage of my device.
  For instance, opening the shell app drawer displays a very janky
  animation, and my CPU will spike to nearly 85% for each open/close.
  This happens regardless of using XOrg or Wayland; however Wayland
  appears to have an overall lower impact on resource usage. The CPU in
  this laptop isn't the greatest (being a 2014 Celeron), but this is
  noticeably more sluggish compared to previous releases like 16.04 and
  16.10.

  This same issue is still existent, but somewhat less noticeable on my
  other i5-6400 (GTX 1050) machine. Also, emulating this release in a VM
  with 2 CPUS and 4096MB of RAM renders it unresponsive for 3-5 seconds
  after opening/closing the app drawer.

  Please do not hesitate to follow up with requests for more info, as I
  will be happy to help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 17 19:13:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   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/1750197/+subscriptions

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

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  Printer service looping after update/upgrade; Canon MX490 printer

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 13:28:03 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-15 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x55e0a1e5c5f1:mov0x90(%rbp),%rsi
   PC (0x55e0a1e5c5f1) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1756400] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()

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

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 #1720441, 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/1756400/+attachment/5081653/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGABRT in g_assertion_message()

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

Bug description:
  hangs system

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 23:01:09 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2016-01-08 (798 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: gnome-control-center wifi
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libnma.so.0
   () at /usr/lib/x86_64-linux-gnu/libnma.so.0
   () at /usr/lib/x86_64-linux-gnu/libnma.so.0
  Title: gnome-control-center crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to bionic on 2018-01-24 (50 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1754425] Re: Lots of pcieport and nvme kernel errors - system non-responsive

2018-03-16 Thread tom

So today, woke up properly from lid close.

I'm not sure what to make of it, as I haven't restarted for over 2 days.

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

Title:
  Lots of pcieport and nvme kernel errors - system non-responsive

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

Bug description:
  If I open the lid, it seems that the computer flat-out doesn't wake
  up. HOWEVER, if I wait patiently more than 20 seconds, and press (not
  hold) the power button, SOMETIMES, the computer will "snap out of it"
  and come back to my desktop. Although RAM is 25% used, and CPU usage
  is around 25-50% or less (depending on apps), mouse will regularly
  freeze up for some seconds every 10 seconds or so. Wifi will claim to
  be "on", but there aren't any networks in the "select network"
  dialogue. Turning wifi off and then on does not fix this problem. So
  I'll be in this terrifying state of non-responsive every few seconds
  computer, with no ability to reconnect to networks and report bug.

  I force restart. The first restart, upon login, will hang indefinitely
  on a purple screen with the cursor in the middle. I will have to force
  restart again. Upon 2nd restart, it will boot "normally".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  8 12:38:24 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  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)
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1387 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-02 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  MachineType: Dell Inc. XPS 15 9560
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash 
acpi_rev_override=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tom1387 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-02 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228)
  MachineType: Dell Inc. XPS 15 9560
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=9ccc05c8-ea98-4229-a4d3-6d3a292df6df ro quiet splash 
acpi_rev_override=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version:

[Desktop-packages] [Bug 1756372] Re: Merge 2.24.32-1 from Debian

2018-03-16 Thread Hans Joachim Desserud

** Tags added: needs-debian-merge upgrade-software-version

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

Title:
  Merge 2.24.32-1 from Debian

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Please merge gtk+2.0 (2.24.32-1) from Debian. It's a bug-fix release.

  Overview of Changes from GTK+ 2.24.31 to 2.24.32
  

  * Build:
   - Support Visual Studio 2017

  * Bug fixes:
   136059 Ctrl-navigation works in opposite direction in right-to-left text
   165385 Win32 keyboard handling still incomplete
   358970 gtk_scale_set_digits does not cause value to be rounded if 
draw-value...
   468868 Popup of "appears-as-list" ComboBox does not change screen with its 
t...
   554057 Calling gtk_menu_shell_select_item() on GtkMenuBar can break grabs 
(a...
   569581 Using the US-Intl keyboard layout causes unexpected character 
combina...
   618160 Documentation for gtk_combo_box_get_active_iter is unclear
   658111 gtk_label_set_pattern() is reset by a call to gtk_box_pack_start()
   676550 Adding underlines to Label with gtk_label_set_pattern() does not work
   696624 Japanese (Korean/Chinese) XIM input mode indicator has not been 
worki...
   701296 gtkfixed accepts toplevel windows into its children list after 
gtk_wi...
   729651 Crash in GtkFileChooserButton with appears-as-list
   734946 Implement GContentType on OSX
   768722 Keyboard shortcuts for russian characters doesn't work
   769214 keyval field not filled correctly for Pause key
   772389 Appending a character to a GtkEntry control in overwrite mode rings 
t...
   772794 segfault when on unchecked XListInputDevices return value
   773587 recent-manager: Add a limit to the list's size
   776909 gtk_adjustment_clamp_page: Conditional jump or move depends on 
uninit...
   777683 SIGBUS due to gdk_x11_window_set_opacity
   778542 Use UTF-8 encoding for tooltips on files in the "recently used" list
   778811 Enter submenus when activating their parent item
   779009 Missing property-change::accessible-description events when the 
toolt...
   779081 GtkTextView: expose API to get Pango line direction
   779605 GLib-CRITICAL Source ID xxx was not found when attempting to remove it
   781020 GIMP UI vector icons are drawn way too small
   781605 GtkVolumeButton limited to 10 values
   785165 Set translation domain for parameter_string in gtk_init_with_args
   785672 Entry: Setting icon tooltip to empty disables tooltip on whole widget
   786771 Critical about mismatched GdkDisplays when opening Inspector combobox
   787158 gtk_widget_get_preferred_width on GtkToolbar gives wrong minimum width
   787195 gtk_toolbar_set_show_arrow does not show an arrow
   787410 entry: fix memory leak
   788577 Global -GtkComboBox-appears-as-list breaks opening menu-mode CBs by 
k...

  * Translation updates:
   Hungarian
   Indonesian
   Polish
  

  gtk+2.0 (2.24.32-1) unstable; urgency=medium

* New upstream release
* debian/libgtk2.0-0.symbols: Add symbols
* Update Vcs fields for migration to https://salsa.debian.org/
* Drop patches applied in new release:
  - 0001-Don-t-use-guint32-with-XChangeProperty.patch
  - 0002-GtkMenuShell-always-activate-menu-shells.patch

   -- Jeremy Bicha   Sat, 20 Jan 2018 07:46:38 -0500

  gtk+2.0 (2.24.31-5) unstable; urgency=medium

* Update Vcs fields for conversion to git
* Add debian/gbp.conf
* Bump Standards-Version to 4.1.2

   -- Jeremy Bicha   Thu, 21 Dec 2017 14:05:20 -0500

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

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

[Desktop-packages] [Bug 1725749] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

Reported upstream as

https://github.com/apple/cups/issues/5268

** Bug watch added: github.com/apple/cups/issues #5268
   https://github.com/apple/cups/issues/5268

** Also affects: cups via
   https://github.com/apple/cups/issues/5268
   Importance: Unknown
   Status: Unknown

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  crashed immediately after starting LUbuntu 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Oct 19 21:56:40 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HEWLETT-PACKARD-DESKJET-990C: parallel:/dev/lp0
   device for HP-LaserJet-5: socket://192.168.22.65:9100
   device for PDF: cups-pdf:/
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Papersize: a4
  PpdFiles:
   HEWLETT-PACKARD-DESKJET-990C: HP Deskjet 990c, hpcups 3.17.7
   PDF: Generic CUPS-PDF Printer
   HP-LaserJet-5: HP LaserJet 5 - CUPS+Gutenprint v5.2.13
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro rhgb plymouth:debug 
drm.debug=0xe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro rhgb plymouth:debug 
drm.debug=0xe
  SegvAnalysis:
   Segfault happened at: 0x7f57d0318954 : cmpq   
$0x0,(%rdi)
   PC (0x7f57d0318954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88X-D3HP
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

2018-03-16 Thread herrtimson

bug still not solved, got the update to firefox-59 on lubuntu-14.04
today, it still segfaults. So I spent a few hours to an install of arch
linux on my rpi2, simply because firefox never had this issue over
there, and it still doesn't hit this bug as of today.

arch linux is rolling release, atm the toolchain is: gcc-7.2.1,
glibc-2.26, binutils-2.29 or 2.30, rust-1.24.1, clang/llvm-5.0.1

I made a screenshot for everyone, with the cflags and compile switches.
--enable-rust-simd caught eye, what is this all about? Also anyone tried
to run the binary from bionic, which should be built with gcc-7 as well?

** Attachment added: "screenshot with cflags and compile switches"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711337/+attachment/5081632/+files/firefox-59-arch-linux-gcc-7.2.1.png

-- 
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:
  Expired
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 1756160] Re: cupsd crashed with SIGSEGV in mime_compare_srcs()

Reported upstream as

https://github.com/apple/cups/issues/5267

** Bug watch added: github.com/apple/cups/issues #5267
   https://github.com/apple/cups/issues/5267

** Also affects: cups via
   https://github.com/apple/cups/issues/5267
   Importance: Unknown
   Status: Unknown

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

Title:
  cupsd crashed with SIGSEGV in mime_compare_srcs()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New

Bug description:
  No clue. This came up after the update this afternoon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Mar  7 16:41:29 2018
  ExecutablePath: /usr/sbin/cupsd
  ExecutableTimestamp: 1518257679
  InstallationDate: Installed on 2018-03-05 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lpstat: device for LBP252: smb://izcpm3/Canon-P-64
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  Papersize: a4
  PpdFiles: LBP252: Canon LBP252 PPD PS
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: /usr/sbin/cupsd -l
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_rev_override=1 enable_fbc=1 
enable_psr=1 disable_power_well=0 pci=nommconf
  SegvAnalysis:
   Segfault happened at: 0x7fb76b986e8e <__strcmp_sse2_unaligned+30>:   movdqu 
(%rsi),%xmm0
   PC (0x7fb76b986e8e) ok
   source "(%rsi)" (0x353250424c4e4334) not located in a known VMA region 
(needed readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   mimeFilter2 () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in mimeFilter2()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 11/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  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.6.2:bd11/12/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1751892] Re: Unable to set different Scale on different Monitors

Another note, I'm able to make chrome usable on my external monitor by
opening it using the following command. Obviously if I move chrome to my
4k laptop monitor it becomes unusable. But just documenting it as
another avenue.

GDK_DPI_SCALE=.5 google-chrome

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

Title:
  Unable to set different Scale on different Monitors

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  My laptop screen is 3840x2160 while my external monitor is only
  1680x1050. In order for the laptop monitor to be usable I have the
  scaling set at 200 (this works wonderful). However, when I plug in my
  external monitor it is scaled up to 200% as well making it unusable.

  Attempting to scale one to 100 and the other 200 looks to be possible;
  however, the Apply button keeps appearing and disappearing randomly
  with no actual effect.

  It looks like practically you can only set one scale for both monitors
  even though the UI looks to be letting you do it.

  I have tried this on Wayland and Xorg with similar results.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 15:12:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:83b9]
  InstallationDate: Installed on 2018-02-21 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd01/23/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1756324] Re: No signal after upgrading on 18.04

2018-03-16 Thread Brian Murray

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  No signal after upgrading on 18.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Basically, yesterday I upgraded from 17.10 to 18.04 Bionic Beaver. At
  the reboot, when I boot onto Ubuntu, after the GRUB has been shown, it
  just boots to nothing, my screen display "No signal detected",
  although I can hear the drum sound. Using nomodeset works but my
  computer is set at a wrong frequency (stuck to 77Hz, even forcing via
  xrandr doesn't work). So using nomodeset  I got into i3, downloaded
  mesa drivers and tried radeon too, and rebooted. Now still shows no
  signal, but I can get into a fluent 60Hz i3, if I go to recovery mode,
  then press normal boot. The problem also with that is that GNOME
  doesn't work, when I leave i3, log onto GNOME, it shows a blackscreen
  and just sends me back to the login menu. I've noticed this error
  appeared at boot: [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

  Here's xrandr output: xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080  0.00* 
 1280x1024  0.00  
 1024x768   0.00  
 800x6000.00  
 640x4800.00  

  
  Thanks for any future help!

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

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

[Desktop-packages] [Bug 1756389] [NEW] Delay startup of evolution-calendar-factory

Public bug reported:

On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

evolution-calendar-factory startup should be delayed if it cannot be
disabled completely.

The following changes to evolution-calendar-factory.service do this:
""" 
[Unit]
Description=Evolution calendar service

[Service]
Type=dbus
BusName=org.gnome.evolution.dataserver.Calendar7
ExecStartPre=/bin/sleep 60
ExecStart=/usr/lib/evolution/evolution-calendar-factory
"""

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evolution-data-server 3.28.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 17:52:45 2018
InstallationDate: Installed on 2013-09-03 (1654 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution-data-server
UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic rls-bb-incoming

** Attachment added: "bootchart_nodelay.png"
   
https://bugs.launchpad.net/bugs/1756389/+attachment/5081626/+files/bootchart_nodelay.png

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

Title:
  Delay startup of evolution-calendar-factory

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
  With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

  evolution-calendar-factory startup should be delayed if it cannot be
  disabled completely.

  The following changes to evolution-calendar-factory.service do this:
  """ 
  [Unit]
  Description=Evolution calendar service

  [Service]
  Type=dbus
  BusName=org.gnome.evolution.dataserver.Calendar7
  ExecStartPre=/bin/sleep 60
  ExecStart=/usr/lib/evolution/evolution-calendar-factory
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:52:45 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1756389] Re: Delay startup of evolution-calendar-factory

bootchart with ev-cal-factory delayed by 1 minute.

** Attachment added: "bootchart_evcal_delayed-60s.png"
   
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1756389/+attachment/5081630/+files/bootchart_evcal_delayed-60s.png

** Tags added: rls-bb-incoming

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

Title:
  Delay startup of evolution-calendar-factory

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, evolution-calendar-factory starts 
early and slows down session startup. In the bootchart attached, it overlaps 
with gnome-shell startup which is also resource intensive.
  With evolution-calendar-factory delayed gnome-shell starts 2 seconds faster.

  evolution-calendar-factory startup should be delayed if it cannot be
  disabled completely.

  The following changes to evolution-calendar-factory.service do this:
  """ 
  [Unit]
  Description=Evolution calendar service

  [Service]
  Type=dbus
  BusName=org.gnome.evolution.dataserver.Calendar7
  ExecStartPre=/bin/sleep 60
  ExecStart=/usr/lib/evolution/evolution-calendar-factory
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:52:45 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution-data-server
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1756387] [NEW] Whish: a Unity like desktop bar in Gnome, or the default desktop manager of Ubuntu

2018-03-16 Thread Péter Prőhle

Public bug reported:

I wish a Unity like desktop bar in Gnome, or the default desktop manager
of Ubuntu.

More precisely:  a desktop bar which is capable to steal, to take away
the menu bars of the application windows, and show the menu bar of that
application window which is in focus currently.

I wish this in the default desktop manager, what is currently Gnome if I
know correctly.

The only reason why I still use the Unity is this feature what I find
very comfortable.

Can I configure the Gnome desktop this way right now, or it needs an
amount of programming, and a better knowledge of the gnome system?

If my wish is not only a simple configuration or a bit more only, and if
the solution does not need far too deep knowledge of the Gnome desktop
programming, then I am ready to program it, if someone gives me the
references to concise reading materials enough for this work (I use and
program computers since 1972 on regular daily base, and a I am fluent in
unix/linux tools, including C/C++ what I teach regularly at the
university).

[[it was suggested me at the AskUbuntu, that this kind of wishes fits
here to the bug reports better, and somebody with enough privileges will
mark this as a "wish list" item]]

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

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

Title:
  Whish: a Unity like desktop bar in Gnome, or the default desktop
  manager of Ubuntu

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

Bug description:
  I wish a Unity like desktop bar in Gnome, or the default desktop
  manager of Ubuntu.

  More precisely:  a desktop bar which is capable to steal, to take away
  the menu bars of the application windows, and show the menu bar of
  that application window which is in focus currently.

  I wish this in the default desktop manager, what is currently Gnome if
  I know correctly.

  The only reason why I still use the Unity is this feature what I find
  very comfortable.

  Can I configure the Gnome desktop this way right now, or it needs an
  amount of programming, and a better knowledge of the gnome system?

  If my wish is not only a simple configuration or a bit more only, and
  if the solution does not need far too deep knowledge of the Gnome
  desktop programming, then I am ready to program it, if someone gives
  me the references to concise reading materials enough for this work (I
  use and program computers since 1972 on regular daily base, and a I am
  fluent in unix/linux tools, including C/C++ what I teach regularly at
  the university).

  [[it was suggested me at the AskUbuntu, that this kind of wishes fits
  here to the bug reports better, and somebody with enough privileges
  will mark this as a "wish list" item]]

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

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

[Desktop-packages] [Bug 1756324] [NEW] No signal after upgrading on 18.04

You have been subscribed to a public bug:

Basically, yesterday I upgraded from 17.10 to 18.04 Bionic Beaver. At
the reboot, when I boot onto Ubuntu, after the GRUB has been shown, it
just boots to nothing, my screen display "No signal detected", although
I can hear the drum sound. Using nomodeset works but my computer is set
at a wrong frequency (stuck to 77Hz, even forcing via xrandr doesn't
work). So using nomodeset  I got into i3, downloaded mesa drivers and
tried radeon too, and rebooted. Now still shows no signal, but I can get
into a fluent 60Hz i3, if I go to recovery mode, then press normal boot.
The problem also with that is that GNOME doesn't work, when I leave i3,
log onto GNOME, it shows a blackscreen and just sends me back to the
login menu. I've noticed this error appeared at boot: [drm:amdgpu_init
[amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

Here's xrandr output: xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080  0.00* 
   1280x1024  0.00  
   1024x768   0.00  
   800x6000.00  
   640x4800.00  


Thanks for any future help!

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


** Tags: bot-comment
-- 
No signal after upgrading on 18.04
https://bugs.launchpad.net/bugs/1756324
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

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

[Desktop-packages] [Bug 1480673] Re: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly

2018-03-16 Thread Luca

The problem persists with 4.15.0-12, touchpad doesn't work altogether,
it works perfectly with 4.15.0-041500 from the kernel-ppa.

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

Title:
  [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized
  incorrectly

Status in libinput:
  Won't Fix
Status in Linux:
  Unknown
Status in xinput package in Ubuntu:
  Triaged

Bug description:
  Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI]
  Synaptics Touch Digitizer V04 - no multitouch".

  The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo.
  Both (touchscreen, touchpad) only work like a mouse (moving pointer, left and 
right click), scrolling, zooming, etc. is not working.
  the keyboard works fine.

  relevant  content of  /proc/bus/input/devices:

  [...]
  I: Bus=0003 Vendor=06cb Product=11f0 Version=0111
  N: Name="SYNAPTICS Synaptics Touch Digitizer V04"
  P: Phys=usb-:00:14.0-7/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input9
  U: Uniq=
  H: Handlers=mouse1 event9
  B: PROP=2
  B: EV=b
  B: KEY=400 0 0 0 0 0
  B: ABS=2608003

  I: Bus=0003 Vendor=06cb Product=11f0 Version=0111
  N: Name="SYNAPTICS Synaptics Touch Digitizer V04 Pen"
  P: Phys=usb-:00:14.0-7/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input10
  U: Uniq=
  H: Handlers=mouse2 event10
  B: PROP=0
  B: EV=1b
  B: KEY=c03 1 0 0 0 0
  B: ABS=103
  B: MSC=10

  [...]

  I: Bus=0005 Vendor=0b05 Product=8502 Version=0001
  N: Name="ASUS T300CHI DOCKING"
  P: Phys=34:02:86:7b:3b:9d
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0006/input/input18
  U: Uniq=1c:b7:2c:15:94:8b
  H: Handlers=sysrq kbd mouse3 event17
  B: PROP=0
  B: EV=12001f
  B: KEY=20 0 0 2000 40 3 10207 ff9f387ad9405fff 
febeffdfffef fffe
  B: REL=303
  B: ABS=700
  B: MSC=10
  B: LED=1f

  output of  xinput --list:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ B16_b_02 USB-PS/2 Optical Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ HID 0566:3108   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen id=14   [slave  pointer 
 (2)]
  ⎜   ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=15   [slave  pointer 
 (2)]
  ⎜   ↳ ASUS T300CHI DOCKINGid=18   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ HID 0566:3108   id=10   [slave  
keyboard (3)]
  ↳ C-Media Electronics Inc. USB Multimedia Audio Deviceid=12   [slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=13   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=16   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=17   [slave  
keyboard (3)]

  output of synclient is:
  Couldn't find synaptics properties. No synaptics driver loaded?

  but I'm unsure if the synaptics driver is the right place to look
  since basic functionality is working and the "ASUS T300CHI DOCKING" is
  recognized as "pointer"

  it seems that the device is recognized by the kernel but only used as a 
pointing device.
  I've also attached the xorg.log

  output of uname -a:
  Linux xxx 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 21:17:31 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  it's a completely fresh install of xubuntu 15.04 with software-updater run 
once (so no strange hacks or drivers installed)
  output of lsb_release -rd:
  Description:  Ubuntu 15.04
  Release:  15.04

  output of apt-cache policy xinput
  xinput:
    Installed: 1.6.1-1
    Candidate: 1.6.1-1
    Version table:
   *** 1.6.1-1 0
  500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  expected results:
  - scrolling on touchpad and touchscreen should work with a two-finger gesture
  - zooming on touchpad and touchscreen should work with a two-finger gesture

  actual results:
  two fingers are not recognized on touchscreen or touchpad

  Any help would be appreciated, if you need more console output or
  logs, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu

[Desktop-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor

2018-03-16 Thread Krister

Today the fuzzy screen depicted in the attachment appears spontaneously
while using google maps.  This time with a block around the pointer,
that continued to move with the pointer.

** Attachment added: "IMG_20180316_172748_697.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1752145/+attachment/5081615/+files/IMG_20180316_172748_697.jpg

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

Title:
  system freeze after full screen video viewing with Xorg on ultrawide
  monitor

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  1. open a video (either youtube or totem)
  2. put it in full screen.
  3. wait

  Eventually (within minutes) the system will freeze in one of 2 ways.

  1. There will be only blackness with no response ( even
  unresponsive).

  2. There will be snow that shifts with keyboard and mouse interaction
  (see photo).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 19:08:13 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (53 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago)

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

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

[Desktop-packages] [Bug 1756160] Re: cupsd crashed with SIGSEGV in mime_compare_srcs()

** Information type changed from Private to Public

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

Title:
  cupsd crashed with SIGSEGV in mime_compare_srcs()

Status in cups package in Ubuntu:
  New

Bug description:
  No clue. This came up after the update this afternoon.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CupsErrorLog:
   
  Date: Wed Mar  7 16:41:29 2018
  ExecutablePath: /usr/sbin/cupsd
  ExecutableTimestamp: 1518257679
  InstallationDate: Installed on 2018-03-05 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lpstat: device for LBP252: smb://izcpm3/Canon-P-64
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  Papersize: a4
  PpdFiles: LBP252: Canon LBP252 PPD PS
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: /usr/sbin/cupsd -l
  ProcCwd: /
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro acpi_rev_override=1 enable_fbc=1 
enable_psr=1 disable_power_well=0 pci=nommconf
  SegvAnalysis:
   Segfault happened at: 0x7fb76b986e8e <__strcmp_sse2_unaligned+30>:   movdqu 
(%rsi),%xmm0
   PC (0x7fb76b986e8e) ok
   source "(%rsi)" (0x353250424c4e4334) not located in a known VMA region 
(needed readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   mimeFilter2 () from /usr/lib/x86_64-linux-gnu/libcupsmime.so.1
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in mimeFilter2()
  UpgradeStatus: Upgraded to bionic on 2018-03-05 (10 days ago)
  UserGroups:
   
  dmi.bios.date: 11/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.2
  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.6.2:bd11/12/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1756369] Re: Google Calendar is not syncing in Ubuntu 18.04 Beta.

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

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

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

Title:
  Google Calendar is not syncing in Ubuntu 18.04 Beta.

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  My google Calendar is not syncing using Ubuntu 18.04 Beta
  I can add my gmail account to Ubuntu
  But when opening the Calendar, I don't my Google Calendar info.
  If I click sync manualy, neither

  Had no problems with 17.10

  JF

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.27.90-1build1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Mar 16 11:38:11 2018
  InstallationDate: Installed on 2018-03-11 (4 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1727710] Re: Unable to access more than 20 languages in 1080p

2018-03-16 Thread Iain Lane

OK, I think we should hide the 'install more' thing for 18.04. It
doesn't work on Ubuntu and I don't think we're going to get to fix it
before the release.

It's been a 'known' item for us for a while, and we would like to fix it
but it requires some thought/effort/coordination/time that we haven't
put into the problem yet.

I'll look into this soon, possibly at the start of next week. Thanks for
your work so far.

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

Title:
  Unable to access more than 20 languages in 1080p

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Bionic:
  In Progress

Bug description:
  There is no scroll bar on the language selection GUI, causing issues
  if you install more than 20 language selections. The ... button is on
  the bottom off the screen, meaning you can't access it. On resolutions
  smaller than 1080p, you could expect the same issues but with less
  language options.

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

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

[Desktop-packages] [Bug 1751892] Re: Unable to set different Scale on different Monitors

Just a follow up. I've gotten some good information from this AskUbuntu
post at https://askubuntu.com/questions/875832/how-to-set-per-monitor-
scaling-on-wayland

Following these directions seem to help with certain applications (e.g.
gnome-terminal, gedit, nautilus); however, it does not work for others
(e.g. thunderbird, pidgin, google-chrome).

It apears it's an issue with XWayland.

I would further mention even though applications like nautilus look
correct, things like their context menu are blown up. I assume that some
other application is handling that (gnome?) - I'm unsure of how that
part of the rendering works.

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

Title:
  Unable to set different Scale on different Monitors

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  My laptop screen is 3840x2160 while my external monitor is only
  1680x1050. In order for the laptop monitor to be usable I have the
  scaling set at 200 (this works wonderful). However, when I plug in my
  external monitor it is scaled up to 200% as well making it unusable.

  Attempting to scale one to 100 and the other 200 looks to be possible;
  however, the Apply button keeps appearing and disappearing randomly
  with no actual effect.

  It looks like practically you can only set one scale for both monitors
  even though the UI looks to be letting you do it.

  I have tried this on Wayland and Xorg with similar results.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 15:12:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:83b9]
  InstallationDate: Installed on 2018-02-21 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd01/23/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1756336] Re: cupsd crashed with SIGSEGV in finalize_job()

Reported upstream as

https://github.com/apple/cups/issues/5266

** Bug watch added: github.com/apple/cups/issues #5266
   https://github.com/apple/cups/issues/5266

** Also affects: cups via
   https://github.com/apple/cups/issues/5266
   Importance: Unknown
   Status: Unknown

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

Title:
  cupsd crashed with SIGSEGV in finalize_job()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New

Bug description:
  I tried to print to an HP P1102w printer. I don't have more detailed
  information.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 16 12:31:49 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2018-03-02 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  Lpstat: device for HP-LaserJet-Professional-P-1102w: 
hp:/usb/HP_LaserJet_Professional_P_1102w?serial=0W473S3TPR1a
  MachineType: LENOVO 20HR006CMX
  Papersize: a4
  PpdFiles: HP-LaserJet-Professional-P-1102w: HP LaserJet Professional P 1102w, 
hpcups 3.17.10, requires proprietary plugin
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x5563faec0ee9:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x5563faec0ee9) ok
   source "%es:(%rdi)" (0x5563faee0898) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5563fae9f2b0, argc=2, argv=0x7ffd075f3808, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd075f37f8) at ../csu/libc-start.c:310
  Title: cupsd crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR006CMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HR006CMX:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR006CMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR006CMX
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1756378] Re: Udisks2 flacky test (regression from 2.7)

2018-03-16 Thread Iain Lane

** Also affects: udisks2 (Ubuntu Bionic)
   Importance: High
 Assignee: Sebastien Bacher (seb128)
   Status: New

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

Title:
  Udisks2 flacky test (regression from 2.7)

Status in udisks2 package in Ubuntu:
  New
Status in udisks2 source package in Bionic:
  New

Bug description:
  One of the udisks2 tests has become flacky in the 2.7 update

  ERROR: test_ext4 (__main__.FS)
  fs: ext4
  --
  Traceback (most recent call last):
File "src/tests/integration-test", line 680, in test_ext4
  self._do_fs_check('ext4')
File "src/tests/integration-test", line 841, in _do_fs_check
  self._do_udisks_check(fs_type)
File "src/tests/integration-test", line 1045, in _do_udisks_check
  cd_fs.call_mount_sync(ro_options, None)
  AttributeError: 'NoneType' object has no attribute 'call_mount_sync'

  That needs to be resolved

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

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

[Desktop-packages] [Bug 1756379] Re: Delay start of gnome-software service

in this bootchart the system is quiet after 49s if gnome-software
service is delayed by 1 minute.

** Attachment added: "bootchart_gs_delayed-60s.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+attachment/5081595/+files/bootchart_gs_delayed-60s.png

** Description changed:

- On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive. 
- gnome-software service should be delayed if it cannot be stop completely.
+ On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
+ With gnome-software delayed gnome-shell starts 2 seconds faster.
+ 
+ 
+ gnome-software service startup should be delayed if it cannot be stop 
completely.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
-  gnome-software-plugin-flatpak 3.28.0-0ubuntu3
-  gnome-software-plugin-limba   N/A
-  gnome-software-plugin-snap3.28.0-0ubuntu3
+  gnome-software-plugin-flatpak 3.28.0-0ubuntu3
+  gnome-software-plugin-limba   N/A
+  gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
-  TERM=screen-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=screen-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

** Tags added: rls-bb-incoming

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

Title:
  Delay start of gnome-software service

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
  With gnome-software delayed gnome-shell starts 2 seconds faster.

  
  gnome-software service startup should be delayed if it cannot be stop 
completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1756379] [NEW] Delay start of gnome-software service

Public bug reported:

On a default Bionic Desktop installation, gnome-software starts early and slows 
down session startup. In the bootchart attached, it overlaps with gnome-shell 
startup which is also resource intensive.
With gnome-software delayed gnome-shell starts 2 seconds faster.


gnome-software service startup should be delayed if it cannot be stop 
completely.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 16 17:11:41 2018
InstallationDate: Installed on 2013-09-03 (1654 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.28.0-0ubuntu3
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.0-0ubuntu3
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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


** Tags: amd64 apport-bug bionic rls-bb-incoming

** Attachment added: "bootchart_gs_nodelay.png"
   
https://bugs.launchpad.net/bugs/1756379/+attachment/5081591/+files/bootchart_gs_nodelay.png

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

Title:
  Delay start of gnome-software service

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On a default Bionic Desktop installation, gnome-software starts early and 
slows down session startup. In the bootchart attached, it overlaps with 
gnome-shell startup which is also resource intensive.
  With gnome-software delayed gnome-shell starts 2 seconds faster.

  
  gnome-software service startup should be delayed if it cannot be stop 
completely.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 17:11:41 2018
  InstallationDate: Installed on 2013-09-03 (1654 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu3
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-01-26 (49 days ago)

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

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

[Desktop-packages] [Bug 1751892] Re: Unable to set different Scale on different Monitors

I've now reported this upstream to gnome-control-center here:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/17

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

Title:
  Unable to set different Scale on different Monitors

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  My laptop screen is 3840x2160 while my external monitor is only
  1680x1050. In order for the laptop monitor to be usable I have the
  scaling set at 200 (this works wonderful). However, when I plug in my
  external monitor it is scaled up to 200% as well making it unusable.

  Attempting to scale one to 100 and the other 200 looks to be possible;
  however, the Apply button keeps appearing and disappearing randomly
  with no actual effect.

  It looks like practically you can only set one scale for both monitors
  even though the UI looks to be letting you do it.

  I have tried this on Wayland and Xorg with similar results.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 15:12:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:83b9]
  InstallationDate: Installed on 2018-02-21 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.37
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd01/23/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1745440] Re: "Apply" button is missing from Displays

I've now reported this directly to gnome-control-center here
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/18

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

Title:
  "Apply" button is missing from Displays

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

Bug description:
  Steps to reproduce:

1. Click [1] -> [2] -> Devices -> Displays -> Scale: 100 %.

  Expected behavior:

An "Apply" button appears.

  Actual behavior:

No "Apply" button appears. This behavior prevents me from changing
  display settings.

  
  [1]: the nameless menu in the top right corner of the screen labeled by five 
images depicting a network, the Bluetooth logo, a speaker, a battery, and 
downward pointing triangle
  [2]: the nameless button labeled by an image of a socket screwdriver and 
wrench

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 09:04:39 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2016-09-15 (497 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/usr/bin/zsh
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2018-01-21 (4 days ago)

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

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

[Desktop-packages] [Bug 1756336] Re: cupsd crashed with SIGSEGV in finalize_job()

** Information type changed from Private to Public

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

Title:
  cupsd crashed with SIGSEGV in finalize_job()

Status in CUPS:
  Unknown
Status in cups package in Ubuntu:
  New

Bug description:
  I tried to print to an HP P1102w printer. I don't have more detailed
  information.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: cups-daemon 2.2.6-5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Mar 16 12:31:49 2018
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2018-03-02 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180301)
  Lpstat: device for HP-LaserJet-Professional-P-1102w: 
hp:/usb/HP_LaserJet_Professional_P_1102w?serial=0W473S3TPR1a
  MachineType: LENOVO 20HR006CMX
  Papersize: a4
  PpdFiles: HP-LaserJet-Professional-P-1102w: HP LaserJet Professional P 1102w, 
hpcups 3.17.10, requires proprietary plugin
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x5563faec0ee9:repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x5563faec0ee9) ok
   source "%es:(%rdi)" (0x5563faee0898) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x5563fae9f2b0, argc=2, argv=0x7ffd075f3808, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffd075f37f8) at ../csu/libc-start.c:310
  Title: cupsd crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET37W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HR006CMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET37W(1.22):bd07/04/2017:svnLENOVO:pn20HR006CMX:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HR006CMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HR006CMX
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1756378] Re: Udisks2 flacky test (regression from 2.7)

2018-03-16 Thread Sebastien Bacher

There are also issues on s390x but disks handling is different on that
arch, it's worth still looking at that as well

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

Title:
  Udisks2 flacky test (regression from 2.7)

Status in udisks2 package in Ubuntu:
  New
Status in udisks2 source package in Bionic:
  New

Bug description:
  One of the udisks2 tests has become flacky in the 2.7 update

  ERROR: test_ext4 (__main__.FS)
  fs: ext4
  --
  Traceback (most recent call last):
File "src/tests/integration-test", line 680, in test_ext4
  self._do_fs_check('ext4')
File "src/tests/integration-test", line 841, in _do_fs_check
  self._do_udisks_check(fs_type)
File "src/tests/integration-test", line 1045, in _do_udisks_check
  cd_fs.call_mount_sync(ro_options, None)
  AttributeError: 'NoneType' object has no attribute 'call_mount_sync'

  That needs to be resolved

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

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

[Desktop-packages] [Bug 1756374] Re: Xwayland crashed with SIGABRT in OsAbort()

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

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 #1731911, 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/1756374/+attachment/5081530/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1731911
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_read_events() from ospoll_wait()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xwayland crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  on boot

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 16 16:37:30 2018
  DistUpgraded: 2018-02-23 18:43:25,406 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xwayland
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [17aa:3902]
  InstallationDate: Installed on 2018-02-21 (23 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 5986:0671 Acer, Inc 
   Bus 001 Device 003: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80M1
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=7c316ffa-779d-4eda-a8d6-f7a20492e6bb ro quiet splash
  Renderer: Software
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xwayland crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to bionic on 2018-02-23 (21 days ago)
  UserGroups:
   
  dmi.bios.date: 08/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C7CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J91204WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 300-11IBR
  dmi.modalias: 
dmi:bvnLENOVO:bvrC7CN31WW:bd08/05/2016:svnLENOVO:pn80M1:pvrLenovoYoga300-11IBR:rvnLENOVO:rnMini:rvrSDK0J91204WIN:cvnLENOVO:ct10:cvrLenovoYoga300-11IBR:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M1
  dmi.product.version: Lenovo Yoga 300-11IBR
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A

[Desktop-packages] [Bug 1756378] [NEW] Udisks2 flacky test (regression from 2.7)

2018-03-16 Thread Sebastien Bacher

Public bug reported:

One of the udisks2 tests has become flacky in the 2.7 update

ERROR: test_ext4 (__main__.FS)
fs: ext4
--
Traceback (most recent call last):
  File "src/tests/integration-test", line 680, in test_ext4
self._do_fs_check('ext4')
  File "src/tests/integration-test", line 841, in _do_fs_check
self._do_udisks_check(fs_type)
  File "src/tests/integration-test", line 1045, in _do_udisks_check
cd_fs.call_mount_sync(ro_options, None)
AttributeError: 'NoneType' object has no attribute 'call_mount_sync'

That needs to be resolved

** Affects: udisks2 (Ubuntu)
 Importance: High
 Assignee: Sebastien Bacher (seb128)
 Status: New

** Affects: udisks2 (Ubuntu Bionic)
 Importance: High
 Assignee: Sebastien Bacher (seb128)
 Status: New

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

** Changed in: udisks2 (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  Udisks2 flacky test (regression from 2.7)

Status in udisks2 package in Ubuntu:
  New
Status in udisks2 source package in Bionic:
  New

Bug description:
  One of the udisks2 tests has become flacky in the 2.7 update

  ERROR: test_ext4 (__main__.FS)
  fs: ext4
  --
  Traceback (most recent call last):
File "src/tests/integration-test", line 680, in test_ext4
  self._do_fs_check('ext4')
File "src/tests/integration-test", line 841, in _do_fs_check
  self._do_udisks_check(fs_type)
File "src/tests/integration-test", line 1045, in _do_udisks_check
  cd_fs.call_mount_sync(ro_options, None)
  AttributeError: 'NoneType' object has no attribute 'call_mount_sync'

  That needs to be resolved

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

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

[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling

2018-03-16 Thread Eduardo Silva

+1, using Ubuntu 18.04-beta here and it's not there.

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

Title:
  GNOME Shell should support fractional (non-integer) Hi-DPI scaling

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

Bug description:
  https://trello.com/c/r12LY9iA (for 17.04 was
  https://trello.com/c/TvwNvXOo)

  ---

  I'm using fully updated Ubuntu GNOME 17.04.

  In Ubuntu Gnome, you only allow for integer scaling of things for high
  DPI monitors. While in theory this sounds good, on a 27 inch 4k
  monitor like mine, restricting it to integers is a problem. 1x is
  annoyingly small, and 2x is WAY too big. You need a 1.5x, and
  presumably to just allow most noninteger values to future proof the
  distribution given 8k monitors and all sorts of new and weird things
  coming out, like windows 10 has.

  Photos of the two annoying sizes are available here (it won't let me
  attach two files):

  http://i.imgur.com/vWrvZxq.jpg
  http://i.imgur.com/11p19k7.jpg

  I apologize for my photography skills in advance., you'll have to look
  at the ruler for scale to see the problem. Please contact me if you
  need any more information etc.

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

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

[Desktop-packages] [Bug 1756372] [NEW] Merge 2.24.32-1 from Debian

2018-03-16 Thread Amr Ibrahim

Public bug reported:

Please merge gtk+2.0 (2.24.32-1) from Debian. It's a bug-fix release.

Overview of Changes from GTK+ 2.24.31 to 2.24.32


* Build:
 - Support Visual Studio 2017

* Bug fixes:
 136059 Ctrl-navigation works in opposite direction in right-to-left text
 165385 Win32 keyboard handling still incomplete
 358970 gtk_scale_set_digits does not cause value to be rounded if draw-value...
 468868 Popup of "appears-as-list" ComboBox does not change screen with its t...
 554057 Calling gtk_menu_shell_select_item() on GtkMenuBar can break grabs (a...
 569581 Using the US-Intl keyboard layout causes unexpected character combina...
 618160 Documentation for gtk_combo_box_get_active_iter is unclear
 658111 gtk_label_set_pattern() is reset by a call to gtk_box_pack_start()
 676550 Adding underlines to Label with gtk_label_set_pattern() does not work
 696624 Japanese (Korean/Chinese) XIM input mode indicator has not been worki...
 701296 gtkfixed accepts toplevel windows into its children list after gtk_wi...
 729651 Crash in GtkFileChooserButton with appears-as-list
 734946 Implement GContentType on OSX
 768722 Keyboard shortcuts for russian characters doesn't work
 769214 keyval field not filled correctly for Pause key
 772389 Appending a character to a GtkEntry control in overwrite mode rings t...
 772794 segfault when on unchecked XListInputDevices return value
 773587 recent-manager: Add a limit to the list's size
 776909 gtk_adjustment_clamp_page: Conditional jump or move depends on uninit...
 777683 SIGBUS due to gdk_x11_window_set_opacity
 778542 Use UTF-8 encoding for tooltips on files in the "recently used" list
 778811 Enter submenus when activating their parent item
 779009 Missing property-change::accessible-description events when the toolt...
 779081 GtkTextView: expose API to get Pango line direction
 779605 GLib-CRITICAL Source ID xxx was not found when attempting to remove it
 781020 GIMP UI vector icons are drawn way too small
 781605 GtkVolumeButton limited to 10 values
 785165 Set translation domain for parameter_string in gtk_init_with_args
 785672 Entry: Setting icon tooltip to empty disables tooltip on whole widget
 786771 Critical about mismatched GdkDisplays when opening Inspector combobox
 787158 gtk_widget_get_preferred_width on GtkToolbar gives wrong minimum width
 787195 gtk_toolbar_set_show_arrow does not show an arrow
 787410 entry: fix memory leak
 788577 Global -GtkComboBox-appears-as-list breaks opening menu-mode CBs by k...

* Translation updates:
 Hungarian
 Indonesian
 Polish


gtk+2.0 (2.24.32-1) unstable; urgency=medium

  * New upstream release
  * debian/libgtk2.0-0.symbols: Add symbols
  * Update Vcs fields for migration to https://salsa.debian.org/
  * Drop patches applied in new release:
- 0001-Don-t-use-guint32-with-XChangeProperty.patch
- 0002-GtkMenuShell-always-activate-menu-shells.patch

 -- Jeremy Bicha   Sat, 20 Jan 2018 07:46:38 -0500

gtk+2.0 (2.24.31-5) unstable; urgency=medium

  * Update Vcs fields for conversion to git
  * Add debian/gbp.conf
  * Bump Standards-Version to 4.1.2

 -- Jeremy Bicha   Thu, 21 Dec 2017 14:05:20 -0500

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Merge 2.24.32-1 from Debian

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Please merge gtk+2.0 (2.24.32-1) from Debian. It's a bug-fix release.

  Overview of Changes from GTK+ 2.24.31 to 2.24.32
  

  * Build:
   - Support Visual Studio 2017

  * Bug fixes:
   136059 Ctrl-navigation works in opposite direction in right-to-left text
   165385 Win32 keyboard handling still incomplete
   358970 gtk_scale_set_digits does not cause value to be rounded if 
draw-value...
   468868 Popup of "appears-as-list" ComboBox does not change screen with its 
t...
   554057 Calling gtk_menu_shell_select_item() on GtkMenuBar can break grabs 
(a...
   569581 Using the US-Intl keyboard layout causes unexpected character 
combina...
   618160 Documentation for gtk_combo_box_get_active_iter is unclear
   658111 gtk_label_set_pattern() is reset by a call to gtk_box_pack_start()
   676550 Adding underlines to Label with gtk_label_set_pattern() does not work
   696624 Japanese (Korean/Chinese) XIM input mode indicator has not been 
worki...
   701296 gtkfixed accepts toplevel windows into its children list after 
gtk_wi...
   729651 Crash in GtkFileChooserButton with appears-as-list
   734946 Implement GContentType on OSX
   768722 Keyboard shortcuts for russian characters doesn't work
   769214 keyval field not filled correctly for Pause key
   772389 Appending a character to a GtkEntry

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  no specific action appeared to trier the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.27.92-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 16 15:09:32 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-03-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x5592d4fc05f1:mov0x90(%rbp),%rsi
   PC (0x5592d4fc05f1) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1756369] [NEW] Google Calendar is not syncing in Ubuntu 18.04 Beta.

2018-03-16 Thread Jean-Francois Bourdeau

Public bug reported:

My google Calendar is not syncing using Ubuntu 18.04 Beta
I can add my gmail account to Ubuntu
But when opening the Calendar, I don't my Google Calendar info.
If I click sync manualy, neither

Had no problems with 17.10

JF

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.27.90-1build1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri Mar 16 11:38:11 2018
InstallationDate: Installed on 2018-03-11 (4 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Google Calendar is not syncing in Ubuntu 18.04 Beta.

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  My google Calendar is not syncing using Ubuntu 18.04 Beta
  I can add my gmail account to Ubuntu
  But when opening the Calendar, I don't my Google Calendar info.
  If I click sync manualy, neither

  Had no problems with 17.10

  JF

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.27.90-1build1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Mar 16 11:38:11 2018
  InstallationDate: Installed on 2018-03-11 (4 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180311)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

2018-03-16 Thread Pioterus

Almost year old bug still there. This is core functionality of any OS
(secure VPNs, DNS) which just does not work on Ubuntu. I don't know how
about other distros but I doubt that Ubuntu can claim to be the desktop
system with such a bug.

I can confirm that the simplest workaround is comment out dnsmasq in 
NetworkManager config (ubuntu 16.04). But there are drawbacks of course so this 
makes the system less secure/reliable  in some situations. And of course it 
took me about 5 hours to figure out what is going on. Those hours could be 
spend more productive.
P.

-- 
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 1755106] Re: /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/ fails to load

2018-03-16 Thread Péter Prőhle

No I had a possibility to check the situation for the question:

Do you have an active "gsd-media-keys" process when getting the issue?

I have the /usr/lib/gnome-settings-daemon/gsd-media-keys ELV binary, but
I do NOT see in the linting of "ps auxw", and even the output of "ps
acuwx | fgrep gsd" is empty.

Interestingly the output of "journalctl | grep gsd-media-keys" remained
exactly the same, as 3 days before, no new entry.

But none of the two user defined shortcuts work, while all the usual
system default shortcuts work.

I welcome further test suggestions in order to be prepared if next time
the issue appears.

One thing is interesting, that just after updating to 18.04, the
frequency of the issue became high for a few days, and as soon as I
submitted this issue, I had to wait 3 days (4 booting) in order to get
the issue again.

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

Title:
  /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  fails to load

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  $ dconf dump /org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/
  [custom1]
  binding='BackSpace'
  command='gnome-session-quit --power-off'
  name='gnome-session-quit --power-off'

  [custom0]
  binding='g'
  command='gnome-terminal --geometry=80x99-0+0'
  name='gnome-terminal --geometry=80x99-0+0'
  $

  In spite of the above, time to time, not always, but since 18.04 much
  much more frequently this settings fails to become active just after
  booting, ... my account is logged in automatically just after boot.

  If I log out and log in again, then these key bindings work.

  If I go to the system settings, and define again, then these work
  again.

  Earlier, before 18.04 this phenomenon was rare, namely once a week at
  most.

  But since 18.04 it is almost guaranteed, not deterministic, but highly
  probable, that after an initial boot or a warm reboot these key
  bindings will not work.

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

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

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The crash message appears shortly each time within a couple of minutes
  after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 16 14:37:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1755232] Re: Xorg crashes when tapping Unity system tray icons

2018-03-16 Thread Jean-Noël AVILA

Maybe something similar to what I experience. See
https://bugs.freedesktop.org/show_bug.cgi?id=105557

** Bug watch added: freedesktop.org Bugzilla #105557
   https://bugs.freedesktop.org/show_bug.cgi?id=105557

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

Title:
  Xorg crashes when tapping Unity system tray icons

Status in xorg package in Ubuntu:
  New

Bug description:
  This bug requires some prerequisites to reproduce:

  0. Make sure you've got multitouch-enable display
  1. Start Unity+xorg session
  2. Verify that four-finger tap gesture works (shows unity app search tool)
  3. Wait some time for this gesture to stop working - this is another bug, not 
necessarily xorg one,  already known and thought to be connected with Google 
Chrome running.
  4. Once it stops working, quickly tap all icons in the Unity system tray like 
you would be pretending to play a piano (tapping them individually or slowly 
does not cause any problems).
  5. Xorg crashes immediately.

  This scenario is 100% reproducible on my setup.

  I recompiled xorg with debug info enabled and got this nice trace:

  
  [ 22705.385] (EE) 
  [ 22705.385] (EE) Backtrace: 
  [ 22705.385] (EE) 0: /usr/lib/xorg/Xorg (OsSigHandler+0x3b) [0x562a36b6f25f]  
   
  [ 22705.387] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (__restore_rt+0x0) 
[0x7f382f64414f]   
  [ 22705.389] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7f382f2880bb] 
  [ 22705.391] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x16d) 
[0x7f382f289f5d]  
  [ 22705.393] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__fsetlocking+0x2fd) 
[0x7f382f2d22bd]  
  [ 22705.395] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0xa3a) 
[0x7f382f2d9f7a]
  [ 22705.397] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (_IO_str_seekoff+0x2b2e) 
[0x7f382f2de0fe]   
  [ 22705.399] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (cfree+0x6e) 
[0x7f382f2e044e]   
  [ 22705.400] (EE) 8: /usr/lib/xorg/Xorg (FreeGrab+0xb8) [0x562a3699ac32]
  [ 22705.400] (EE) 9: /usr/lib/xorg/Xorg (DeactivatePointerGrab+0x279) 
[0x562a3698428f]   
  [ 22705.400] (EE) 10: /usr/lib/xorg/Xorg (DeleteWindowFromAnyEvents+0x70) 
[0x562a3698ea8b]   
  [ 22705.401] (EE) 11: /usr/lib/xorg/Xorg (UnrealizeTree+0x100) 
[0x562a369bc371]  
  [ 22705.401] (EE) 12: /usr/lib/xorg/Xorg (UnmapWindow+0x195) [0x562a369bc689] 
   
  [ 22705.402] (EE) 13: /usr/lib/xorg/Xorg (ProcUnmapWindow+0x74) 
[0x562a3696e488] 
  [ 22705.402] (EE) 14: /usr/lib/xorg/Xorg (Dispatch+0x21e) [0x562a3696d2d9]
  [ 22705.402] (EE) 15: /usr/lib/xorg/Xorg (dix_main+0x651) [0x562a3697c4e3]
   
  [ 22705.403] (EE) 16: /usr/lib/xorg/Xorg (main+0x28) [0x562a3695cf22] 
   
  [ 22705.405] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7f382f2721c1]  
  [ 22705.405] (EE) 18: /usr/lib/xorg/Xorg (_start+0x2a) [0x562a3695ce1a]   
   
  [ 22705.407] (EE) 19: ? (?+0x2a) [0x2a] 


  Looks like FreeGrab tries to free pGrab for the second time (some
  multithreading issue?)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 12 17:03:34 2018
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:2245]
  InstallationDate: Installed on 2017-09-01 (192 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 20HES2130Q
  ProcEnviron:
   LANGUAGE=pl_PL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi.ec_freeze_events=Y 
acpi.ec_suspend_yield=Y intel_pstate=skylake_hwp i915.enable_guc_loading=1 
i915.enable_guc_submission=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to artful on 2018-02-11 (29 days ago)
  dmi.bios.date: 05/23/2017
  dmi.bios.vendor:

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Got that crash after closing chromium and doing a cold reboot.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 16 15:03:14 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1756347] [NEW] [3.28] gnome-shell crashed with signal 5 in g_log_default_handler()

2018-03-16 Thread dino99

Public bug reported:

Got that crash after closing chromium and doing a cold reboot.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Mar 16 15:03:14 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Summary changed:

- gnome-shell crashed with signal 5 in g_log_default_handler()
+ [3.28] gnome-shell crashed with signal 5 in g_log_default_handler()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Got that crash after closing chromium and doing a cold reboot.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 16 15:03:14 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Error message is popping up

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Mar 15 14:41:07 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-06 (161 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180223)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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