date:20171020

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Got this after ubuntu dock crashed and failed to load on subsequent
  reboots.Running dash to dock instead.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 20 16:50:09 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-02 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

> correction - needed to disable dnsmasq service as network manager
> starts it instead.

network-manager in 17.04 and later is not expected to start dnsmasq, it
integrates with resolved instead.  Have you overridden the default
network-manager config?

Is it possible your issue is related to LP: #1694156?

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1725570] [NEW] gnome-shell crashed with signal 5 in _XIOError()

2017-10-20 Thread krishnan sampath

Public bug reported:

Got this after ubuntu dock crashed and failed to load on subsequent
reboots.Running dash to dock instead.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Oct 20 16:50:09 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2017-10-02 (18 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash artful need-amd64-retrace

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Got this after ubuntu dock crashed and failed to load on subsequent
  reboots.Running dash to dock instead.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 20 16:50:09 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-02 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

netcfg is also fixed.

netcfg (1.142ubuntu4) artful; urgency=medium

  * Add resolved support. LP: #1714167

 -- Dimitri John Ledkov   Wed, 20 Sep 2017 09:52:03
+0100


** Changed in: netcfg (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Desktop-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

network-manager is also fixed:

network-manager (1.8.2-1ubuntu6) artful; urgency=medium

  * src/dns/nm-dns-manager.c:
- Fix resolved detection, the symlink target is usually relative to
the root, such that in chroots the file points to a file inside the
chroot. But keep absolute targets too, as these may have been in use
with older version of systemd.
- Add support for stub-resolv.conf detection.


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

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Desktop-packages] [Bug 1725564] Re: gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()

Status in gvfs package in Ubuntu:
  New

Bug description:
  Crashed when trying to mount my Android in MTP mode, first time since
  the installation of Ubuntu 17.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 03:59:22 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2017-10-09 (11 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.15 
/org/gtk/gvfs/exec_spaw/10
  SegvAnalysis:
   Segfault happened at: 0x7fa9726244c0:mov0x198(%rdx),%r10
   PC (0x7fa9726244c0) ok
   source "0x198(%rdx)" (0x0198) not located in a known VMA region (needed 
readable region)!
   destination "%r10" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV in g_vfs_job_run()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

livecd-rootfs fixed in version 2.468:

livecd-rootfs (2.468) artful; urgency=medium

  [ Dimitri John Ledkov ]
  * Drop obsolete fix-ups of resolv.conf, debootstrap should now result in
correct symlink to resolved without any further fixes.

  [ Michael Hudson-Doyle ]
  * Have subiquity.service order after on a service defined by the subiquity
snap, which in turn will order after the job that mounts the subiquity
snap. (LP: #1721414)


** Changed in: livecd-rootfs (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Desktop-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

So how was /etc/resolv.conf configured before you removed it?  To my
understanding, there should be no problems after upgrade from any of the
default configurations in 17.04.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Desktop-packages] [Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay

2017-10-20 Thread Cleber Cassol

Ok, a little workaround did restore the System Settings for me (assuming
one had this problem after changing the dock position just like me):

- sudo apt install dconf-editor
- Navigate to org>gnome>shell-extensions>dash-to-dock>dock-position
- Restore dock position to it's default value

System Settings is working properly now. However, my mouse cursor still
disappears if I move it to the screen edge to the right.

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't dislay

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

Bug description:
  When i click on system settings, icon is displaying but settings
  window doesn't visible. I have already reinstalled ubuntu desktop and
  gnome-control-center, but without any success.(reboot also didn't
  help).If i try to open gnome-control-center in terminal the same
  result only icon appearce

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

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

[Desktop-packages] [Bug 1725236] Re: vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10

2017-10-20 Thread Christopher Crouzet

Here are some further investigations, if it can help:

- I have upgraded from 17.04 to 17.10 rather than doing a fresh install
- by default, the file /usr/share/vulkan/icd.d/nvidia_icd.json has its ICD's 
library_path set to libGL.so.1. If I change the value to libGLX_nvidia.so.0 
instead, I can run vulkaninfo again without any problem
- `echo $XDG_SESSION_TYPE` returns x11. At the login screen, when clicking the 
cogwheel icon, I am not given the choice to use Wayland so I am using 'Gnome on 
Xorg' instead

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

Title:
  vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10

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

Bug description:
  I'm using a Dell XPS 9560 with a Geforce 1050.

  Back on 17.04 (libvulkan-dev-1.0.42.0, nvidia-375) I could run
  vulkaninfo and my own Vulkan applications without a problem but, after
  switching to 17.10 (libvulkan-dev-1.0.61.1, nvidia-384), running
  vulkaninfo now results in the error attached. In other words, I cannot
  run any Vulkan-based application anymore.

  I have tried using Vulkan's SDK 1.0.42.2 from LunarG's website without
  success.

  I have been tempted to try rolling back to nvidia-375 but not being so
  familiar with Linux, I am a bit worried that things might go wrong.

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

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

[Desktop-packages] [Bug 1304072] Re: deja-dup crashed with SIGSEGV in g_hash_table_lookup_node()

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

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  deja-dup crashed with SIGSEGV in g_hash_table_lookup_node()

Status in deja-dup package in Ubuntu:
  Expired

Bug description:
  Backup runs for a few minutes then crashes with this message.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 23:09:16 2014
  ExecutablePath: /usr/bin/deja-dup
  ProcCmdline: deja-dup --backup
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_quark_from_string () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () 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_object_thaw_notify () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: deja-dup crashed with SIGSEGV in g_hash_table_lookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 988370] Re: deja-dup-monitor crashed with signal 7 in g_settings_schema_source_lookup()

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

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  deja-dup-monitor crashed with signal 7 in
  g_settings_schema_source_lookup()

Status in deja-dup package in Ubuntu:
  Expired

Bug description:
  Again, no idea how this happened -- left computer on overnight,
  unlocked today and crash dialog. No symptom, apparently.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr 25 12:06:02 2012
  ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
  ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF8
   SHELL=/bin/bash
  Signal: 7
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_schema_source_lookup () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: deja-dup-monitor crashed with signal 7 in 
g_settings_schema_source_lookup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: admin cdrom dialout floppy fuse libvirtd lp lpadmin plugdev video

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

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

[Desktop-packages] [Bug 1102676] Re: nautilus crashed with SIGSEGV in _int_malloc()

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

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nautilus crashed with SIGSEGV in _int_malloc()

Status in deja-dup package in Ubuntu:
  Expired

Bug description:
  Auto report 13.04

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: deja-dup 25.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Sun Jan 20 14:27:13 2013
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2011-03-05 (688 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f6cc3c75c96 <_int_malloc+102>:  mov
0x10(%r14),%r8
   PC (0x7f6cc3c75c96) ok
   source "0x10(%r14)" (0x0011) not located in a known VMA region (needed 
readable region)!
   destination "%r8" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f6cc3fb1740 , bytes=bytes@entry=31) 
at malloc.c:3352
   __GI___libc_malloc (bytes=31) at malloc.c:2858
   g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to raring on 2013-01-20 (1 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1301609] Re: deja-dup crashed with SIGSEGV in GI_pthread_mutex_lock()

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

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  deja-dup crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in deja-dup package in Ubuntu:
  Expired

Bug description:
  Deja-dup has been causing me a lot of problems over the last few days
  - many instant reboots - no errors, no messages in syslog.  This error
  came about after this evening's set of updates - so a step in the
  right direction.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  2 22:03:29 2014
  ExecutablePath: /usr/bin/deja-dup
  ProcCmdline: deja-dup --backup --auto
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ffec725a414 <__GI___pthread_mutex_lock+4>:  mov
0x10(%rdi),%esi
   PC (0x7ffec725a414) ok
   source "0x10(%rdi)" (0xff60462fff5e443d) not located in a known VMA region 
(needed readable region)!
   destination "%esi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x12a8560) at 
../nptl/pthread_mutex_lock.c:66
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_signal_handlers_destroy () 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_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: deja-dup crashed with SIGSEGV in __GI___pthread_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 936721] Re: deja-dup crashed with SIGABRT in __assert_fail_base()

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

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  deja-dup crashed with SIGABRT in __assert_fail_base()

Status in deja-dup package in Ubuntu:
  Expired

Bug description:
  No

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 21.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic i686
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Mon Feb 20 08:27:53 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/deja-dup
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  ProcCmdline: deja-dup --prompt
  Signal: 6
  SourcePackage: deja-dup
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
  Title: deja-dup crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to precise on 2012-02-17 (2 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1711897] Re: gnome-control-center crashed with signal 5 in g_settings_get_value()

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

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

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

Title:
  gnome-control-center crashed with signal 5 in g_settings_get_value()

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

Bug description:
  Clicking on 'Displays' will crash the program.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 20 18:40:32 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-08-20 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
  Title: gnome-control-center crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: Upgraded to artful on 2017-08-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay

2017-10-20 Thread Cleber Cassol

I believe I know what's happening: it looks like Ubuntu created a
virtual screen. If I put my mouse pointer to the right, it vanishes the
same way it does when there's a second monitor/screen attached to the
system. Don't know how it happened, though, since I haven't changed my
screen resolution or displays.

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't dislay

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

Bug description:
  When i click on system settings, icon is displaying but settings
  window doesn't visible. I have already reinstalled ubuntu desktop and
  gnome-control-center, but without any success.(reboot also didn't
  help).If i try to open gnome-control-center in terminal the same
  result only icon appearce

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

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

[Desktop-packages] [Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay

2017-10-20 Thread Cleber Cassol

I'm having the same problem. Started soon after I changed the dock
position from left to bottom. Have already tried to reinstall gnome-
control-center, but to no avail. Rebooting won't help either.

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

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't dislay

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

Bug description:
  When i click on system settings, icon is displaying but settings
  window doesn't visible. I have already reinstalled ubuntu desktop and
  gnome-control-center, but without any success.(reboot also didn't
  help).If i try to open gnome-control-center in terminal the same
  result only icon appearce

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

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

[Desktop-packages] [Bug 1725116] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-10-20 Thread grenouille

occurred during upgrade from 17.04 to 17.10 using update-manager.

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

Title:
  package cracklib-runtime 2.9.2-5build1 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  Confirmed

Bug description:
  Update to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-5build1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 19 21:36:09 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2012-04-02 (2026 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120328)
  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
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?)

** Changed in: gnome-shell
   Status: Incomplete => 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/1714989

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() (dash-to-panel specific?)

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1721821] Re: Kubuntu 17.10 freezes 50 seconds before KDE Plasma starts

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Kubuntu 17.10 freezes 50 seconds before KDE Plasma starts

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my Kubuntu 17.04 to 17.10 four days ago.

  My PC is booting fast: ~10 seconds to see the greeter. But when I
  connect to my Plasma session, the greeter is staying ~50 seconds at
  screen, before Plasma is starting (in ~10 more seconds). There was no
  problem before upgrading to Kubuntu 17.10.

  I connected to a terminal session just after having entered my
  password in the greeter, and I launched the htop command: all I can
  say is that there is no cpu eating process. The cpu is nearly idle
  during these 50 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: sddm 0.14.0-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct  6 18:13:42 2017
  InstallationDate: Installed on 2012-07-31 (1893 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  SourcePackage: sddm 0.14.0-4ubuntu1
  UpgradeStatus: Upgraded to artful on 2017-10-02 (3 days ago)

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

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

[Desktop-packages] [Bug 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile

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

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

Title:
  Bluetooth speaker used the HSP/HFP profile by default rather than the
  higher-quality A2DP profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 17.04
  Bluetooth device: 
https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1
 (itentifies itself as "C6")

  The above Bluetooth speaker paired and started streaming audio
  perfectly in Kubuntu 17.04. But the audio quality was poor, because
  the default audio profile was the low-quality HSP/HFP one. When I
  switched it to the A2DP profile, it sounded perfect again.

  Can we make A2DP the default playback profile for Bluetooth audio
  devices?

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

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

[Desktop-packages] [Bug 1725559] [NEW] 17.10 - multi-monitor screen positions are not saved

Public bug reported:

wayland, gnome-shell, 17.10, up-to-date system.

It seems my monitors.xml is not consulted on gdm launch/session launch,
either wayland or X.  I have two monitors, and I want to place one on
the right and one on the left.  This isn't working, I just get the
default sort, which, of course is wrong.

I've attached standard apport-collect information, I'm willing to debug
more, but it's just plain not working for me right now.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 21:23:53 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['world_clock@ailin.nemui', 
'system-monitor', 'system-moni...@paradoxxx.zero.gmail.com', 
'openweather-extens...@jenslody.de', 'sound-output-device-choo...@kgshank.net', 
'clipboard-indica...@tudmotu.com']"
 b'org.gnome.shell' b'favorite-apps' b"['terminator.desktop', 
'google-chrome.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2017-10-03 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful 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/1725559

Title:
  17.10 - multi-monitor screen positions are not saved

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  wayland, gnome-shell, 17.10, up-to-date system.

  It seems my monitors.xml is not consulted on gdm launch/session
  launch, either wayland or X.  I have two monitors, and I want to place
  one on the right and one on the left.  This isn't working, I just get
  the default sort, which, of course is wrong.

  I've attached standard apport-collect information, I'm willing to
  debug more, but it's just plain not working for me right now.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 21:23:53 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['world_clock@ailin.nemui', 
'system-monitor', 'system-moni...@paradoxxx.zero.gmail.com', 
'openweather-extens...@jenslody.de', 'sound-output-device-choo...@kgshank.net', 
'clipboard-indica...@tudmotu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['terminator.desktop', 
'google-chrome.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This error came up after setting the Arc theme via gnome tweak tool and 
rebooting.
  Fresh install of Ubuntu 17.10 running vanilla Gnome on X

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 20 22:47:17 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

2017-10-20 Thread diabloneo

I just upgraded from 17.04 to release version of 17.10, then I encounter
this problem, too. comment #6's method fixed this issue for me.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Desktop-packages] [Bug 1725555] [NEW] control-center display panel cannot move monitors

Public bug reported:

Running wayland, gnome-shell, 17.10, up-to-date.

I have two monitors plugged into my computer, a couple days ago,
everything was fine.  Now, after a couple of crashes, and package
upgrades, I can no longer re-arrange my monitors on the control center
interface.  When I mouse over a monitor, the cursor changes into a
grabby-hand, but when I click and drag, the monitors just stay where
they are.  No movement at all.

Things I've tried so far --

- removing .config/monitors.xml and rebooting
- disabling & re-enabling monitors

I'm happy to do some debugging on this, but my searches and
troubleshooting so far is coming up empty.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 21:03:06 2017
InstallationDate: Installed on 2017-10-03 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
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)

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

Title:
  control-center display panel cannot move monitors

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

Bug description:
  Running wayland, gnome-shell, 17.10, up-to-date.

  I have two monitors plugged into my computer, a couple days ago,
  everything was fine.  Now, after a couple of crashes, and package
  upgrades, I can no longer re-arrange my monitors on the control center
  interface.  When I mouse over a monitor, the cursor changes into a
  grabby-hand, but when I click and drag, the monitors just stay where
  they are.  No movement at all.

  Things I've tried so far --

  - removing .config/monitors.xml and rebooting
  - disabling & re-enabling monitors

  I'm happy to do some debugging on this, but my searches and
  troubleshooting so far is coming up empty.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 21:03:06 2017
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  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/ubuntu/+source/gnome-control-center/+bug/172/+subscriptions

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

[Desktop-packages] [Bug 1725169] Re: Black Screen after Upgrade from Kubuntu 17.04 to 17.10

2017-10-20 Thread Tom Kidman

Same problem here - booting kubuntu 17.10 using the new, default
'lowlatency' kernel led to a black screen. Manually selecting the
'generic' kernel via the advanced options in grub worked fine.  I've got
an nvidia 780 card.

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

Title:
  Black Screen after Upgrade from Kubuntu 17.04 to 17.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the
  same Result:

  After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'.
  This kernel does not work with the nvidia-grafic-card and lead to a black 
screen.

  After purging this kernel in a tty-session it booted up smothely.

  I think this can help many others.

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Oct 20 09:57:26 2017
  DistUpgraded: 2017-10-20 08:57:01,633 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti] 
[1458:362d]
  InstallationDate: Installed on 2016-12-23 (300 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 062a:4102 Creative Labs 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=99e6e2ce-07c5-4553-be22-2ccd3c3a73cc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22d
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22d:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z170X-Gaming 3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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

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

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

[Desktop-packages] [Bug 1725169] Re: Black Screen after Upgrade from Kubuntu 17.04 to 17.10

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

Title:
  Black Screen after Upgrade from Kubuntu 17.04 to 17.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the
  same Result:

  After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'.
  This kernel does not work with the nvidia-grafic-card and lead to a black 
screen.

  After purging this kernel in a tty-session it booted up smothely.

  I think this can help many others.

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Oct 20 09:57:26 2017
  DistUpgraded: 2017-10-20 08:57:01,633 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti] 
[1458:362d]
  InstallationDate: Installed on 2016-12-23 (300 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 062a:4102 Creative Labs 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=99e6e2ce-07c5-4553-be22-2ccd3c3a73cc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22d
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22d:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z170X-Gaming 3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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

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

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

[Desktop-packages] [Bug 1725549] Re: Crash on resume with multiple monitors

Installed package versions

dpb@aries:~[0]$ dpkg -l |grep gnome-shell
ii  chrome-gnome-shell 9-0ubuntu1   
   all  GNOME Shell extensions integration for web browsers
ii  gnome-shell3.26.1-0ubuntu4  
   amd64graphical shell for the GNOME desktop
ii  gnome-shell-common 3.26.1-0ubuntu4  
   all  common files for the GNOME graphical shell
ii  gnome-shell-extension-appindicator 17.10.1  
   all  App indicators for GNOME Shell
ii  gnome-shell-extension-move-clock   1.01-1   
   all  move clock extension for GNOME shell
ii  gnome-shell-extension-system-monitor   32-3 
   all  Display system information in GNOME Shell status bar
ii  gnome-shell-extension-ubuntu-dock  0.7  
   all  Ubuntu Dock for GNOME Shell
dpb@aries:~[0]$ dpkg -l |grep wayland
ii  libwayland-client0:amd64   1.14.0-1 
   amd64wayland compositor infrastructure - client library
ii  libwayland-cursor0:amd64   1.14.0-1 
   amd64wayland compositor infrastructure - cursor library
ii  libwayland-egl1-mesa:amd64 17.2.2-0ubuntu1  
   amd64implementation of the Wayland EGL platform -- runtime
ii  libwayland-server0:amd64   1.14.0-1 
   amd64wayland compositor infrastructure - server library
ii  xwayland   2:1.19.5-0ubuntu2
   amd64Xwayland X server
dpb@aries:~[0]$ dpkg -l |grep mutter
ii  gir1.2-mutter-1:amd64  3.26.1-2ubuntu1  
   amd64GObject introspection data for Mutter
ii  libmutter-1-0:amd643.26.1-2ubuntu1  
   amd64window manager library from the Mutter window manager
ii  mutter 3.26.1-2ubuntu1  
   amd64lightweight GTK+ window manager
ii  mutter-common  3.26.1-2ubuntu1  
   all  shared files for the Mutter window manager
dpb@aries:~[0]$ uname -a
Linux aries 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
dpb@aries:~[0]$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful

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

Title:
  Crash on resume with multiple monitors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm resuming from suspend with multiple monitors attached, and
  occasionally I get a crash of gnome-shell.  Will attach the core file

 PID: 1349 (gnome-shell)
 UID: 1000 (dpb)
 GID: 1000 (dpb)
  Signal: 8 (FPE)
   Timestamp: Fri 2017-10-20 20:24:01 MDT (8min ago)
Command Line: /usr/bin/gnome-shell
  Executable: /usr/bin/gnome-shell
   Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
   Slice: user-1000.slice
 Session: 2
   Owner UID: 1000 (dpb)
 Boot ID: 10e0e8b9f3bc4937a94e4f4cbae411d2
  Machine ID: 58b9ae27536a4e6bb76f4f1b9c561651
Hostname: aries
 Storage: 
/var/lib/systemd/coredump/core.gnome-shell.1000.10e0e8b9f3bc4937a94e4f4cbae411d2.1349.150855264100.lz4
 Message: Process 1349 (gnome-shell) of user 1000 dumped core.
  
  Stack trace of thread 1349:
  #0  0x7f7e5fd30450 n/a (libmutter-1.so.0)
  #1  0x7f7e5fcfb683 meta_window_move_resize_internal 
(libmutter-1.so.0)
  #2  0x7f7e617d16ad g_slist_foreach (libglib-2.0.so.0)
  #3  0x7f7e5fced114 meta_screen_foreach_window 
(libmutter-1.so.0)
  #4  0x7f7e5fcefc86 n/a (libmutter-1.so.0)
  #5  0x7f7e61a8bf9d g_closure_invoke (libgobject-2.0.so.0)
  #6  0x7f7e61a9ecde n/a (libgobject-2.0.so.0)
  #7  0x7f7e61aa74b5 g_signal_emit_valist 
(libgobject-2.0.so.0)
  #8  0x7f7e61aa7ecf g_signal_emit (libgobject-2.0.so.0)
  #9  0x7f7e5fcb2e3d n/a (libmutter-1.so.0)
  #10 0x7f7e5fcb5187 meta_monitor_manager_rebuild 
(libmutter-1.so.0)
  #11 0x7f7e5fd3a132 n/a (libmutter-1.so.0)
  #12 0x7f7e5fcb2e7c n/a

[Desktop-packages] [Bug 1725549] Re: Crash on resume with multiple monitors

core file

** Attachment added: "core.1.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725549/+attachment/4980795/+files/core.1.xz

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

Title:
  Crash on resume with multiple monitors

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm resuming from suspend with multiple monitors attached, and
  occasionally I get a crash of gnome-shell.  Will attach the core file

 PID: 1349 (gnome-shell)
 UID: 1000 (dpb)
 GID: 1000 (dpb)
  Signal: 8 (FPE)
   Timestamp: Fri 2017-10-20 20:24:01 MDT (8min ago)
Command Line: /usr/bin/gnome-shell
  Executable: /usr/bin/gnome-shell
   Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
   Slice: user-1000.slice
 Session: 2
   Owner UID: 1000 (dpb)
 Boot ID: 10e0e8b9f3bc4937a94e4f4cbae411d2
  Machine ID: 58b9ae27536a4e6bb76f4f1b9c561651
Hostname: aries
 Storage: 
/var/lib/systemd/coredump/core.gnome-shell.1000.10e0e8b9f3bc4937a94e4f4cbae411d2.1349.150855264100.lz4
 Message: Process 1349 (gnome-shell) of user 1000 dumped core.
  
  Stack trace of thread 1349:
  #0  0x7f7e5fd30450 n/a (libmutter-1.so.0)
  #1  0x7f7e5fcfb683 meta_window_move_resize_internal 
(libmutter-1.so.0)
  #2  0x7f7e617d16ad g_slist_foreach (libglib-2.0.so.0)
  #3  0x7f7e5fced114 meta_screen_foreach_window 
(libmutter-1.so.0)
  #4  0x7f7e5fcefc86 n/a (libmutter-1.so.0)
  #5  0x7f7e61a8bf9d g_closure_invoke (libgobject-2.0.so.0)
  #6  0x7f7e61a9ecde n/a (libgobject-2.0.so.0)
  #7  0x7f7e61aa74b5 g_signal_emit_valist 
(libgobject-2.0.so.0)
  #8  0x7f7e61aa7ecf g_signal_emit (libgobject-2.0.so.0)
  #9  0x7f7e5fcb2e3d n/a (libmutter-1.so.0)
  #10 0x7f7e5fcb5187 meta_monitor_manager_rebuild 
(libmutter-1.so.0)
  #11 0x7f7e5fd3a132 n/a (libmutter-1.so.0)
  #12 0x7f7e5fcb2e7c n/a (libmutter-1.so.0)
  #13 0x7f7e5fcb3e99 meta_monitor_manager_ensure_configured 
(libmutter-1.so.0)
  #14 0x7f7e5b710e18 ffi_call_unix64 (libffi.so.6)
  #15 0x7f7e5b71087a ffi_call (libffi.so.6)
  #16 0x7f7e61a8c799 g_cclosure_marshal_generic 
(libgobject-2.0.so.0)
  #17 0x7f7e61a8bf9d g_closure_invoke (libgobject-2.0.so.0)
  #18 0x7f7e61a9ecde n/a (libgobject-2.0.so.0)
  #19 0x7f7e61aa74b5 g_signal_emit_valist 
(libgobject-2.0.so.0)
  #20 0x7f7e61aa7ecf g_signal_emit (libgobject-2.0.so.0)
  #21 0x7f7e541429d4 n/a (libgudev-1.0.so.0)
  #22 0x7f7e617b2e25 g_main_context_dispatch 
(libglib-2.0.so.0)
  #23 0x7f7e617b31f0 n/a (libglib-2.0.so.0)
  #24 0x7f7e617b3502 g_main_loop_run (libglib-2.0.so.0)
  #25 0x7f7e5fce868c meta_run (libmutter-1.so.0)
  #26 0x563b4961e2e7 n/a (gnome-shell)
  #27 0x7f7e5f67a1c1 __libc_start_main (libc.so.6)
  #28 0x563b4961e3fa n/a (gnome-shell)
  
  Stack trace of thread 1391:
  #0  0x7f7e5f761901 __GI___poll (libc.so.6)
  #1  0x7f7e39188451 n/a (libpulse.so.0)
  #2  0x7f7e39179e10 pa_mainloop_poll (libpulse.so.0)
  #3  0x7f7e3917a4a0 pa_mainloop_iterate (libpulse.so.0)
  #4  0x7f7e3917a530 pa_mainloop_run (libpulse.so.0)
  #5  0x7f7e39188399 n/a (libpulse.so.0)
  #6  0x7f7e38f29ed8 n/a (libpulsecommon-10.0.so)
  #7  0x7f7e5fa407fc start_thread (libpthread.so.0)
  #8  0x7f7e5f76db0f __clone (libc.so.6)
  
  Stack trace of thread 1394:
  #0  0x7f7e5fa47072 futex_wait_cancelable (libpthread.so.0)
  #1  0x7f7e582f4864 n/a (libmozjs-52.so.0)
  #2  0x7f7e582f4ab5 n/a (libmozjs-52.so.0)
  #3  0x7f7e586ead15 n/a (libmozjs-52.so.0)
  #4  0x7f7e5870b352 n/a (libmozjs-52.so.0)
  #5  0x7f7e5fa407fc start_thread (libpthread.so.0)
  #6  0x7f7e5f76db0f __clone (libc.so.6)
  
  Stack trace of thread 1352:
  #0  0x7f7e5f761901 __GI___poll (libc.so.6)
  #1  0x7f7e617b3169 n/a (libglib-2.0.so.0)
  #2

[Desktop-packages] [Bug 1722298] Re: keyboard autorepeat not happening when I hold down any key

2017-10-20 Thread Alessandro Stamatto

I'm having the same problem, following Marius Tip theres one Input
Device that keeps repeating events. Is this normal? It's really
annoying, it interrupts all key holdings (even the arrow ones, ugh). The
device that keeps repeating the events, and the repeated events:

/dev/input/event9:  PEAQ WMI hotkeys

E: 0.01 0001 00d5 0001  # EV_KEY / KEY_SOUND1
E: 0.01     #  SYN_REPORT (0) -- +0ms
E: 0.17 0001 00d5   # EV_KEY / KEY_SOUND0
E: 0.17     #  SYN_REPORT (0) -- +0ms
E: 0.768001 0001 00d5 0001  # EV_KEY / KEY_SOUND1
E: 0.768001     #  SYN_REPORT (0) -- +768ms
E: 0.768017 0001 00d5   # EV_KEY / KEY_SOUND0
E: 0.768017     #  SYN_REPORT (0) -- +0ms
E: 1.535971 0001 00d5 0001  # EV_KEY / KEY_SOUND1
E: 1.535971     #  SYN_REPORT (0) -- +767ms
E: 1.535988 0001 00d5   # EV_KEY / KEY_SOUND0
E: 1.535988     #  SYN_REPORT (0) -- +0ms
E: 2.303989 0001 00d5 0001  # EV_KEY / KEY_SOUND1
E: 2.303989     #  SYN_REPORT (0) -- +768ms
E: 2.304007 0001 00d5   # EV_KEY / KEY_SOUND0
E: 2.304007     #  SYN_REPORT (0) -- +1ms

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

Title:
  keyboard autorepeat not happening when I hold down any key

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  The failure to auto repeat happens in all terminal apps I've tried in
  Artful. If I open a virtual console, it looks like a phantom is typing
  ^@ about once per second. This prevents successfully typing a
  password, and is probably what is breaking autorepeat in the GUI
  terminals, although they don't show the ^@.  Gnome terminal and guake
  also can't stay scrolled up in the buffer for more than a second
  before popping back down to the bottom.

  This problem happens in the Ubuntu desktop or Gnome and it doesn't
  matter if I pick the xorg or default Wayland options. It happens under
  both the open source and proprietary nvidia drivers. It also happens
  with a newly created user with no home directory baggage.

  xev reports a constant stream of the following about the same frequency as 
the ^@ in console:
  KeyPress event, serial 62, synthetic NO, window 0x381,
  root 0x1dd, subw 0x0, time 2243032, (20,-13), root:(1375,501),
  state 0x10, keycode 221 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  
  If I boot into a recovery shell, the problem does _not_ appear. 

  My system was built with a fresh install of 17.04, installed my usual
  packages, then upgrade to 17.10 when the problem began. I'm certain it
  was not present in 17.04 for the few days before I upgraded. There
  were similar bugs reported a decade ago, but didn't help me.

  Expectation: Hold down any key in terminal window. After a moment, the
  letter should repeat until key is released.

  Actually: Key will repeat 0 or a few times, but stop repeating before
  I release the key.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Oct  9 10:43:56 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago)

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

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

[Desktop-packages] [Bug 1725487] Re: ubuntu.css styling issues - hot corner ripple box

See bugs

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725545 (user
avatar)

and

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725546
(login background)

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

Title:
  ubuntu.css styling issues - hot corner ripple box

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
  hot-corner' as true, the colour of the ripple is still blue (Adwaita
  default scheme) since the compiled shell theme still uses the
  specified asset resource:///org/gnome/shell/theme/corner-ripple-
  ltr.png - this is also valid for the rtl asset.

  I have solved the issue by appending an override to match the current
  ubuntu.css overrides as follows:

  .ripple-box {
    border-radius: 0px 0px 64px 0px !important;
    background: #e95420 !important;
    width:64px !important;
    height:64px !important;
  }

  .ripple-box:rtl {
    border-radius: 0px 0px 0px 64px !important;
    background: #e95420 !important;
    width:64px !important;
    height:64px !important;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:25:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1725487/+subscriptions

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

[Desktop-packages] [Bug 1725546] [NEW] ubuntu.css styling issues - gdm login background inconsistency

Public bug reported:

An important factor in staying consistent with the overall aesthetics of
the ubuntu design language would be to disable the use of the noise
texture on gdm to provide a seamless transition from the plymouth boot
splash onto the gdm login. Here is the override provided to fix the
inconsistency in ubuntu.css under the gnome-shell themes directory:

#lockDialogGroup {
  background: #2c001e !important;
}

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 22:23:07 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ubuntu.css styling issues - gdm login background inconsistency

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  An important factor in staying consistent with the overall aesthetics
  of the ubuntu design language would be to disable the use of the noise
  texture on gdm to provide a seamless transition from the plymouth boot
  splash onto the gdm login. Here is the override provided to fix the
  inconsistency in ubuntu.css under the gnome-shell themes directory:

  #lockDialogGroup {
    background: #2c001e !important;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 22:23:07 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1725546/+subscriptions

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

[Desktop-packages] [Bug 1725549] [NEW] Crash on resume with multiple monitors

Public bug reported:

I'm resuming from suspend with multiple monitors attached, and
occasionally I get a crash of gnome-shell.  Will attach the core file

   PID: 1349 (gnome-shell)
   UID: 1000 (dpb)
   GID: 1000 (dpb)
Signal: 8 (FPE)
 Timestamp: Fri 2017-10-20 20:24:01 MDT (8min ago)
  Command Line: /usr/bin/gnome-shell
Executable: /usr/bin/gnome-shell
 Control Group: /user.slice/user-1000.slice/session-2.scope
  Unit: session-2.scope
 Slice: user-1000.slice
   Session: 2
 Owner UID: 1000 (dpb)
   Boot ID: 10e0e8b9f3bc4937a94e4f4cbae411d2
Machine ID: 58b9ae27536a4e6bb76f4f1b9c561651
  Hostname: aries
   Storage: 
/var/lib/systemd/coredump/core.gnome-shell.1000.10e0e8b9f3bc4937a94e4f4cbae411d2.1349.150855264100.lz4
   Message: Process 1349 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 1349:
#0  0x7f7e5fd30450 n/a (libmutter-1.so.0)
#1  0x7f7e5fcfb683 meta_window_move_resize_internal 
(libmutter-1.so.0)
#2  0x7f7e617d16ad g_slist_foreach (libglib-2.0.so.0)
#3  0x7f7e5fced114 meta_screen_foreach_window 
(libmutter-1.so.0)
#4  0x7f7e5fcefc86 n/a (libmutter-1.so.0)
#5  0x7f7e61a8bf9d g_closure_invoke (libgobject-2.0.so.0)
#6  0x7f7e61a9ecde n/a (libgobject-2.0.so.0)
#7  0x7f7e61aa74b5 g_signal_emit_valist 
(libgobject-2.0.so.0)
#8  0x7f7e61aa7ecf g_signal_emit (libgobject-2.0.so.0)
#9  0x7f7e5fcb2e3d n/a (libmutter-1.so.0)
#10 0x7f7e5fcb5187 meta_monitor_manager_rebuild 
(libmutter-1.so.0)
#11 0x7f7e5fd3a132 n/a (libmutter-1.so.0)
#12 0x7f7e5fcb2e7c n/a (libmutter-1.so.0)
#13 0x7f7e5fcb3e99 meta_monitor_manager_ensure_configured 
(libmutter-1.so.0)
#14 0x7f7e5b710e18 ffi_call_unix64 (libffi.so.6)
#15 0x7f7e5b71087a ffi_call (libffi.so.6)
#16 0x7f7e61a8c799 g_cclosure_marshal_generic 
(libgobject-2.0.so.0)
#17 0x7f7e61a8bf9d g_closure_invoke (libgobject-2.0.so.0)
#18 0x7f7e61a9ecde n/a (libgobject-2.0.so.0)
#19 0x7f7e61aa74b5 g_signal_emit_valist 
(libgobject-2.0.so.0)
#20 0x7f7e61aa7ecf g_signal_emit (libgobject-2.0.so.0)
#21 0x7f7e541429d4 n/a (libgudev-1.0.so.0)
#22 0x7f7e617b2e25 g_main_context_dispatch 
(libglib-2.0.so.0)
#23 0x7f7e617b31f0 n/a (libglib-2.0.so.0)
#24 0x7f7e617b3502 g_main_loop_run (libglib-2.0.so.0)
#25 0x7f7e5fce868c meta_run (libmutter-1.so.0)
#26 0x563b4961e2e7 n/a (gnome-shell)
#27 0x7f7e5f67a1c1 __libc_start_main (libc.so.6)
#28 0x563b4961e3fa n/a (gnome-shell)

Stack trace of thread 1391:
#0  0x7f7e5f761901 __GI___poll (libc.so.6)
#1  0x7f7e39188451 n/a (libpulse.so.0)
#2  0x7f7e39179e10 pa_mainloop_poll (libpulse.so.0)
#3  0x7f7e3917a4a0 pa_mainloop_iterate (libpulse.so.0)
#4  0x7f7e3917a530 pa_mainloop_run (libpulse.so.0)
#5  0x7f7e39188399 n/a (libpulse.so.0)
#6  0x7f7e38f29ed8 n/a (libpulsecommon-10.0.so)
#7  0x7f7e5fa407fc start_thread (libpthread.so.0)
#8  0x7f7e5f76db0f __clone (libc.so.6)

Stack trace of thread 1394:
#0  0x7f7e5fa47072 futex_wait_cancelable (libpthread.so.0)
#1  0x7f7e582f4864 n/a (libmozjs-52.so.0)
#2  0x7f7e582f4ab5 n/a (libmozjs-52.so.0)
#3  0x7f7e586ead15 n/a (libmozjs-52.so.0)
#4  0x7f7e5870b352 n/a (libmozjs-52.so.0)
#5  0x7f7e5fa407fc start_thread (libpthread.so.0)
#6  0x7f7e5f76db0f __clone (libc.so.6)

Stack trace of thread 1352:
#0  0x7f7e5f761901 __GI___poll (libc.so.6)
#1  0x7f7e617b3169 n/a (libglib-2.0.so.0)
#2  0x7f7e617b3502 g_main_loop_run (libglib-2.0.so.0)
#3  0x7f7e61d9cb26 n/a (libgio-2.0.so.0)
#4  0x7f7e617da645 n/a (libglib-2.0.so.0)
#5  0x7f7e5fa407fc start_thread (libpthread.so.0)
#6  0x7f7e5f76db0f __clone (libc.so.6)

Stack trace of thread 28678:
#0  0x7f7e5f7679f9 syscall (libc.so.6)
#1  0x7f7e617f880a g_cond_wait_until (libglib-2.0.so.0)
#2  0x7f7e617872e1 n/a (libglib-2.0.so.0)

[Desktop-packages] [Bug 1725545] [NEW] ubuntu.css styling issues - gdm user avatar alignment

Public bug reported:


The gdm login avatar vertical alignment alignment is off by a couple of
pixels and can be easily fixed by correcting the user icon margin setup
like so using an override in ubuntu.css in the gnome-shell themes
directory:

.framed-user-icon {
  margin: 4px 0px 0px 2px !important;
  padding: 0px 0px 0px 0px !important;
}

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 22:19:00 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ubuntu.css styling issues - gdm user avatar alignment

Status in gnome-shell package in Ubuntu:
  New

Bug description:

  The gdm login avatar vertical alignment alignment is off by a couple
  of pixels and can be easily fixed by correcting the user icon margin
  setup like so using an override in ubuntu.css in the gnome-shell
  themes directory:

  .framed-user-icon {
    margin: 4px 0px 0px 2px !important;
    padding: 0px 0px 0px 0px !important;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 22:19:00 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1725545/+subscriptions

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

[Desktop-packages] [Bug 1725487] Re: ubuntu.css styling issues - hot corner ripple box

** Summary changed:

- ubuntu.css styling issues
+ ubuntu.css styling issues - hot corner ripple box

** Description changed:

  Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
  hot-corner' as true, the colour of the ripple is still blue (Adwaita
  default scheme) since the compiled shell theme still uses the specified
  asset resource:///org/gnome/shell/theme/corner-ripple-ltr.png - this is
  also valid for the rtl asset.
  
  I have solved the issue by appending an override to match the current
  ubuntu.css overrides as follows:
  
  .ripple-box {
-   border-radius: 0px 0px 64px 0px !important;
-   background: #e95420 !important;
-   width:64px !important;
-   height:64px !important;
+   border-radius: 0px 0px 64px 0px !important;
+   background: #e95420 !important;
+   width:64px !important;
+   height:64px !important;
  }
  
  .ripple-box:rtl {
-   border-radius: 0px 0px 0px 64px !important;
-   background: #e95420 !important;
-   width:64px !important;
-   height:64px !important;
- }
- 
- The gdm login avatar alignment is also off by a couple of pixels and can
- be easily fixed by correcting the user icon margin setup like so:
- 
- .framed-user-icon {
-   margin: 4px 0px 0px 2px !important;
-   padding: 0px 0px 0px 0px !important;
- }
- 
- Another important factor in staying consistent with the overall
- aesthetics of the ubuntu design language would be to disable the use of
- the noise texture on gdm to provide a seamless transition from the
- plymouth boot splash onto the gdm login. Here is the override:
- 
- #lockDialogGroup {
-   background: #2c001e !important;
+   border-radius: 0px 0px 0px 64px !important;
+   background: #e95420 !important;
+   width:64px !important;
+   height:64px !important;
  }
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:25:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ubuntu.css styling issues - hot corner ripple box

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
  hot-corner' as true, the colour of the ripple is still blue (Adwaita
  default scheme) since the compiled shell theme still uses the
  specified asset resource:///org/gnome/shell/theme/corner-ripple-
  ltr.png - this is also valid for the rtl asset.

  I have solved the issue by appending an override to match the current
  ubuntu.css overrides as follows:

  .ripple-box {
    border-radius: 0px 0px 64px 0px !important;
    background: #e95420 !important;
    width:64px !important;
    height:64px !important;
  }

  .ripple-box:rtl {
    border-radius: 0px 0px 0px 64px !important;
    background: #e95420 !important;
    width:64px !important;
    height:64px !important;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:25:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1725487/+subscriptions

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

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

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 17.10

  I was having a problem with my Focaltech touchpad on my Asus laptop -
  the right click didn't work.

  https://bugs.launchpad.net/bugs/1725210

  Title:
Focaltech touchpad right click doesn't work

  Alexander Browne from the bug team said "AFAIK 17.10 is the first release to 
use the libinput touchpad driver by
  default and drop the synaptics driver, but synaptics stills works if you
  install it (or upgrade from an install that had it like my current
  system). So try installing synaptics

  sudo apt install xserver-xorg-input-synaptics

  and reboot."

  I did this and I got this new bug.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Oct 21 10:31:20 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1724307] Re: Mouse cursor flickers when using external DisplayLink monitor

2017-10-20 Thread Wei Cai

Hi all,

I have the exact same issue on my primary monitor.

Alienware Alpha R2
Primary monitor connected to Nvidia GTX 960
Secondary monitor connected to Startech USB32HD4K (Displaylink Driver)
Ubuntu 16.04.3 LTS

One interesting thing I noticed is that if you set rotation in "All
Settings"->"Screen Display" to "Clockwise", "Anti-clockwise" or "180
degrees" (just not "Normal"), this issue disappeared.

This my workaround currently.

Dont know if this helps.

Cheers

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

Title:
  Mouse cursor flickers when using external DisplayLink monitor

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  When I connect my laptop to my DisplayLink based device with USB
  (Wavlink universal USB 3.0 docking station
  https://www.wavlink.com/en/product/150 WL-UG39DK1V), and connect the
  Wavlink to my AOC E2775SJ Monitor via HDMI, the mouse icon flickers.
  Only if the mouse is on the laptop monitor, it can vanish for several
  minutes, but remains active.

  Animations/overlays or typing inside a Chrome window causes the mouse
  pointer to flicker more often. If there is no interaction or
  animation, the mouse pointer remains static and drawn.

  Monitor 1: 1920 x 1080 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - DisplayLink (USB) connected AOC E2775SJ Monitor

  This issue doesn't happen if I don't connect my laptop to an external
  monitor via the Wavlink device.

  This issue is reproducible with DisplayLink driver 1.4, and 1.3.54.

  This issue is reproducible with Ubuntu 16.04, 17.04, and 17.10 x64.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Oct 17 10:01:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:082a]
  InstallationDate: Installed on 2017-10-16 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.1
  dmi.board.name: 05FPM2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.1:bd08/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05FPM2:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.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: Tue Oct 17 09:39:15 2017
  xserver.configfile: default
  xserver.errors: modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5193
   vendor SHP
  xserver.version: 2:1.19.3-1ubuntu1~16.04.3

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

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

[Desktop-packages] [Bug 1725534] Re: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1716208
   epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()

Status in epiphany-browser package in Ubuntu:
  New

Bug description:
  After the first restart after upgrading from Ubuntu Gnome 17.04 to
  Ubuntu 17.10 I got this crash report.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 20 20:21:06 2017
  ExecutablePath: /usr/lib/epiphany-search-provider
  InstallationDate: Installed on 2017-04-07 (196 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  ProcCmdline: /usr/lib/epiphany-search-provider
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f2d35869e30 :   mov
%rbp,(%rax)
   PC (0x7f2d35869e30) ok
   source "%rbp" ok
   destination "(%rax)" (0x0005) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: epiphany-browser
  StacktraceTop:
   wl_list_insert_list () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
   () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
   wl_display_destroy () at /usr/lib/x86_64-linux-gnu/libwayland-server.so.0
   () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   () at /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
  Title: epiphany-search-provider crashed with SIGSEGV in wl_list_insert_list()
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Description changed:

- This seems to be the same problem as described in bug #1636262, only
- this time it happened during upgrade from 16.10 to 17.04. The setup
- process (do-release-upgrade -d) aborted and I had to finish it manually.
+ [Impact]
+ Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.
  
- ProblemType: Package
- DistroRelease: Ubuntu 17.04
+ [Test Case]
+ While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.
+ 
+ Test A
+ --
+ 1) Install cracklib-runtime from -proposed.
+ 2) Reinstall dictionaires-common and verify that the trigger is called
+ 
+ Test B
+ --
+ 1) With the version of cracklib-runtime from -proposed installed confirm that 
a distribution upgrade to next supported release succeeds.
+ 
+ Test C
+ --
+ 1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.
+ 
+ [Regression Potential]
+ It's possible that upgrades will break hence all the regression tests in the 
Test Case.
+ 
+ Original Description
+ 
+ This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.
+ 
+ ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
-  dpkg 1.18.10ubuntu1
-  apt  1.4
- SourcePackage: cracklib2
+  dpkg 1.18.10ubuntu1
+  apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Triaged
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  Upgrading cracklib-runtime is not working for some systems due to trigger 
cycles. This is making distribution upgrades challenging.

  [Test Case]
  While we haven't been able to replicate this directly the following tests 
will confirm that there are no regressions.

  Test A
  --
  1) Install cracklib-runtime from -proposed.
  2) Reinstall dictionaires-common and verify that the trigger is called

  Test B
  --
  1) With the version of cracklib-runtime from -proposed installed confirm that 
a distribution upgrade to next supported release succeeds.

  Test C
  --
  1) Test a release upgrade from an affected release (Trusty, Xenial) to the 
next supported release (Xenial, Zesty) with -proposed enabled. To do this 
upgrade you'll need to edit /etc/apt/sources.list to the target release and run 
'sudo apt-get dist-upgrade' as ubuntu-release-upgrader will disable -proposed.

  [Regression Potential]
  It's possible that upgrades will break hence all the regression tests in the 
Test Case.

  Original Description
  
  This seems to be the same problem as described in bug #1636262, only this 
time it happened during upgrade from 16.10 to 17.04. The setup process 
(do-release-upgrade -d) aborted and I had to finish it manually.

  ProblemType: PackageDistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4SourcePackage: cracklib2
  Title: package cracklib-runtime

[Desktop-packages] [Bug 1725533] Re: gvfsd-mtp crashed with SIGSEGV

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  Intentando instalar netbeans.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 19:35:17 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/14
  ProcEnviron:
   LANG=es_PE.UTF-8
   LANGUAGE=es_PE:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fbfd91ea5a9:mov0x18(%rax),%rax
   PC (0x7fbfd91ea5a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1725532] [NEW] wired network ignores auto connect setting and does not auto connect

2017-10-20 Thread Scott Palmer

Public bug reported:

My onboard Intel network adapter has [X] Connect automatically but when
I start my Gnome session, I always have to tell it to Connect which it
does without error.

You can't see it in the Gnome dialog windows but this connection is set
to also connect to a VPN.  I setup this connection with nm-connection-
editor.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager-gnome 1.8.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:26:18 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-03 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug artful

** Tags removed: wayland-session

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

Title:
  wired network ignores auto connect setting and does not auto connect

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

Bug description:
  My onboard Intel network adapter has [X] Connect automatically but
  when I start my Gnome session, I always have to tell it to Connect
  which it does without error.

  You can't see it in the Gnome dialog windows but this connection is
  set to also connect to a VPN.  I setup this connection with nm-
  connection-editor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:26:18 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-03 (17 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1725528] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Tags removed: need-duplicate-check

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

Title:
  package cracklib-runtime 2.9.2-5build1 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  Trying to upgrade to 17.10, on 21 Oct 2017.
  I experienced this error on both my machines - a 2007 intel iMac & a 2016 
Zenbook.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-5build1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 10:46:50 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-09 (11 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1720768] Re: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subpr

2017-10-20 Thread Treviño

Extensions installed?

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

Title:
  gnome-shell crashed with SIGTRAP in object_instance_finalize from
  js::Class::doFinalize ["Finalizing proxy for an object that's
  scheduled to be unrooted: Gio.Subprocess\n"]

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  Logged in with one new user, switched to login under another account.
  Was logged in for a few moments then got kicked out - session crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  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: GNOME-Greeter:GNOME
  Date: Mon Oct  2 10:39:27 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-08-02 (60 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

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

2017-10-20 Thread Seth Arnold

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

** Information type changed from Public Security to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Error just came up, multiple times.  Could not see any faults in
  appearance or operation so reported it and requested that it not
  appear again.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 20 11:08:31 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1725385] Re: one

2017-10-20 Thread Seth Arnold

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

Title:
  one

Status in xorg package in Ubuntu:
  New

Bug description:
  no further information

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic i686
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  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 Oct 20 18:21:34 2017
  DistUpgraded: 2017-10-13 20:50:46,659 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, i686: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-97-generic, i686: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-98-generic, i686: installed
   ndiswrapper, 1.60, 4.4.0-97-generic, i686: installed
   ndiswrapper, 1.60, 4.4.0-98-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
 Subsystem: Dell RV620/M82 [Mobility Radeon HD 3450/3470] [1028:0254]
  InstallationDate: Installed on 2017-10-13 (7 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  MachineType: Dell Inc. Studio 1535
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=18271d74-75ec-4847-a14e-5541b0a44390 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-10-13 (6 days ago)
  XorgLogOld:
   
  dmi.bios.date: 07/02/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0F700C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/02/2008:svnDellInc.:pnStudio1535:pvr:rvnDellInc.:rn0F700C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Studio 1535
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Desktop-packages] [Bug 1725528] [NEW] package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-10-20 Thread clairepresto

Public bug reported:

Trying to upgrade to 17.10, on 21 Oct 2017.
I experienced this error on both my machines - a 2007 intel iMac & a 2016 
Zenbook.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: cracklib-runtime 2.9.2-5build1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 21 10:46:50 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-10-09 (11 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
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
SourcePackage: cracklib2
Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)

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


** Tags: amd64 apport-package artful need-duplicate-check

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

Title:
  package cracklib-runtime 2.9.2-5build1 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  Trying to upgrade to 17.10, on 21 Oct 2017.
  I experienced this error on both my machines - a 2007 intel iMac & a 2016 
Zenbook.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-5build1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sat Oct 21 10:46:50 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-10-09 (11 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: 
dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)

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

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

[Desktop-packages] [Bug 1725513] Re: HP hs3110 WWAN adapter not recognized

2017-10-20 Thread Michael von Glasow

PS: Debian apparently added the udev rules in usb-modeswitch-data,
version 20160803-1; see https://launchpad.net/debian/+source/usb-
modeswitch-data/+changelog.

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

Title:
  HP hs3110 WWAN adapter not recognized

Status in network-manager package in Ubuntu:
  New

Bug description:
  The HP hs3110 WWAN adapter is not recognized and does not work out of
  the box.

  The device is a rebranded Huawei MU736 but reports a different VID/PID
  pair (03f0:521d). With a few manual steps the device will work.

  Add the following two udev rules:

  # HP hs3110 (Huawei MU736)
  ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="usb_modeswitch '%b/%k'"
  ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="/bin/bash -c 'modprobe 
option && echo 03f0 521d > /sys/bus/usb-serial/drivers/option1/new_id'"

  After that, a PIN prompt appears on boot, the device appears in
  Network Manager and can be configured. Before a conection can be
  established, the following AT commands need to be sent to
  /dev/ttyUSB2:

  ATZ
  ATQ0 V1 E1 S0=0   +FCLASS=0
  AT+CGDCONT=1,"IP"

  (I’ve successfully automated this using wvdial and running it once
  manually before establishing a 3G connection.)

  After that, a 3G connection can be established.

  Would be great if this were supported out of the box, especially if
  sending the AT commands could be automated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct 21 02:15:58 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-09 (1045 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-01-24T03:17:24.095174
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

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

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I used "sudo systemctl stop gdm" to stop and restart gdm greeter after
  a config change and apport pops up and asks to report a crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Oct 20 15:03:00 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-19 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1725524] Re: gvfsd-mtp crashed with SIGSEGV

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  Solo reinicié el equipo.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 18:44:05 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/8
  ProcEnviron:
   LANG=es_PE.UTF-8
   LANGUAGE=es_PE:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fb904e795a9:mov0x18(%rax),%rax
   PC (0x7fb904e795a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Changed in: cracklib2 (Ubuntu Zesty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: cracklib2 (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: cracklib2 (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: cracklib2 (Ubuntu Xenial)
   Status: Incomplete => Triaged

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Triaged
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1720745] Re: connecting to a WPA-enterprise network from gnome-shell opens up the "Networks" panel instead of the Wi-Fi panel

** Changed in: gnome-control-center
   Status: Unknown => Fix Released

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

Title:
  connecting to a WPA-enterprise network from gnome-shell opens up the
  "Networks" panel instead of the Wi-Fi panel

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

Bug description:
  When selecting a WPA-ENTERPRISE Network for the first time, using gnome-shell 
"select network" popup, gnome-control-center is automatically started with the 
"Network" panel open.
  But in gnome 3.26's new control center this panel only lists Wired, Mobile 
Broadband, VPN connections and Network Proxy setup. 
  WiFi configuration has been moved to a separate "Wi-Fi" panel, which I think 
should be opened instead.

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

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

[Desktop-packages] [Bug 1722078] Re: When switching prime profiles to Intel & using kms for nvidia the ubuntu session is not available

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

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

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

Title:
  When switching prime profiles to Intel & using kms for nvidia the
  ubuntu session is not available

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

Bug description:
  Extended test case:
  Prerequisites: A laptop with nvidia hybrid gpu 
 Latest repo nvidia drivers installed (384
 Prime sync not yet enabled

  While on the nvidia driver profile boot up, login screen should only offer 
the xorg session.
  In nvidia-settings switch to Intel, restart (one must *always restart with 
gdm3*
  What happens: 
  At log in both the wayland & xorg session options are present (correct 
behavior

  Switch back to nvidia in nvidia-settings
  Enable prime sync (how below
  Restart 
  What happens:
  At login only the xorg session is presented (correct behavior

  Now again open nvidia-settings, switch to Intel
  Restart
  What happens:
  At log in only the xorg session is present (incorrect behavior
  What should happen:
  Both the wayland & xorg sessions should be present

  To enable prime sync:

  sudo nano /etc/modprobe.d/zz-nvidia-modeset.conf

  Insert this line, save:
  options nvidia_384_drm modeset=1

  Run
  sudo update-initramfs -u

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  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: Sun Oct  8 09:29:25 2017
  InstallationDate: Installed on 2017-10-06 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1722078] Re: When switching prime profiles to Intel & using kms for nvidia the ubuntu session is not available

2017-10-20 Thread QkiZ

I dont have Wayland session choice, even on Intel gfx card.

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

Title:
  When switching prime profiles to Intel & using kms for nvidia the
  ubuntu session is not available

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

Bug description:
  Extended test case:
  Prerequisites: A laptop with nvidia hybrid gpu 
 Latest repo nvidia drivers installed (384
 Prime sync not yet enabled

  While on the nvidia driver profile boot up, login screen should only offer 
the xorg session.
  In nvidia-settings switch to Intel, restart (one must *always restart with 
gdm3*
  What happens: 
  At log in both the wayland & xorg session options are present (correct 
behavior

  Switch back to nvidia in nvidia-settings
  Enable prime sync (how below
  Restart 
  What happens:
  At login only the xorg session is presented (correct behavior

  Now again open nvidia-settings, switch to Intel
  Restart
  What happens:
  At log in only the xorg session is present (incorrect behavior
  What should happen:
  Both the wayland & xorg sessions should be present

  To enable prime sync:

  sudo nano /etc/modprobe.d/zz-nvidia-modeset.conf

  Insert this line, save:
  options nvidia_384_drm modeset=1

  Run
  sudo update-initramfs -u

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  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: Sun Oct  8 09:29:25 2017
  InstallationDate: Installed on 2017-10-06 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1722078] Re: When switching prime profiles to Intel & using kms for nvidia the ubuntu session is not available

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

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

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

Title:
  When switching prime profiles to Intel & using kms for nvidia the
  ubuntu session is not available

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

Bug description:
  Extended test case:
  Prerequisites: A laptop with nvidia hybrid gpu 
 Latest repo nvidia drivers installed (384
 Prime sync not yet enabled

  While on the nvidia driver profile boot up, login screen should only offer 
the xorg session.
  In nvidia-settings switch to Intel, restart (one must *always restart with 
gdm3*
  What happens: 
  At log in both the wayland & xorg session options are present (correct 
behavior

  Switch back to nvidia in nvidia-settings
  Enable prime sync (how below
  Restart 
  What happens:
  At login only the xorg session is presented (correct behavior

  Now again open nvidia-settings, switch to Intel
  Restart
  What happens:
  At log in only the xorg session is present (incorrect behavior
  What should happen:
  Both the wayland & xorg sessions should be present

  To enable prime sync:

  sudo nano /etc/modprobe.d/zz-nvidia-modeset.conf

  Insert this line, save:
  options nvidia_384_drm modeset=1

  Run
  sudo update-initramfs -u

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-session (not installed)
  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: Sun Oct  8 09:29:25 2017
  InstallationDate: Installed on 2017-10-06 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171004)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1705951] Re: Ubuntu 17.10 freezes soon after login.

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

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

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

Title:
  Ubuntu 17.10 freezes soon after login.

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

Bug description:
  Edited 1: After some updates received, it freezes just after login,
  making any action impossible.

  
  I have a PC with a nVidia GeForce 6800XT graphics card. I installed ubuntu 
17.10 and have had many problems with crashes and freezes. After login, the 
normal screen appears, the screen flashes and the top bar disappears, flashes 
again and appears normal, but frozen. Clicking again blinks back to the login 
screen. In order to access the system I was forced to install GNOME Classic. I 
noticed that in ubuntu 17.04 and ubuntu GNOME 16.04 it works normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.agp.gpu:
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:8x 4x
   Registers:0xff000e1b:0x1f000302
  .proc.driver.nvidia.agp.host-bridge:
   Host Bridge:  PCI device 1106:0308
   Fast Writes:  Supported
   SBA:  Supported
   AGP Rates:8x 4x
   Registers:0x1f000a1b:0x0b02
  .proc.driver.nvidia.agp.status:
   Status:   Enabled
   Driver:   AGPGART
   AGP Rate: 8x
   Fast Writes:  Disabled
   SBA:  Enabled
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.135  Tue Jan 17 15:26:26 
PST 2017
   GCC version:  gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1)
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jul 23 18:13:59 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus: nvidia-304, 304.135, 4.11.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard: NVIDIA Corporation NV40 [GeForce 6800 XT] [10de:0048] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-07-17 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=7a3a72ab-cccf-4c14-97c3-1dcd85b1aca8 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:

  dmi.bios.date: 11/08/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5VDC-X
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0701:bd11/08/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5VDC-X:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.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: Sun Jul 23 18:12:42 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSleep Button KEYBOARD, id 8
   inputMicrosoft Basic Optical Mouse MOUSE, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log

[Desktop-packages] [Bug 1725513] [NEW] HP hs3110 WWAN adapter not recognized

2017-10-20 Thread Michael von Glasow

Public bug reported:

The HP hs3110 WWAN adapter is not recognized and does not work out of
the box.

The device is a rebranded Huawei MU736 but reports a different VID/PID
pair (03f0:521d). With a few manual steps the device will work.

Add the following two udev rules:

# HP hs3110 (Huawei MU736)
ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="usb_modeswitch '%b/%k'"
ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="/bin/bash -c 'modprobe 
option && echo 03f0 521d > /sys/bus/usb-serial/drivers/option1/new_id'"

After that, a PIN prompt appears on boot, the device appears in Network
Manager and can be configured. Before a conection can be established,
the following AT commands need to be sent to /dev/ttyUSB2:

ATZ
ATQ0 V1 E1 S0=0   +FCLASS=0
AT+CGDCONT=1,"IP"

(I’ve successfully automated this using wvdial and running it once
manually before establishing a 3G connection.)

After that, a 3G connection can be established.

Would be great if this were supported out of the box, especially if
sending the AT commands could be automated.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Oct 21 02:15:58 2017
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-12-09 (1045 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-01-24T03:17:24.095174
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

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

Title:
  HP hs3110 WWAN adapter not recognized

Status in network-manager package in Ubuntu:
  New

Bug description:
  The HP hs3110 WWAN adapter is not recognized and does not work out of
  the box.

  The device is a rebranded Huawei MU736 but reports a different VID/PID
  pair (03f0:521d). With a few manual steps the device will work.

  Add the following two udev rules:

  # HP hs3110 (Huawei MU736)
  ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="usb_modeswitch '%b/%k'"
  ATTR{idVendor}=="03f0", ATTR{idProduct}=="521d", RUN+="/bin/bash -c 'modprobe 
option && echo 03f0 521d > /sys/bus/usb-serial/drivers/option1/new_id'"

  After that, a PIN prompt appears on boot, the device appears in
  Network Manager and can be configured. Before a conection can be
  established, the following AT commands need to be sent to
  /dev/ttyUSB2:

  ATZ
  ATQ0 V1 E1 S0=0   +FCLASS=0
  AT+CGDCONT=1,"IP"

  (I’ve successfully automated this using wvdial and running it once
  manually before establishing a 3G connection.)

  After that, a 3G connection can be established.

  Would be great if this were supported out of the box, especially if
  sending the AT commands could be automated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct 21 02:15:58 2017
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-12-09 (1045 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-01-24T03:17:24.095174
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1288655] Re: terminal gets smaller when maximized and then restored

2017-10-20 Thread Egmont Koblinger

Ubuntu's gnome-terminal has patch, originating from Red Hat, with the
title "Extra padding around transparent terminals in Wayland". Just by
its name it's truly suspicious, but I don't have time now to verify if
that's causing this terrible look. Anyway, as said, it's probably
irrelevant.

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

Title:
  terminal gets smaller when maximized and then restored

Status in GNOME Terminal:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt 
+ T)
  2. "stty -a | grep rows" reports "rows 24; columns 80;"
  3. Maximize the window (by clicking on the maximize button, or double 
clicking the title bar, or dragging the window up to the panel)
  4. Do the same again to un-maximize the window
  5. Now "stty -a | grep rows" reports "rows 23; columns 79;"

  Each time I do this, the window keeps getting one character shorter
  and one character narrower!

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Mar  6 10:22:46 2014
  InstallationDate: Installed on 2010-04-15 (1421 days ago)
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago)

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

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

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

** Changed in: mutter
   Status: Unknown => Confirmed

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

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

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

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

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries

2017-10-20 Thread Gunnar Hjalmarsson

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

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

Title:
  Migrate to hunspell-en-us in libreoffice-dictionaries

Status in hunspell-en-us package in Ubuntu:
  New
Status in libreoffice-dictionaries package in Ubuntu:
  New
Status in scowl package in Ubuntu:
  New
Status in hunspell-en-us package in Debian:
  Fix Released
Status in libreoffice-dictionaries package in Debian:
  Won't Fix

Bug description:
  libreoffice-dictionaries upstream ships hunspell-en-us, which is
  properly maintained and is newer than the one currently in Debian and
  Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in
  libreoffice-dictionaries. The other English variants (British,
  Australian and others) are already provided by libreoffice-
  dictionaries and are more up-to-date than the US variant.

  Debian bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159

  Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff 
and en_US.dic but there is not a built package for them.
  
https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/

  See this README from the Libreoffice/dictionaries git,
  https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt

  It seems that this is now dead,
  https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hunspell-en-us 20070829-6ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 09:43:32 2017
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: hunspell-en-us
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+subscriptions

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

[Desktop-packages] [Bug 1725509] [NEW] Cannot uninstall aisleriot solitaire from "Software"

2017-10-20 Thread Javi

Public bug reported:

When I try to uninstall aisleriot solitaire from "Software", it is
impossible because that app is not listed in.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: aisleriot 1:3.22.2-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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 00:06:41 2017
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 PATH=(custom, no username)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: aisleriot
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Cannot uninstall aisleriot solitaire from "Software"

Status in aisleriot package in Ubuntu:
  New

Bug description:
  When I try to uninstall aisleriot solitaire from "Software", it is
  impossible because that app is not listed in.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: aisleriot 1:3.22.2-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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 00:06:41 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: aisleriot
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1288655] Re: terminal gets smaller when maximized and then restored

2017-10-20 Thread Egmont Koblinger

Geez... indeed. I can confirm that look with vte and gnome-terminal
Ubuntu packages. It looks awful.

I'm using vte and gnome-terminal from git (the rest is stock 17.10).
They don't have this visual problem, but the shrinkage is there. So
probably it's irrelevant.

Also, Ubuntu's vte & gnome-terminal packages look okay under Unity 7.

Not sure by the way if it's something that's been fixed in vte/g-t since
(I can't recall anything like that) or it's caused by an Ubuntu patch
(that would be my primary guess).

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

Title:
  terminal gets smaller when maximized and then restored

Status in GNOME Terminal:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt 
+ T)
  2. "stty -a | grep rows" reports "rows 24; columns 80;"
  3. Maximize the window (by clicking on the maximize button, or double 
clicking the title bar, or dragging the window up to the panel)
  4. Do the same again to un-maximize the window
  5. Now "stty -a | grep rows" reports "rows 23; columns 79;"

  Each time I do this, the window keeps getting one character shorter
  and one character narrower!

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Mar  6 10:22:46 2014
  InstallationDate: Installed on 2010-04-15 (1421 days ago)
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago)

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

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

[Desktop-packages] [Bug 1725227] Re: mission-control-5 crashed with signal 5 in g_object_new_valist()

2017-10-20 Thread Seth Arnold

** 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 telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1725227

Title:
  mission-control-5 crashed with signal 5 in g_object_new_valist()

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  fter upgrade from 16.04 to 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: telepathy-mission-control-5 1:5.16.4-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 20 02:03:43 2017
  ExecutablePath: /usr/lib/telepathy/mission-control-5
  InstallationDate: Installed on 2017-10-16 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  KernLog:
   
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=9bb2a796-4147-45c9-8e2b-460f44857d45 ro quiet splash vt.handoff=7
  Signal: 5
  SourcePackage: telepathy-mission-control-5
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? ()
  Title: mission-control-5 crashed with signal 5 in g_object_new_valist()
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1725227/+subscriptions

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

[Desktop-packages] [Bug 1725371] Re: 17.10 nautilus 3.26.0 fails to recognize mouse middle button to lower window

2017-10-20 Thread Scott Stensland

** Description changed:

  It's very handy to send any open Ubuntu application window to below all
- other open windows (it says open yet now occluded) by clicking mouse
+ other open windows (it stays open yet now occluded) by clicking mouse
  middle button on window title bar (opposite of left mouse click to bring
  to focus front) ... this works fine on all Ubuntu 17.10 applications
  except fails on Ubuntu 17.10's file explorer nautilus 3.26.0 which has a
  non-standard looking title bar.
  
  This behavior continues to be OK on all other 17.10 applications...
  Nautilus worked on previous Ubuntu releases  ... I hope other apps
  refrain from using this new window behavior
  
  Any ideas on why nautilus breaks this convention? Or how to fix it?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1: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
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Oct 20 10:53:51 2017
  InstallationDate: Installed on 2017-05-17 (155 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-07-30 (81 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

Title:
   17.10 nautilus 3.26.0 fails to recognize mouse middle button to lower
  window

Status in nautilus package in Ubuntu:
  New

Bug description:
  It's very handy to send any open Ubuntu application window to below
  all other open windows (it stays open yet now occluded) by clicking
  mouse middle button on window title bar (opposite of left mouse click
  to bring to focus front) ... this works fine on all Ubuntu 17.10
  applications except fails on Ubuntu 17.10's file explorer nautilus
  3.26.0 which has a non-standard looking title bar.

  This behavior continues to be OK on all other 17.10 applications...
  Nautilus worked on previous Ubuntu releases  ... I hope other apps
  refrain from using this new window behavior

  Any ideas on why nautilus breaks this convention? Or how to fix it?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1: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
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Oct 20 10:53:51 2017
  InstallationDate: Installed on 2017-05-17 (155 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-07-30 (81 days ago)
  usr_lib_nautilus: dropbox 2015.10.28

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

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

[Desktop-packages] [Bug 1725507] [NEW] keyboard shortcut to lock screen doesn't work on 17.10

2017-10-20 Thread Tessa

Public bug reported:

After upgrading to Ubuntu 17.10, the keyboard shortcut to lock the
screen (by default, Win-L) doesn't lock the screen anymore. If I go into
the keyboard shortcuts settings panel and change it, whatever I change
it to does nothing, either. However, the icon in the gnome login menu in
the top right does still work, so screen lock isn't entirely broken.

Not sure what component actually controls this, so I'm filing under
gnome-shell, since it seems like the thing that'd interpret keyboard
hotkeys.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 20 15:59:58 2017
DisplayManager: lightdm
InstallationDate: Installed on 2016-07-08 (468 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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


** Tags: amd64 apport-bug artful third-party-packages 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/1725507

Title:
  keyboard shortcut to lock screen doesn't work on 17.10

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 17.10, the keyboard shortcut to lock the
  screen (by default, Win-L) doesn't lock the screen anymore. If I go
  into the keyboard shortcuts settings panel and change it, whatever I
  change it to does nothing, either. However, the icon in the gnome
  login menu in the top right does still work, so screen lock isn't
  entirely broken.

  Not sure what component actually controls this, so I'm filing under
  gnome-shell, since it seems like the thing that'd interpret keyboard
  hotkeys.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 20 15:59:58 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-07-08 (468 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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

[Desktop-packages] [Bug 1288655] Re: terminal gets smaller when maximized and then restored

2017-10-20 Thread Paul

Literally one pixel beyond the edges of the window. I've attached a
screenshot that I hope illustrates this.

You see two windows which were auto-placed by the window manager. If
they didn't have scroll bars, they wouldn't overlap, but they do, by one
pixel. Depending on which window is in the foreground, the rightmost
pixel of the scroll bar is either below or above the other window.

The bottommost pixel of the scroll bar extending below the window is
evident in both cases.

** Attachment added: "scrollbar_beyond_window_boundary.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+attachment/4980480/+files/scrollbar_beyond_window_boundary.png

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

Title:
terminal gets smaller when maximized and then restored

Status in GNOME Terminal:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed

Bug description:
1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt
+ T)
2. "stty -a | grep rows" reports "rows 24; columns 80;"
3. Maximize the window (by clicking on the maximize button, or double
clicking the title bar, or dragging the window up to the panel)
4. Do the same again to un-maximize the window
5. Now "stty -a | grep rows" reports "rows 23; columns 79;"

Each time I do this, the window keeps getting one character shorter
and one character narrower!

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-terminal 3.6.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Thu Mar 6 10:22:46 2014
InstallationDate: Installed on 2010-04-15 (1421 days ago)
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
MarkForUpload: True
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago)

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

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

[Desktop-packages] [Bug 1725487] Re: ubuntu.css styling issues

Thanks for your response Jeremy.

I filed all three issues in a same report since all three refer to the
same styling file (ubuntu.css) under the gnome-shell themes folder.

If it's a must I'll separate the report later on.

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

Title:
  ubuntu.css styling issues

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
  hot-corner' as true, the colour of the ripple is still blue (Adwaita
  default scheme) since the compiled shell theme still uses the
  specified asset resource:///org/gnome/shell/theme/corner-ripple-
  ltr.png - this is also valid for the rtl asset.

  I have solved the issue by appending an override to match the current
  ubuntu.css overrides as follows:

  .ripple-box {
border-radius: 0px 0px 64px 0px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
  }

  .ripple-box:rtl {
border-radius: 0px 0px 0px 64px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
  }

  The gdm login avatar alignment is also off by a couple of pixels and
  can be easily fixed by correcting the user icon margin setup like so:

  .framed-user-icon {
margin: 4px 0px 0px 2px !important;
padding: 0px 0px 0px 0px !important;
  }

  Another important factor in staying consistent with the overall
  aesthetics of the ubuntu design language would be to disable the use
  of the noise texture on gdm to provide a seamless transition from the
  plymouth boot splash onto the gdm login. Here is the override:

  #lockDialogGroup {
background: #2c001e !important;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:25:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1725487/+subscriptions

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

[Desktop-packages] [Bug 1725501] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Tags removed: need-duplicate-check

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  I'm new to this, but my Ubuntu MATE upgrade from 17.04 to 17.10 had
  Cracklib configuration crash out and it made a long mess on the
  terminal. My system told me I should report this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:10:21 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-08-06 (75 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.4.6~17.04.1
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1725501] [NEW] package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-10-20 Thread George Jr West

Public bug reported:

I'm new to this, but my Ubuntu MATE upgrade from 17.04 to 17.10 had
Cracklib configuration crash out and it made a long mess on the
terminal. My system told me I should report this.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: cracklib-runtime 2.9.2-3
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Fri Oct 20 18:10:21 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-08-06 (75 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.4.6~17.04.1
SourcePackage: cracklib2
Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  I'm new to this, but my Ubuntu MATE upgrade from 17.04 to 17.10 had
  Cracklib configuration crash out and it made a long mess on the
  terminal. My system told me I should report this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:10:21 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-08-06 (75 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.4.6~17.04.1
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1288655] Re: terminal gets smaller when maximized and then restored

2017-10-20 Thread Egmont Koblinger

Paul, what do you mean by "scroll bars extending one pixel past the
right and bottom edges"??

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

Title:
  terminal gets smaller when maximized and then restored

Status in GNOME Terminal:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt 
+ T)
  2. "stty -a | grep rows" reports "rows 24; columns 80;"
  3. Maximize the window (by clicking on the maximize button, or double 
clicking the title bar, or dragging the window up to the panel)
  4. Do the same again to un-maximize the window
  5. Now "stty -a | grep rows" reports "rows 23; columns 79;"

  Each time I do this, the window keeps getting one character shorter
  and one character narrower!

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Mar  6 10:22:46 2014
  InstallationDate: Installed on 2010-04-15 (1421 days ago)
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago)

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

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

[Desktop-packages] [Bug 1721189] Re: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface

2017-10-20 Thread Rachel Greenham

Yes, I see what you see: the borders around the tabs are missing. Not
just on the Security prefpane, on all of them, that have tabs.

But that's all that's wrong. (Or at least all that's obviously wrong.)
So while I can corroborate you, I think it's a different error and
should have a separate bug report. This bug was for the whole user
interface falling apart, rendering the application unusable, and has
been fixed.

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

Title:
  Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Just received the update 1:52.4.0+build1-0ubuntu1 which has a broken
  user interface.

  See attached screenshot.

  Downgraded to thunderbird_52.3.0+build1-0ubuntu0.17.04.1_amd64.deb
  which solved the problem.

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

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

[Desktop-packages] [Bug 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries

** Changed in: hunspell-en-us (Debian)
   Status: New => Fix Released

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

Title:
  Migrate to hunspell-en-us in libreoffice-dictionaries

Status in hunspell-en-us package in Ubuntu:
  New
Status in libreoffice-dictionaries package in Ubuntu:
  New
Status in hunspell-en-us package in Debian:
  Fix Released
Status in libreoffice-dictionaries package in Debian:
  Won't Fix

Bug description:
  libreoffice-dictionaries upstream ships hunspell-en-us, which is
  properly maintained and is newer than the one currently in Debian and
  Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in
  libreoffice-dictionaries. The other English variants (British,
  Australian and others) are already provided by libreoffice-
  dictionaries and are more up-to-date than the US variant.

  Debian bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159

  Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff 
and en_US.dic but there is not a built package for them.
  
https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/

  See this README from the Libreoffice/dictionaries git,
  https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt

  It seems that this is now dead,
  https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hunspell-en-us 20070829-6ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 09:43:32 2017
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: hunspell-en-us
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+subscriptions

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

[Desktop-packages] [Bug 1725495] Re: gedit crashed with SIGSEGV in g_closure_invoke()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gedit crashed with SIGSEGV in g_closure_invoke()

Status in gedit package in Ubuntu:
  New

Bug description:
  I double clicked on a sh file to execute it but gedit opened and
  crashed. The file was an installation file of 4.5mb

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:50:55 2017
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2017-10-19 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: gedit 
/home/username/Downloads/anyconnect-linux64-4.4.01054-core-vpn-webdeploy-k9.sh
  SegvAnalysis:
   Segfault happened at: 0x7fcb05e29ee6:mov0xc8(%rax),%rbp
   PC (0x7fcb05e29ee6) ok
   source "0xc8(%rax)" (0x00c8) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gedit
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gedit crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1725487] Re: ubuntu.css styling issues

2017-10-20 Thread Jeremy Bicha

I think the GDM login screen texture was intentional for Ubuntu 17.10.

Please file separate bugs for separate issues. I count 3 separate issues
here (the ripple, the login avatar alignment, the login texture).

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

Title:
  ubuntu.css styling issues

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
  hot-corner' as true, the colour of the ripple is still blue (Adwaita
  default scheme) since the compiled shell theme still uses the
  specified asset resource:///org/gnome/shell/theme/corner-ripple-
  ltr.png - this is also valid for the rtl asset.

  I have solved the issue by appending an override to match the current
  ubuntu.css overrides as follows:

  .ripple-box {
border-radius: 0px 0px 64px 0px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
  }

  .ripple-box:rtl {
border-radius: 0px 0px 0px 64px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
  }

  The gdm login avatar alignment is also off by a couple of pixels and
  can be easily fixed by correcting the user icon margin setup like so:

  .framed-user-icon {
margin: 4px 0px 0px 2px !important;
padding: 0px 0px 0px 0px !important;
  }

  Another important factor in staying consistent with the overall
  aesthetics of the ubuntu design language would be to disable the use
  of the noise texture on gdm to provide a seamless transition from the
  plymouth boot splash onto the gdm login. Here is the override:

  #lockDialogGroup {
background: #2c001e !important;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:25:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1725487/+subscriptions

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

[Desktop-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

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

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

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

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

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715435/+subscriptions

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

[Desktop-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

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

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

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

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

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  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/1715435/+subscriptions

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

[Desktop-packages] [Bug 1288655] Re: terminal gets smaller when maximized and then restored

2017-10-20 Thread Paul

@egmont-gmail Do the other affected terminals also have scroll bars
extending one pixel past the right and bottom edges, the way gnome-
terminal has?

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

Title:
  terminal gets smaller when maximized and then restored

Status in GNOME Terminal:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt 
+ T)
  2. "stty -a | grep rows" reports "rows 24; columns 80;"
  3. Maximize the window (by clicking on the maximize button, or double 
clicking the title bar, or dragging the window up to the panel)
  4. Do the same again to un-maximize the window
  5. Now "stty -a | grep rows" reports "rows 23; columns 79;"

  Each time I do this, the window keeps getting one character shorter
  and one character narrower!

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Mar  6 10:22:46 2014
  InstallationDate: Installed on 2010-04-15 (1421 days ago)
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago)

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

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

[Desktop-packages] [Bug 1725491] [NEW] Application icons disappear after waking PC up from sleep

2017-10-20 Thread Vasya Pupkin

Public bug reported:

Application icons (Telegram, Dropbox, etc) disappear after waking PC up
from sleep. Applications are still running, but icons are gone.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 00:49:13 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-19 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Application icons disappear after waking PC up from sleep

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Application icons (Telegram, Dropbox, etc) disappear after waking PC
  up from sleep. Applications are still running, but icons are gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 00:49:13 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-19 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1725491/+subscriptions

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

[Desktop-packages] [Bug 1613729] Re: NetworkManager autoconnects to wired profiles in reverse order

2017-10-20 Thread Simon Wydooghe

I'm no longer working there so it's not very important to me anymore. I
suppose if somebody still needed this fix they would have made a comment
here by now... With 18.04 around the corner I imagine desktop usage of
14.04 isn't very applicable anymore.

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

Title:
  NetworkManager autoconnects to wired profiles in reverse order

Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager source package in Trusty:
  New

Bug description:
  When I select a wired profile manually and reboot, NetworkManager
  instead connects to the profile that has the oldest timestamp. So it's
  not connecting to the last used profile, which is troublesome.

  On all of our machines (about 500), we define three wired network
  profiles, one DHCP and two static. We're migrating from Debian to
  Ubuntu, so this bug has only surfaced now for us.

  This can be reproduced by creating a couple of network profiles on the
  same wired interface and then rebooting or restarting network-manager.
  It will loop through the network profiles in the same order always. So
  it's doing the exact reverse of what's supposed to happen.

  I did some digging and I applied a simple patch to the source code.
  This seems to have fixed the issue. I posted my patch for verification
  on the networkmanager mailing list and it was verified as being
  correct by Beniamino Galvani, one of the developers.

  Here is the link to the network-manager topic:
  https://mail.gnome.org/archives/networkmanager-
  list/2016-August/msg00053.html

  This is the patch (also included as attachment):

  --- nm-device.c 2016-08-16 15:37:50.0 +0200
  +++ nm-device_patched.c 2016-08-16 15:44:08.308729955 +0200
  @@ -1267,7 +1267,7 @@
  s_con = nm_connection_get_setting_connection (connection);
  g_assert (s_con);
  if (nm_setting_connection_get_autoconnect (s_con))
  -   available_conns = g_slist_prepend (available_conns, 
connection);
  +   available_conns = g_slist_append (available_conns, 
connection);
  }

  if (!available_conns)

  I hope to get this patch included in the trusty package, so somebody
  else can benefit from this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.3
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CRDA: Error: [Errno 2] Bestand of map bestaat niet: 'iw'
  CurrentDesktop: Unity
  Date: Tue Aug 16 15:23:17 2016
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.30.6.1 dev em1  proto static 
   10.30.6.0/24 dev em1  proto kernel  scope link  src 10.30.6.204  metric 1 
   10.40.8.0/21 dev tun0  proto kernel  scope link  src 10.40.8.31
  IwConfig:
   tun0  no wireless extensions.
   
   em1   no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=nl_BE:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   DHCP  702624f9-f052-473a-b131-acd2045e6ec2   
802-3-ethernet1471353746   di 16 aug 2016 15:22:26 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   Proximus  7a9a5bc2-d51a-46b4-b721-050a607951bc   
802-3-ethernet1471353744   di 16 aug 2016 15:22:24 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   em1802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1725487] [NEW] ubuntu.css styling issues

Public bug reported:

Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
hot-corner' as true, the colour of the ripple is still blue (Adwaita
default scheme) since the compiled shell theme still uses the specified
asset resource:///org/gnome/shell/theme/corner-ripple-ltr.png - this is
also valid for the rtl asset.

I have solved the issue by appending an override to match the current
ubuntu.css overrides as follows:

.ripple-box {
  border-radius: 0px 0px 64px 0px !important;
  background: #e95420 !important;
  width:64px !important;
  height:64px !important;
}

.ripple-box:rtl {
  border-radius: 0px 0px 0px 64px !important;
  background: #e95420 !important;
  width:64px !important;
  height:64px !important;
}

The gdm login avatar alignment is also off by a couple of pixels and can
be easily fixed by correcting the user icon margin setup like so:

.framed-user-icon {
  margin: 4px 0px 0px 2px !important;
  padding: 0px 0px 0px 0px !important;
}

Another important factor in staying consistent with the overall
aesthetics of the ubuntu design language would be to disable the use of
the noise texture on gdm to provide a seamless transition from the
plymouth boot splash onto the gdm login. Here is the override:

#lockDialogGroup {
  background: #2c001e !important;
}

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:25:06 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  ubuntu.css styling issues

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
  hot-corner' as true, the colour of the ripple is still blue (Adwaita
  default scheme) since the compiled shell theme still uses the
  specified asset resource:///org/gnome/shell/theme/corner-ripple-
  ltr.png - this is also valid for the rtl asset.

  I have solved the issue by appending an override to match the current
  ubuntu.css overrides as follows:

  .ripple-box {
border-radius: 0px 0px 64px 0px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
  }

  .ripple-box:rtl {
border-radius: 0px 0px 0px 64px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
  }

  The gdm login avatar alignment is also off by a couple of pixels and
  can be easily fixed by correcting the user icon margin setup like so:

  .framed-user-icon {
margin: 4px 0px 0px 2px !important;
padding: 0px 0px 0px 0px !important;
  }

  Another important factor in staying consistent with the overall
  aesthetics of the ubuntu design language would be to disable the use
  of the noise texture on gdm to provide a seamless transition from the
  plymouth boot splash onto the gdm login. Here is the override:

  #lockDialogGroup {
background: #2c001e !important;
  }

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:25:06 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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/1725487/+subscriptions

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

[Desktop-packages] [Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle

2017-10-20 Thread LGB [Gábor Lénárt]

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

So, as thinking on this, I must say, maybe this is my mis-interpretation
of the problem. Maybe not the colour prompt causes this, but if I use a
newer (or ssh into a newer) ubuntu box versus ssh into an older version
(in both cases ssh in the window only changes the situation of
"shrinking" if the window title is modified to reflect this, ie like
username@machine1:~ changes into username@machine2:~ because of the
ssh). I really feel bad not to be able to express this in a sane way,
but it's kind of odd issue for me at least. Just changing PS1 does not
change the situation for me either.

Ok, now it's even more odd, just trying to test it ... Now window
shrinks by TWO lines not only one, and the behaviour I tried to describe
above seems not to apply at all :-O I don't know what I can say, maybe
this is a more complex issue and my assumption was only true for the
given case when I last tested it ...Sorry about that.

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

Title:
  gnome-terminal window becomes one line shorter after every
  fullscreen/windowed cycle

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11
  configured to toggle between fullscreen and windowed mode. Just
  noticed, that every time I press F11 to get full screen, then F11 to
  get back windowed mode, the window becomes one line shorter ...
  Continuing this I can hit the situation to have only a one line tall
  window. It's kinda annoying, since during my work I use tons of
  terminal windows, and I often use full screen / windowed mode
  switching. Now, I have to resize the window again and again before it
  becomes too shallow ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 24 11:14:01 2017
  InstallationDate: Installed on 2015-07-10 (744 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago)

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

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

[Desktop-packages] [Bug 1666681] Re: Drop interactive_search.patch (type-ahead search)

2017-10-20 Thread drunckoder

That's an essential feature that should never be abandoned. I'm facing
similar issues like Dmitriy did. Are there ways to patch or downgrade
Nautilus? It's working perfectly in 17.04

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

Title:
Drop interactive_search.patch (type-ahead search)

Status in nautilus package in Ubuntu:
Confirmed

Bug description:
Nautilus dropped the popular type-ahead search feature years ago.
Ubuntu has been carrying a patch to revert that change. See bug
1164016 for the original LP bug and patch proposal.

Nautilus is now under very active development. During the 3.22 cycle,
that patch needed to be rebased. I tried to do it and what I came up
with caused a crash (it didn't really crash for me, but ricotz and
some others experienced it) and the first letter typed activated type-
ahead search but the first letter was dropped. In other words, you
would need to type "ddow" to activate the Downloads folder instead of
just "dow" like in previous releases. (LP: #1635988)

I did that rebase in October 2016 and no one has stepped up then to
improve the patch.

The Nautilus maintainer csoriano has said that the slots and views
changed significantly during 3.22 and will likely be refactored more
in the future.

If there's no one available to maintain the patch, unfortunately,
we'll eventually have to drop the patch to not be stuck on an ancient
version of Nautilus.

I am proposing that we do this at the start of the 17.10 development
cycle. This gives 6 months for a developer to step up and try to fix
the patch and 12 months before 18.04 LTS.

Other Items
===
- For better performance with the built-in search, we need to reconsider
avoiding tracker in Unity (LP: #176)

- There is an option in Preferences for users to disable searching in
subfolders. I don't think we want to do that by default but maybe it
can help some people.

The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with
this patch now disabled.

https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?)

2017-10-20 Thread Paul

I use dash to dock rather than dash-to-panel but am now running the
command and will try and get an output for you.

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() (dash-to-panel specific?)

Status in GNOME Shell:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1164016] Re: restore type-ahead find

2017-10-20 Thread drunckoder

I can confirm there's an issue again on Ubuntu 17.10

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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

[Desktop-packages] [Bug 1706008] Re: gnome-terminal window becomes one line shorter after every fullscreen/windowed cycle

2017-10-20 Thread LGB [Gábor Lénárt]

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

I don't know how to tell, but it seems the bug happens when the prompt
has effect on the title of the window. What I mean here: opening a
gnome-terminal with a colourful PS1 causes this. However if I ssh into
another machine which does update the title of the window and the prompt
does not use colour, the shrinking stops if I try fullscreen/back cycles
again ... If I ssh into a machine which does have this "new" colour
prompt then it continues ... If I ssh into a machine which does not
effect the title bar, it does not effect the strange behaviour though.
So, what I can think about there is some connection about the window bar
title updating by the prompt (???) sorry, I have really no idea hot it
happens :-O

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

Title:
  gnome-terminal window becomes one line shorter after every
  fullscreen/windowed cycle

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  It's 17.04 64 bit Ubuntu, wayland+gnome-shell. I have key F11
  configured to toggle between fullscreen and windowed mode. Just
  noticed, that every time I press F11 to get full screen, then F11 to
  get back windowed mode, the window becomes one line shorter ...
  Continuing this I can hit the situation to have only a one line tall
  window. It's kinda annoying, since during my work I use tons of
  terminal windows, and I often use full screen / windowed mode
  switching. Now, I have to resize the window again and again before it
  becomes too shallow ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jul 24 11:14:01 2017
  InstallationDate: Installed on 2015-07-10 (744 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to zesty on 2017-06-20 (33 days ago)

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

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

[Desktop-packages] [Bug 1725432] Re: Restore failed due to missing source option

** Branch linked: lp:~ubuntu-desktop/deja-dup/ubuntu

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

Title:
  Restore failed due to missing source option

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  Users can't restore a backup on a fresh install from the deja-dup UI.

  [ Test Case ]

  Open "Backups" (or run 'deja-dup') and click the "Restore..." button.

  You should see a dropdown with options for a location, but instead
  with this bug, you see an empty dialog.

  [ Regression Potential ]

  Pretty small.  The proposed patch just moves some widget
  initialization earlier.

  [ Original Bug Description ]

  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

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

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

[Desktop-packages] [Bug 1697146] Re: Unable to use apport to report any bugs prior to the first software update

I just installed the final release of Artful, without choosing to
install updates from the network, and /var/lib/apt/lists is full and I
am able to use 'ubuntu-bug apport' without having to run a software
update.

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

** Changed in: apport (Ubuntu)
   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/1697146

Title:
  Unable to use apport to report any bugs prior to the first software
  update

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

Bug description:
  Running `ubuntu-bug gnome-shell` from within an installed artful
  system claims that it is not an official ubuntu package. Running it
  from the live CD session works fine.

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

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

[Desktop-packages] [Bug 1725432] Re: Restore failed due to missing source option

2017-10-20 Thread Michael Terry

Fixed upstream in 36.3.  I've uploaded to artful-proposed.

** Description changed:

+ [ Impact ]
+ 
+ Users can't restore a backup on a fresh install from the deja-dup UI.
+ 
+ [ Test Case ]
+ 
+ Open "Backups" (or run 'deja-dup') and click the "Restore..." button.
+ 
+ You should see a dropdown with options for a location, but instead with
+ this bug, you see an empty dialog.
+ 
+ [ Regression Potential ]
+ 
+ Pretty small.  The proposed patch just moves some widget initialization
+ earlier.
+ 
+ [ Original Bug Description ]
+ 
  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

** Changed in: deja-dup
   Status: Fix Committed => Fix Released

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

Title:
  Restore failed due to missing source option

Status in Déjà Dup:
  Fix Released
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  Users can't restore a backup on a fresh install from the deja-dup UI.

  [ Test Case ]

  Open "Backups" (or run 'deja-dup') and click the "Restore..." button.

  You should see a dropdown with options for a location, but instead
  with this bug, you see an empty dialog.

  [ Regression Potential ]

  Pretty small.  The proposed patch just moves some widget
  initialization earlier.

  [ Original Bug Description ]

  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

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

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

[Desktop-packages] [Bug 1724295] Re: All Apps screen aren't removed from overview when there's no apps to show

2017-10-20 Thread Gustavo Milczwski

I installed Ubuntu 17.10 and the bug isn't there :)

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

Title:
  All Apps screen aren't removed from overview when there's no apps to
  show

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After install the Ubuntu 16 with Gnome, I opened the Activities
  screen. I pressed the button "Show All Apps". Then I pressed the
  button "Show All Apps" again. The All Apps screen did'nt close. Then,
  I closed the overview and opened it again. The All Apps Screen was
  still there behind the opened windows.

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.3-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 17 14:15:22 2017
  InstallationDate: Installed on 2017-04-17 (183 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gdm3
  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/1724295/+subscriptions

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

[Desktop-packages] [Bug 1613729] Re: NetworkManager autoconnects to wired profiles in reverse order

Wow, I'm sorry I totally forget about this. Are you still interested in
seeing this fixed in the Ubuntu archive?

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

Title:
  NetworkManager autoconnects to wired profiles in reverse order

Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager source package in Trusty:
  New

Bug description:
  When I select a wired profile manually and reboot, NetworkManager
  instead connects to the profile that has the oldest timestamp. So it's
  not connecting to the last used profile, which is troublesome.

  On all of our machines (about 500), we define three wired network
  profiles, one DHCP and two static. We're migrating from Debian to
  Ubuntu, so this bug has only surfaced now for us.

  This can be reproduced by creating a couple of network profiles on the
  same wired interface and then rebooting or restarting network-manager.
  It will loop through the network profiles in the same order always. So
  it's doing the exact reverse of what's supposed to happen.

  I did some digging and I applied a simple patch to the source code.
  This seems to have fixed the issue. I posted my patch for verification
  on the networkmanager mailing list and it was verified as being
  correct by Beniamino Galvani, one of the developers.

  Here is the link to the network-manager topic:
  https://mail.gnome.org/archives/networkmanager-
  list/2016-August/msg00053.html

  This is the patch (also included as attachment):

  --- nm-device.c 2016-08-16 15:37:50.0 +0200
  +++ nm-device_patched.c 2016-08-16 15:44:08.308729955 +0200
  @@ -1267,7 +1267,7 @@
  s_con = nm_connection_get_setting_connection (connection);
  g_assert (s_con);
  if (nm_setting_connection_get_autoconnect (s_con))
  -   available_conns = g_slist_prepend (available_conns, 
connection);
  +   available_conns = g_slist_append (available_conns, 
connection);
  }

  if (!available_conns)

  I hope to get this patch included in the trusty package, so somebody
  else can benefit from this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.3
  ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CRDA: Error: [Errno 2] Bestand of map bestaat niet: 'iw'
  CurrentDesktop: Unity
  Date: Tue Aug 16 15:23:17 2016
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.30.6.1 dev em1  proto static 
   10.30.6.0/24 dev em1  proto kernel  scope link  src 10.30.6.204  metric 1 
   10.40.8.0/21 dev tun0  proto kernel  scope link  src 10.40.8.31
  IwConfig:
   tun0  no wireless extensions.
   
   em1   no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=nl_BE:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_BE
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   DHCP  702624f9-f052-473a-b131-acd2045e6ec2   
802-3-ethernet1471353746   di 16 aug 2016 15:22:26 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/1
   Proximus  7a9a5bc2-d51a-46b4-b721-050a607951bc   
802-3-ethernet1471353744   di 16 aug 2016 15:22:24 CEST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   em1802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1723774] Re: gnome-software assert failure: *** Error in `/usr/bin/gnome-software': malloc() (gs_plugin_action_stop)

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

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

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

Title:
  gnome-software assert failure: *** Error in `/usr/bin/gnome-software':
  malloc() (gs_plugin_action_stop)

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I answered the question about reporting this bug in the affirmative.
  When I changed the setting on CPU view from compact is when the
  message to report this as a bug popped up.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.1-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
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-software': malloc(): memory 
corruption: 0x7f947801d4b0 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 15 14:44:43 2017
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2017-10-15 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.1-0ubuntu1
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f94a95994e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f94a9595eb0 "malloc(): 
memory corruption", ptr=, ar_ptr=) at 
malloc.c:5425
   _int_malloc (av=av@entry=0x7f946c20, bytes=bytes@entry=1024) at 
malloc.c:3740
   __libc_calloc (n=, elem_size=) at malloc.c:3438
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-software assert failure: *** Error in `/usr/bin/gnome-software': 
malloc(): memory corruption: 0x7f947801d4b0 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() (dash-to-panel specific?)

2017-10-20 Thread Treviño

So this is mostly triggered by extensions (and considering how things are done, 
we can't prevent them).
Or some wrong JS code which we didn't identified yet.

Crash for users using dash-to-panel is fixed (I've proposed the fix
upstream https://github.com/jderose9/dash-to-panel/pull/263), for the
others, gjs_dumpstack's are welcome, or we need to wait some debugging
bits to be there.

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() (dash-to-panel specific?)

Status in GNOME Shell:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1725432] Re: Restore failed due to missing source option

2017-10-20 Thread Michael Terry

** Changed in: deja-dup
   Status: Confirmed => Fix Committed

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

Title:
  Restore failed due to missing source option

Status in Déjà Dup:
  Fix Committed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

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

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

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

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1724439
   gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from 
ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from 
function_call()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Another bug report.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 21:36:02 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 
'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 
'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 
'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-10-19 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fcde8a56d94 :mov
0x18(%rax),%eax
   PC (0x7fcde8a56d94) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_window_get_monitor () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

** Changed in: cracklib2 (Ubuntu Yakkety)
   Status: Triaged => Won't Fix

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Triaged
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Won't Fix
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1175608] Re: Thumbnails too small in 'open file' dialog nautilus

** Changed in: nautilus
   Status: Confirmed => In Progress

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

Title:
  Thumbnails too small in 'open file' dialog nautilus

Status in Nautilus:
  In Progress
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When trying to upload image files to e.g. websites like marktplaats.nl
  (kind of ebay) I get  very, very small image thumbnails. There seems
  no way to enlarge these thumbnails. All options only work if Nautilus
  is used stand alone, but not with the open file dialog that is being
  used to upload files.

  I have attached a screen dump just to show what I mean.

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

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

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

2017-10-20 Thread Treviño

pullasuti, do you have a *.crash file in /var/crash/ related to gnome-
shell?

Please attach them mentioning here the versions of gnome-shell and
libmutter you're using in your systems (mostly for recording them for
later times).

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

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

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=788764
   Importance: Unknown
   Status: Unknown

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

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

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hi all, 
  Originally I was reporting bug 1717170, about session crash after monitor 
disconnect/switch-off/input change on desktop PC and the bug was fixed 
according to bug tracker. But now, after gnome-shell and mutter update, the 
crash goes worse. Now it is not just session kick-out but complete crash. Same 
events can be used to reproduce the crash. This time also crash files was 
created.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 13:52:07 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-09-11 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f475acbac30 :   
movss  0x38(%rdi),%xmm0
   PC (0x7f475acbac30) ok
   source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_logical_monitor_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_window_wayland_get_geometry_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_get_scale () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   meta_surface_actor_wayland_sync_state () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1725432] Re: Restore failed due to missing source option

2017-10-20 Thread Michael Terry

** Changed in: deja-dup
   Importance: Undecided => Critical

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

Title:
  Restore failed due to missing source option

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

Bug description:
  Installed a new Ubuntu 17.10, created my user and tried to restore the 
backups from the server.
  Pressed Overview, Restore and get an empty dialog. From screen shots I found 
I assume there should be some drop downs or buttons etc. but my dialog is empty.

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

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

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

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

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

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

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

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

Bug description:
  When I run gnome-control-center I get the following error message:

  (gnome-control-center:18823): GLib-CRITICAL **: g_strsplit: assertion 'string 
!= NULL' failed
  Segmentation fault (core dumped)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:33:23 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: gnome-control-center user-accounts
  SegvAnalysis:
   Segfault happened at: 0x7fbb994a3b59:mov(%rsi),%rsi
   PC (0x7fbb994a3b59) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1725432] Re: Restore failed due to missing source option