[Desktop-packages] [Bug 1717170] [NEW] Gnome-shell session crash after monitor switch-off/input change.

[ryzko]

Public bug reported:

I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core i5-6500
CPU and Intel HD Graphics 530 (skylake GT2). Session is crashing (login
screen is displayed again) every time I change the monitor Input (e.g.
from DP to HDMI) or switching off the monitor. It is happening since
some updated from beginning of September were installed. Same situation
is for both session types, default Wayland and also for X.org. Tested
also with Live USB, same behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu4
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: Thu Sep 14 07:28:54 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-09-11 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Gnome-shell session crash after monitor switch-off/input change.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org. Tested also with Live USB, same behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  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: Thu Sep 14 07:28:54 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-11 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
  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/1717170/+subscriptions

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

[Desktop-packages] [Bug 1712759] Re: /usr/bin/gnome-control-center:11:manager_recheck_permissions:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic:g_closure_invoke

[Jean-Baptiste Lallement]

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

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

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

Title:
  /usr/bin/gnome-control-
  
center:11:manager_recheck_permissions:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic:g_closure_invoke

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

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

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

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

[Desktop-packages] [Bug 1717168] Re: /usr/bin/gnome-shell:11:__GI___libc_free:g_free:meta_wayland_finalize:meta_finalize:meta_run

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1715179
   gnome-shell crashed with SIGSEGV in __GI___libc_free() from g_free() from 
meta_wayland_finalize() from meta_finalize() from meta_run()

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

Title:
  /usr/bin/gnome-
  shell:11:__GI___libc_free:g_free:meta_wayland_finalize:meta_finalize:meta_run

Status in gnome-shell package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1717168] [NEW] /usr/bin/gnome-shell:11:__GI___libc_free:g_free:meta_wayland_finalize:meta_finalize:meta_run

[errors.ubuntu.com bug bridge]

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

Public bug reported:

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

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


** Tags: artful

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

Title:
  /usr/bin/gnome-
  shell:11:__GI___libc_free:g_free:meta_wayland_finalize:meta_finalize:meta_run

Status in gnome-shell package in Ubuntu:
  New

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

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

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

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

[starkus]

The same happens when I disable or enable ssh via gnome-control-center,
using the sharing panel.

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

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

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  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/1704618/+subscriptions

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

[Desktop-packages] [Bug 1702539] Re: Snap packages have too big descriptions in search result list

[Robert Ancell]

The reason for this what not what I expected...

The snap descriptions contain carriage return characters (\r). GNOME
Software replaces all the newline characters (\n) with spaces, but the
carriage returns remain.

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

Title:
  Snap packages have too big descriptions in search result list

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Snap packages have too big descriptions in search result list. Please
  check out the screenshot.

  System:
  Ubuntu 17.10 amd64 daily build 29.06.17 (updated)
  gnome-software 3.24.3

  Also 17.04 has same issue.

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

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

[Desktop-packages] [Bug 956070] Re: [info]: gnome-control-center crashed with SIGSEGV in on_pk_transaction_signal()

[Tony]

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Tony (toekneemi)

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

Title:
  [info]: gnome-control-center crashed with SIGSEGV in
  on_pk_transaction_signal()

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

Bug description:
  I opened the Printers setting!

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.91-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Thu Mar 15 15:44:09 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f3b07b33f0e:mov0x60(%rax),%rdi
   PC (0x7f3b07b33f0e) ok
   source "0x60(%rax)" (0xab0a) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/control-center-1/panels/libinfo.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
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: [info]: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to precise on 2012-03-13 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.3-0ubuntu1
   deja-dup21.90-0ubuntu1
   gnome-bluetooth 3.2.2-0ubuntu3
   indicator-datetime  0.3.91-0ubuntu1

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

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

[Desktop-packages] [Bug 976165] Re: [background]: gnome-control-center crashed with SIGSEGV in cc_background_xml_load_xml_internal()

[Tony]

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Tony (toekneemi)

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

Title:
  [background]: gnome-control-center crashed with SIGSEGV in
  cc_background_xml_load_xml_internal()

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

Bug description:
  after install gnome-tweak-tool

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14
  Uname: Linux 3.2.0-22-generic-pae i686
  ApportVersion: 2.0-0ubuntu4
  Architecture: i386
  Date: Sat Apr  7 23:42:13 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328)
  ProcCmdline: gnome-control-center
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  Title: [background]: gnome-control-center crashed with SIGSEGV in 
ffi_call_SYSV()
  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/976165/+subscriptions

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

[Desktop-packages] [Bug 1064862] Re: [bluetooth]: gnome-control-center crashed with SIGSEGV in get_iter_from_path()

[Tony]

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Tony (toekneemi)

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

Title:
  [bluetooth]: gnome-control-center crashed with SIGSEGV in
  get_iter_from_path()

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

Bug description:
  While fiddling with Bluetooth & Sound..

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu19
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.6.1-0ubuntu2
  Architecture: i386
  CheckboxSubmission: e56271c144a9c8f9f675c77e2e4edb56
  CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b
  Date: Wed Oct 10 12:07:34 2012
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center bluetooth
  SegvAnalysis:
   Segfault happened at: 0xa854de8a:mov0x8(%esi),%ecx
   PC (0xa854de8a) ok
   source "0x8(%esi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/libgnome-bluetooth.so.11
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_SYSV()
  UpgradeStatus: Upgraded to quantal on 2012-09-21 (18 days ago)
  UserGroups: adm admin audio cdrom dialout kvm libvirtd lpadmin netdev plugdev 
pulse pulse-access sambashare video
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu4
   deja-dup24.0-0ubuntu1
   gnome-control-center-signon 0.0.18-0ubuntu1
   indicator-datetime  12.10.2-0ubuntu3

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

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

[Desktop-packages] [Bug 1553034] Re: gnome-software crashed with SIGSEGV in gs_page_app_installed_cb()

[Tony]

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Tony (toekneemi)

** Changed in: gnome-software (Ubuntu)
 Assignee: Tony (toekneemi) => (unassigned)

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Tony (toekneemi)

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

Title:
  gnome-software crashed with SIGSEGV in gs_page_app_installed_cb()

Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  While he is trying to install stellarium using gnome-software...
  Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160304.279bc80-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Mar  4 00:19:20 2016
  ExecutablePath: /usr/bin/gnome-software
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=es_EC:es
   PATH=(custom, no user)
   LANG=es_EC.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x423357:  mov0x8(%rax),%r12
   PC (0x00423357) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%r12" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-software crashed with SIGSEGV in g_main_context_dispatch()
  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/ubuntu/+source/gnome-software/+bug/1553034/+subscriptions

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

[Desktop-packages] [Bug 1717155] Re: Xwayland refresh rate reported by xrandr is incorrect

[Bug Watch Updater]

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

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

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

Title:
  Xwayland refresh rate reported by xrandr is incorrect

Status in wayland:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xwayland refresh rate reported by 'xrandr' is incorrect:

1920x1200   59.88*+

  Actually my hardware runs at 59.95Hz, as confirmed by 'weston-info'.

  If Xwayland is reporting the wrong frequency to apps via Xrandr then
  apps and toolkits implementing frame clocks (i.e. not synchronously
  tied to swap buffers) may animate at the wrong frequency, causing some
  stuttering and skipped frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Sep 14 11:40:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[8086:041a] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[17aa:30a1]
  InstallationDate: Installed on 2017-05-03 (133 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  MachineType: LENOVO 30AJS05700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=1446940d-616b-4f78-926f-05ddb67580b8 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
  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: Mon Jul 31 16:27:11 2017
  xserver.configfile: default
  xserver.errors:
   modeset(G0): eglGetDisplay() failed
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1704594] Re: Brother MFC 7820N printer is not working in Ubuntu 15.10

[Launchpad Bug Tracker]

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

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

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

Title:
  Brother MFC 7820N printer is not working in Ubuntu 15.10

Status in cups package in Ubuntu:
  Expired

Bug description:
  tera@tera-NV57H:~$ lsmod | grep usb
  usblp  20480  0
  usbhid 49152  0
  hid   118784  2 hid_generic,usbhid
  tera@tera-NV57H:~$ tail -f /var/log/syslog
  Jul 15 15:30:15 tera-NV57H systemd[1]: Started Hostname Service.
  Jul 15 15:30:20 tera-NV57H org.gnome.zeitgeist.SimpleIndexer[1217]: ** 
(zeitgeist-fts:1691): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
  Jul 15 15:30:20 tera-NV57H gnome-session[1286]: javaldx: Could not find a 
Java Runtime Environment!
  Jul 15 15:30:20 tera-NV57H gnome-session[1286]: Warning: failed to read path 
from javaldx
  Jul 15 15:30:27 tera-NV57H com.ubuntu.OneConf[1217]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/tera/.cache/oneconf/ecc8c8b5f47f48d7848575bfc2692722/other_hosts'
  Jul 15 15:37:13 tera-NV57H kernel: [ 2310.456175] usb 2-1.1: USB disconnect, 
device number 3
  Jul 15 15:37:13 tera-NV57H kernel: [ 2310.456510] usblp0: removed
  Jul 15 15:37:13 tera-NV57H udev-configure-printer[6879]: remove 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Jul 15 15:37:13 tera-NV57H systemd[1]: printer.target: Unit not needed 
anymore. Stopping.
  Jul 15 15:37:13 tera-NV57H systemd[1]: Stopped target Printer.
  Jul 15 15:39:31 tera-NV57H kernel: [ 2448.849130] usb 2-1.1: new full-speed 
USB device number 5 using ehci-pci
  Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945798] usb 2-1.1: New USB device 
found, idVendor=04f9, idProduct=0181
  Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945809] usb 2-1.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=3
  Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945824] usb 2-1.1: SerialNumber: 
000G5J363027
  Jul 15 15:39:32 tera-NV57H kernel: [ 2448.948742] usblp 2-1.1:1.0: usblp0: 
USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0181
  Jul 15 15:39:32 tera-NV57H mtp-probe: checking bus 2, device 5: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1"
  Jul 15 15:39:33 tera-NV57H mtp-probe: bus: 2, device: 5 was not an MTP device
  Jul 15 15:39:33 tera-NV57H systemd[1]: Created slice 
system-udev\x2dconfigure\x2dprinter.slice.
  Jul 15 15:39:33 tera-NV57H systemd[1]: Starting Automatic USB/Bluetooth 
printer setup (-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1)...
  Jul 15 15:39:33 tera-NV57H systemd[1]: Reached target Printer.
  Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: add 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: MFG:Brother 
MDL:MFC-7820N SERN:- serial:000G5J363027
  Jul 15 15:39:38 tera-NV57H udev-configure-printer[6896]: IPP request 16395 
failed (1280)
  Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Control process exited, code=exited status=1
  Jul 15 15:39:38 tera-NV57H systemd[1]: Failed to start Automatic 
USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1).
  Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Unit entered failed state.
  Jul 15 15:39:38 tera-NV57H systemd[1]: 
udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service:
 Failed with result 'exit-code'.
  ^C
  tera@tera-NV57H:~$ lsusb
  Bus 002 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
  Bus 002 Device 005: ID 04f9:0181 Brother Industries, Ltd MFC-7820N 
Port(FaxModem)
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 1bcf:288a Sunplus Innovation Technology Inc. 
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  tera@tera-NV57H:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/*
  crw-rw-r-- 1 root root 189,   0 Jul 15 14:58 /dev/bus/usb/001/001
  crw-rw-r-- 1 root root 189,   1 Jul 15 14:58 /dev/bus/usb/001/002
  crw-rw-r-- 1 root root 189,   2 Jul 15 14:58 /dev/bus/usb/001/003
  crw-rw-r-- 1 root root 189, 128 Jul 15 14:58 /dev/bus/usb/002/001
  crw-rw-r-- 1 root root 189, 129 Jul 15 14:58 /dev/bus/usb/002/002
  crw-rw-r-- 1 root root 189, 131 Jul 15 14:58 /dev/bus/usb/002/004
  crw-rw-r-- 1 root lp   189, 132 Jul 15 15:39 

[Desktop-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations

[Daniel van Vugt]

I understand and agree gnome-shell's animations are poor in places. Sub-
optimal performance of the shell in general makes them sometimes miss
frames and stutter. Plus the chosen easing curves are also questionable
(bug 1713021).

But these are all fixable bugs. I would be disappointed if we disabled
animations to work around the problems rather than fixing the problems.

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

Title:
  Add option to disable gnome-shell animations

Status in ubuntu-settings package in Ubuntu:
  Invalid

Bug description:
  I believe doing so will provide the better experience for most users. Those 
that see use in it can enable if desired.
  Am filing this bug first rather than specific against gnome-shell because 
this is immediately  remedied in settings & there are reports of other poor 
behavior than the below test case.

  Test case 1:
  In current 'pseudo' default of xorg
  In any common video player (totem, vlc, mpv, ect.) open a video.
  Go from window to fullscreen, fullscreen to windowed, notice the distortion.

  May be even worse in wayland or when using hw decoding.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-settings 17.10.15
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 17:21:52 2017
  InstallationDate: Installed on 2017-09-10 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717160] [NEW] [Satellite S55Dt-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all

[Sanjay Jagannath]

Public bug reported:

I have added all the relevant outputs below. I am new to Ubuntu so
please let me know if you need any more info. I have also checked the
levels using alsamixer but had no luck. I have also made sure that
nothing is muted. I have also turned auto mute off in the alsamixer.

sanjay@sanjay-laptop:~$ alsactl restore
alsactl: state_lock:125: file /var/lib/alsa/asound.state lock error: File exists
alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: 
File exists
Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100300" 
"0x1002" "0x9902"
Hardware is initialized using a generic method
Found hardware: "HDA-Intel" "IDT 92HD99BXX" "HDA:111d76e5,1179fa95,00100303" 
"0x1179" "0xfa95"
Hardware is initialized using a generic method
sanjay@sanjay-laptop:~$ pactl list | grep 'Active Port.*output.*'
Active Port: hdmi-output-0
Active Port: analog-output-speaker
sanjay@sanjay-laptop:~$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 0: 92HD99BXX Analog [92HD99BXX 
Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
sanjay@sanjay-laptop:~$ cat /proc/asound/card0/codec* | grep Codec
Codec: ATI R6xx HDMI
sanjay@sanjay-laptop:~$ sudo nano /etc/modprobe.d/alsa-base
[sudo] password for sanjay: 
sanjay@sanjay-laptop:~$ sudo nano /etc/modprobe.d/alsa-base.conf
sanjay@sanjay-laptop:~$ cat /proc/asound/card0/pcm0c/info
cat: /proc/asound/card0/pcm0c/info: No such file or directory
sanjay@sanjay-laptop:~$ cat /proc/asound/card0/codec*
Codec: ATI R6xx HDMI
Address: 0
AFG Function Id: 0x1 (unsol 0)
Vendor Id: 0x1002aa01
Subsystem Id: 0x00aa0100
Revision Id: 0x100300
No Modem Function Group found
Default PCM:
rates [0x70]: 32000 44100 48000
bits [0x2]: 16
formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
State of AFG node 0x01:
  Power states:  D0 D3 CLKSTOP EPSS
  Power: setting=D0, actual=D0, Clock-stop-OK
GPIO: io=0, o=0, i=0, unsolicited=0, wake=0
Node 0x02 [Audio Output] wcaps 0x221: Stereo Digital Stripe
  Converter: stream=1, channel=0
  Digital: Enabled
  Digital category: 0x0
  IEC Coding Type: 0x0
Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital
  Control: name="IEC958 Playback Con Mask", index=0, device=0
  Control: name="IEC958 Playback Pro Mask", index=0, device=0
  Control: name="IEC958 Playback Default", index=0, device=0
  Control: name="IEC958 Playback Switch", index=0, device=0
  Pincap 0x0094: OUT Detect HDMI
  Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI
Conn = Digital, Color = Unknown
DefAssociation = 0xf, Sequence = 0x0
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=01, enabled=1
  Connection: 1
 0x02
Node 0x04 [Audio Output] wcaps 0x221: Stereo Digital Stripe
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  IEC Coding Type: 0x0
Node 0x05 [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x0094: OUT Detect HDMI
  Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI
Conn = Digital, Color = Unknown
DefAssociation = 0xf, Sequence = 0x0
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
 0x04
Node 0x06 [Audio Output] wcaps 0x221: Stereo Digital Stripe
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  IEC Coding Type: 0x0
Node 0x07 [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x0094: OUT Detect HDMI
  Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI
Conn = Digital, Color = Unknown
DefAssociation = 0xf, Sequence = 0x0
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
 0x06
Node 0x08 [Audio Output] wcaps 0x221: Stereo Digital Stripe
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  IEC Coding Type: 0x0
Node 0x09 [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x0094: OUT Detect HDMI
  Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI
Conn = Digital, Color = Unknown
DefAssociation = 0xf, Sequence = 0x0
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
 0x08
Node 0x0a [Audio Output] wcaps 0x221: Stereo Digital Stripe
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  IEC Coding Type: 0x0
Node 0x0b [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x0094: OUT Detect HDMI
  Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI
Conn = Digital, Color = Unknown
DefAssociation = 0xf, Sequence = 0x0
  Pin-ctls: 0x40: OUT
  Unsolicited: tag=00, enabled=0
  Connection: 1
 0x0a
Node 0x0c [Audio Output] wcaps 0x221: Stereo Digital Stripe
  Converter: stream=0, channel=0
  Digital:
  Digital category: 0x0
  IEC Coding Type: 0x0
Node 0x0d [Pin Complex] wcaps 0x400381: Stereo Digital
  Pincap 0x0094: OUT Detect HDMI
  Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI
Conn = Digital, Color = Unknown

[Desktop-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations

[Doug McMahon]

At best this would have only been an opinion. (And in retrospect as I only see 
some issues in video playback not to the greater good..
So marking invalid.
I think if others (possibly just weaker hardware) see problems in general then 
I'm sure you'll all hear about it later. (I can't duplicate any reports I've 
seen not invoving vidoe playback.

** Changed in: ubuntu-settings (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Add option to disable gnome-shell animations

Status in ubuntu-settings package in Ubuntu:
  Invalid

Bug description:
  I believe doing so will provide the better experience for most users. Those 
that see use in it can enable if desired.
  Am filing this bug first rather than specific against gnome-shell because 
this is immediately  remedied in settings & there are reports of other poor 
behavior than the below test case.

  Test case 1:
  In current 'pseudo' default of xorg
  In any common video player (totem, vlc, mpv, ect.) open a video.
  Go from window to fullscreen, fullscreen to windowed, notice the distortion.

  May be even worse in wayland or when using hw decoding.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-settings 17.10.15
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 17:21:52 2017
  InstallationDate: Installed on 2017-09-10 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717155] [NEW] Xwayland refresh rate reported by xrandr is incorrect

[Daniel van Vugt]

Public bug reported:

Xwayland refresh rate reported by 'xrandr' is incorrect:

  1920x1200   59.88*+

Actually my hardware runs at 59.95Hz, as confirmed by 'weston-info'.

If Xwayland is reporting the wrong frequency to apps via Xrandr then
apps and toolkits implementing frame clocks (i.e. not synchronously tied
to swap buffers) may animate at the wrong frequency, causing some
stuttering and skipped frames.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xwayland 2:1.19.3-1ubuntu6
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Thu Sep 14 11:40:31 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[8086:041a] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[17aa:30a1]
InstallationDate: Installed on 2017-05-03 (133 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
MachineType: LENOVO 30AJS05700
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=1446940d-616b-4f78-926f-05ddb67580b8 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: FBKTB6AUS
dmi.board.name: SHARKBAY
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50519 PRO
dmi.chassis.type: 7
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 30AJS05700
dmi.product.version: ThinkStation P300
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
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: Mon Jul 31 16:27:11 2017
xserver.configfile: default
xserver.errors:
 modeset(G0): eglGetDisplay() failed
 modeset(G0): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu2

** Affects: wayland
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug artful performance reproducible ubuntu visual-quality

** Bug watch added: freedesktop.org Bugzilla #102721
   https://bugs.freedesktop.org/show_bug.cgi?id=102721

** Also affects: wayland via
   https://bugs.freedesktop.org/show_bug.cgi?id=102721
   Importance: Unknown
   Status: Unknown

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

Title:
  Xwayland refresh rate reported by xrandr is incorrect

Status in wayland:
  Unknown
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xwayland refresh rate reported by 'xrandr' is incorrect:

1920x1200   59.88*+

  Actually my hardware runs at 59.95Hz, as confirmed by 'weston-info'.

  If Xwayland is reporting the wrong frequency to apps via Xrandr then
  apps and toolkits implementing frame clocks (i.e. not synchronously
  tied to swap buffers) may animate at the wrong frequency, causing some
  stuttering and skipped frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Sep 14 11:40:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[8086:041a] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[17aa:30a1]
  InstallationDate: Installed on 2017-05-03 (133 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  MachineType: LENOVO 

[Desktop-packages] [Bug 1712085] Re: gnome-control-center crashed with SIGSEGV

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  It just happened. Didn't have settings open at the time. However I
  don't know of that is related the past few updates bluetooth is not
  working as expected. Pairing a new device is behaving abnormally.
  Without putting device into pair mode somehow it gets added to the
  system and it shoes it connected and right after that disconnected.
  Then sometimes the settings app hangs when i turn it on/off.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 19 20:18:52 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-07-19 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717)
  ProcCmdline: gnome-control-center online-accounts
  SegvAnalysis:
   Segfault happened at: 0x7f70ba7beb6b:mov0x8(%rax),%rax
   PC (0x7f70ba7beb6b) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1717150] Re: gnome-control-center crashed with SIGSEGV

[Apport retracing service]

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

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 #1712085, 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/1717150/+attachment/4949787/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1712085
   gnome-control-center 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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1717150

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  Opened Software, searched for an app, Pomodoro. Software froze and
  threw up this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 21:43:35 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-14 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812)
  ProcCmdline: gnome-control-center online-accounts
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe64c806aeb:mov0x8(%rax),%rax
   PC (0x7fe64c806aeb) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1717145] [NEW] ubuntu 14.04 - Could not calculate upgrade

[Paul Garff]

Public bug reported:

Tried to upgrade ubuntu to version 14.04.   Downloaded all the files -
then got an error that said could not calculate upgrade.  The error
message said to report this as a bug.  I have tried to upgrade several
times with the same result.

An unresolvable problem occurred while calculating the upgrade.

Please report this bug against the 'update-manager' package and include the 
following error message:
'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.'

I was hoping upgrade from, I think version 10...  -  I don't get anymore
changes for this version.

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

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

Title:
  ubuntu 14.04 - Could not calculate upgrade

Status in nautilus package in Ubuntu:
  New

Bug description:
  Tried to upgrade ubuntu to version 14.04.   Downloaded all the files -
  then got an error that said could not calculate upgrade.  The error
  message said to report this as a bug.  I have tried to upgrade several
  times with the same result.

  An unresolvable problem occurred while calculating the upgrade.

  Please report this bug against the 'update-manager' package and include the 
following error message:
  'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.'

  I was hoping upgrade from, I think version 10...  -  I don't get
  anymore changes for this version.

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

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

[Desktop-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()

[edgar]

no comment

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

Title:
  udisksd crashed with SIGSEGV in g_mutex_lock()

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  Showed up after login

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udisks2 2.6.5-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 30 00:35:31 2017
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2017-06-22 (37 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170622)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcCmdline: /usr/lib/udisks2/udisksd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed 
root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f4900fb5c65 :   lock xadd 
%eax,(%rdi)
   PC (0x7f4900fb5c65) ok
   source "%eax" ok
   destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   main ()
  Title: udisksd crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: Z87 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

[Daniel van Vugt]

The classic option requires you have it installed already, do you?...

  sudo apt install gnome-shell-extensions

Otherwise try running just:

  gnome-shell --wayland --display-server

or

  gnome-shell --wayland --display-server --sm-disable

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Package: gnome-shell 
  Version: 3.25.91-0ubuntu4

  marcogh@fate:~$ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  
  Since a couple of version of gnome-shell, --wayland doesn't work anymore.

  When launching from console with:

gnome-shell --wayland --display-server --mode=classic

  the screen remains black, the cursor appears in the middle, and
  nothing else.

  killing gnome-shell from remote ssh brings the console back, with no
  error.

  Curiously, it works (and it's wayland) when i add

--mode=initial-setup

  The Xorg version works fine.

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

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

[Desktop-packages] [Bug 1716503] Re: gnome-shell --wayland works only when --mode=initial-setup

[Daniel van Vugt]

Your log shows repeating errors from "gnome-shell --wayland ..."

set 13 10:51:11 fate dbus[772]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.1" (uid=0 pid=757 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.76" (uid=1000 pid=1629 comm="gnome-shell --wayland 
--display-server --mode=clas")
set 13 10:51:11 fate dbus[772]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.1" (uid=0 pid=757 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.76" (uid=1000 pid=1629 comm="gnome-shell --wayland 
--display-server --mode=clas")
set 13 10:51:11 fate dbus[772]: [system] Rejected send message, 2 matched 
rules; type="error", sender=":1.1" (uid=0 pid=757 
comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error 
name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" 
destination=":1.76" (uid=1000 pid=1629 comm="gnome-shell --wayland 
--display-server --mode=clas")

That makes me think some extra environment is required to make it work.
Either that or systemd-logind is preventing it from working and requires
some custom syntax.

Have you tried waiting for a full minute or two on the black screen? If
a DBus call is timing out then each one will require 25 seconds to
unblock.

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

Title:
  gnome-shell --wayland works only when --mode=initial-setup

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Package: gnome-shell 
  Version: 3.25.91-0ubuntu4

  marcogh@fate:~$ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  
  Since a couple of version of gnome-shell, --wayland doesn't work anymore.

  When launching from console with:

gnome-shell --wayland --display-server --mode=classic

  the screen remains black, the cursor appears in the middle, and
  nothing else.

  killing gnome-shell from remote ssh brings the console back, with no
  error.

  Curiously, it works (and it's wayland) when i add

--mode=initial-setup

  The Xorg version works fine.

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

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

[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

[Daniel van Vugt]

** Tags added: nvidia

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

Title:
  gdm3, hybrid nvidia with modeset=1, no external monitors detected

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Desktop-packages] [Bug 1716872] Re: Alt+Tab inconsistent behavior between Alt+Backtick/Tilde and down arrow key

[Daniel van Vugt]

** Summary changed:

- alt-tab inconsistent behavior between alt+ and down array key
+ Alt+Tab inconsistent behavior between Alt+Backtick/Tilde and down arrow key

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

Title:
  Alt+Tab inconsistent behavior between Alt+Backtick/Tilde and down
  arrow key

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

Bug description:
  There is an inconsistent behavior when you want to only raise the last 
focused window of an application:
  1. Press Alt+Tab until the switcher is visible and you go to the hilight the 
desired multi-window application. Keep alt pressed
  2. a) if you press the down arrow key, the first window of that application 
is hilighted and you can raise only that instance if desired
 b) if you press key-above-tab (² or ~, depending on your keyboard 
configuration), however the second window of that application is highlight, so 
you need to cycle back all the way down to first one to only raise that one.

  I suggest that when the switcher is displayed, after an alt-tab with
  alt keep being pressed, the first key-above-tab press highlight the
  first window instead of the second (as if you pressed the down arrow
  key).

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

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

[Desktop-packages] [Bug 1508146] Re: alt + left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Daniel van Vugt]

** Summary changed:

- alt + left/right arrows switch between tty consoles, cannot disable
+ alt + left/right arrows switch between tty consoles (Gnome Shell vanishes), 
cannot disable

** Summary changed:

- alt + left/right arrows switch between tty consoles (Gnome Shell vanishes), 
cannot disable
+ Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), 
cannot disable

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

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

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

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Desktop-packages] [Bug 1716415] Re: Alt + Tab then Alt + Right / Left arrow logs me out

[Daniel van Vugt]

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

Duplicate of bug 1508146 maybe?

** This bug has been marked a duplicate of bug 1508146
   alt + left/right arrows switch between tty consoles, cannot disable

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

Title:
  Alt + Tab then Alt + Right / Left arrow logs me out

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  One of my systems if I use Alt + Tab to launch the window switcher and
  then use Alt + Right or Left arrow to switch windows I either receive
  a tty or get the gdm lock screen. Neither behavior is what I'd expect
  - the key stroke moving through the window list.  This seems to work
  on another system of mine and certainly did work on this system
  (otherwise I wouldn't be using the key stroke) so perhaps a package
  was updated and I haven't rebooted yet?

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 11 07:32:15 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1698 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  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/1716415/+subscriptions

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

[Desktop-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations

[Daniel van Vugt]

I'm not comfortable classifying this as "Wishlist" with the original
description because that implies it's something we would do if we had
time. Actually, animations are important to achieving optical flow,
which guides human perception of what's happening.

So I strongly disagree with disabling animations by default, but do
agree the current ones are very poor and need improving. For example,
see bug 1713021.

I'm not quite sure what you mean by distortion in test case 1 though.
The transitions to/from fullscreen retain the original square pixel
aspect ratio so there is zero distortion. Can you clarify what you mean?
Maybe provide an external video or is "distortion" the wrong word?


** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Incomplete

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

Title:
  Add option to disable gnome-shell animations

Status in ubuntu-settings package in Ubuntu:
  Incomplete

Bug description:
  I believe doing so will provide the better experience for most users. Those 
that see use in it can enable if desired.
  Am filing this bug first rather than specific against gnome-shell because 
this is immediately  remedied in settings & there are reports of other poor 
behavior than the below test case.

  Test case 1:
  In current 'pseudo' default of xorg
  In any common video player (totem, vlc, mpv, ect.) open a video.
  Go from window to fullscreen, fullscreen to windowed, notice the distortion.

  May be even worse in wayland or when using hw decoding.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-settings 17.10.15
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 17:21:52 2017
  InstallationDate: Installed on 2017-09-10 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations

[Daniel van Vugt]

** Summary changed:

- Please consider disabling gnome-shell animations by default
+ Add option to disable gnome-shell animations

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

Title:
  Add option to disable gnome-shell animations

Status in ubuntu-settings package in Ubuntu:
  Incomplete

Bug description:
  I believe doing so will provide the better experience for most users. Those 
that see use in it can enable if desired.
  Am filing this bug first rather than specific against gnome-shell because 
this is immediately  remedied in settings & there are reports of other poor 
behavior than the below test case.

  Test case 1:
  In current 'pseudo' default of xorg
  In any common video player (totem, vlc, mpv, ect.) open a video.
  Go from window to fullscreen, fullscreen to windowed, notice the distortion.

  May be even worse in wayland or when using hw decoding.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-settings 17.10.15
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 17:21:52 2017
  InstallationDate: Installed on 2017-09-10 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1117944] Re: intltool confused by separate build-dir

[Aleksander Morgado]

Yeah I know, it's just not my problem any more. Everyone should migrate,
gettext is at least maintained.

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

Title:
  intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Confirmed

Bug description:
  systemd uses 'intltool-update -m' from intltoolize in its 'make check'.
  $(top_srcdir)/po/POTFILES.skip contains the name of a generated file 
(src/core/org.freedesktop.systemd1.policy.in), which will be generated as 
$(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If 
$(builddir)==$(srcdir) than everything works fine. When they are different, 
there's no way to instruct intltool-update to skip the file. Since the name of 
the build directory is not known and can be arbitrary, there should be a way to 
instruct intltool-update to ignore files relative to the $(top_builddir), or 
something like that. One option would be to turn the file list into a list of 
globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in 
our case).

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

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

[Desktop-packages] [Bug 1717084] Re: No menu from systray icon

[Till Kamppeter]

** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  No menu from systray icon

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  There is no menu from clicking the left or right mouse buttons on the systray 
icon from the hplip-gui package in Ubuntu 17.10. Other systray icons, like the 
one from Dropbox, can be fixed by setting XDG_CURRENT_DESKTOP=Unity before 
running the program.  However, this does not restore the systray menu for the 
hplip-gui package:
  XDG_CURRENT_DESKTOP=Unity hp-systray

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

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

[Desktop-packages] [Bug 1717113] [NEW] FTBFS on armhf and s390x in Artful

[Balint Reczey]

Public bug reported:

Thunderbird 1:52.2.1+build1-0ubuntu1 fails to build in Artful.

https://launchpad.net/ubuntu/+source/thunderbird/1:52.2.1+build1-0ubuntu1/+build/12854586
 :
...
  ^~~~
In file included from 
/<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/nsExceptionHandler.cpp:62:0,
 from 
/<>/thunderbird-52.2.1+build1/obj-arm-linux-gnueabihf/toolkit/crashreporter/Unified_cpp_crashreporter0.cpp:2:
/<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/google-breakpad/src/client/linux/handler/exception_handler.h:194:21:
 error: field ‘context’ has incomplete type ‘google_breakpad::ucontext’
 struct ucontext context;
 ^~~
/<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/google-breakpad/src/client/linux/handler/exception_handler.h:194:12:
 note: forward declaration of ‘struct google_breakpad::ucontext’
 struct ucontext context;
^~~~
/<>/thunderbird-52.2.1+build1/mozilla/config/rules.mk:951: recipe for 
target 'Unified_cpp_crashreporter0.o' failed
make[5]: *** [Unified_cpp_crashreporter0.o] Error 1
...

The new upstream release (52.3.0) may fix the issue.

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


** Tags: ftbfs

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

Title:
  FTBFS on armhf and s390x in Artful

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Thunderbird 1:52.2.1+build1-0ubuntu1 fails to build in Artful.

  
https://launchpad.net/ubuntu/+source/thunderbird/1:52.2.1+build1-0ubuntu1/+build/12854586
 :
  ...
^~~~
  In file included from 
/<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/nsExceptionHandler.cpp:62:0,
   from 
/<>/thunderbird-52.2.1+build1/obj-arm-linux-gnueabihf/toolkit/crashreporter/Unified_cpp_crashreporter0.cpp:2:
  
/<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/google-breakpad/src/client/linux/handler/exception_handler.h:194:21:
 error: field ‘context’ has incomplete type ‘google_breakpad::ucontext’
   struct ucontext context;
   ^~~
  
/<>/thunderbird-52.2.1+build1/mozilla/toolkit/crashreporter/google-breakpad/src/client/linux/handler/exception_handler.h:194:12:
 note: forward declaration of ‘struct google_breakpad::ucontext’
   struct ucontext context;
  ^~~~
  /<>/thunderbird-52.2.1+build1/mozilla/config/rules.mk:951: recipe 
for target 'Unified_cpp_crashreporter0.o' failed
  make[5]: *** [Unified_cpp_crashreporter0.o] Error 1
  ...

  The new upstream release (52.3.0) may fix the issue.

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

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

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

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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:
  During upgrade from UbuntuMATE 17.04 to 17.10b1 using update-manager
  -d, I got a dialog box which read "Could not install 'cracklib-
  runtime'

  The upgrade will continue but the 'cracklib-runtime' package may not
  be in a working state. Please consider submitting a bug report about
  it.

  dependency problems - leaving triggers unprocessed".

  At reboot, a message came up that the upgrade failed.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-5build1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Wed Sep 13 14:55:00 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc3
  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-09-13 (0 days ago)

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

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

[Desktop-packages] [Bug 1717084] [NEW] No menu from systray icon

[Jason Wood]

Public bug reported:

There is no menu from clicking the left or right mouse buttons on the systray 
icon from the hplip-gui package in Ubuntu 17.10. Other systray icons, like the 
one from Dropbox, can be fixed by setting XDG_CURRENT_DESKTOP=Unity before 
running the program.  However, this does not restore the systray menu for the 
hplip-gui package:
XDG_CURRENT_DESKTOP=Unity hp-systray

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

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

Title:
  No menu from systray icon

Status in hplip package in Ubuntu:
  New

Bug description:
  There is no menu from clicking the left or right mouse buttons on the systray 
icon from the hplip-gui package in Ubuntu 17.10. Other systray icons, like the 
one from Dropbox, can be fixed by setting XDG_CURRENT_DESKTOP=Unity before 
running the program.  However, this does not restore the systray menu for the 
hplip-gui package:
  XDG_CURRENT_DESKTOP=Unity hp-systray

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

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

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

[grenouille]

Public bug reported:

During upgrade from UbuntuMATE 17.04 to 17.10b1 using update-manager -d,
I got a dialog box which read "Could not install 'cracklib-runtime'

The upgrade will continue but the 'cracklib-runtime' package may not be
in a working state. Please consider submitting a bug report about it.

dependency problems - leaving triggers unprocessed".

At reboot, a message came up that the upgrade failed.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: cracklib-runtime 2.9.2-5build1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
Date: Wed Sep 13 14:55:00 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~rc3
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-09-13 (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/1717085

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:
  During upgrade from UbuntuMATE 17.04 to 17.10b1 using update-manager
  -d, I got a dialog box which read "Could not install 'cracklib-
  runtime'

  The upgrade will continue but the 'cracklib-runtime' package may not
  be in a working state. Please consider submitting a bug report about
  it.

  dependency problems - leaving triggers unprocessed".

  At reboot, a message came up that the upgrade failed.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cracklib-runtime 2.9.2-5build1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Wed Sep 13 14:55:00 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.13, python-minimal, 2.7.13-2
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc3
  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-09-13 (0 days ago)

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

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

[Desktop-packages] [Bug 1712400] Re: [RFE] Show Ubuntu logo on the GDM login screen

[Jeremy Bicha]

This is fixed now:

https://launchpad.net/ubuntu/+source/ubuntu-settings/17.10.15

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

** Changed in: ubuntu-ux
   Status: New => Fix Released

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Invalid

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

Title:
  [RFE] Show Ubuntu logo on the GDM login screen

Status in Ubuntu UX:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  Fedora, Debian and many other distributions have their logo displayed
  on the bottom of the GDM screen, Ubuntu has nothing there. I think it
  could be a good idea to show Ubuntu logo or other Ubuntu branding
  there.

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

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

[Desktop-packages] [Bug 1704618] Dependencies.txt

[Apport retracing service]

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1704618/+attachment/4949728/+files/Dependencies.txt

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

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

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  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/1704618/+subscriptions

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

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

[Apport retracing service]

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1704618/+attachment/4949730/+files/Stacktrace.txt

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

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

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  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/1704618/+subscriptions

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

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

[Apport retracing service]

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1704618/+attachment/4949731/+files/ThreadStacktrace.txt

** Tags removed: apport-request-retrace

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

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

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  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/1704618/+subscriptions

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

[Desktop-packages] [Bug 1704618] Updated stack trace from duplicate bug 1717042

[Apport retracing service]

Package: gnome-control-center 1:3.25.92.1-0ubuntu2
ProcCmdline: gnome-control-center --overview

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

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

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  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/1704618/+subscriptions

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

[Desktop-packages] [Bug 1704618] ProcMaps.txt

[Apport retracing service]

** Attachment added: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1704618/+attachment/4949729/+files/ProcMaps.txt

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

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

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  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/1704618/+subscriptions

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

[Desktop-packages] [Bug 1717042] Re: gnome-control-center crashed with SIGSEGV in ffi_call_unix64(). Crash whent i want to unlock user preferences in settings app

[Apport retracing service]

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

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 #1704618, 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/1717042/+attachment/4949714/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-control-center crashed with SIGSEGV in ffi_call_unix64(). Crash
  whent i want to unlock user preferences in settings app

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

Bug description:
  App crash whent i want to unlock user preferences in settings app in
  order to delete my old system account

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.25.92.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 16:39:10 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-04-14 (152 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7fb571843499:cmpq   $0x0,0x58(%rax)
   PC (0x7fb571843499) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to artful on 2017-09-04 (9 days ago)
  UserGroups: adm lpadmin sambashare sudo

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

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

[Desktop-packages] [Bug 1010724] Re: NM fails to start dnsmasq such that it listens on ::1

[miip]

It's 2017 now, this is still broken. Please fix this.

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

Title:
  NM fails to start dnsmasq such that it listens on ::1

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  I have IPv6 activated on Ubuntu 12.04 LTS and I receive an IPv6
  address through DHCPv6. However, requests sent through IPv6 fail. For
  example:

  strainu@emily:~$ dig  -6 google.com

  ; <<>> DiG 9.8.1-P1 <<>>  -6 google.com
  ;; global options: +cmd
  ;; connection timed out; no servers could be reached

  But:

  strainu@emily:~$ dig  google.com

  ; <<>> DiG 9.8.1-P1 <<>>  google.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60426
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

  ;; QUESTION SECTION:
  ;google.com.  IN  

  ;; ANSWER SECTION:
  google.com.   94  IN  2a00:1450:400d:805::1000

  
  Looking into /etc/resolv.conf, I see:

  strainu@emily:~$ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 127.0.0.1
  search lan

  And with netstat:

  strainu@emily:~$ netstat -ln
  Active Internet connections (only servers)
  Proto Recv-Q Send-Q Local Address   Foreign Address State 
 
  tcp0  0 127.0.0.1:530.0.0.0:*   LISTEN
 
  tcp0  0 127.0.0.1:631   0.0.0.0:*   LISTEN
 
  tcp6   0  0 ::1:631 :::*LISTEN
 
  udp0  0 127.0.0.1:530.0.0.0:* 
 
  udp0  0 0.0.0.0:68  0.0.0.0:* 
 
  udp0  0 0.0.0.0:53530.0.0.0:* 
 
  udp0  0 0.0.0.0:38399   0.0.0.0:* 
 
  udp6   0  0 :::47973:::*  
 
  udp6   0  0 :::5353 :::*  

  Apparently, the local dnsmasq server does not listen on IPv6, which is
  wrong. The server should also listen on ::1:53, to allow IPv6-only
  connections. Alternatively, the resolvconf package should write the
  actual DNS server received through DHCPv6 in /etc/resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: resolvconf 1.63ubuntu14
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Sat Jun  9 02:27:02 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to precise on 2012-05-28 (11 days ago)

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

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

[Desktop-packages] [Bug 1716752] Re: LightDM Bypass - lock screen doesn't resize after adding new display

[Robert Ancell]

** Changed in: lightdm (Ubuntu)
   Status: New => Invalid

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

Title:
  LightDM Bypass - lock screen doesn't resize after adding new display

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  I'm able to consistently bypass LightDM and access my desktop without
  a password, simply by plugging in my external monitor. I'm running it
  on Linux Mint - let me know if this bug is more appropriate for their
  issue tracker.

  I made a 1 minute video demonstrating the issue, which might be easier
  to understand than text. Sorry in advance for filming vertically.
  https://www.youtube.com/watch?v=EWs_SQJ1-Ak

  1)

  $ lsb_release -rd
  Description:  Linux Mint 18.2 Sonya
  Release:  18.2

  2)

  $ apt-cache policy lightdm
  lightdm:
Installed: 1.18.3-0ubuntu1.1
Candidate: 1.18.3-0ubuntu1.1
Version table:
   *** 1.18.3-0ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.18.1-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3)

  I plugged in my external monitor to my laptop while it was locked. I
  expected my computer to remain locked even though I had plugged in a
  new display.

  4)

  The new monitor was not covered by LightDM, allowing me to interact
  with it. Additionally, parts of my laptop monitor became uncovered.

  Notes:

  My laptop display is a 3200x1800 QHD (HiDPI) display when it's
  standalone but I downscale it to 1600x900 when it has an attached
  monitor, due to Ubuntu's scaling issues when connecting HiDPI and
  regular monitors. It's possible that LightDM doesn't think to resize,
  or resizes incorrectly, when the laptop screen automatically
  downscales as the new display is attached.

  I use Nvidia's proprietary graphics drivers (nvidia-375) on a GeForce
  840M.

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

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

[Desktop-packages] [Bug 1705280] Re: Gnome software fails to install snap apps with classic confinement

[Robert Ancell]

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

** This bug is no longer a duplicate of bug 1705023
   Do not promote or show classic snaps as installable or display the warning 
before installation
** This bug has been marked a duplicate of bug 1690280
   Classic confined snaps don't install

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

Title:
  Gnome software fails to install snap apps with classic confinement

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I'm trying to install the anbox-installer snap from gnome-software and
  it fails without any advice.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.24.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 19 16:22:02 2017
  InstallationDate: Installed on 2015-03-21 (851 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.24.3-0ubuntu6
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.24.3-0ubuntu6
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago)

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

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

[Desktop-packages] [Bug 1690280] Re: Classic confined snaps don't install

[Launchpad Bug Tracker]

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

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

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

Title:
  Classic confined snaps don't install

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

Bug description:
  [Impact]
  Apps that use classic confinement show up in search results but don't install.

  [Test Case]
  1. Open GNOME Software
  2. Search for a classic snap, e.g. "atom"
  3. Install snap

  Expected result:
  Either:
  a) Snap is installed
  b) Snap is not installed and error given
  c) Snap is installed but user needs to provide some sort of confirmation 
since it is not confined.

  Observed result:
  Snap is not installed, no error given.

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

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

[Desktop-packages] [Bug 1690280] Re: Classic confined snaps don't install

[Launchpad Bug Tracker]

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

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

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

Title:
  Classic confined snaps don't install

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

Bug description:
  [Impact]
  Apps that use classic confinement show up in search results but don't install.

  [Test Case]
  1. Open GNOME Software
  2. Search for a classic snap, e.g. "atom"
  3. Install snap

  Expected result:
  Either:
  a) Snap is installed
  b) Snap is not installed and error given
  c) Snap is installed but user needs to provide some sort of confirmation 
since it is not confined.

  Observed result:
  Snap is not installed, no error given.

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

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

[Desktop-packages] [Bug 1705023] Re: Do not promote or show classic snaps as installable or display the warning before installation

[Robert Ancell]

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

** This bug has been marked a duplicate of bug 1690280
   Classic confined snaps don't install

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

Title:
  Do not promote or show classic snaps as installable or display the
  warning before installation

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  artful desktop

  Test Case:
  1. Search atom (or any classic snap) and install it

  Actual result
  It is not installable in gnome-software and fails without a user visible 
error message.

  Expected result
  When a classic snap is installed from the command line, there is a warning 
message that explains the risk and asks the user to repeat the installation 
with --classic if he understood the message.

  In gnome-software it just fails without any message. There are several 
options:
  1. Do not show classic snaps
  2. Show the warning and the user must acknowledge before proceeding with the 
installation, in which case the snap is installed in classic mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.24.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 14:02:36 2017
  InstallationDate: Installed on 2013-09-03 (1413 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.24.3-0ubuntu6
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1717004] Re: Failed to install an app with classic confinement using Softwarre Store

[Robert Ancell]

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

** This bug has been marked a duplicate of bug 1690280
   Classic confined snaps don't install

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

Title:
   Failed to install an app with classic confinement using Softwarre
  Store

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Tried to install an app with classic confinement using software center
  and it failed with the error in a window

  
  Instalation of Visual Studio Code failed. If the problem persist contact your 
software provider.
  Details:

  Detailed error from the package manager follow:
  snap returned status code 400: Bad Request

  ===

  Then I tried installing through CLI and had the error below 
  ===
  error: This revision of snap "vscode" was published using classic confinement
  and thus may perform arbitrary system changes outside of the security
  sandbox that snaps are usually confined to, which may put your system at
  risk.

 If you understand and want to proceed repeat the command including 
--classic.
  ===

  and it worked using --classic confinement on CLI.

  Shouldn't this warn or auto selects the confinement that was set when
  packaging?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.7-0ubuntu3.17.04.7
  ProcVersionSignature: Ubuntu 4.10.0-34.38-generic 4.10.17
  Uname: Linux 4.10.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 20:26:14 2017
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1691479] Re: can't send message

[rasos]

Issue still relevant with Thunderbird 52.2.1 on Xubuntu 16.04. Even in
safe mode without Add-Ons.

An error occurred executing the cmd_sendButton command: [Exception...
"Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED)
[nsIMsgCompose.expandMailingLists]"  nsresult: "0x80004001
(NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame ::
chrome://messenger/content/messengercompose/MsgComposeCommands.js ::
expandRecipients :: line 4456"  data: no]

Using Webmail until 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/1691479

Title:
  can't send message

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After last thunderbird update, I am not able to send a message from 
Thunderbird.
  I press the send button and nothing happens (I haven't noticed any debug log).
  The same happens with the ctrl+enter combination.
  I have tried to run Thunderbird in the safe mode (all add-ons disabled) and 
the issue is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: thunderbird 1:52.1.1+build1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: openafs
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   5023 F pulseaudio
   /dev/snd/controlC1:  afiergol   5023 F pulseaudio
  BuildID: 20170510140118
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7
  Date: Wed May 17 11:38:11 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Enigmail - {847b3a00-7ab1-11d4-8f02-006008948af5}
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Polski Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-04-02 (775 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   [Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
   
[Profile]/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.1.1/20170510140118 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (28 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3009CD10002:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3009CD10002
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1716833] Re: NM manages /etc/resolv.conf directly in artful after removal of resolvconf

[Dimitri John Ledkov]

current base cloud-image does not have resolvconf, but has ifupdown.

The following happens:

1) cloud-init starts
2) picks ifupdown renderer
3) renders eni
4) which uses auto dhcp
5) which calls dhclient
6) because there is no resolvconf installed, default make_resolve_conf function 
is used which is internal to isc-dhcp
7) /etc/resolv.conf stops being a symlink and is a regular file
8) NM starts, notices that /etc/resolv.conf is a regular file and thus is not 
managed by resolvconf/resolved
9) NM decides to manage /etc/resolv.conf, poorly

This does kind of mean that on upgrades, if one removes resolvconf without 
removing ifupdown things go pear shaped.
One option is to re-introduce ifupdown dependency on resolvconf.

Another option is to ship isc-dhclient (dhcp-enter-hook) in systemd to
override make_resolve_conf function. I've started writing such a hook
which uses busctl to feed per-link dhcp info to resolved. However, that
has it's own problems. dbus is not started early enough, and there is no
private socket to resolved, meaning that updates are getting lost on
boot when ifup@.service units are udev triggered on hotplug. Currently
working on preserving state in /run and replaying isc-dhclient gathered
settings to resolved.

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

Title:
  NM manages /etc/resolv.conf directly in artful after removal of
  resolvconf

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

Bug description:
  The nplan autopkgtests are now failing in artful following the removal
  of resolvconf from the base system, with the following error:

  ==
  FAIL: test_manual_addresses (__main__.TestNetworkManager)
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.4I4oae/build.Xcu/nplan-0.26/tests/integration.py", 
line 1110, in test_manual_addresses
  self.assertRegex(resolv_conf, 'search.*fakesuffix')
  AssertionError: Regex didn't match: 'search.*fakesuffix' not found in '# 
Generated by NetworkManager\nnameserver 127.0.1.1\n'

  
  It is possible that there is *also* a bug with nplan's integration with 
systemd-resolved; however, what this error message exposes is that NM is 
overwriting /etc/resolv.conf when this should now be managed by 
systemd-resolved instead.

  NM needs to inject its DNS server information into resolved instead of
  editing /etc/resolv.conf directly.

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[Josep Pujadas-Jubany]

We migrated all the computers to Lubuntu (Ubuntu + LXDE) 16.04 64 bit.
The problem is solved for us.

We had the problem with Lubuntu 14.04 32 & 64 bit with kernel enablement stack.
( https://wiki.ubuntu.com/Kernel/LTSEnablementStack )

We can't test this with 32 bit systems because we haven't them anymore.

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Relevant details]
  This bug also affects Trusty and all distributions based on it, like 
Elementary OS Freya.

  
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1716966] Re: package ubuntu-software 3.22.7-0ubuntu3.17.04.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package ubuntu-software 3.22.7-0ubuntu3.17.04.7 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in dpkg package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  i don't know what it is.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-software 3.22.7-0ubuntu3.17.04.7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Sep 13 22:54:37 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-09-13 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gnome-software
  Title: package ubuntu-software 3.22.7-0ubuntu3.17.04.7 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716966] Re: package ubuntu-software 3.22.7-0ubuntu3.17.04.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Title:
  package ubuntu-software 3.22.7-0ubuntu3.17.04.7 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in dpkg package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  i don't know what it is.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-software 3.22.7-0ubuntu3.17.04.7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Sep 13 22:54:37 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-09-13 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gnome-software
  Title: package ubuntu-software 3.22.7-0ubuntu3.17.04.7 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1713742] Re: [snap] libreoffice 5.4.0 snap has incorrect file permissions for some files installed by stage packages

[Olivier Tilloy]

The snap for libreoffice 5.3.4.2 doesn't have those files, it doesn't
have messed up directory permissions for $SNAP/usr/share/application-
registry and $SNAP/usr/share/mime-info either.

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

Title:
  [snap] libreoffice 5.4.0 snap has incorrect file permissions for some
  files installed by stage packages

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  In the snap built by launchpad at
  https://code.launchpad.net/~libreoffice/+snap/libreoffice, the
  following directories have incorrect permissions:

  drw-r--r--$SNAP/usr/share/application-registry
  drw-r--r--$SNAP/usr/share/mime-info

  Both are missing the executable flag. This triggers bug #1712476,
  where the store refuses the snap.

  Those paths are being installed by openjdk-8-jre as a stage package,
  and I'm seeing that libreoffice-common also installs files into those
  paths, so it could very well be that building libreoffice tempers with
  the original permissions.

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

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

[Desktop-packages] [Bug 1717012] [NEW] package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal instal

[Thomas Kügler]

Public bug reported:

no further

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libwacom2:amd64 0.22-1~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Sep 13 20:50:01 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgHistoryLog:
 Start-Date: 2017-09-13  20:49:13
 Commandline: apt-get install -f
 Requested-By: thomas (1000)
 Install: linux-image-extra-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, 
automatic), linux-headers-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, 
automatic), linux-image-4.10.0-33-generic:amd64 (4.10.0-33.37~16.04.1, 
automatic), linux-headers-4.10.0-33:amd64 (4.10.0-33.37~16.04.1, automatic)
 Upgrade: linux-image-generic-hwe-16.04:amd64 (4.10.0.32.34, 4.10.0.33.35), 
linux-generic-hwe-16.04:amd64 (4.10.0.32.34, 4.10.0.33.35), 
linux-headers-4.10.0-32:amd64 (4.10.0-32.36~16.04.1, 4.10.0-32.36~16.04.1), 
linux-headers-generic-hwe-16.04:amd64 (4.10.0.30.33, 4.10.0.33.35)
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller 
[10cf:150a]
InstallationDate: Installed on 2017-07-22 (53 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: FUJITSU LIFEBOOK AH530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=27e085d5-ec9d-4e23-81e3-fe76537c7d5c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libwacom
Title: package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to install/upgrade: 
Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  
nochmal installieren, bevor Sie die Konfiguration versuchen.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.19
dmi.board.name: FJNBB06
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd08/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK AH530
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Sep 13 21:38:57 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

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


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

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

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

Status in libwacom package in Ubuntu:
  New

Bug description:
  no further

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libwacom2:amd64 0.22-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Sep 13 20:50:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2017-09-13  20:49:13
   Commandline: apt-get install -f
   Requested-By: thomas (1000)
  

[Desktop-packages] [Bug 1614593] Re: gimp freezes at end of cage-base transform

[Ads20000]

(fixed by depending on gegl-0.2)

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

Title:
  gimp freezes at end of cage-base transform

Status in The Gimp:
  Confirmed
Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  
  Hello.

  I am currently unable to apply the cage-base transform, whatever the
  image: at the end of the two first computations (creation of the cage
  and first deformation), gimp freezes (at the last pixel of the
  circle)!

  And no way to get it back...  Except closing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gimp 2.8.16-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug 18 17:36:44 2016
  InstallationDate: Installed on 2013-07-29 (1116 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (18 days ago)

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

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

[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

[kabeza]

Hi guys

Does anyone know if some kinda-new fix or workaround was released for
Freya in these latest months?

I've same versions/config/OS as @ledel (previous post)

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

Title:
  Mouse cursor lost when unlocking with Intel graphics

Status in elementary OS:
  Fix Released
Status in xf86-video-intel:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel source package in Xenial:
  Fix Released
Status in xserver-xorg-video-intel package in Debian:
  Fix Released

Bug description:
  [Relevant details]
  This bug also affects Trusty and all distributions based on it, like 
Elementary OS Freya.

  
  [Impact]
  Mouse cursor is no longer visible after VT-switch for systems with Intel 
graphics.

  Switching VTs again may cause the cursor to become visible again.
  - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7)

  This is often observed in systems that lock the session and return to
  the greeter (including at least Xubuntu, Ubuntu Mate, and elementary
  OS).

  [Test Case]
  (Requires a lightdm-based screen locking solution)
  1. Start a new session.
  2. Lock your screen.
  2a. You are redirected to the lightdm greeter.
  3. Login/Unlock your session.
  4. Cursor is no longer visible.

  [Regression Potential]
  remains to be seen

  ===

  [Original Report]
  Cursor is visible at unlock screen either after returning from suspend or 
just locking.

  After unlocking screen cursor is invisible.

  Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor
  returns

  

  no matter if you suspend or sleep, to swap or disk when you return
  from it, the mouse cursor is missing.you can still move the mouse
  and you can see (because it highlights the window) as you move it
  around.   But the cursor is not displayed on the screen.

  i am using a lenovo W540 laptop.   I downloaded the latest beta on
  april 8 2016.

  this is xubuntu using the xfce window manager.

  the cursor does return if i log off and log back in, but that actually 
defeats the purpose of going to sleep.
  ---
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-08 (2 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: light-locker 1.7.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1614593] Re: gimp freezes at end of cage-base transform

[Ads20000]

This is fixed in the GIMP snap. Install with `sudo snap install gimp`.

https://forum.snapcraft.io/t/call-for-testing-gimp/1281/41

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

Title:
  gimp freezes at end of cage-base transform

Status in The Gimp:
  Confirmed
Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  
  Hello.

  I am currently unable to apply the cage-base transform, whatever the
  image: at the end of the two first computations (creation of the cage
  and first deformation), gimp freezes (at the last pixel of the
  circle)!

  And no way to get it back...  Except closing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gimp 2.8.16-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug 18 17:36:44 2016
  InstallationDate: Installed on 2013-07-29 (1116 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (18 days ago)

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

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

[Desktop-packages] [Bug 1708664] Re: usb 1-1.4: device descriptor read/64, error -110

[Phillip Susi]

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

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

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


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

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

Title:
  usb 1-1.4: device descriptor read/64, error -110

Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  ERRORS:

  usb 1-1.4: device descriptor read/64, error -110
  usb 1-1.4: device not accepting address 5, error -32
  Bluetooth: hci0 command 0x0c56 tx timeout

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udisks2 2.1.7-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug  4 16:39:00 2017
  InstallationDate: Installed on 2017-08-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ARCELIK 13Y-GNB1562A2I3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=44d38c50-3e9a-4d6b-8412-f82a0dd15f67 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  Symptom: storage
  Title: No permission to access files on storage device
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P023
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr203:bd04/03/2012:svnARCELIK:pn13Y-GNB1562A2I3:pvrV107:rvnPEGATRONCORPORATION:rnP023:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.name: 13Y-GNB1562A2I3
  dmi.product.version: V107
  dmi.sys.vendor: ARCELIK

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

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

[Desktop-packages] [Bug 1716752] Re: LightDM Bypass - lock screen doesn't resize after adding new display

[Rodney Folz]

I filed a new bug with Cinnamon at https://github.com/linuxmint
/cinnamon-screensaver/issues/246. Feel free to close this issue - I
don't seem to have that option available to me. Thanks for your quick
response and helpful triage!

** Bug watch added: github.com/linuxmint/cinnamon-screensaver/issues #246
   https://github.com/linuxmint/cinnamon-screensaver/issues/246

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

Title:
  LightDM Bypass - lock screen doesn't resize after adding new display

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm able to consistently bypass LightDM and access my desktop without
  a password, simply by plugging in my external monitor. I'm running it
  on Linux Mint - let me know if this bug is more appropriate for their
  issue tracker.

  I made a 1 minute video demonstrating the issue, which might be easier
  to understand than text. Sorry in advance for filming vertically.
  https://www.youtube.com/watch?v=EWs_SQJ1-Ak

  1)

  $ lsb_release -rd
  Description:  Linux Mint 18.2 Sonya
  Release:  18.2

  2)

  $ apt-cache policy lightdm
  lightdm:
Installed: 1.18.3-0ubuntu1.1
Candidate: 1.18.3-0ubuntu1.1
Version table:
   *** 1.18.3-0ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.18.1-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3)

  I plugged in my external monitor to my laptop while it was locked. I
  expected my computer to remain locked even though I had plugged in a
  new display.

  4)

  The new monitor was not covered by LightDM, allowing me to interact
  with it. Additionally, parts of my laptop monitor became uncovered.

  Notes:

  My laptop display is a 3200x1800 QHD (HiDPI) display when it's
  standalone but I downscale it to 1600x900 when it has an attached
  monitor, due to Ubuntu's scaling issues when connecting HiDPI and
  regular monitors. It's possible that LightDM doesn't think to resize,
  or resizes incorrectly, when the laptop screen automatically
  downscales as the new display is attached.

  I use Nvidia's proprietary graphics drivers (nvidia-375) on a GeForce
  840M.

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

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

[Desktop-packages] [Bug 1717004] [NEW] Failed to install an app with classic confinement using Softwarre Store

[Danilo]

Public bug reported:

Tried to install an app with classic confinement using software center
and it failed with the error in a window


Instalation of Visual Studio Code failed. If the problem persist contact your 
software provider.
Details:

Detailed error from the package manager follow:
snap returned status code 400: Bad Request

===

Then I tried installing through CLI and had the error below 
===
error: This revision of snap "vscode" was published using classic confinement
and thus may perform arbitrary system changes outside of the security
sandbox that snaps are usually confined to, which may put your system at
risk.

   If you understand and want to proceed repeat the command including --classic.
===

and it worked using --classic confinement on CLI.

Shouldn't this warn or auto selects the confinement that was set when
packaging?

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-software 3.22.7-0ubuntu3.17.04.7
ProcVersionSignature: Ubuntu 4.10.0-34.38-generic 4.10.17
Uname: Linux 4.10.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 13 20:26:14 2017
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
   Failed to install an app with classic confinement using Softwarre
  Store

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Tried to install an app with classic confinement using software center
  and it failed with the error in a window

  
  Instalation of Visual Studio Code failed. If the problem persist contact your 
software provider.
  Details:

  Detailed error from the package manager follow:
  snap returned status code 400: Bad Request

  ===

  Then I tried installing through CLI and had the error below 
  ===
  error: This revision of snap "vscode" was published using classic confinement
  and thus may perform arbitrary system changes outside of the security
  sandbox that snaps are usually confined to, which may put your system at
  risk.

 If you understand and want to proceed repeat the command including 
--classic.
  ===

  and it worked using --classic confinement on CLI.

  Shouldn't this warn or auto selects the confinement that was set when
  packaging?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.7-0ubuntu3.17.04.7
  ProcVersionSignature: Ubuntu 4.10.0-34.38-generic 4.10.17
  Uname: Linux 4.10.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 20:26:14 2017
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716986] [NEW] Unity session entry in lightdm has a white circle logo

[Walter Garcia-Fontes]

Public bug reported:

After upgrading to 17.10 from 17.04, and switching back to lightdm from
gdm3 to be able to start the Unity 7 desktop, the entry in the login
screen for Unity 7 has a white circle as a logo (the Ubuntu logo is now
assigned to the default Gnome option). A logo should be created to
distinguish the Unity 7 desktop.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: unity-session 3.25.90-0ubuntu4
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Sep 13 19:31:07 2017
InstallationDate: Installed on 2015-10-17 (696 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: gnome-session
UpgradeStatus: Upgraded to artful on 2017-09-12 (1 days ago)

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


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

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

Title:
  Unity session entry in lightdm has a white circle logo

Status in gnome-session package in Ubuntu:
  New

Bug description:
  After upgrading to 17.10 from 17.04, and switching back to lightdm
  from gdm3 to be able to start the Unity 7 desktop, the entry in the
  login screen for Unity 7 has a white circle as a logo (the Ubuntu logo
  is now assigned to the default Gnome option). A logo should be created
  to distinguish the Unity 7 desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unity-session 3.25.90-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Sep 13 19:31:07 2017
  InstallationDate: Installed on 2015-10-17 (696 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to artful on 2017-09-12 (1 days ago)

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

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

[Desktop-packages] [Bug 1699731] Re: Icons appear corrupted when dragged on the Desktop or in Nautilus

[Taras Denysenko]

Hello Sebastien.
`apt list nautilus` gives the following output, which I assume contains the 
version number in question:

Listing... Done
nautilus/zesty,now 1:3.20.4-0ubuntu2 amd64 [installed]

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

Title:
  Icons appear corrupted when dragged on the Desktop or in Nautilus

Status in Ayatana Design:
  Invalid
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.04 I noticed that dragging an icon from Desktop 
or from a Nautilus window now looks quite strange.
  In both cases the image under cursor, which represents the icon being 
dragged, has no transparency and includes a piece of the background, on which 
the original icon is located, and the dragged icon itself appears to be 
somewhat corrupted. I've attached 2 screenshots, which demonstrate the issue.

  When searching for the solution for this issue, I found the following
  question on askubuntu, which seems to describe the same problem:
  https://askubuntu.com/questions/906452/graphical-glitch-in-nautilus-
  when-dragging-icons . Unfortunately, the question is unanswered and
  there are no mentions of a bug report, so I decided to go ahead and
  submit one myself.

  I am on a laptop running Ubuntu 17.04 with switchable graphics. NVidia
  driver v.375.66 is installed. The problem reproduces regardless of
  which graphics card is selected via nvidia-prime.

  Here's my output from `lspci -k | grep -EA3 'VGA|3D|Display'` command:

  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller
   Kernel driver in use: i915
   Kernel modules: i915
  --
  08:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M 
/ GT 620M/625M/630M/720M] (rev a1)
   Subsystem: Dell GeForce 820M
   Kernel driver in use: nvidia
   Kernel modules: nvidiafb, nouveau, nvidia_375_drm, nvidia_375

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1699731/+subscriptions

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

[Desktop-packages] [Bug 1716529] Re: Wayland will not work with my adm video.

[Dave Stroud]

Did a compete reinstall of ubuntu gnome.  It now works but with a few
problems I think most have been reported. Thanks and sorry.Would like to
close the bug.

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

Title:
  Wayland will not work with my adm video.

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  Am running ubuntu  gnome 17.10 up to date on a HP laptop, with amd
  redeon  video. When trying to log into gnome all I get  is a  black
  screen and then  back to log in screen. Have to log into gnome x. All
  I have read and seen is that wayland will work on amd.

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

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

[Desktop-packages] [Bug 1715211] Re: gvfsd-smb-browse crashed with signal 7

[Sebastien Bacher]

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

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

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

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

Title:
  gvfsd-smb-browse crashed with signal 7

Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  It crashed while the Preferences of epiphany-browser was opening.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Tue Sep  5 20:17:44 2017
  Disassembly: => 0x7ff3b2702fb6:   Cannot access memory at address 
0x7ff3b2702fb6
  ExecutablePath: /usr/lib/gvfs/gvfsd-smb-browse
  InstallationDate: Installed on 2017-06-21 (75 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/lib/gvfs/gvfsd-smb-browse --spawner :1.4 
/org/gtk/gvfs/exec_spaw/3
  Signal: 7
  SourcePackage: gvfs
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: gvfsd-smb-browse crashed with signal 7
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1716529] Re: Wayland will not work with my adm video.

[Sebastien Bacher]

Thank you for your bug report, could you add your syslog and Xorg.0.log
to the bug?

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

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

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

Title:
  Wayland will not work with my adm video.

Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  Am running ubuntu  gnome 17.10 up to date on a HP laptop, with amd
  redeon  video. When trying to log into gnome all I get  is a  black
  screen and then  back to log in screen. Have to log into gnome x. All
  I have read and seen is that wayland will work on amd.

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

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

[Desktop-packages] [Bug 1716419] Re: File Transfer progress indicator would not go away

[Sebastien Bacher]

Thanks but the copy icon in the toolbar is not present in the 16.04
nautilus version, could you check what package you are using exactly?
(dpkg -l | grep nautilus)

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

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

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

Title:
  File Transfer progress indicator would not go away

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I use stock Ubuntu 16.04 with Unity. Since some time I have been
  noticing that the file transfer indicator on launcher icon for
  Nautilus won't go away ( even if file transfer is complete )

  The icon indicator gives an idea that there is still file transfer in
  progress, while there is none. I could see the progress indicator
  across various icon theme. For eg. in Unity Icon Theme, Papirus Icon
  Theme.

  If I remember correctly, it's been there since Sept 2016 ( at the
  least ).

  It would be great if you guys can fix it.

  PS: I tried the commands you gave for a good bug report.I couldn't get
  any output on the terminal for those commands. Just to be clear, I
  have latest updates installed.

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

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

[Desktop-packages] [Bug 1699731] Re: Icons appear corrupted when dragged on the Desktop or in Nautilus

[Sebastien Bacher]

ignore the video card part of the question, that's in the description

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

Title:
  Icons appear corrupted when dragged on the Desktop or in Nautilus

Status in Ayatana Design:
  Invalid
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.04 I noticed that dragging an icon from Desktop 
or from a Nautilus window now looks quite strange.
  In both cases the image under cursor, which represents the icon being 
dragged, has no transparency and includes a piece of the background, on which 
the original icon is located, and the dragged icon itself appears to be 
somewhat corrupted. I've attached 2 screenshots, which demonstrate the issue.

  When searching for the solution for this issue, I found the following
  question on askubuntu, which seems to describe the same problem:
  https://askubuntu.com/questions/906452/graphical-glitch-in-nautilus-
  when-dragging-icons . Unfortunately, the question is unanswered and
  there are no mentions of a bug report, so I decided to go ahead and
  submit one myself.

  I am on a laptop running Ubuntu 17.04 with switchable graphics. NVidia
  driver v.375.66 is installed. The problem reproduces regardless of
  which graphics card is selected via nvidia-prime.

  Here's my output from `lspci -k | grep -EA3 'VGA|3D|Display'` command:

  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller
   Kernel driver in use: i915
   Kernel modules: i915
  --
  08:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M 
/ GT 620M/625M/630M/720M] (rev a1)
   Subsystem: Dell GeForce 820M
   Kernel driver in use: nvidia
   Kernel modules: nvidiafb, nouveau, nvidia_375_drm, nvidia_375

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1699731/+subscriptions

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

[Desktop-packages] [Bug 1699731] Re: Icons appear corrupted when dragged on the Desktop or in Nautilus

[Sebastien Bacher]

thank you for your bug report, what nautilus package version and video
card/driver do you use?

** Changed in: ayatana-design
   Status: New => Invalid

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

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

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

Title:
  Icons appear corrupted when dragged on the Desktop or in Nautilus

Status in Ayatana Design:
  Invalid
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 17.04 I noticed that dragging an icon from Desktop 
or from a Nautilus window now looks quite strange.
  In both cases the image under cursor, which represents the icon being 
dragged, has no transparency and includes a piece of the background, on which 
the original icon is located, and the dragged icon itself appears to be 
somewhat corrupted. I've attached 2 screenshots, which demonstrate the issue.

  When searching for the solution for this issue, I found the following
  question on askubuntu, which seems to describe the same problem:
  https://askubuntu.com/questions/906452/graphical-glitch-in-nautilus-
  when-dragging-icons . Unfortunately, the question is unanswered and
  there are no mentions of a bug report, so I decided to go ahead and
  submit one myself.

  I am on a laptop running Ubuntu 17.04 with switchable graphics. NVidia
  driver v.375.66 is installed. The problem reproduces regardless of
  which graphics card is selected via nvidia-prime.

  Here's my output from `lspci -k | grep -EA3 'VGA|3D|Display'` command:

  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller
   Kernel driver in use: i915
   Kernel modules: i915
  --
  08:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M 
/ GT 620M/625M/630M/720M] (rev a1)
   Subsystem: Dell GeForce 820M
   Kernel driver in use: nvidia
   Kernel modules: nvidiafb, nouveau, nvidia_375_drm, nvidia_375

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1699731/+subscriptions

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

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

[Sebastien Bacher]

** Tags added: apport-request-retrace

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

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

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

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  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/1704618/+subscriptions

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

[Desktop-packages] [Bug 1716775] Re: Please consider disabling gnome-shell animations by default

[Sebastien Bacher]

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please consider disabling gnome-shell animations by default

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  I believe doing so will provide the better experience for most users. Those 
that see use in it can enable if desired.
  Am filing this bug first rather than specific against gnome-shell because 
this is immediately  remedied in settings & there are reports of other poor 
behavior than the below test case.

  Test case 1:
  In current 'pseudo' default of xorg
  In any common video player (totem, vlc, mpv, ect.) open a video.
  Go from window to fullscreen, fullscreen to windowed, notice the distortion.

  May be even worse in wayland or when using hw decoding.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-settings 17.10.15
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 17:21:52 2017
  InstallationDate: Installed on 2017-09-10 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716967] Re: Amarok causes gnome-shell to crash

[monochromec]

The gnome shell seems to be the only environment affected by this issue
- I tried Plasma, Cinnamon, XFCE and Mate. None of them crash when
Amarok exits.

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

Title:
  Amarok causes gnome-shell to crash

Status in amarok package in Ubuntu:
  New

Bug description:
  The subject says it all: when quitting Amarok, the surrounding gnome-
  shell is restarted.

  Apparently, something sends a SIGABRT to the shell:

  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
**
  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: ** AMAROK WAS STARTED 
IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: **
  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: ** amarok --debug 
  **
  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
**
  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) 
are not possible
  Sep 13 18:17:45 darkstar-xps gnome-shell[8058]: JS WARNING: 
[resource:///org/gnome/shell/ui/messageList.js 353]: reference to undefined 
property this._useBodyMarkup
  Sep 13 18:17:45 darkstar-xps gnome-shell[8058]: JS WARNING: 
[resource:///org/gnome/shell/ui/messageList.js 386]: reference to undefined 
property this._useBodyMarkup
  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
  Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) 
are not possible
  Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
  Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
  Sep 13 18:17:46 darkstar-xps gnome-shell[8058]: Allocating size to 
ShellEmbeddedWindow 0x5564c98fe8a0 without calling 
gtk_widget_get_preferred_width/height(). How does 
  the code know the size to allocate?
  Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: "
  Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: User not found
  Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: 
  Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: "
  Sep 13 18:17:50 darkstar-xps kde4-amarok.desktop[8715]: Calling appendChild() 
on a null node does nothing.
  Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: amarok(8717)/kdecore 
(KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
  Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: message repeated 2 
times: [ amarok(8717)/kdecore (KConfigSkeleton) 
KCoreConfigSkeleton::writeConfig:]
  Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: Calling appendChild() 
on a null node does nothing.
  Sep 13 18:17:58 darkstar-xps org.gnome.Shell.desktop[8058]: **
  Sep 13 18:17:58 darkstar-xps org.gnome.Shell.desktop[8058]: 
St:ERROR:st/st-bin.c:186:st_bin_dispose: assertion failed: (priv->child == NULL)
  Sep 13 18:17:58 darkstar-xps gnome-session[7902]: gnome-session-binary[7902]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
  Sep 13 18:17:58 darkstar-xps gnome-session-binary[7902]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6

  
  Amarok seems to end normally as --debug tells me but invoking it from the 
command line produces the same effect as from within the shell: it restarts.

  More than happy to send more info as required.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: amarok 2:2.8.0-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 18:22:05 2017
  InstallationDate: Installed on 2017-08-31 (12 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: amarok
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1714881] Re: no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not optimus)

[Sebastien Bacher]

** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu)

** Changed in: gdm3 (Ubuntu)
   Importance: Undecided => High

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

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

** Also affects: gdm via
   https://bugzilla.gnome.org/show_bug.cgi?id=787207
   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/1714881

Title:
  no  gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia
  (not optimus)

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Triaged

Bug description:
  This is to track 
  https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with 
modeset=1 causes loop, does not launch greeter "

  I don't know if this is an nvidia bug or a gdm3 bug but it requires
  both to reproduce.

  
  [reply] [−] Description t...@tim-richardson.net [reporter] 2017-09-03 
10:46:21 UTC
  Created attachment 359016 [details]
  syslog

  reproduced on two Thinkpad laptops with bios set to Discrete graphics.
  In this mode, the integrated Intel graphics is bypassed by a hardware
  mux and the machines appears to have only Nvidia graphics.

  Environment is Ubuntu 17.10 development version, pre-release packages
  One laptop has Quadro 1000M, the other Quadro M1000M. Both cards are 
supported by the latest Nvidia drivers. 

  Nvidia driver 375 or 384 (as packaged by Ubuntu)
  /etc/modprobe.d/zz-nvidia.conf has
  options nvidia_384_drm modeset=1

  and after that setting 
  sudo update-initramfs -u

  This problem does not occur when 
  lightdm is used in instead of gdm3
  or
  modeset=1 
  is not deployed.

  The session attempted to launch is either gnome or the new "ubuntu"
  desktop session, which is gnome

  The boot process fails.Sometimes there is just black screen (and high
  CPU activity driving the fans) and sometimes there is a message about
  NVIDIA persistence daemon starting and stopping, as well as gdm
  messages.

  I mounted the filesystem after a crash, and I attach syslog.

  In the attached syslog, search for persistenced to see messages like
  this

  Sep  2 12:42:15 tim-ThinkPad-W520 org.gnome.Shell.desktop[1206]: Window 
manager warning: Failed to create renderer: Failed
   to initialize renderer: Missing extension for GBM renderer: 
EGL_KHR_platform_gbm, Failed to find matching EGLDeviceEXT
   Sep  2 12:42:15 tim-ThinkPad-W520 gnome-shell[1206]: Failed to create 
backend: Failed to create MetaRenderer
   Sep  2 12:42:15 tim-ThinkPad-W520 systemd[1]: Starting NVIDIA Persistence 
Daemon...
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Verbose syslog 
connection opened
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Now running with user 
ID 123 and group ID 131
   Sep  2 12:42:15 tim-ThinkPad-W520 systemd[1]: Started NVIDIA Persistence 
Daemon.
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Started (1237)
   Sep  2 12:42:15 tim-ThinkPad-W520 gnome-session[1196]: 
gnome-session-binary[1196]: WARNING: App 'org.gnome.Shell.desktop'
   exited with code 1
   Sep  2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
   Sep  2 12:42:15 tim-ThinkPad-W520 gnome-session-binary[1196]: Unrecoverable 
failure in required component org.gnome.Shell.
   desktop
   Sep  2 12:42:15 tim-ThinkPad-W520 systemd-networkd-wait-online[536]: 
ignoring: lo
   Sep  2 12:42:15 tim-ThinkPad-W520 systemd[1]: Stopping NVIDIA Persistence 
Daemon...
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Received signal 15
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file unlocked.
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: PID file closed.
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: The daemon no longer 
has permission to remove its runtime data
   directory /var/run/nvidia-persistenced
   Sep  2 12:42:15 tim-ThinkPad-W520 nvidia-persistenced: Shutdown (1237)

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

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

[Desktop-packages] [Bug 1716907] Re: Gnome session crash after monitor switch-off/input change.

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the 
crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently. Thanks in advance for your cooperation and understanding.

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

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

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

Title:
  Gnome session crash after monitor switch-off/input change.

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org.

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

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

[Desktop-packages] [Bug 1716601] Re: video decoders don't work correctly

[Sebastien Bacher]

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

** Changed in: gstreamer1.0 (Ubuntu)
   Importance: Undecided => Low

** This bug has been marked a duplicate of bug 1716250
   totem and cheese show bright pink/purple video

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

Title:
  video decoders don't work correctly

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Playing videos sometimes just displays black images (audio coming in
  clearly) or with one colour channel missing (magenta tint mostly).

  Tried with several videos, there seems to be no pattern (avi as well
  as mpeg, different encoders).

  A significant amount of first calls (after waiting a period of
  minutes) brings up black (no video).

  Ubuntu 17.10
  plain installation (with additional media support though)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.2-1
  ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1
  Uname: Linux 4.13.0-10-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 10:03:44 2017
  InstallationDate: Installed on 2017-09-05 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+subscriptions

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

[Desktop-packages] [Bug 1716967] [NEW] Amarok causes gnome-shell to crash

[monochromec]

Public bug reported:

The subject says it all: when quitting Amarok, the surrounding gnome-
shell is restarted.

Apparently, something sends a SIGABRT to the shell:

Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
**
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: ** AMAROK WAS STARTED 
IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: **
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: ** amarok --debug   
**
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
**
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) 
are not possible
Sep 13 18:17:45 darkstar-xps gnome-shell[8058]: JS WARNING: 
[resource:///org/gnome/shell/ui/messageList.js 353]: reference to undefined 
property this._useBodyMarkup
Sep 13 18:17:45 darkstar-xps gnome-shell[8058]: JS WARNING: 
[resource:///org/gnome/shell/ui/messageList.js 386]: reference to undefined 
property this._useBodyMarkup
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) 
are not possible
Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:46 darkstar-xps gnome-shell[8058]: Allocating size to 
ShellEmbeddedWindow 0x5564c98fe8a0 without calling 
gtk_widget_get_preferred_width/height(). How does 
the code know the size to allocate?
Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: "
Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: User not found
Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: 
Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: "
Sep 13 18:17:50 darkstar-xps kde4-amarok.desktop[8715]: Calling appendChild() 
on a null node does nothing.
Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: amarok(8717)/kdecore 
(KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: message repeated 2 
times: [ amarok(8717)/kdecore (KConfigSkeleton) 
KCoreConfigSkeleton::writeConfig:]
Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: Calling appendChild() 
on a null node does nothing.
Sep 13 18:17:58 darkstar-xps org.gnome.Shell.desktop[8058]: **
Sep 13 18:17:58 darkstar-xps org.gnome.Shell.desktop[8058]: 
St:ERROR:st/st-bin.c:186:st_bin_dispose: assertion failed: (priv->child == NULL)
Sep 13 18:17:58 darkstar-xps gnome-session[7902]: gnome-session-binary[7902]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Sep 13 18:17:58 darkstar-xps gnome-session-binary[7902]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6


Amarok seems to end normally as --debug tells me but invoking it from the 
command line produces the same effect as from within the shell: it restarts.

More than happy to send more info as required.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: amarok 2:2.8.0-0ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 13 18:22:05 2017
InstallationDate: Installed on 2017-08-31 (12 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: amarok
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Amarok causes gnome-shell to crash

Status in amarok package in Ubuntu:
  New

Bug description:
  The subject says it all: when quitting Amarok, the surrounding gnome-
  shell is restarted.

  Apparently, something sends a SIGABRT to the shell:

  Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 

Re: [Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Jordi Miralles]

Hi! There is a fix submitted as a patch i. The thread I have been using for a 
while. Works flawlessly for me.
--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

13. Sep 2017 14:55 by 1624...@bugs.launchpad.net:


> Does anyone know if this happens to be fixed in 17.10?  I have little
> hope that the fix is ever going to make into 17.04...
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1624317
>
> Title:
>   systemd-resolved breaks VPN with split-horizon DNS
>
> Status in NetworkManager:
>   Unknown
> Status in network-manager package in Ubuntu:
>   Confirmed
> Status in network-manager source package in Zesty:
>   Confirmed
> Status in network-manager source package in Artful:
>   Confirmed
>
> Bug description:
>   [Impact]
>
>* NetworkManager incorrectly handles dns-priority of the VPN-like
>   connections, which leads to leaking DNS queries outside of the VPN
>   into the general internet.
>
>* Upstream has resolved this issue in master and 1.8 to correctly
>   configure any dns backends with negative dns-priority settings.
>
>   [Test Case]
>
>   #FIXME#
>
>* detailed instructions how to reproduce the bug
>
>* these should allow someone who is not familiar with the affected
>  package to reproduce the bug and verify that the updated package fixes
>  the problem.
>
>   #FIXME#
>
>   [Regression Potential]
>
>* If this issue is changed DNS resolution will change, for certain
>   queries, to go via VPN rather than general internet. And therefore,
>   one may get new/different results or even loose access to
>   resolve/access certain parts of the interent depending on what the DNS
>   server on VPN chooses to respond to.
>
>   [Other Info]
>
>* Original bug report
>
>   I use a VPN configured with network-manager-openconnect-gnome in which
>   a split-horizon DNS setup assigns different addresses to some names
>   inside the remote network than the addresses seen for those names from
>   outside the remote network.  However, systemd-resolved often decides
>   to ignore the VPN’s DNS servers and use the local network’s DNS
>   servers to resolve names (whether in the remote domain or not),
>   breaking the split-horizon DNS.
>
>   This related bug, reported by Lennart Poettering himself, was closed with 
> the current Fedora release at the time reaching EOL:
>   > https://bugzilla.redhat.com/show_bug.cgi?id=1151544
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Desktop-packages] [Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out

[Sebastien Bacher]

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  Settings for external monitor are deleted after reboot, suspension,
  log out

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  New Gnome Settings on Ubuntu 17.10

  Settings for external monitor are working but after reboot/suspension
  /log-out log-in, the system will not remember the setup.

  Example:
  1- open Gnome Settings and select "Devices → Displays"
  2- set the external monitor as "Single Display" and click on "Apply"
  3- log-out

  After log-in the laptop monitor will be set as default instead of the
  external monitor.

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

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

[Desktop-packages] [Bug 1716940] Re: gvfsd-trash crashed with signal 5 in g_main_context_new()

[Bug Watch Updater]

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

** Changed in: gvfs
   Importance: Unknown => Critical

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

Title:
  gvfsd-trash crashed with signal 5 in g_main_context_new()

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  New

Bug description:
  Hello,

  I do not know how this happened.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-daemons 1.33.91-0ubuntu1
  Uname: Linux 4.13.1-041301-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 11:53:40 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  InstallationDate: Installed on 2017-07-05 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 
/org/gtk/gvfs/exec_spaw/0
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-trash crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1716946] Re: gvfsd-network crashed with signal 5 in g_main_context_new()

[Bug Watch Updater]

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

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

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

Title:
  gvfsd-network crashed with signal 5 in g_main_context_new()

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  New

Bug description:
  Hello,

  I do not know how this happened.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.33.91-0ubuntu1
  Uname: Linux 4.13.1-041301-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 12:10:50 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-network
  InstallationDate: Installed on 2017-07-05 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gvfs/gvfsd-network --spawner :1.7 
/org/gtk/gvfs/exec_spaw/3
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-network crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1716957] [NEW] Google maps missing details using Italian locale

[corrado venturini]

Public bug reported:

Using Italian locale most details are missing in Google maps; map displayed 
correctly with US locale. Problem does not occur with chromium.
Problem may be caused by the same reason of 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1716250 and 
https://bugzilla.gnome.org/show_bug.cgi?id=787328
In the attached picture on left the map displayed using US locale, on right 
with Italia locale

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: firefox 50.1.0+build2-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  corrado1393 F pulseaudio
 /dev/snd/controlC0:  corrado1393 F pulseaudio
BuildID: 20161213225349
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 13 17:17:32 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2017-09-12 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170911)
IpRoute:
 default via 192.168.1.1 dev wlo1 proto static metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.8 metric 600
Locales: extensions.sqlite corrupt or missing
Plugins: GNOME Shell Integration - 
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=50.1.0/20161213225349 (In use)
RelatedPackageVersions: gnome-shell 3.25.91-0ubuntu4
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/18/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2211
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.49
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP250G3NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN G=N L=CON B=HP S=PAV
dmi.product.name: HP 250 G3 Notebook PC
dmi.product.version: 0991100600087
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug artful

** Attachment added: "Map with US and Italy locale"
   
https://bugs.launchpad.net/bugs/1716957/+attachment/4949457/+files/Screenshot%20from%202017-09-13%2017-30-54.png

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

Title:
  Google maps missing details using Italian locale

Status in firefox package in Ubuntu:
  New

Bug description:
  Using Italian locale most details are missing in Google maps; map displayed 
correctly with US locale. Problem does not occur with chromium.
  Problem may be caused by the same reason of 
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1716250 and 
https://bugzilla.gnome.org/show_bug.cgi?id=787328
  In the attached picture on left the map displayed using US locale, on right 
with Italia locale

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 50.1.0+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  corrado1393 F pulseaudio
   /dev/snd/controlC0:  corrado1393 F pulseaudio
  BuildID: 20161213225349
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 13 17:17:32 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-09-12 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170911)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto static metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.8 metric 600
  Locales: extensions.sqlite 

[Desktop-packages] [Bug 1716946] Re: gvfsd-network crashed with signal 5 in g_main_context_new()

[Cristian Aravena Romero]

** Information type changed from Private to Public

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

** Also affects: gvfs via
   https://bugzilla.gnome.org/show_bug.cgi?id=787636
   Importance: Unknown
   Status: Unknown

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

Title:
  gvfsd-network crashed with signal 5 in g_main_context_new()

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  New

Bug description:
  Hello,

  I do not know how this happened.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.33.91-0ubuntu1
  Uname: Linux 4.13.1-041301-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 12:10:50 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-network
  InstallationDate: Installed on 2017-07-05 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gvfs/gvfsd-network --spawner :1.7 
/org/gtk/gvfs/exec_spaw/3
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-network crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1716940] Re: gvfsd-trash crashed with signal 5 in g_main_context_new()

[Cristian Aravena Romero]

** Information type changed from Private to Public

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

** Also affects: gvfs via
   https://bugzilla.gnome.org/show_bug.cgi?id=787633
   Importance: Unknown
   Status: Unknown

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

Title:
  gvfsd-trash crashed with signal 5 in g_main_context_new()

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  New

Bug description:
  Hello,

  I do not know how this happened.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-daemons 1.33.91-0ubuntu1
  Uname: Linux 4.13.1-041301-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 13 11:53:40 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-trash
  InstallationDate: Installed on 2017-07-05 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.7 
/org/gtk/gvfs/exec_spaw/0
  Signal: 5
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new_valist () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_initable_new () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-trash crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1716385] Re: crash on change focus between apps in two workspaces

[Edson T. Marques]

I'm doing some tests but there is a possibility that the cause of these
crashs is some or some gnome extensions.

I turned off the extensions:

- Native Windows Placement 
(https://extensions.gnome.org/extension/18/native-window-placement/)
- Auto Move Windows 
(https://extensions.gnome.org/extension/16/auto-move-windows/)
- Window Navigator (https://extensions.gnome.org/extension/10/windownavigator/)

... and I tried to repeat the incident but it looks like the gnome-shell
has stabilized

I'm setting this bug as invalid.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Invalid

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

Title:
  crash on change focus between apps in two workspaces

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

Bug description:
  I believe this bug is related to the video driver but I'm not sure ...
  Anyway there goes the report:

  This is a crash that happens every time I open two different
  applications (for example: Chromium and Nautilus), one of them in
  workspace 1 and the other in workspace 2.

  When I change the focus between them for some time (from 3 to 5
  times), there is a crash that causes, first, the window manager (or
  gnome shell, I'm not sure) to reboot, then, if I insist on trying to
  switch between the applications for some more times, the crash seems
  to be more severe and ubuntu returns to the login screen (gdm3).

  I'm using a dell inspiron 15 series 7000 (gaming), notebook with 2
  displays (one is the display of the notebook itself and the other is
  an LG 23EA53, connected via HDMI and configured as a primary)

  To make the focus change I use the mouse, I click on "Activities" and,
  with the mouse, I click on the application that appears in the
  workspaces pile to the right of the display, below and above,
  successively until the crach occurs.

  Usando Alt-TAB parece, a princípio, que o crash não ocorre... or it
  takes longer to occur :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  BootLog: /dev/sda2: clean, 465520/2293760 files, 2530420/9175040 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 08:43:27 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2017-08-12 (29 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 413c:301d Dell Computer Corp. 
   Bus 001 Device 004: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=dc283744-d6ae-456e-add5-b57366aabd43 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.07
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.07:bd05/24/2017:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83+git20170905.d55d0804-0ubuntu0ricotz
  version.libgl1-mesa-dri: libgl1-mesa-dri 
17.2.0+git20170905+17.2.b4473dd5-0ubuntu0ricotz
  version.libgl1-mesa-glx: libgl1-mesa-glx 
17.2.0+git20170905+17.2.b4473dd5-0ubuntu0ricotz
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
  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

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1716456] Re: crash on click Activities when app is running

[Edson T. Marques]

Thanks for the tip!

I made new tests today and noticed that while keeping the gnome
extensions off, gnome-shell stabilizes completely. I think the crash was
being caused by one of the extensions or the combination of them.

At the moment I'm enjoying the new ubuntu-session interface (with the
gnome-shell) and I'm reviewing the need for extensions that I had
installed more by inertia than by necessity.

I think I can consider this Bug as solved.

Thank you very much for your attention!

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

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

Title:
  crash on click Activities when app is running

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I believe this bug is related to the video driver but I'm not sure ...
  Anyway there goes the report:

  This is a crash that happens every time I open two different
  applications (for example: Chromium and Nautilus), one of them in
  workspace 1 and the other in workspace 2.

  When I change the focus between them for some time (from 3 to 5
  times), there is a crash that causes, first, the window manager (or
  gnome shell, I'm not sure) to reboot, then, if I insist on trying to
  switch between the applications for some more times, the crash seems
  to be more severe and ubuntu returns to the login screen (gdm3).

  I'm using a dell inspiron 15 series 7000 (gaming), notebook with 2
  displays (one is the display of the notebook itself and the other is
  an LG 23EA53, connected via HDMI and configured as a primary)

  To make the focus change I use the mouse, I click on "Activities" and,
  with the mouse, I click on the application that appears in the
  workspaces pile to the right of the display, below and above,
  successively until the crach occurs.

  Using Alt-TAB it seems at first that the crash does not occur ... or
  it takes longer to occur :-)

  This crash occurs when both applications are in the same workspace as
  well ... And if one of the applications is a virtual machine session
  of Virtualbox, crash occurs more quickly (with less focus shifts).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 11 14:46:38 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-12 (29 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170812)
  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/1716456/+subscriptions

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

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

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The problem occurs randomly in Ubuntu 17.10

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4 [modified: 
usr/share/applications/gnome-shell-extension-prefs.desktop]
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Sep 13 10:55:13 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-06-08 (96 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170608)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7fbd791da836:mov0x1a0(%rax),%rax
   PC (0x7fbd791da836) ok
   source "0x1a0(%rax)" (0x01a0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
   meta_monitor_manager_kms_wait_for_flip () from 
/usr/lib/x86_64-linux-gnu/libmutter-1.so.0
  Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out

[Olivier Tilloy]

Reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=787629

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

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

Title:
  Settings for external monitor are deleted after reboot, suspension,
  log out

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

Bug description:
  New Gnome Settings on Ubuntu 17.10

  Settings for external monitor are working but after reboot/suspension
  /log-out log-in, the system will not remember the setup.

  Example:
  1- open Gnome Settings and select "Devices → Displays"
  2- set the external monitor as "Single Display" and click on "Apply"
  3- log-out

  After log-in the laptop monitor will be set as default instead of the
  external monitor.

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

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

[Desktop-packages] [Bug 1716921] Re: Enable quick alt-tab to switch between last windows of the 2 recent applications

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => Wishlist

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

Title:
  Enable quick alt-tab to switch between last windows of the 2 recent
  applications

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

Bug description:
  Alt-tab is generally showing up the switcher and give people the
  ability to switch between applications, raising all windows of an
  application if you don't enter into the window thumbnail subview to
  select a particular window.

  Alt + key above tab enables switching between the last 2 windows of
  the current focused applications.

  A case that happens to more advanced user is to switch between 2
  windows of the last 2 applications. You can see a documentation
  browser in the background for instance and a terminal overlapping it.
  (the terminal has more than one window on this workspace).

  The issue is that you are fine with the terminal on top of the
  browser. However, if you alt-tab to the browser and alt-tab back (even
  without the switcher displayed), you will end up with all windows from
  your terminal raising, and so, covering your browser.

  This is clearly for advanced users, and that's why I think we can
  achieve a smarter/more advanced alt-tab behavior without breaking the
  paradigm:

  In case of a quick alt-tab (before the switcher UI shows up), we can
  cover the power user use-case, which is to switch quickly between the
  last focused window of the last 2 applications.

  To sum that up in a simple case:
  - you have an application with one instance, maximized
  - you have another application with multiple instances, like multiple
terminals, not maximized.
  If you press alt-tab, even quickly, the whole second application would be
  raised (as no window has been selected). The consequence is that you have
  all terminal in front of, for instance, your browser or documentation viewer
  you are using.
  The behavior we implement enables this. However, as soon as the switcher ui
  is displayed to the user, not selecting a particular window instance will
  raise the whole applications. Consequently only "quick alt-tab" flow is 
impacted.

  Here is a video of the current upstream behavior: https://youtu.be/D32VEP0sFk4
  Here is a video of the proposal: https://youtu.be/k-IBk-Fibj4

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

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

[Desktop-packages] [Bug 1716921] [NEW] Enable quick alt-tab to switch between last windows of the 2 recent applications

[Didier Roche]

Public bug reported:

Alt-tab is generally showing up the switcher and give people the ability
to switch between applications, raising all windows of an application if
you don't enter into the window thumbnail subview to select a particular
window.

Alt + key above tab enables switching between the last 2 windows of the
current focused applications.

A case that happens to more advanced user is to switch between 2 windows
of the last 2 applications. You can see a documentation browser in the
background for instance and a terminal overlapping it. (the terminal has
more than one window on this workspace).

The issue is that you are fine with the terminal on top of the browser.
However, if you alt-tab to the browser and alt-tab back (even without
the switcher displayed), you will end up with all windows from your
terminal raising, and so, covering your browser.

This is clearly for advanced users, and that's why I think we can
achieve a smarter/more advanced alt-tab behavior without breaking the
paradigm:

In case of a quick alt-tab (before the switcher UI shows up), we can
cover the power user use-case, which is to switch quickly between the
last focused window of the last 2 applications.

To sum that up in a simple case:
- you have an application with one instance, maximized
- you have another application with multiple instances, like multiple
  terminals, not maximized.
If you press alt-tab, even quickly, the whole second application would be
raised (as no window has been selected). The consequence is that you have
all terminal in front of, for instance, your browser or documentation viewer
you are using.
The behavior we implement enables this. However, as soon as the switcher ui
is displayed to the user, not selecting a particular window instance will
raise the whole applications. Consequently only "quick alt-tab" flow is 
impacted.

Here is a video of the current upstream behavior: https://youtu.be/D32VEP0sFk4
Here is a video of the proposal: https://youtu.be/k-IBk-Fibj4

** Affects: gnome-shell
 Importance: Unknown
 Status: Unknown

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

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

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=787627
   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/1716921

Title:
  Enable quick alt-tab to switch between last windows of the 2 recent
  applications

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Alt-tab is generally showing up the switcher and give people the
  ability to switch between applications, raising all windows of an
  application if you don't enter into the window thumbnail subview to
  select a particular window.

  Alt + key above tab enables switching between the last 2 windows of
  the current focused applications.

  A case that happens to more advanced user is to switch between 2
  windows of the last 2 applications. You can see a documentation
  browser in the background for instance and a terminal overlapping it.
  (the terminal has more than one window on this workspace).

  The issue is that you are fine with the terminal on top of the
  browser. However, if you alt-tab to the browser and alt-tab back (even
  without the switcher displayed), you will end up with all windows from
  your terminal raising, and so, covering your browser.

  This is clearly for advanced users, and that's why I think we can
  achieve a smarter/more advanced alt-tab behavior without breaking the
  paradigm:

  In case of a quick alt-tab (before the switcher UI shows up), we can
  cover the power user use-case, which is to switch quickly between the
  last focused window of the last 2 applications.

  To sum that up in a simple case:
  - you have an application with one instance, maximized
  - you have another application with multiple instances, like multiple
terminals, not maximized.
  If you press alt-tab, even quickly, the whole second application would be
  raised (as no window has been selected). The consequence is that you have
  all terminal in front of, for instance, your browser or documentation viewer
  you are using.
  The behavior we implement enables this. However, as soon as the switcher ui
  is displayed to the user, not selecting a particular window instance will
  raise the whole applications. Consequently only "quick alt-tab" flow is 
impacted.

  Here is a video of the current upstream behavior: https://youtu.be/D32VEP0sFk4
  Here is a video of the proposal: https://youtu.be/k-IBk-Fibj4

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

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

[Desktop-packages] [Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable

[Jeremy LaCroix]

In my case, I am also using keepassxc. But I'm using the AppImage
version rather than the Snap package. (The Snap version doesn't seem to
be able to display a status/tray icon, while the AppImage version does).

It's possible keepassxc is related, or it's a coincidence.

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

Title:
  alt + left/right arrows switch between tty consoles, cannot disable

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

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Desktop-packages] [Bug 1716907] Re: Gnome session crash after monitor switch-off/input change.

[ryzko]

** Package changed: ubuntu => gnome-shell (Ubuntu)

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

Title:
  Gnome session crash after monitor switch-off/input change.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core
  i5-6500 CPU and Intel HD Graphics 530 (skylake GT2). Session is
  crashing (login screen is displayed again) every time I change the
  monitor Input (e.g. from DP to HDMI) or switching off the monitor. It
  is happening since some updated from beginning of September were
  installed. Same situation is for both session types, default Wayland
  and also for X.org.

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

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

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Thomas]

Does anyone know if this happens to be fixed in 17.10?  I have little
hope that the fix is ever going to make into 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/1624317

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Desktop-packages] [Bug 1716885] Re: Community Wallpapers need packaging for 17.10

[Iain Lane]

I converted the PNG to a jpeg, resized them all to 4K, reduced the
quality slightly. The size is now 12M. I hope it's acceptable - if not,
the originals are here for someone else to try to work on. 116M would
increased the size of the ISO by 100M - it's that much bigger than
zesty's wallpapers - that can't happen IMO.

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-wallpapers (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  Community Wallpapers need packaging for 17.10

Status in ubuntu-wallpapers package in Ubuntu:
  In Progress

Bug description:
  The community wallpapers (attached) have been collated by Nathan from
  the entries on Flickr.

  Nathan is asking for our help to package these for 17.10:

  Nathan Haines:  I have a tab-delimited list of the winners (the URLs
  shouldn't be needed for packaging), and the wallpapers.  They need
  resized and optimized to reasonable file sizes and then all the
  package stuff needs done.

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

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

[Desktop-packages] [Bug 1683862] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: package libreoffice-common is already installed and configured

[dino99]

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

** This bug is no longer a duplicate of bug 1656475
   Plenty of packages failing to install: reported as already installed and 
configured
** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to
  install/upgrade: package libreoffice-common is already installed and
  configured

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I leave the computer alone for a few minutes and when I return there
  is a crash.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Mon Apr 17 19:56:14 2017
  DuplicateSignature:
   package:libreoffice-common:1:5.1.6~rc2-0ubuntu1~xenial1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libnss3-nssdb (--configure):
package libnss3-nssdb is already installed and configured
  ErrorMessage: package libreoffice-common is already installed and configured
  InstallationDate: Installed on 2017-04-17 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial1 failed to 
install/upgrade: package libreoffice-common is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716907] [NEW] Gnome session crash after monitor switch-off/input change.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core i5-6500
CPU and Intel HD Graphics 530 (skylake GT2). Session is crashing (login
screen is displayed again) every time I change the monitor Input (e.g.
from DP to HDMI) or switching off the monitor. It is happening since
some updated from beginning of September were installed. Same situation
is for both session types, default Wayland and also for X.org.

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


** Tags: bot-comment
-- 
Gnome session crash after monitor switch-off/input change.
https://bugs.launchpad.net/bugs/1716907
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1713126] Re: package libjpeg62:amd64 1:6b2-2 failed to install/upgrade: package libjpeg62:amd64 is already installed and configured

[dino99]

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

** This bug is no longer a duplicate of bug 1713124
   package libjpeg62:amd64 1:6b2-2 failed to install/upgrade: package 
libjpeg62:amd64 is already installed and configured
** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package libjpeg62:amd64 1:6b2-2 failed to install/upgrade: package
  libjpeg62:amd64 is already installed and configured

Status in libjpeg6b package in Ubuntu:
  New

Bug description:
  ubuntu 16

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg62:amd64 1:6b2-2
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Aug 25 18:24:19 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   multiarch-support 2.23-0ubuntu9
  DuplicateSignature:
   package:libjpeg62:amd64:1:6b2-2
   Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package libjpeg62:amd64 (--configure):
package libjpeg62:amd64 is already installed and configured
  ErrorMessage: package libjpeg62:amd64 is already installed and configured
  InstallationDate: Installed on 2017-08-24 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libjpeg6b
  Title: package libjpeg62:amd64 1:6b2-2 failed to install/upgrade: package 
libjpeg62:amd64 is already installed and configured
  UpgradeStatus: Upgraded to xenial on 2017-08-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1674769] Re: package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: package libpurple-bin is already installed and configured

[dino99]

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

** This bug is no longer a duplicate of bug 1674768
   package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: package 
libpurple-bin is already installed and configured
** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade:
  package libpurple-bin is already installed and configured

Status in pidgin package in Ubuntu:
  New

Bug description:
  I try to install Transmaggedon, and gstreamer. There was a package
  named gstreamer ffmpeg. I choose to install. The installation began,
  but that stop because there is no more package gstreamer for ffmpeg.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpurple-bin 1:2.10.9-0ubuntu3.4
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Tue Mar 21 18:23:37 2017
  DuplicateSignature: package:libpurple-bin:1:2.10.9-0ubuntu3.4:package 
libpurple-bin is already installed and configured
  ErrorMessage: package libpurple-bin is already installed and configured
  InstallationDate: Installed on 2017-03-12 (9 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: pidgin
  Title: package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: 
package libpurple-bin is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Apport retracing service]

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

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 #1714989, 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/1716901/+attachment/4949360/+files/CoreDump.gz

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

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

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

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

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

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

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

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Just doing everyday work on Artful and gnome-shell keeps crashes every
  couple of minutes.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Sep 13 13:06:04 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-05-25 (110 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f119ab6ee32 :
mov(%rdi),%rbp
   PC (0x7f119ab6ee32) ok
   source "(%rdi)" (0x805e) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   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
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1716904] Re: simple-scan page-feeder fails on canon printer mb2050

[Etienne Papegnies]

** Also affects: simple-scan (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-mate

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

Title:
  simple-scan page-feeder fails on canon printer mb2050

Status in simple-scan package in Ubuntu:
  New

Bug description:
  Hi,

  The simple-scan page-feeder option (ctrl-f) does not work on the canon mb2050.
  It does on canon's own scangear2 app, which is open-source (link below)

  http://support-th.canon-asia.com/contents/TH/EN/0100840001.html

  There is also a debian package which works out of the box after
  installing via dpkg

  http://support-th.canon-asia.com/contents/TH/EN/0100840201.html

  If this can be fixed it would be awesome.

  Everything else works, which was a welcome experience in my book.

  Thanks a lot guys,

  Mike

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

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

[Desktop-packages] [Bug 1716900] [NEW] apt-get: order of the dependencies ends in a diffrent result

[Dominik Zogg]

Public bug reported:

While trying to use the php installation delivered by
https://launchpad.net/%7Eondrej/+archive/ubuntu/php, we found out, that
the order within apt-get install change the solved packages.

Which means if we do:
apt-get install php-apcu php7.1-cli => installs newest php and 7.1
apt-get install php7.1-cli php-apcu) => > installs only 7.1

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

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

Title:
  apt-get: order of the dependencies ends in a diffrent result

Status in appstream package in Ubuntu:
  New

Bug description:
  While trying to use the php installation delivered by
  https://launchpad.net/%7Eondrej/+archive/ubuntu/php, we found out,
  that the order within apt-get install change the solved packages.

  Which means if we do:
  apt-get install php-apcu php7.1-cli => installs newest php and 7.1
  apt-get install php7.1-cli php-apcu) => > installs only 7.1

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

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