[Desktop-packages] [Bug 1716633] Re: Installed, popular and featured snaps are loaded in parallel threads can crash

2017-11-30 Thread Jean-Baptiste Lallement
Marking as verification-done per Robert's comment. Also I cannot
reproduce the crash and there is no other occurrence of it.

** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

Title:
  Installed, popular and featured snaps are loaded in parallel threads
  can crash

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  GNOME Software has a cache that can be accessed by multiple threads. This can 
cause GNOME Software to crash. This seems to have been caused by adding support 
for featured snaps (bug 1663097) as the popular, featured and installed snaps 
are all requested on different threads.

  [Test Case]
  Since this is a random crash there's not a good test case. Could be checked 
by looking at errors.ubuntu.com crash reports or repeated restarts of GNOME 
Software to see if it crashes on startup.

  [Regression Potential]
  Solution is to add a lock around this cache. Some risk of breaking related 
code.

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

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


[Desktop-packages] [Bug 1735666] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2017-11-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  This popped up out of the blue.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Thu Nov 23 10:10:49 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-tBrFZ4/52-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2012-03-23 (2078 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735666] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

2017-11-30 Thread Vadim Peretokin
Public bug reported:

This popped up out of the blue.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Thu Nov 23 10:10:49 2017
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-tBrFZ4/52-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2012-03-23 (2078 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful package-conflict

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  This popped up out of the blue.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Thu Nov 23 10:10:49 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-tBrFZ4/52-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2012-03-23 (2078 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735662] ThreadStacktrace.txt

2017-11-30 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1735662/+attachment/5016867/+files/ThreadStacktrace.txt

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

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Bug description:
  after login...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Dec  1 10:20:08 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-02 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x562609051183 :
jmpq   *0xc0(%rax)
   PC (0x562609051183) ok
   source "*0xc0(%rax)" ok
   SP (0x7fff345b7df8) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   net_device_simple_get_speed ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
net_device_simple_get_speed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1735662] Stacktrace.txt

2017-11-30 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1735662/+attachment/5016865/+files/Stacktrace.txt

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

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

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

Bug description:
  after login...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Dec  1 10:20:08 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-02 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x562609051183 :
jmpq   *0xc0(%rax)
   PC (0x562609051183) ok
   source "*0xc0(%rax)" ok
   SP (0x7fff345b7df8) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   net_device_simple_get_speed ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
net_device_simple_get_speed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1735662] StacktraceSource.txt

2017-11-30 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1735662/+attachment/5016866/+files/StacktraceSource.txt

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

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

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

Bug description:
  after login...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Dec  1 10:20:08 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-02 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x562609051183 :
jmpq   *0xc0(%rax)
   PC (0x562609051183) ok
   source "*0xc0(%rax)" ok
   SP (0x7fff345b7df8) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   net_device_simple_get_speed ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
net_device_simple_get_speed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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


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

2017-11-30 Thread Sosha
** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1735662

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

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

Bug description:
  after login...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Dec  1 10:20:08 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-02 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x562609051183 :
jmpq   *0xc0(%rax)
   PC (0x562609051183) ok
   source "*0xc0(%rax)" ok
   SP (0x7fff345b7df8) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   net_device_simple_get_speed ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
net_device_simple_get_speed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1735662] gnome-control-center crashed with SIGSEGV in net_device_simple_get_speed()

2017-11-30 Thread Apport retracing service
StacktraceTop:
 net_device_simple_get_speed (device_simple=0x56260b432950) at 
net-device-simple.c:253
 device_ethernet_refresh_ui (device=0x56260b432950) at net-device-ethernet.c:222
 g_closure_invoke (closure=0x56260b461220, return_value=0x0, n_param_values=2, 
param_values=0x7fff345b8060, invocation_hint=0x7fff345b7fe0) at 
../../../../gobject/gclosure.c:804
 signal_emit_unlocked_R (node=node@entry=0x56260b09e000, detail=detail@entry=0, 
instance=instance@entry=0x56260b1e1260, 
emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fff345b8060) at 
../../../../gobject/gsignal.c:3635
 g_signal_emit_valist (instance=0x56260b1e1260, signal_id=, 
detail=0, var_args=var_args@entry=0x7fff345b8230) at 
../../../../gobject/gsignal.c:3391

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

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

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

Bug description:
  after login...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Dec  1 10:20:08 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-02 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center network
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x562609051183 :
jmpq   *0xc0(%rax)
   PC (0x562609051183) ok
   source "*0xc0(%rax)" ok
   SP (0x7fff345b7df8) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   net_device_simple_get_speed ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in 
net_device_simple_get_speed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

2017-11-30 Thread Nick Smolinske
False alarm! The problem just happened again. Froze while downloading
the google chrome installer.

It does seem like the vm.dirty modifications definitely helped. But it
could have been coincidence. At least it didn't freeze during the
updater and ruin my filesystem this time.

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hi

  While copying many and large files to and from a USB drive, the system
  becomes incredibly slow and sometimes hangs. I watched the system
  monitor while it was running slowly but cpu was not above 50% at any
  time, the same for memory.

  I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD"
  laptop.

  Description:  Ubuntu 13.04
  Release:  13.04

  nautilus:
Installed: 1:3.6.3-0ubuntu16
Candidate: 1:3.6.3-0ubuntu16
Version table:
   *** 1:3.6.3-0ubuntu16 0
  500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:
  1) Aquire many large files (like your totally legit moviecollection)
  2) Copy files to external HD
  3) Open your browser and be sad when your system becomes incredibly slow 
after a few minutes


  This is my first bugreport so if I'm missing something, please tell
  me.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Aug  6 22:56:34 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-05-31 (67 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

2017-11-30 Thread Nick Smolinske
Same issue here on a new 16.04 install on a new HP laptop. SSD. It was
crashing randomly during the install, then when I got it installed it
crashed every time I tried to run the updater.

Setting the vm.dirty_ratio and vm.dirty_background_ratio to 10 and 5
worked for me as well  so far.

I did notice one interesting thing, which I feel might help diagnose
what's going on behind the scenes. When I was having the problem, the
CPU temp would get pretty high (up to 70 C) and the fan on the laptop
was running very loudly. These symptoms happened every time. The mouse
became slower, and slower, and unresponsive. Ctrl-Alt-F1 and other
keyboard shortcuts were unresponsive as well.

After changing those vm values, I was able to go through the updater
with no issue. And my CPU temp was about 10 C lower, hovering around 60
during the updater. The cooling fan did not go on high either. So
somehow the higher vm.dirty values are creating a situation where the
CPU is working much harder than it needs to for the job it's trying to
do.

I don't know nearly enough about the inner workings of linux to know
what this means, but my instincts tell me it might be an important clue
for anyone trying to fix this bug. Hopefully it helps.

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hi

  While copying many and large files to and from a USB drive, the system
  becomes incredibly slow and sometimes hangs. I watched the system
  monitor while it was running slowly but cpu was not above 50% at any
  time, the same for memory.

  I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD"
  laptop.

  Description:  Ubuntu 13.04
  Release:  13.04

  nautilus:
Installed: 1:3.6.3-0ubuntu16
Candidate: 1:3.6.3-0ubuntu16
Version table:
   *** 1:3.6.3-0ubuntu16 0
  500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  Steps to reproduce:
  1) Aquire many large files (like your totally legit moviecollection)
  2) Copy files to external HD
  3) Open your browser and be sad when your system becomes incredibly slow 
after a few minutes


  This is my first bugreport so if I'm missing something, please tell
  me.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  Date: Tue Aug  6 22:56:34 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2013-05-31 (67 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735649] [NEW] not sure

2017-11-30 Thread Kenneth Wright
Public bug reported:

seriously I've no idea

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Dec  1 00:13:04 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1094]
InstallationDate: Installed on 2017-03-19 (257 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:57f3 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 
root=UUID=80176af4-8ce5-4fc0-8f62-7b7cbba90c42 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd04/26/2016:svnAcer:pnAspireE5-575:pvrV1.04:rvnAcer:rnIronman_SK:rvrV1.04:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E5-575
dmi.product.version: V1.04
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Nov 30 21:46:06 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  not sure

Status in xorg package in Ubuntu:
  New

Bug description:
  seriously I've no idea

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec  1 00:13:04 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake Integrated Graphics [1025:1094]
  InstallationDate: Installed on 2017-03-19 (257 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57f3 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-575
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic 

[Desktop-packages] [Bug 1038578] Re: vlc crash

2017-11-30 Thread Launchpad Bug Tracker
[Expired for libproxy (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  vlc crash

Status in libproxy package in Ubuntu:
  Expired
Status in vlc package in Ubuntu:
  Expired

Bug description:
  1

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.3-1
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu8
  Architecture: i386
  Date: Sun Aug 19 08:05:28 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
  ProcCmdline: /usr/bin/vlc file://[...]/video.avi
  Signal: 6
  SourcePackage: vlc
  UpgradeStatus: Upgraded to quantal on 2012-07-30 (20 days ago)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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

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


[Desktop-packages] [Bug 1038578] Re: vlc crash

2017-11-30 Thread Launchpad Bug Tracker
[Expired for vlc (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  vlc crash

Status in libproxy package in Ubuntu:
  Expired
Status in vlc package in Ubuntu:
  Expired

Bug description:
  1

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: vlc-nox 2.0.3-1
  ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
  Uname: Linux 3.5.0-6-generic i686
  ApportVersion: 2.4-0ubuntu8
  Architecture: i386
  Date: Sun Aug 19 08:05:28 2012
  ExecutablePath: /usr/bin/vlc
  InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
  ProcCmdline: /usr/bin/vlc file://[...]/video.avi
  Signal: 6
  SourcePackage: vlc
  UpgradeStatus: Upgraded to quantal on 2012-07-30 (20 days ago)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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

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


[Desktop-packages] [Bug 911591] Re: gnome-shell crashes when resizing OpenGL window

2017-11-30 Thread James Cuzella
At first glance, bug may be related to this upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=768204

** Bug watch added: GNOME Bug Tracker #768204
   https://bugzilla.gnome.org/show_bug.cgi?id=768204

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

Title:
  gnome-shell crashes when resizing OpenGL window

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a couple of applications that I wrote myself. They are OpenGL
  graphics applications. One application uses SDL for OpenGL context
  management, and the other uses GLFW.

  When I resize the windows of these applications by dragging the window
  edges, gnome-shell crashes almost 100 % of the time after a certain
  amount of resizing back and forth. This does not happen when instantly
  resizing the window (e.g. with Alt+F10, which effectively does a
  resize as far as SDL and GLFW are concerned anyway).

  Rapidly resizing the window of glxgears does not seem to crash gnome-
  shell, which confuses me. I guess it is interacting with things
  differently or something.

  Anyways, I'm using the following versions of involved software
  packages:

  gnome-shell: 3.2.1-0ubuntu1.1
  nvidia-current: 290.10-0ubuntu1~oneiric~xup1 (from the ubuntu-x-swat PPA)
  SDL: 1.2.14-6.1ubuntu4
  GLFW: 2.7.2-1

  I'm thinking that maybe the two libraries I use (SDL and GLFW) create
  new OpenGL contexts every time when using their respective resizing
  mechanisms, whereas glxgears does something different, and requesting
  new contexts with new sizes too often during a small period of time
  might not go too well? Not sure at all what details I can provide
  regarding this problem. Hopefully someone can ask the right questions
  and I will be able to provide the necessary information.

  I will be very lucky if the applications were started from a terminal.
  That way the undecorated window of the terminal has focus after the
  crash, and I can relaunch gnome-shell from there.

  Any help is appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-shell 3.2.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Wed Jan  4 04:19:48 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  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/911591/+subscriptions

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


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

2017-11-30 Thread James Cuzella
I've added more details for the crash I am seeing in this bug:

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591

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

Title:
  gnome-shell crashes often

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

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


[Desktop-packages] [Bug 911591] Re: gnome-shell crashes when resizing OpenGL window

2017-11-30 Thread James Cuzella
Adding journalctl logs for gnome-shell crash.  After segfault line,
gnome-shell crashes and I'm returned to gdm login screen.  Once I login,
everything works again until next crash, usually caused by OpenGL window
resizing or xrandr resolution changes.

** Attachment added: "gnome-shell-crash.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+attachment/5016779/+files/gnome-shell-crash.log

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

Title:
  gnome-shell crashes when resizing OpenGL window

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a couple of applications that I wrote myself. They are OpenGL
  graphics applications. One application uses SDL for OpenGL context
  management, and the other uses GLFW.

  When I resize the windows of these applications by dragging the window
  edges, gnome-shell crashes almost 100 % of the time after a certain
  amount of resizing back and forth. This does not happen when instantly
  resizing the window (e.g. with Alt+F10, which effectively does a
  resize as far as SDL and GLFW are concerned anyway).

  Rapidly resizing the window of glxgears does not seem to crash gnome-
  shell, which confuses me. I guess it is interacting with things
  differently or something.

  Anyways, I'm using the following versions of involved software
  packages:

  gnome-shell: 3.2.1-0ubuntu1.1
  nvidia-current: 290.10-0ubuntu1~oneiric~xup1 (from the ubuntu-x-swat PPA)
  SDL: 1.2.14-6.1ubuntu4
  GLFW: 2.7.2-1

  I'm thinking that maybe the two libraries I use (SDL and GLFW) create
  new OpenGL contexts every time when using their respective resizing
  mechanisms, whereas glxgears does something different, and requesting
  new contexts with new sizes too often during a small period of time
  might not go too well? Not sure at all what details I can provide
  regarding this problem. Hopefully someone can ask the right questions
  and I will be able to provide the necessary information.

  I will be very lucky if the applications were started from a terminal.
  That way the undecorated window of the terminal has focus after the
  crash, and I can relaunch gnome-shell from there.

  Any help is appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-shell 3.2.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Wed Jan  4 04:19:48 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  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/911591/+subscriptions

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


[Desktop-packages] [Bug 911591] Re: gnome-shell crashes when resizing OpenGL window

2017-11-30 Thread James Cuzella
Bug seems to be reported also elsewhere:

- ArchLinux: https://bbs.archlinux.org/viewtopic.php?id=231158
- RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1250128

The RHEL bug report mentions that they have Xorg configured without
RandR support.  I do see a message in my logs that says gdm has RandR
disabled for some reason:

Nov 30 15:25:53 saturn /usr/lib/gdm3/gdm-x-session[3918]: (--) RandR
disabled

I'm not sure why gdm wants to run with it disabled.  I don't seem to
have a /etc/X11/xorg.conf file anymore... it's been quite some time
since I've even had to edit Xorg config in recent Ubuntu versions. Seems
like all this is managed by gdm-x-session now?


** Bug watch added: Red Hat Bugzilla #1250128
   https://bugzilla.redhat.com/show_bug.cgi?id=1250128

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

Title:
  gnome-shell crashes when resizing OpenGL window

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a couple of applications that I wrote myself. They are OpenGL
  graphics applications. One application uses SDL for OpenGL context
  management, and the other uses GLFW.

  When I resize the windows of these applications by dragging the window
  edges, gnome-shell crashes almost 100 % of the time after a certain
  amount of resizing back and forth. This does not happen when instantly
  resizing the window (e.g. with Alt+F10, which effectively does a
  resize as far as SDL and GLFW are concerned anyway).

  Rapidly resizing the window of glxgears does not seem to crash gnome-
  shell, which confuses me. I guess it is interacting with things
  differently or something.

  Anyways, I'm using the following versions of involved software
  packages:

  gnome-shell: 3.2.1-0ubuntu1.1
  nvidia-current: 290.10-0ubuntu1~oneiric~xup1 (from the ubuntu-x-swat PPA)
  SDL: 1.2.14-6.1ubuntu4
  GLFW: 2.7.2-1

  I'm thinking that maybe the two libraries I use (SDL and GLFW) create
  new OpenGL contexts every time when using their respective resizing
  mechanisms, whereas glxgears does something different, and requesting
  new contexts with new sizes too often during a small period of time
  might not go too well? Not sure at all what details I can provide
  regarding this problem. Hopefully someone can ask the right questions
  and I will be able to provide the necessary information.

  I will be very lucky if the applications were started from a terminal.
  That way the undecorated window of the terminal has focus after the
  crash, and I can relaunch gnome-shell from there.

  Any help is appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-shell 3.2.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Wed Jan  4 04:19:48 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  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/911591/+subscriptions

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


[Desktop-packages] [Bug 1704870] Re: Keys can't be grabbed under Wayland

2017-11-30 Thread Bug Watch Updater
** Bug watch added: Red Hat Bugzilla #1479682
   https://bugzilla.redhat.com/show_bug.cgi?id=1479682

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

Title:
  Keys can't be grabbed under Wayland

Status in remmina:
  New
Status in wayland:
  Confirmed
Status in remmina package in Ubuntu:
  Confirmed
Status in wayland package in Fedora:
  Confirmed

Bug description:
  Special keys are not working under Remmina.

  Seems to be a Wayland specification and implementation of that
  specification.

  This bug could embrace all apps that need this behavior (VirtualBox,
  vncviewer, etc)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: remmina 1.1.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 15:36:36 2017
  InstallationDate: Installed on 2017-07-04 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1704870]

2017-11-30 Thread Rubén
It works for me after upgrading to Fedora 27 (gnome-boxes)

Thanks very much.

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

Title:
  Keys can't be grabbed under Wayland

Status in remmina:
  New
Status in wayland:
  Confirmed
Status in remmina package in Ubuntu:
  Confirmed
Status in wayland package in Fedora:
  Confirmed

Bug description:
  Special keys are not working under Remmina.

  Seems to be a Wayland specification and implementation of that
  specification.

  This bug could embrace all apps that need this behavior (VirtualBox,
  vncviewer, etc)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: remmina 1.1.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 15:36:36 2017
  InstallationDate: Installed on 2017-07-04 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1704870]

2017-11-30 Thread Christophe
(In reply to Matěj Cepl from comment #29)
> I wonder whether it is the same bug, but I don’t have ANY keys inside of the
> VM machine when virt-manager runs under Xsession. Is it?

Could it be https://bugzilla.redhat.com/show_bug.cgi?id=1479682 ?

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

Title:
  Keys can't be grabbed under Wayland

Status in remmina:
  New
Status in wayland:
  Confirmed
Status in remmina package in Ubuntu:
  Confirmed
Status in wayland package in Fedora:
  Confirmed

Bug description:
  Special keys are not working under Remmina.

  Seems to be a Wayland specification and implementation of that
  specification.

  This bug could embrace all apps that need this behavior (VirtualBox,
  vncviewer, etc)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: remmina 1.1.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 15:36:36 2017
  InstallationDate: Installed on 2017-07-04 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1704870]

2017-11-30 Thread Matěj
I wonder whether it is the same bug, but I don’t have ANY keys inside of
the VM machine when virt-manager runs under Xsession. Is it?

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

Title:
  Keys can't be grabbed under Wayland

Status in remmina:
  New
Status in wayland:
  Confirmed
Status in remmina package in Ubuntu:
  Confirmed
Status in wayland package in Fedora:
  Confirmed

Bug description:
  Special keys are not working under Remmina.

  Seems to be a Wayland specification and implementation of that
  specification.

  This bug could embrace all apps that need this behavior (VirtualBox,
  vncviewer, etc)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: remmina 1.1.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 15:36:36 2017
  InstallationDate: Installed on 2017-07-04 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1704870]

2017-11-30 Thread Olivier
(In reply to Christophe Fergeau from comment #30)
> (In reply to Matěj Cepl from comment #29)
> > I wonder whether it is the same bug, but I don’t have ANY keys inside of the
> > VM machine when virt-manager runs under Xsession. Is it?
> 
> Could it be https://bugzilla.redhat.com/show_bug.cgi?id=1479682 ?

If this affects virt-manager under a plain X session (as comment 30
states), then it's completely unrelated to either bugs (i.e. neither
Wayland nor Xwayland).

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

Title:
  Keys can't be grabbed under Wayland

Status in remmina:
  New
Status in wayland:
  Confirmed
Status in remmina package in Ubuntu:
  Confirmed
Status in wayland package in Fedora:
  Confirmed

Bug description:
  Special keys are not working under Remmina.

  Seems to be a Wayland specification and implementation of that
  specification.

  This bug could embrace all apps that need this behavior (VirtualBox,
  vncviewer, etc)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: remmina 1.1.2-4ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 17 15:36:36 2017
  InstallationDate: Installed on 2017-07-04 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  SourcePackage: remmina
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 911591] Re: gnome-shell crashes when resizing OpenGL window

2017-11-30 Thread James Cuzella
As original reporter stated, it usually appears related to OpenGL window
resize events.  I have also noted that xrandr display resolution changes
can trigger the crash.

I see errors in dmesg that mention libmutter:

[15040.472843] gnome-shell[32127]: segfault at 8 ip 7f327f29d5d0 sp
7ffeccf94a38 error 4 in libmutter-1.so.0.0.0[7f327f243000+142000]

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

Title:
  gnome-shell crashes when resizing OpenGL window

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a couple of applications that I wrote myself. They are OpenGL
  graphics applications. One application uses SDL for OpenGL context
  management, and the other uses GLFW.

  When I resize the windows of these applications by dragging the window
  edges, gnome-shell crashes almost 100 % of the time after a certain
  amount of resizing back and forth. This does not happen when instantly
  resizing the window (e.g. with Alt+F10, which effectively does a
  resize as far as SDL and GLFW are concerned anyway).

  Rapidly resizing the window of glxgears does not seem to crash gnome-
  shell, which confuses me. I guess it is interacting with things
  differently or something.

  Anyways, I'm using the following versions of involved software
  packages:

  gnome-shell: 3.2.1-0ubuntu1.1
  nvidia-current: 290.10-0ubuntu1~oneiric~xup1 (from the ubuntu-x-swat PPA)
  SDL: 1.2.14-6.1ubuntu4
  GLFW: 2.7.2-1

  I'm thinking that maybe the two libraries I use (SDL and GLFW) create
  new OpenGL contexts every time when using their respective resizing
  mechanisms, whereas glxgears does something different, and requesting
  new contexts with new sizes too often during a small period of time
  might not go too well? Not sure at all what details I can provide
  regarding this problem. Hopefully someone can ask the right questions
  and I will be able to provide the necessary information.

  I will be very lucky if the applications were started from a terminal.
  That way the undecorated window of the terminal has focus after the
  crash, and I can relaunch gnome-shell from there.

  Any help is appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-shell 3.2.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Wed Jan  4 04:19:48 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  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/911591/+subscriptions

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


[Desktop-packages] [Bug 17752] Re: "Select all" doesn't really select all

2017-11-30 Thread Bug Watch Updater
** Changed in: evolution
   Status: Confirmed => Fix Released

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

Title:
  "Select all" doesn't really select all

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  While using the threaded view, if you collapse a few entries and then choose
  "select all", the hidden entries aren't selected, but choosing "select thread"
  does select even hidden entries from the thread.  This seems inconsistant.  
(I'd
  personally prefer hidden entries also get selected.)

  http://bugzilla.gnome.org/show_bug.cgi?id=306671:
  http://bugzilla.gnome.org/show_bug.cgi?id=306671

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

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


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

2017-11-30 Thread James Cuzella
I am seeing gnome-shell crashes also.  However, it usually appears
related to OpenGL window resize events as well as xrandr display
resolution changes.

Errors in dmesg mention libmutter:

[15040.472843] gnome-shell[32127]: segfault at 8 ip 7f327f29d5d0 sp
7ffeccf94a38 error 4 in libmutter-1.so.0.0.0[7f327f243000+142000]

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

Title:
  gnome-shell crashes often

Status in gnome-shell package in Ubuntu:
  Confirmed

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

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

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

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

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

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


[Desktop-packages] [Bug 911591] Re: gnome-shell crashes when resizing OpenGL window

2017-11-30 Thread James Cuzella
I can confirm this bug is still happening on:

Ubuntu 17.10 (Artful Aardvark)
gnome-shell 3.26.1-0ubuntu5

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

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

Title:
  gnome-shell crashes when resizing OpenGL window

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I have a couple of applications that I wrote myself. They are OpenGL
  graphics applications. One application uses SDL for OpenGL context
  management, and the other uses GLFW.

  When I resize the windows of these applications by dragging the window
  edges, gnome-shell crashes almost 100 % of the time after a certain
  amount of resizing back and forth. This does not happen when instantly
  resizing the window (e.g. with Alt+F10, which effectively does a
  resize as far as SDL and GLFW are concerned anyway).

  Rapidly resizing the window of glxgears does not seem to crash gnome-
  shell, which confuses me. I guess it is interacting with things
  differently or something.

  Anyways, I'm using the following versions of involved software
  packages:

  gnome-shell: 3.2.1-0ubuntu1.1
  nvidia-current: 290.10-0ubuntu1~oneiric~xup1 (from the ubuntu-x-swat PPA)
  SDL: 1.2.14-6.1ubuntu4
  GLFW: 2.7.2-1

  I'm thinking that maybe the two libraries I use (SDL and GLFW) create
  new OpenGL contexts every time when using their respective resizing
  mechanisms, whereas glxgears does something different, and requesting
  new contexts with new sizes too often during a small period of time
  might not go too well? Not sure at all what details I can provide
  regarding this problem. Hopefully someone can ask the right questions
  and I will be able to provide the necessary information.

  I will be very lucky if the applications were started from a terminal.
  That way the undecorated window of the terminal has focus after the
  crash, and I can relaunch gnome-shell from there.

  Any help is appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-shell 3.2.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Wed Jan  4 04:19:48 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  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/911591/+subscriptions

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


[Desktop-packages] [Bug 1612226] Re: Calc EDITING - Selecting a Range pressing enter and dragging Closes App

2017-11-30 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Unknown => Confirmed

** Changed in: df-libreoffice
   Importance: Unknown => Critical

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

Title:
  Calc EDITING - Selecting a Range pressing enter and dragging Closes
  App

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Using the 5.2 Snap Release under Ubuntu OS when selecting a range of Cells By 
Highlighting and Pressing Enter Then trying to move then by dragging closes the 
app. This does not happen in my 5.1 install. Have attached the stdout when 
starting the app from the command line (not sure this is of any use?)
  (from https://bugs.documentfoundation.org/show_bug.cgi?id=101377)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1612226/+subscriptions

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


[Desktop-packages] [Bug 1728467] Re: All files on ntfs partitions are marked executable

2017-11-30 Thread Doug McMahon
If the intention of the changes was to make all files executable then
that was a poor decision (it does not appear that was the focus of the
whatsoever...

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

Title:
  All files on ntfs partitions are marked executable

Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  This did not happen in 14.04 but somewhere since then udisks2 sets any & all 
files on ntfs partitions as executable.
  Additionally if file is copied over to user's ext4 partion the bit remains 
set.
  Can't see why this would be intentional??

  In 14.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077", 
"fmask=0177", NULL };

  In 16.04, 17.04, 17.10,18.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Sun Oct 29 21:20:19 2017
  InstallationDate: Installed on 2017-09-16 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1735324] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

2017-11-30 Thread Emily Ratliff
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

** Information type changed from Private Security to Public

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  SIGSEGV signal caught! Sorry, you have found a bug in LyX, hope you
  have not lost any data. Please read the bug-reporting instructions in
  'Help->Introduction' and send us a bug report, if necessary. Thanks!
  Bye.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Wed Nov 29 08:49:00 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-UnXpLA/14-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-09-11 (80 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170829.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1732204] Re: Totem could not get a screenshot of the video

2017-11-30 Thread Doug McMahon
*** This bug is a duplicate of bug 1721248 ***
https://bugs.launchpad.net/bugs/1721248

** This bug has been marked a duplicate of bug 1721248
   Totem could not get a screenshot of the video when using gstreamer1.0-vaapi 
plugin on supported videos

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

Title:
  Totem could not get a screenshot of the video

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 17.10
  2) totem 3.26.0-0ubuntu1
  3) I have selected 'Take screenshot' option and I expected to get a 
screenshot of the video in the pictures folder
  4) I got an error message, a pop-up showing 'Totem could not get a screenshot 
of the video. This is not supposed to happen; please file a bug report.' and no 
screenshot available in 'Pictures' folder

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 15:46:44 2017
  InstallationDate: Installed on 2017-10-22 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1735561] [NEW] Segfault in libglib-2.0.so caused by rhythmbox

2017-11-30 Thread Oliver Egginger
Public bug reported:

Rhythmbox just segfaults as it runs normally (paused) in the background.
Happened only once so far. However, I would like to report it because it
may also be a security issue. I added the crash dump.

dmesg output:
---
rhythmbox[4608]: segfault at 5556 ip 7ff002a89190 sp 
7ffc5717ef90 error 4 in libglib-2.0.so.0.5200.0[7ff002a5b000+111000]
---

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: rhythmbox 3.4.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.8
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov 30 22:25:26 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2016-04-23 (586 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to zesty on 2017-04-14 (230 days ago)

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


** Tags: amd64 apport-bug zesty

** Attachment added: "crash dump"
   
https://bugs.launchpad.net/bugs/1735561/+attachment/5016743/+files/_usr_bin_rhythmbox.1000.crash

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

Title:
  Segfault in libglib-2.0.so caused by rhythmbox

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Rhythmbox just segfaults as it runs normally (paused) in the
  background. Happened only once so far. However, I would like to report
  it because it may also be a security issue. I added the crash dump.

  dmesg output:
  ---
  rhythmbox[4608]: segfault at 5556 ip 7ff002a89190 sp 
7ffc5717ef90 error 4 in libglib-2.0.so.0.5200.0[7ff002a5b000+111000]
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: rhythmbox 3.4.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov 30 22:25:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2016-04-23 (586 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (230 days ago)

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

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


[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-30 Thread Ray Link
The autopkgtest failure on s390x is in a test that checks rfkill
integration.  s390 kernels do not have CONFIG_RFKILL set.  Behavior
change might have something to do with the recent change to s390x
autopkgtest from LXC containers to VMs?

https://lists.ubuntu.com/archives/ubuntu-devel/2017-November/040052.html

Successful s390 autpkgtests of previous versions of network-manager
skipped this test (among others):

> urfkill-integration  SKIP Test requires machine-level isolation but
testbed does not provide that

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  SRU REQUEST:

  Debdiff (nm-dhcp-helper.debdiff) attached.

  Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This
  bug was fixed upstream in 1.4.

  [Impact]

   * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
     lease renewal due to a DBus race condition.

   * Upstream NetworkManager 1.4 fixes the race condition by changing
     nm-dhcp-helper's DBus notification from signal "Event" to method
     "Notify".

   * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
     NM 1.2.x.

  [Test Case]

   * Not reliably reproducible. Out of hundreds of machines, only a
     dozen or so fail to notify NetworkManager of a DHCP lease
     renewal about 30-50% of the time. (i.e. It's always the same
     handful of machines that fail.)

   * All such machines with the patched packages have been fine for weeks,
     over many dozens of lease renewals.

  [Regression Potential]

  * The patch changes both nm-dhcp-helper and NetworkManager itself. As
  soon as the new packages are unpacked, the new nm-dhcp-helper will be
  used on DHCP lease renewals, with the new Notify mechanism. Since the
  running, old NetworkManager is still expecting Event notifications,
  the patched nm-dhcp-helper has fallback capability to Event.

  * Once NetworkManager is restarted and is running the patched version,
  it will have the new Notify support.

  [Other Info]

   * Upstream bug w/ patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=784636

   * RHEL bug with links to the 1.4 commits from which the patch was
     derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

   * NOTE:  The final comment on the upstream GNOME bug claims that the
  fix is incomplete.  However, it is possible that the running
  NetworkManager was not restarted (see Regression Potential notes
  above), which is why nm-dhcp-helper is falling back to Event.  The
  remainder of the log messages in that final comment are from a custom
  wrapper the submitter was running around nm-dhcp-helper.  I have
  deployed the exact same patch (without said wrapper) to real-world
  systems and tested extensively, and see nothing but successful DHCP
  lease renewal notifications using D-Bus Notify, not D-Bus Event.


  
  I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').

  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   

[Desktop-packages] [Bug 1735556] [NEW] package libxcursor1:amd64 1:1.1.14-1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren,

2017-11-30 Thread Björn Rathsack
Public bug reported:

trying to install drivers for Optimus graphics at Lenovo T420,
additional fan control. After reboot the system does not work, so i have
to repair it with the console...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libxcursor1:amd64 1:1.1.14-1
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Nov 30 22:41:41 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21d0]
 NVIDIA Corporation GF119M [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GF119M [Quadro NVS 4200M] [17aa:21d0]
MachineType: LENOVO 4236VML
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=05281740-a0da-4925-a99e-014a01c71f61 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: libxcursor
Title: package libxcursor1:amd64 1:1.1.14-1 failed to install/upgrade: Paket 
ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  nochmal 
installieren, bevor Sie die Konfiguration versuchen.
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 07/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET76WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4236VML
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236VML:pvrThinkPadT420:rvnLENOVO:rn4236VML:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4236VML
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Nov 30 22:34:48 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: modeset

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


** Tags: amd64 apport-package compiz-0.9 ubuntu xenial

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

Title:
  package libxcursor1:amd64 1:1.1.14-1 failed to install/upgrade: Paket
  ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es
  nochmal installieren, bevor Sie die Konfiguration versuchen.

Status in libxcursor package in Ubuntu:
  New

Bug description:
  trying to install drivers for Optimus graphics at Lenovo T420,
  additional fan control. After reboot the system does not work, so i
  have to repair it with the console...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxcursor1:amd64 1:1.1.14-1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Nov 30 22:41:41 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
  

[Desktop-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

2017-11-30 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => Confirmed

** Changed in: gnome-control-center
   Importance: Unknown => Medium

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

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in gnome-control-center:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gettext package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

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

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


[Desktop-packages] [Bug 1532508] Re: Screen shown briefly after opening closed laptop lid, before even unlocking

2017-11-30 Thread Brian Murray
Hello Nicolas_Raoul, or anyone else affected,

Accepted unity into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/unity/7.4.5+16.04.20171116 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: unity (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Screen shown briefly after opening closed laptop lid, before even
  unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Committed
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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

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


[Desktop-packages] [Bug 1735549] [NEW] WiFi password asked at every reboot for non-admin users (and LightDM)

2017-11-30 Thread Robert Nurnberg
Public bug reported:

Fresh install of Kubuntu 16.04.3 LTS.

network-manager:
  Installed: 1.2.6-0ubuntu0.16.04.1
  Candidate: 1.2.6-0ubuntu0.16.04.1
  Version table:
 *** 1.2.6-0ubuntu0.16.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.2.2-0ubuntu0.16.04.4 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 1.1.93-0ubuntu4 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Steps to reproduce the bug (first part):
1. After a fresh install, for an administrator account connect to a secure WiFi 
network.
   Store password (in my case WPA) and through NM GUI allow all users to use 
WiFi network.
2. Create non-administrator user, called dummy, say.
3. After every reboot, an error will appear for dummy on login that he does not 
have sufficient  
privileges to make changes to network settings.

After reading 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/comments/26,
 this can be fixed by changing the permissions= entry in 
/etc/NetworkManager/system-connections
for the affected WiFi network.

Steps to reproduce the bug (second part):
Now on every reboot, the user dummy will be asked for the WiFi password once he 
logs in. Nothing that can be done through GUI (either as administrator or as 
dummy) changes that. Similarly, LightDM asks for the WiFi password after every 
reboot.

In my case I could fix the issue by manually editing the following
entries in the SSID file in /etc/NetworkManager/system-connections/:

psk-flags=0
psk=

Note that psk-flags was set to 1 beforehand. The meaning of these values can be 
found with
man nm-settings.

Note that this bug may or may not be related to the following bugs:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270791
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924

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

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

Title:
  WiFi password asked at every reboot for non-admin users (and LightDM)

Status in network-manager package in Ubuntu:
  New

Bug description:
  Fresh install of Kubuntu 16.04.3 LTS.

  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  Steps to reproduce the bug (first part):
  1. After a fresh install, for an administrator account connect to a secure 
WiFi network.
 Store password (in my case WPA) and through NM GUI allow all users to use 
WiFi network.
  2. Create non-administrator user, called dummy, say.
  3. After every reboot, an error will appear for dummy on login that he does 
not have sufficient  
  privileges to make changes to network settings.

  After reading 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020/comments/26,
 this can be fixed by changing the permissions= entry in 
/etc/NetworkManager/system-connections
  for the affected WiFi network.

  Steps to reproduce the bug (second part):
  Now on every reboot, the user dummy will be asked for the WiFi password once 
he logs in. Nothing that can be done through GUI (either as administrator or as 
dummy) changes that. Similarly, LightDM asks for the WiFi password after every 
reboot.

  In my case I could fix the issue by manually editing the following
  entries in the SSID file in /etc/NetworkManager/system-connections/:

  psk-flags=0
  psk=

  Note that psk-flags was set to 1 beforehand. The meaning of these values can 
be found with
  man nm-settings.

  Note that this bug may or may not be related to the following bugs:
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574020
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270791
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924

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

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


[Desktop-packages] [Bug 1735550] [NEW] Privacy: One screen not covered on wake after sleep

2017-11-30 Thread Rhett
Public bug reported:

I have a laptop with an attached HDMI monitor. It is set to require a
password after suspension. When I wake the system after suspending it,
the laptop display is not obscured. The applications that were running
on the laptop display prior to suspension are all visible. The display
will become obscured as I start to enter my password.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 30 15:37:22 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' 
b"['sound-output-device-choo...@kgshank.net', 'grava...@jr.rlabs.io', 
'bitcoin-mark...@ottoallmendinger.github.com']"
 b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'keepass2.desktop', 'kodi.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'calibre-gui.desktop', 
'org.gnome.Terminal.desktop', 'virtualbox.desktop', 
'org.gnome.Screenshot.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2016-03-16 (624 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (42 days ago)

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


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

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

Title:
  Privacy: One screen not covered on wake after sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have a laptop with an attached HDMI monitor. It is set to require a
  password after suspension. When I wake the system after suspending it,
  the laptop display is not obscured. The applications that were running
  on the laptop display prior to suspension are all visible. The display
  will become obscured as I start to enter my password.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 30 15:37:22 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['sound-output-device-choo...@kgshank.net', 'grava...@jr.rlabs.io', 
'bitcoin-mark...@ottoallmendinger.github.com']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'keepass2.desktop', 'kodi.desktop', 'org.gnome.Nautilus.desktop', 
'org.gnome.Software.desktop', 'yelp.desktop', 'calibre-gui.desktop', 
'org.gnome.Terminal.desktop', 'virtualbox.desktop', 
'org.gnome.Screenshot.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-03-16 (624 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (42 days ago)

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

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


[Desktop-packages] [Bug 1729728] Re: window picker is broken in 3.26

2017-11-30 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-applets - 3.26.0-3

---
gnome-applets (3.26.0-3) unstable; urgency=medium

  * Backport upstream patch to fix window-picker crash because of missing
GSettings schema (windowpicker_gschema.diff; LP: #1729728).
  * Remove trailing whitespace from debian/changelog.

 -- Dmitry Shachnev   Thu, 30 Nov 2017 11:02:38
+0300

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

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

Title:
  window picker is broken in 3.26

Status in gnome-applets package in Ubuntu:
  Fix Released
Status in gnome-applets source package in Artful:
  New

Bug description:
  WindowPicker seems to be broken in 3.26.

  It just crashes upon applet addition on fresh 17.10.

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

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


[Desktop-packages] [Bug 1730521] Re: transparency gone in dock panel (wayland)

2017-11-30 Thread Michael Rowland Hunter
*** This bug is a duplicate of bug 1730489 ***
https://bugs.launchpad.net/bugs/1730489

** Summary changed:

- transparencey gone in dock panel (wayland)
+ transparency gone in dock panel (wayland)

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

Title:
  transparency gone in dock panel (wayland)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After update/upgrade transparency is gone on the dock panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.1-0ubuntu6
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 17:38:38 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-10-13 (24 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  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/1730521/+subscriptions

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


[Desktop-packages] [Bug 1221955] Re: GNOME_KEYRING_RESULT_IO_ERROR from launchpadlib

2017-11-30 Thread jaromil
Is there any versioning information of this libsecret?
Not having a test suite is hard to tell.
I'm running 0.18.5-3.1 from devuan ascii and will try to replicate.

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

Title:
  GNOME_KEYRING_RESULT_IO_ERROR from launchpadlib

Status in GNOME Keyring:
  Invalid
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Debian:
  Confirmed

Bug description:
  I have no reliable way to reproduce it, but every now and then when
  using pull-ppa-source (from lp:kubuntu-dev-tools) the script fails
  with this error: (tokens stripped from output)

  Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
  Gkr-Message: call to daemon returned an invalid response: (null).(null)()
  Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
  Gkr-Message: call to daemon returned an invalid response: (null).(null)()
  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Press any key to continue or wait (5) seconds...
  Waiting to hear from Launchpad about your decision...
  00:24:38 unnamed app(24933) ClientApp::doIt: Creating ClientApp
  00:24:38 kioclient(24933) ClientApp::kde_open: 
KUrl("https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION")
  00:24:38 kioclient(24933)/kio (KRun) KRun::slotTimeout: KRun(0x269dbe0)  
slotTimeout called
  00:24:38 kioclient(24933)/kio (KRun) KRun::init: INIT called
  00:24:38 kioclient(24933)/kdecore (KSycoca) KSycocaPrivate::openDatabase: 
Trying to open ksycoca from "/var/tmp/kdecache-yofel/ksycoca4"
  00:24:38 kioclient(24933)/kfile (kdelibs) KRecentDocument::add: 
KRecentDocument::add for  
"https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INT
  EGRATION"
  00:24:38 kioclient(24933)/kio (KRun) runTempService: runTempService: first 
url  
"https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION"
  00:24:38 kioclient(24933)/kio (KRun) supportedProtocols: supportedProtocols: 
("KIO")
  00:24:38 kioclient(24933)/kio (KRun) runTempService: runTempService: KProcess 
args= ("/usr/bin/firefox", 
"https://launchpad.net/+authorize-token?oauth_token=<>_permiss
  ion=DESKTOP_INTEGRATION")
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) 
KStartupInfo::createNewStartupId: creating:  
"yofel-T510;1378506278;233618;24933_TIME0" : ""
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendStartup: 
sending  "new:  ID="yofel-T510;1378506278;233618;24933_TIME0"   BIN="firefox" 
DESCRIPTION="Launching " DESKTOP=1 WM
  CLASS="0" HOSTNAME=yofel-T510 NAME="firefox" SCREEN=0"
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendChange: 
sending  "change:  ID="yofel-T510;1378506278;233618;24933_TIME0"   PID=24935"
  00:24:38 kioclient(24933)/kio (KRun) KRun::slotTimeout: KRun(0x269dbe0)  
slotTimeout called

  (process:24935): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Gtk-Message: Failed to load module "canberra-gtk-module"
  Gtk-Message: Failed to load module "canberra-gtk-module"
  00:24:38 kioclient(24933)/kio (KRun) KProcessRunner::slotProcessExited: 
"firefox" exitCode= 0 exitStatus= 0
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendFinish: 
sending  "remove:  ID="yofel-T510;1378506278;233618;24933_TIME0"   
HOSTNAME=yofel-T510 PID=24935"
  Gkr-Message: secret service operation failed: The secret was transferred or 
encrypted in an invalid way.
  Traceback (most recent call last):
    File "/usr/bin/pull-ppa-source", line 49, in 
  lp = Launchpad.login_with("pull-ppa-source", "production")
    File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 
539, in login_with
  credential_save_failed, version)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 
346, in _authorize_token_and_login
  credentials = authorization_engine(credentials, credential_store)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 
520, in __call__
  credential_store.save(credentials, self.unique_consumer_id)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 
276, in save
  raise e
  keyring.errors.PasswordSetError: GNOME_KEYRING_RESULT_IO_ERROR

  Happens usually when using the kubuntu ppa packages batch backport
  script which calls pull-ppa-source about 160 times (once for every KDE
  SC source).

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: gnome-keyring 3.8.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 

[Desktop-packages] [Bug 1735545] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  I upgraded from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic i686
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  Date: Mon Nov 27 07:18:37 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-02-06 (2489 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-11-27 (3 days ago)

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

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


[Desktop-packages] [Bug 1735545] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-30 Thread Ulf Gröpper
Public bug reported:

I upgraded from 14.04 to 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic i686
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: i386
Date: Mon Nov 27 07:18:37 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2011-02-06 (2489 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2017-11-27 (3 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  I upgraded from 14.04 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic i686
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  Date: Mon Nov 27 07:18:37 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-02-06 (2489 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-11-27 (3 days ago)

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

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


[Desktop-packages] [Bug 1731102] Re: Poor performance with Wayland

2017-11-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Poor performance with Wayland

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE
  env var) I see the following issues on this hardware:

  * Jerky animations (glxgears stutters noticably)
  * Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is 
under load, appearing to worsen over time (> 8 hours uptime)
  * High CPU usage when mousing over icons in left-hand side Unity dock 
(20-30%), also causing mouse cursor to stutter
  * 15fps in Kodi and poor video playback framerate
  * 30-40% CPU usage in Kodi when program idle
  * Gnome shell frequently using 25% of CPU or more

  All issues disappear when using x11 mode (again confirmed with
  XDG_SESSION_TYPE env var). Performance in that case seems as good as
  17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  BootLog:
   * Setting up X socket directories...    
[ OK ]
* Restoring resolver state...    
[ OK ]
   Starting jabber server: ejabberd
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 13:03:08 2017
  DistUpgraded: 2017-11-07 09:38:15,448 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6310] 
[19da:a191]
  InstallationDate: Installed on 2011-12-05 (2165 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=e1bf9820-e70e-4e84-9037-621437cc90f1 ro radeon.audio=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-11-06 (2 days ago)
  dmi.bios.date: 10/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.name: AMD HUDSON-M1
  dmi.board.vendor: ZOTAC
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/28/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.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 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Oct 18 20:39:16 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputRiitek Micro Keyboard KEYBOARD, id 8
   inputRiitek Micro Keyboard MOUSE, id 9
   inputRiitek Micro Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1735529] [NEW] Firefox incorrectly blacklists system for WebGL

2017-11-30 Thread Jeremy Nation
Public bug reported:

This is with Ubuntu 16.04.

Using the Ubuntu-provided Firefox 57.0, if I go to
https://get.webgl.org/ I get the message:

"Hmm. While your browser seems to support WebGL, it is disabled or
unavailable. If possible, please ensure that you are running the latest
drivers for your video card."

In the JavaScript developer console there are some messages, including:

"Error: WebGL warning: Failed to create WebGL context: WebGL creation failed: 
* Refused to create native OpenGL context because of blacklist entry: 
FEATURE_FAILURE_OPENGL_1
* Exhausted GL driver options."

There are similar messages for WebGL in about:support.

However if I download Firefox 57.0 from
https://ftp.mozilla.org/pub/firefox/releases/57.0/linux-x86_64/en-
US/firefox-57.0.tar.bz2 and use that to go to https://get.webgl.org/ , I
get the message "Your browser supports WebGL".

So it looks like Ubuntu-provided Firefox has a problem while Mozilla-
provided Firefox doesn't. (FYI, I reported a similar problem in
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1724705 , where
DRM-protected content doesn't work with Ubuntu-provided Firefox but does
work with Mozilla-provided Firefox.)

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

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

Title:
  Firefox incorrectly blacklists system for WebGL

Status in firefox package in Ubuntu:
  New

Bug description:
  This is with Ubuntu 16.04.

  Using the Ubuntu-provided Firefox 57.0, if I go to
  https://get.webgl.org/ I get the message:

  "Hmm. While your browser seems to support WebGL, it is disabled or
  unavailable. If possible, please ensure that you are running the
  latest drivers for your video card."

  In the JavaScript developer console there are some messages,
  including:

  "Error: WebGL warning: Failed to create WebGL context: WebGL creation failed: 
  * Refused to create native OpenGL context because of blacklist entry: 
FEATURE_FAILURE_OPENGL_1
  * Exhausted GL driver options."

  There are similar messages for WebGL in about:support.

  However if I download Firefox 57.0 from
  https://ftp.mozilla.org/pub/firefox/releases/57.0/linux-x86_64/en-
  US/firefox-57.0.tar.bz2 and use that to go to https://get.webgl.org/ ,
  I get the message "Your browser supports WebGL".

  So it looks like Ubuntu-provided Firefox has a problem while Mozilla-
  provided Firefox doesn't. (FYI, I reported a similar problem in
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1724705 , where
  DRM-protected content doesn't work with Ubuntu-provided Firefox but
  does work with Mozilla-provided Firefox.)

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

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


[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

2017-11-30 Thread LaurentP
hello, 
i have got sound on Line out, rear jack, by applied the proccess documented in 
this forum : 
[url]https://ubuntuforums.org/showthread.php?t=2326126=13496676#post13496676[/url].

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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


[Desktop-packages] [Bug 1221955] Re: GNOME_KEYRING_RESULT_IO_ERROR from launchpadlib

2017-11-30 Thread Jon Gjengset
I believe this has been fixed in libsecret in
https://bugzilla.gnome.org/show_bug.cgi?id=778357.

** Bug watch added: GNOME Bug Tracker #778357
   https://bugzilla.gnome.org/show_bug.cgi?id=778357

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

Title:
  GNOME_KEYRING_RESULT_IO_ERROR from launchpadlib

Status in GNOME Keyring:
  Invalid
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Debian:
  Confirmed

Bug description:
  I have no reliable way to reproduce it, but every now and then when
  using pull-ppa-source (from lp:kubuntu-dev-tools) the script fails
  with this error: (tokens stripped from output)

  Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
  Gkr-Message: call to daemon returned an invalid response: (null).(null)()
  Gkr-Message: received an invalid, unencryptable, or non-utf8 secret
  Gkr-Message: call to daemon returned an invalid response: (null).(null)()
  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Press any key to continue or wait (5) seconds...
  Waiting to hear from Launchpad about your decision...
  00:24:38 unnamed app(24933) ClientApp::doIt: Creating ClientApp
  00:24:38 kioclient(24933) ClientApp::kde_open: 
KUrl("https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION")
  00:24:38 kioclient(24933)/kio (KRun) KRun::slotTimeout: KRun(0x269dbe0)  
slotTimeout called
  00:24:38 kioclient(24933)/kio (KRun) KRun::init: INIT called
  00:24:38 kioclient(24933)/kdecore (KSycoca) KSycocaPrivate::openDatabase: 
Trying to open ksycoca from "/var/tmp/kdecache-yofel/ksycoca4"
  00:24:38 kioclient(24933)/kfile (kdelibs) KRecentDocument::add: 
KRecentDocument::add for  
"https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INT
  EGRATION"
  00:24:38 kioclient(24933)/kio (KRun) runTempService: runTempService: first 
url  
"https://launchpad.net/+authorize-token?oauth_token=<>_permission=DESKTOP_INTEGRATION"
  00:24:38 kioclient(24933)/kio (KRun) supportedProtocols: supportedProtocols: 
("KIO")
  00:24:38 kioclient(24933)/kio (KRun) runTempService: runTempService: KProcess 
args= ("/usr/bin/firefox", 
"https://launchpad.net/+authorize-token?oauth_token=<>_permiss
  ion=DESKTOP_INTEGRATION")
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) 
KStartupInfo::createNewStartupId: creating:  
"yofel-T510;1378506278;233618;24933_TIME0" : ""
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendStartup: 
sending  "new:  ID="yofel-T510;1378506278;233618;24933_TIME0"   BIN="firefox" 
DESCRIPTION="Launching " DESKTOP=1 WM
  CLASS="0" HOSTNAME=yofel-T510 NAME="firefox" SCREEN=0"
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendChange: 
sending  "change:  ID="yofel-T510;1378506278;233618;24933_TIME0"   PID=24935"
  00:24:38 kioclient(24933)/kio (KRun) KRun::slotTimeout: KRun(0x269dbe0)  
slotTimeout called

  (process:24935): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Gtk-Message: Failed to load module "canberra-gtk-module"
  Gtk-Message: Failed to load module "canberra-gtk-module"
  00:24:38 kioclient(24933)/kio (KRun) KProcessRunner::slotProcessExited: 
"firefox" exitCode= 0 exitStatus= 0
  00:24:38 kioclient(24933)/kdecore (KStartupInfo) KStartupInfo::sendFinish: 
sending  "remove:  ID="yofel-T510;1378506278;233618;24933_TIME0"   
HOSTNAME=yofel-T510 PID=24935"
  Gkr-Message: secret service operation failed: The secret was transferred or 
encrypted in an invalid way.
  Traceback (most recent call last):
    File "/usr/bin/pull-ppa-source", line 49, in 
  lp = Launchpad.login_with("pull-ppa-source", "production")
    File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 
539, in login_with
  credential_save_failed, version)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/launchpad.py", line 
346, in _authorize_token_and_login
  credentials = authorization_engine(credentials, credential_store)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 
520, in __call__
  credential_store.save(credentials, self.unique_consumer_id)
    File "/usr/lib/python2.7/dist-packages/launchpadlib/credentials.py", line 
276, in save
  raise e
  keyring.errors.PasswordSetError: GNOME_KEYRING_RESULT_IO_ERROR

  Happens usually when using the kubuntu ppa packages batch backport
  script which calls pull-ppa-source about 160 times (once for every KDE
  SC source).

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: gnome-keyring 3.8.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: 

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-30 Thread Brian Murray
There seems to be an autopkgtest failure on s390x which requires
investigation.

http://autopkgtest.ubuntu.com/packages/n/network-manager/xenial/s390x

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  SRU REQUEST:

  Debdiff (nm-dhcp-helper.debdiff) attached.

  Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This
  bug was fixed upstream in 1.4.

  [Impact]

   * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
     lease renewal due to a DBus race condition.

   * Upstream NetworkManager 1.4 fixes the race condition by changing
     nm-dhcp-helper's DBus notification from signal "Event" to method
     "Notify".

   * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
     NM 1.2.x.

  [Test Case]

   * Not reliably reproducible. Out of hundreds of machines, only a
     dozen or so fail to notify NetworkManager of a DHCP lease
     renewal about 30-50% of the time. (i.e. It's always the same
     handful of machines that fail.)

   * All such machines with the patched packages have been fine for weeks,
     over many dozens of lease renewals.

  [Regression Potential]

  * The patch changes both nm-dhcp-helper and NetworkManager itself. As
  soon as the new packages are unpacked, the new nm-dhcp-helper will be
  used on DHCP lease renewals, with the new Notify mechanism. Since the
  running, old NetworkManager is still expecting Event notifications,
  the patched nm-dhcp-helper has fallback capability to Event.

  * Once NetworkManager is restarted and is running the patched version,
  it will have the new Notify support.

  [Other Info]

   * Upstream bug w/ patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=784636

   * RHEL bug with links to the 1.4 commits from which the patch was
     derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

   * NOTE:  The final comment on the upstream GNOME bug claims that the
  fix is incomplete.  However, it is possible that the running
  NetworkManager was not restarted (see Regression Potential notes
  above), which is why nm-dhcp-helper is falling back to Event.  The
  remainder of the log messages in that final comment are from a custom
  wrapper the submitter was running around nm-dhcp-helper.  I have
  deployed the exact same patch (without said wrapper) to real-world
  systems and tested extensively, and see nothing but successful DHCP
  lease renewal notifications using D-Bus Notify, not D-Bus Event.


  
  I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').

  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is 

[Desktop-packages] [Bug 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2017-11-30 Thread Brian Murray
This needs verification details.

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial)
   Status: Fix Committed => Incomplete

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

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

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

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

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

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


[Desktop-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

2017-11-30 Thread AsciiWolf
** Bug watch added: GNOME Bug Tracker #791035
   https://bugzilla.gnome.org/show_bug.cgi?id=791035

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=791035
   Importance: Unknown
   Status: Unknown

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

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in gnome-control-center:
  Unknown
Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gettext package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

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

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


[Desktop-packages] [Bug 1724872] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2017-11-30 Thread Andy Whitcroft
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  New

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20171018_120806_eb45b@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20171018_121546_eb45b@/log.gz

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

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


[Desktop-packages] [Bug 1528028] Re: gnome-software does not report installing a desktop environment as a dependency

2017-11-30 Thread AsciiWolf
Related bugreport: https://bugzilla.gnome.org/show_bug.cgi?id=711171

** Bug watch added: GNOME Bug Tracker #711171
   https://bugzilla.gnome.org/show_bug.cgi?id=711171

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

Title:
  gnome-software does not report installing a desktop environment as a
  dependency

Status in GNOME Software:
  In Progress
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  The average user cannot tell when they are installing a desktop
  environment as a dependency of a package.

  Having various desktop environments can reduce system performance
  sensibly, as processes from various desktops are running
  simultaneously in the background. Moreover the autoremove tool cannot
  always identify the dependencies when removing some of those installed
  packages.

  For example if I install the "cortina" package, it takes with it the
  GNOME Display Manager and plenty of wallpapers. Then if I uninstall it
  and do "sudo apt-get autoremove" those packages are not detected as
  unused.

  Another example: if I install the "rkward" package plenty of KDE
  services, like the Akonadi indexing service, are installed. Then
  launching applications in my Inter Core 2 Quad becomes noticeably
  slower, because my system is running both GNOME and KDE services
  simultaneously.

  If I remove rkward and then I perform an autoremove, the system still
  stays slow. If I uninstall all the packages in the universe
  repository, perform an autoremove, and then reinstall the applications
  I had, the system becomes fast again.

  The user shall know these potential problems beforehand.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: apt 1.0.10.2ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec 20 18:54:54 2015
  InstallationDate: Installed on 2015-11-14 (36 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


Re: [Desktop-packages] [Bug 1735202] Re: "Continue on PC" feature with signed in Microsoft accounts

2017-11-30 Thread Jeb E.
Really?
All I am asking for is compatibility to pick up handed off websites and
documents from my mobile devices using my signed in Microsoft account

On Nov 30, 2017 10:00 AM, "Sebastien Bacher"  wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we cannot work on this bug because your
> description didn't include enough information. You may find it helpful
> to read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem.
>
> We have instructions on debugging some types of problems at
> http://wiki.ubuntu.com/DebuggingProcedures.
>
> At a minimum, we need:
> 1. The specific steps or actions you took that caused you to encounter the
> problem.
> 2. The behavior you expected.
> 3. The behavior you actually encountered (in as much detail as possible).
> Thanks!
>
> ** Changed in: gnome-control-center (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1735202
>
> Title:
>   "Continue on PC" feature with signed in Microsoft accounts
>
> Status in gnome-control-center:
>   New
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Please bring compatibility with the Windows 10 and Cortana feature
>   "Continue on PC" for users signed into Microsoft Accounts in gnome-
>   control-center.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: gnome-control-center 1:3.26.1-0ubuntu5
>   ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8
>   Uname: Linux 4.13.0-17-lowlatency x86_64
>   ApportVersion: 2.20.7-0ubuntu3.5
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Nov 29 10:43:08 2017
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-control-center/+bug/
> 1735202/+subscriptions
>

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

Title:
  "Continue on PC" feature with signed in Microsoft accounts

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

Bug description:
  Please bring compatibility with the Windows 10 and Cortana feature
  "Continue on PC" for users signed into Microsoft Accounts in gnome-
  control-center.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8
  Uname: Linux 4.13.0-17-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 29 10:43:08 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1724871] Re: nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

2017-11-30 Thread Marcelo Cerri
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  nvidia-graphics-drivers-304 304.135-0ubuntu0.16.04.1 ADT test failure
  with linux-hwe-edge 4.13.0-16.19~16.04.3

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently the DKMS package fails to install in supported custom
  kernels that are based on 4.11 or 4.13. That includes the current 4.11
  hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom
  and cloud kernels as well.

  [Test Case]

  Install the DKMS package with the 4.13 hwe-edge kernel from -proposed.
  The package installation should proceed without any errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel
  version.

  Besides that the new package was tested with the following kernels in
  an amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-304/20171018_120651_877e3@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-304/20171018_121553_877e3@/log.gz

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

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


[Desktop-packages] [Bug 1734975] Re: Firefox man page severly out of date

2017-11-30 Thread To
I've written a man page, starting from Fedora's. see-->
https://bugzilla.redhat.com/attachment.cgi?id=1360974

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

Title:
  Firefox man page severly out of date

Status in manpages:
  Unknown
Status in firefox package in Ubuntu:
  New
Status in manpages package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04 (LTS) the manpage for Firefox reports a date of
  2011-02-09 (!)

  The man page mentions the -private flag, which has been replaced by
  --private-window quite some time ago and to make matters worse,
  -private actually _breaks the private mode_ until firefox gets
  restarted.

  firefox --help shows the new flags that are available.

  The report on Mozilla's bugtracker has been dismissed, because the man
  page is apparently distro-provided.
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1381866)

  A bug has also been filed for Fedora 26 (man page date 2001) here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1334025

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

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


[Desktop-packages] [Bug 602809] Re: add Mouse Click Debounce Feature?

2017-11-30 Thread Alexander Thomas
I also started noticing this recently. I tried a different mouse and it had the 
same problem. I expected to have at least some way to tweak a low-level config 
file to increase the debounce interval, but apparently it isn't implemented to 
begin with.
I reckon this isn't only annoying for people who didn't win the ‘perfect mouse’ 
lottery, but also for those with certain disabilities. If debounce is 
implemented for keyboards, then it only makes sense to implement it for any 
other input device with hardware buttons as well.

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

Title:
  add Mouse Click Debounce Feature?

Status in xserver-xorg-input-evdev:
  New
Status in System76:
  New
Status in xserver-xorg-input-evdev package in Ubuntu:
  Confirmed

Bug description:
  Model:  bonp3
  OS:  Ubuntu 10.04 LTS

  When I single click the mouse (external USB Mouse - Mouse Pad
  disabled) half the time the system responds as though I have double
  clicked the mouse.  I try 2 different USB mouse units and it still
  does this.  I am running Ubuntu 10.04 on a separate PC that does not
  have this mouse problem.  So I am thinking this problem is a System76
  driver issue???

  It's annoying.  :(

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

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


[Desktop-packages] [Bug 21157] Re: Cannot drag-and-drop entire thread

2017-11-30 Thread Bug Watch Updater
** Changed in: evolution
   Status: Confirmed => Fix Released

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

Title:
  Cannot drag-and-drop entire thread

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid

Bug description:
  There's no way (at least it's not obvious) to drag an entire thread of emails
  from the message pane to a folder in the folder list when operating in 
threaded
  view. It seems that each message must be drag-and-dropped manually.

  http://bugzilla.gnome.org/show_bug.cgi?id=315611:
  http://bugzilla.gnome.org/show_bug.cgi?id=315611

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

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


[Desktop-packages] [Bug 1731780] Re: segfaults randomly on libgobject-2.0.so.0

2017-11-30 Thread kkivi
Gnome-session dies seven times per day without obvious cause, to the
effect of killing all app logging out of session.

Nov 30 17:50:51 myhost kernel: [28059.065228] gnome-shell[15991]:
segfault   at 50 ip 7f28b81d3cdf sp 7ffe87210568 error 4 in
libgobject-2.0.so  .0.5400.1[7f28b819e000+52000]


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

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

Title:
  segfaults randomly on libgobject-2.0.so.0

Status in gnome-session package in Ubuntu:
  New
Status in mate-terminal package in Ubuntu:
  Incomplete

Bug description:
  segfaults are quite frequent, had to switch to gnome-terminal :(

  [ 2331.046531] mate-terminal[6528]: segfault at 7001e ip 7f24eca1c77e 
sp 7ffd73596858 error 4 in libgobject-2.0.so.0.5400.1[7f24ec9e7000+52000]
  [ 2417.695601] mate-terminal[6651]: segfault at 7001e ip 7f8e4ecc777e 
sp 7ffd53ede758 error 4 in libgobject-2.0.so.0.5400.1[7f8e4ec92000+52000]
  [ 2492.133087] mate-terminal[6764]: segfault at 7001e ip 7f2390b1577e 
sp 7ffed5830dd8 error 4 in libgobject-2.0.so.0.5400.1[7f2390ae+52000]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: mate-terminal 1.18.1-2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Sun Nov 12 18:34:36 2017
  InstallationDate: Installed on 2017-06-21 (143 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: mate-terminal
  UpgradeStatus: Upgraded to artful on 2017-09-02 (71 days ago)

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

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


[Desktop-packages] [Bug 1735202] Re: "Continue on PC" feature with signed in Microsoft accounts

2017-11-30 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

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

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

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

Title:
  "Continue on PC" feature with signed in Microsoft accounts

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

Bug description:
  Please bring compatibility with the Windows 10 and Cortana feature
  "Continue on PC" for users signed into Microsoft Accounts in gnome-
  control-center.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-lowlatency 4.13.8
  Uname: Linux 4.13.0-17-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 29 10:43:08 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735434] [NEW] bug intel

2017-11-30 Thread reno guacamole
Public bug reported:

lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04


apt-cache policy pkgname
N: Unable to locate package pkgname


3) i wanted to fix intel driver so i could watch videos and audio normally 
without freeeze, the main issue is that i cant because is not sync together.

4)nothing happened it just freezes system and mouse and all the same ol'
continue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: i386
CurrentDesktop: LXDE
Date: Thu Nov 30 09:44:33 2017
InstallationDate: Installed on 2017-08-15 (106 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 xenial

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

Title:
  bug intel

Status in xorg package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  
  apt-cache policy pkgname
  N: Unable to locate package pkgname

  
  3) i wanted to fix intel driver so i could watch videos and audio normally 
without freeeze, the main issue is that i cant because is not sync together.

  4)nothing happened it just freezes system and mouse and all the same
  ol' continue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Thu Nov 30 09:44:33 2017
  InstallationDate: Installed on 2017-08-15 (106 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop

2017-11-30 Thread Sebastien Bacher
** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  GNOME Shell disabling wrong screen when docking laptop

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  I often switch between working with a docking station, closed laptop
  and an external monitor, and an open laptop without docking station or
  monitor.  I noticed since updating to 17.10 that GNOME Shell would not
  switch correctly from the setup where the laptop was being used open
  without a docking station to the other.  When I opened the laptop in
  the docking station the external monitor would come on, and when I
  closed the laptop it went off again.  I manually switched the primary
  screen to be the external one and that solved it for now, so I assume
  that GNOME Shell was disabling the external screen instead of the
  internal one (it is a bit hard to see, and I have not yet tried ssh-
  ing in).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 09:06:34 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-05-31 (497 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago)

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

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


[Desktop-packages] [Bug 1735389] Re: gnome-shell under gdm user eats CPU most of time

2017-11-30 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  gnome-shell under gdm user eats CPU most of time

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell under 'gdm' user most of time eats more CPU than any other
  real user process.

  'top' screenshot attached, see first line, most CPU eating and time
  consuming process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 30 12:27:46 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-24 (36 days ago)

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

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


[Desktop-packages] [Bug 1728467] Re: All files on ntfs partitions are marked executable

2017-11-30 Thread Phillip Susi
The change was intentional.  See bug #453605.


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

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

Title:
  All files on ntfs partitions are marked executable

Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  This did not happen in 14.04 but somewhere since then udisks2 sets any & all 
files on ntfs partitions as executable.
  Additionally if file is copied over to user's ext4 partion the bit remains 
set.
  Can't see why this would be intentional??

  In 14.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077", 
"fmask=0177", NULL };

  In 16.04, 17.04, 17.10,18.04 udisks2 - 
  :static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Sun Oct 29 21:20:19 2017
  InstallationDate: Installed on 2017-09-16 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20217
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop

2017-11-30 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Confirmed => Fix Released

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

Title:
  GNOME Shell disabling wrong screen when docking laptop

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  I often switch between working with a docking station, closed laptop
  and an external monitor, and an open laptop without docking station or
  monitor.  I noticed since updating to 17.10 that GNOME Shell would not
  switch correctly from the setup where the laptop was being used open
  without a docking station to the other.  When I opened the laptop in
  the docking station the external monitor would come on, and when I
  closed the laptop it went off again.  I manually switched the primary
  screen to be the external one and that solved it for now, so I assume
  that GNOME Shell was disabling the external screen instead of the
  internal one (it is a bit hard to see, and I have not yet tried ssh-
  ing in).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 09:06:34 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 
'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2016-05-31 (497 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago)

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

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


[Desktop-packages] [Bug 1734499] Re: InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid://

2017-11-30 Thread Claud S
Got the same error but in my case the backup had already been running for a 
while when suddenly a window was shown:
Backup Failed
InvalidBackendURL: missing // - relative paths not supported for scheme 
invalid: invalid://

uname: 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

packages:
deja-dup/artful,now 36.2-0ubuntu1 amd64 [installed]
deja-dup-caja/artful,artful 0.0.4-0ubuntu2 all
duplicity/artful,now 0.7.12-1ubuntu1 amd64 [installed]


** Attachment added: "deja-dup.gsettings"
   
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1734499/+attachment/5016555/+files/deja-dup.gsettings

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

Title:
   InvalidBackendURL: missing // - relative paths not supported for
  scheme gio+invalid: gio+invalid://

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Same problem as https://bugs.launchpad.net/deja-dup/+bug/1717230 but
  opening a new bug because as far as I know that's standard practice
  when a bug is apparently not fixed by a previous fix? If that's not
  correct, then instead the status of the bug needs to be changed back
  to Confirmed from Fix Released.

  I ran into this bug by plugging in my external drive (with a backup on
  it) and trying to (update my) back up to it.

  The bug is potentially a regression in 36.2-0ubuntu1 (since the bug
  was apparently fixed in 36.1-0ubuntu1).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 02:39:52 2017
  InstallationDate: Installed on 2017-08-03 (114 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to artful on 2017-10-21 (35 days ago)

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

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


[Desktop-packages] [Bug 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos

2017-11-30 Thread corrado venturini
Removed gstreamer1.0-vaapi plugin 
Problem solved!
thanks a lot!

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

Title:
  Totem could not get a screenshot of the video when using
  gstreamer1.0-vaapi plugin on supported videos

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  I try to get a screenshot from my video and totem shows a message
  saying it could not get a screenshot of the video and suggesting to
  open a bug. See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:54:16 2017
  InstallationDate: Installed on 2017-09-29 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly

2017-11-30 Thread Johan Holmberg
The issue is present in 17.10 (using GNOME) as well.

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

Title:
  Keyboard layout changing randomly

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

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


[Desktop-packages] [Bug 1440381] Re: please build bindings for Python3

2017-11-30 Thread Matthias Klose
** Tags added: py2-demotion py2-removal

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

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

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

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

Title:
  please build bindings for Python3

Status in ldb package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged
Status in talloc package in Ubuntu:
  New
Status in tdb package in Ubuntu:
  New
Status in samba package in Debian:
  New

Bug description:
  There is still the goal to remove Python2 from the desktop images, and
  to use Python3 only. please build bindings for Python3

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

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


[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2017-11-30 Thread Kleber Sacilotto de Souza
Although we haven't seen the failure in Bionic yet, it might be a good
idea to apply the fix on Bionic as well, which as of now has the same
package version as Artful.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in linux package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  New
Status in linux source package in Artful:
  Triaged
Status in network-manager source package in Artful:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

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

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


[Desktop-packages] [Bug 1735362] Re: ibus-sunpinyin: port to Python3 needed

2017-11-30 Thread Bug Watch Updater
** Changed in: ibus-sunpinyin (Debian)
   Status: Unknown => New

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

Title:
  ibus-sunpinyin: port to Python3 needed

Status in ibus-sunpinyin package in Ubuntu:
  New
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

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

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


[Desktop-packages] [Bug 1735389] [NEW] gnome-shell under gdm user eats CPU most of time

2017-11-30 Thread Eugene Romanenko
Public bug reported:

gnome-shell under 'gdm' user most of time eats more CPU than any other
real user process.

'top' screenshot attached, see first line, most CPU eating and time
consuming process.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 30 12:27:46 2017
DisplayManager: gdm3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-24 (36 days ago)

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


** Tags: amd64 apport-bug artful gdm

** Attachment added: "Снимок экрана от 2017-11-30 12-22-22-1.png"
   
https://bugs.launchpad.net/bugs/1735389/+attachment/5016546/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202017-11-30%2012-22-22-1.png

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

Title:
  gnome-shell under gdm user eats CPU most of time

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell under 'gdm' user most of time eats more CPU than any other
  real user process.

  'top' screenshot attached, see first line, most CPU eating and time
  consuming process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 30 12:27:46 2017
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-24 (36 days ago)

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

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


[Desktop-packages] [Bug 1735363] Re: inkscape: Use/Port of Python3 needed, or considering demotion

2017-11-30 Thread Mattia Rizzolo
** Also affects: inkscape
   Importance: Undecided
   Status: New

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

Title:
  inkscape: Use/Port of Python3 needed, or considering demotion

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  Unknown

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

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

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


[Desktop-packages] [Bug 1735369] [NEW] libglade2: Please investigate demotion or port to Python3

2017-11-30 Thread Matthias Klose
Public bug reported:

libglade2 depends on Python2, and afaics there is no Python3 port
available.  Please investigate a Python3 port or a demotion of libglade2
and reverse dependencies to universe.

** Affects: libglade2 (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Desktop (ubuntu-desktop)
 Status: New


** Tags: py2-demotion py2-removal

** Tags added: py2-demotion py2-removal

** Changed in: libglade2 (Ubuntu)
 Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

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

Title:
  libglade2: Please investigate demotion or port to Python3

Status in libglade2 package in Ubuntu:
  New

Bug description:
  libglade2 depends on Python2, and afaics there is no Python3 port
  available.  Please investigate a Python3 port or a demotion of
  libglade2 and reverse dependencies to universe.

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

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


[Desktop-packages] [Bug 1732204] Re: Totem could not get a screenshot of the video

2017-11-30 Thread Luca Ciavatta
Thanks for comment. I have already reported above as duplicate in
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/comments/9

> This isn't news, the reason is likely described here & due to the use of 
> gstreamer1.0-vaapi plugin
> https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/comments/3
> (- videos not supported by the gst vaapi plugin will get screenshots

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

Title:
  Totem could not get a screenshot of the video

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 17.10
  2) totem 3.26.0-0ubuntu1
  3) I have selected 'Take screenshot' option and I expected to get a 
screenshot of the video in the pictures folder
  4) I got an error message, a pop-up showing 'Totem could not get a screenshot 
of the video. This is not supposed to happen; please file a bug report.' and no 
screenshot available in 'Pictures' folder

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 14 15:46:44 2017
  InstallationDate: Installed on 2017-10-22 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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


[Desktop-packages] [Bug 1735367] [NEW] Prevent redrawing list of networks when visible

2017-11-30 Thread Nick Rose
Public bug reported:

When selecting a network to connect to from nm-applet's list, sometimes
the list updates and redraws itself the split-second before clicking on
a network. The often results in the order of networks changing, so that
the wrong network is clicked on by mistake.

It would be helpful if the list was prevented from updating/redrawing
when it is visible, so that this cannot happen.

An alternative solution would be to have the option to hide user-
selected networks that will never be used from the list (e.g. ones that
belong to neighbours etc.), so that they can never be clicked on by
mistake in the future.

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

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

Title:
  Prevent redrawing list of networks when visible

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

Bug description:
  When selecting a network to connect to from nm-applet's list,
  sometimes the list updates and redraws itself the split-second before
  clicking on a network. The often results in the order of networks
  changing, so that the wrong network is clicked on by mistake.

  It would be helpful if the list was prevented from updating/redrawing
  when it is visible, so that this cannot happen.

  An alternative solution would be to have the option to hide user-
  selected networks that will never be used from the list (e.g. ones
  that belong to neighbours etc.), so that they can never be clicked on
  by mistake in the future.

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

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


[Desktop-packages] [Bug 1735362] Re: ibus-sunpinyin: port to Python3 needed

2017-11-30 Thread Matthias Klose
** Bug watch added: Debian Bug tracker #883154
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883154

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

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

Title:
  ibus-sunpinyin: port to Python3 needed

Status in ibus-sunpinyin package in Ubuntu:
  New
Status in ibus-sunpinyin package in Debian:
  Unknown

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

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

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


[Desktop-packages] [Bug 1735363] [NEW] inkscape: Use/Port of Python3 needed, or considering demotion

2017-11-30 Thread Matthias Klose
Public bug reported:

inkscape: Use/Port of Python3 needed, or considering demotion.

Currently seeded in usb (???), owned by desktop-packages.

** Affects: inkscape (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Desktop (ubuntu-desktop)
 Status: New

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


** Tags: py2-demotion py2-removal

** Tags added: py2-demotion py2-removal

** Changed in: inkscape (Ubuntu)
 Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

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

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

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

Title:
  inkscape: Use/Port of Python3 needed, or considering demotion

Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  Unknown

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

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

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


[Desktop-packages] [Bug 1735362] [NEW] ibus-sunpinyin: port to Python3 needed

2017-11-30 Thread Matthias Klose
Public bug reported:

ibus-sunpinyin: port to Python3 needed.

Currently in the live seed, package owned by desktop-packages.
Considering the lack of upstream maintenance, demotion might be an
option.

** Affects: ibus-sunpinyin (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu Desktop (ubuntu-desktop)
 Status: New


** Tags: py2-demotion py2-removal

** Tags added: py2-demotion py2-removal

** Changed in: ibus-sunpinyin (Ubuntu)
 Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

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

Title:
  ibus-sunpinyin: port to Python3 needed

Status in ibus-sunpinyin package in Ubuntu:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

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

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


[Desktop-packages] [Bug 1735361] [NEW] "use a prediction service to load pages more quickly" feature works badly

2017-11-30 Thread dino99
Public bug reported:

>From chrome://settings -> privacy & security

if the "use a service to load pages more quickly" option is activated,
then browsing become worst:

- after a few pages loaded, the hdd is continously scanned , the
complete system freeze during this heavy scanning, the ram is fully used
and the swap is fullfiled. This let think that this option is trying to
grab too deeply the related pages (should be limited to the page itself,
not including the embedded links). Maybe this is acceptable with ssd,
but with hdd its a nightmare.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chromium-browser 62.0.3202.94-0ubuntu1.1388
Uname: Linux 4.13.12-041312-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Nov 30 09:19:47 2017
DetectedPlugins:
 
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.chromium-browser: [deleted]

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

Title:
  "use a prediction service to load pages more quickly" feature works
  badly

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  From chrome://settings -> privacy & security

  if the "use a service to load pages more quickly" option is activated,
  then browsing become worst:

  - after a few pages loaded, the hdd is continously scanned , the
  complete system freeze during this heavy scanning, the ram is fully
  used and the swap is fullfiled. This let think that this option is
  trying to grab too deeply the related pages (should be limited to the
  page itself, not including the embedded links). Maybe this is
  acceptable with ssd, but with hdd its a nightmare.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 62.0.3202.94-0ubuntu1.1388
  Uname: Linux 4.13.12-041312-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 30 09:19:47 2017
  DetectedPlugins:
   
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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


[Desktop-packages] [Bug 1735346] Re: bittornado: Python3 port needed, or demotion to universe

2017-11-30 Thread Matthias Klose
** Bug watch added: Debian Bug tracker #883147
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883147

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

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

Title:
  bittornado: Python3 port needed, or demotion to universe

Status in bittornado package in Ubuntu:
  New
Status in bittornado package in Debian:
  Unknown

Bug description:
  bittornado: Python3 port needed, or demotion to universe.

  Currently seeded in supported-desktop-extra

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

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


[Desktop-packages] [Bug 1735346] Re: bittornado: Python3 port needed, or demotion to universe

2017-11-30 Thread Matthias Klose
dead upstream, last maintainer upload in Debian in 2010. Maybe better to
demote.


** Changed in: bittornado (Ubuntu)
 Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

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

Title:
  bittornado: Python3 port needed, or demotion to universe

Status in bittornado package in Ubuntu:
  New
Status in bittornado package in Debian:
  Unknown

Bug description:
  bittornado: Python3 port needed, or demotion to universe.

  Currently seeded in supported-desktop-extra

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

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