[Desktop-packages] [Bug 1847551] [NEW] Mutter 3.34.1 broke Night Light, screen color profiles

[Anders Kaseorg]

Public bug reported:

Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
color profile switching.  The commit at fault is
104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
when processing update” (which was intended to fix LP bug 1847044).

Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

** Affects: mutter
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #851
   https://gitlab.gnome.org/GNOME/mutter/issues/851

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/851
   Importance: Unknown
   Status: Unknown

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

Title:
  Mutter 3.34.1 broke Night Light, screen color profiles

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen
  color profile switching.  The commit at fault is
  104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes
  when processing update” (which was intended to fix LP bug 1847044).

  Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851

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

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

[Desktop-packages] [Bug 1844445] Re: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown()

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown()

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I saw this crash shortly after boot.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-session-bin 3.33.92-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-lowlatency 5.3.0-rc8
  Uname: Linux 5.3.0-10-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 17 12:56:57 2019
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-session/gnome-session-binary
  InstallationDate: Installed on 2016-02-19 (1306 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/lib/gnome-session/gnome-session-binary --debug 
--systemd-service --session=gnome
  SegvAnalysis:
   Segfault happened at: 0x7effd96109e8 <__malloc_arena_thread_freeres+88>: 
mov0x0(%r13),%rax
   PC (0x7effd96109e8) ok
   source "0x0(%r13)" (0x7eff0002) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-session
  StacktraceTop:
   tcache_thread_shutdown () at malloc.c:2963
   __malloc_arena_thread_freeres () at arena.c:949
   __libc_thread_freeres () at thread-freeres.c:38
   start_thread (arg=) at pthread_create.c:493
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown()
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (86 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd 
mock plugdev sambashare sbuild sudo wireshark
  separator:

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

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

[Desktop-packages] [Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

[Anders Kaseorg]

This is fixed by
https://gitlab.gnome.org/GNOME/mutter/merge_requests/792 (I tested
850ef518795dcc20d3b9a4f661f70ff8d0ddacb2).

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in Mutter:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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

[Desktop-packages] [Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

[Anders Kaseorg]

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

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in Mutter:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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

[Desktop-packages] [Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

[Anders Kaseorg]

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #771
   https://gitlab.gnome.org/GNOME/mutter/issues/771

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/771
   Importance: Unknown
   Status: Unknown

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in Mutter:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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

[Desktop-packages] [Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

[Anders Kaseorg]

By adding some debugging output to mutter and gnome-shell I verified
that mutter emits the x11-display-opened signal before gnome-shell is
able to connect a handler for it, and the handler never runs.

(Possibly things would be different in the experimental autostart-
xwayland mode, but the whole system froze when I tried to log in with
that enabled.)

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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

[Desktop-packages] [Bug 1843107] Re: Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

[Anders Kaseorg]

Hmm, I upgraded mutter from eoan-proposed and gnome-shell from eoan-
proposed plus those three commits
(https://launchpad.net/~andersk/+archive/ubuntu/ppa, if you want to
check my work), but it didn’t resolve the problem.  Even after a reboot,
gsd-xsettings doesn’t start and X11 applications don’t get themed.

$ dpkg-query -W gir1.2-mutter-5 libmutter-5-0 mutter mutter-common gnome-shell 
gnome-shell-common
gir1.2-mutter-5:amd64   3.33.92-1ubuntu1
gnome-shell 3.33.92-1ubuntu1andersk1
gnome-shell-common  3.33.92-1ubuntu1andersk1
libmutter-5-0:amd64 3.33.92-1ubuntu1
mutter  3.33.92-1ubuntu1
mutter-common   3.33.92-1ubuntu1

$ strings /usr/lib/gnome-shell/libgnome-shell.so | grep x11-display
global.display.connect('x11-display-opened', () => {
global.display.connect('x11-display-closing', () => {

$ systemctl --user status gnome-session-x11-services.target 
gsd-xsettings.target gsd-xsettings.service
● gnome-session-x11-services.target - GNOME session X11 services
   Loaded: loaded (/usr/lib/systemd/user/gnome-session-x11-services.target; 
static; vendor preset: enabled)
   Active: inactive (dead)

● gsd-xsettings.target - GNOME XSettings
   Loaded: loaded (/usr/lib/systemd/user/gsd-xsettings.target; static; vendor 
preset: enabled)
   Active: inactive (dead)

● gsd-xsettings.service - GNOME XSettings
   Loaded: loaded (/usr/lib/systemd/user/gsd-xsettings.service; static; vendor 
preset: enabled)
   Active: inactive (dead)

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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

[Desktop-packages] [Bug 1843107] [NEW] Themes and font settings don’t apply to X apps running in Wayland (g-s-d 3.33.90 → 3.33.92 regression)

[Anders Kaseorg]

Public bug reported:

After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
tweaks are no longer applied to X11 applications when running in a
Wayland session (I tried Firefox and Emacs).  This seems to be because
gsd-xsettings is not running.

Known workarounds:
• downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
• use Xorg instead of Wayland; or
• manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-settings-daemon 3.33.92-1ubuntu1
Uname: Linux 5.2.11-050211-lowlatency x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Fri Sep  6 17:24:02 2019
InstallationDate: Installed on 2016-02-19 (1295 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Themes and font settings don’t apply to X apps running in Wayland
  (g-s-d 3.33.90 → 3.33.92 regression)

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  After upgrading gnome-settings-daemon from 3.33.90-1ubuntu2 to
  3.33.92-1ubuntu1, my GTK theme and font settings selected with gnome-
  tweaks are no longer applied to X11 applications when running in a
  Wayland session (I tried Firefox and Emacs).  This seems to be because
  gsd-xsettings is not running.

  Known workarounds:
  • downgrade gnome-settings-daemon to 3.33.90-1ubuntu2 and reboot; or
  • use Xorg instead of Wayland; or
  • manually start /usr/lib/gnome-settings-daemon/gsd-xsettings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.33.92-1ubuntu1
  Uname: Linux 5.2.11-050211-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Fri Sep  6 17:24:02 2019
  InstallationDate: Installed on 2016-02-19 (1295 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-06-23 (75 days ago)

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Anders Kaseorg]

The situation with apache2 is what I documented in
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1792544/comments/9:

“But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454. (As you can see, this support was added by creating separate
conditionally compiled code paths for PCRE and PCRE2.)

https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570”

trunk is the 2.5.x branch, not 2.4.x.

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Incomplete
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Fix Released

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

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

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

[Desktop-packages] [Bug 1820331] Re: gnome-shell crashed with SIGABRT. Assertion failure in meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"

[Anders Kaseorg]

I hope 3.32.1 will get into Disco, but in case this can’t happen and a
more minimal set of patches is required, these are the nine upstream
patches I added to my mutter package to get it to stop crashing on
wakeup:

fe86694dd renderer/native: Make EGLStream page flip errors non-fatal
1eabaf12d renderer/native: Make the EGLStreams operate in mailbox mode
4cae9b5b1 monitor-manager: Clean up DPMS state tracking
40e7e5d35 renderer-native: Fix page flip retry timeout calculation
53b59d8bf renderer-native: Fake page flipped if power saving when retrying
3cc3b7526 renderer-native: Fake page flipping slower when power saving
88e4ff740 backend: Add API to freeze/thaw frame clock
808a75b23 renderer-native: Add helper to get backend from renderer
b2d0184c6 renderer-native: Freeze frames while retrying to page flip

Note that they were accepted into master nonconsecutively, with other
commits between 1eabaf12d and 4cae9b5b1.

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

Title:
  gnome-shell crashed with SIGABRT. Assertion failure in
  meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode ==
  META_POWER_SAVE_ON"

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

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/509
  https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971

  ---

  In the last few weeks, gnome-shell has been crashing almost every time
  I open my laptop to wake it from suspend.  The rapid pace of package
  updates has stopped Apport from letting me report it until now, but
  the problem persists.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 15 11:22:20 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (1120 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to disco on 2018-12-15 (90 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd 
mock plugdev sambashare sbuild sudo wireshark
  separator:

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

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

[Desktop-packages] [Bug 1820331] Re: gnome-shell crashed with SIGABRT

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGABRT

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In the last few weeks, gnome-shell has been crashing almost every time
  I open my laptop to wake it from suspend.  The rapid pace of package
  updates has stopped Apport from letting me report it until now, but
  the problem persists.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 15 11:22:20 2019
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (1120 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to disco on 2018-12-15 (90 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd 
mock plugdev sambashare sbuild sudo wireshark
  separator:

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

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

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

1.12.4 is in cosmic-proposed now with the upstream fix.

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

** Changed in: network-manager (Ubuntu)
 Assignee: Anders Kaseorg (andersk) => (unassigned)

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1795556] Re: mutter 3.30.0-4 FTBFS

[Anders Kaseorg]

As long as you're working on this package would you mind including the
one-line upstream patch for bug 1788483, if you haven't already?

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

Title:
  mutter 3.30.0-4 FTBFS

Status in mutter package in Ubuntu:
  Invalid

Bug description:
  mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1).
  A full build log is attached.  The relevant part is these test
  failures.

  ==
 clutter 1.26.1: tests/conform/test-suite.log
  ==

  # TOTAL: 83
  # PASS:  81
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  0
  # XPASS: 0
  # ERROR: 2

  .. contents:: :depth: 2

  ERROR: actor-offscreen-redirect
  ===

  # random seed: R02Sb2875ff7949f70873efba32072c693a6
  1..1
  # Start of actor tests
  **
  Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: 
assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 
<= 2)
  # Start of offscreen tests
  Aborted (core dumped)
  Bail out! 
Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion 
failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2)
  ERROR: actor-offscreen-redirect - Bail out! 
Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion 
failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2)

  ERROR: actor-shader-effect
  ==

  # random seed: R02S35d2b55cc4cd821aa7b19454f0028a03
  1..1
  **
  Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed 
(get_pixel (50, 50) == 0xff): (0 == 16711680)
  # Start of actor tests
  Aborted (core dumped)
  Bail out! Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion 
failed (get_pixel (50, 50) == 0xff): (0 == 16711680)
  ERROR: actor-shader-effect - Bail out! 
Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed 
(get_pixel (50, 50) == 0xff): (0 == 16711680)

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

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

[Desktop-packages] [Bug 1795556] Re: mutter 3.30.0-4 FTBFS

[Anders Kaseorg]

That was a local build.  I also saw it on Launchpad with an unrelated
patch (bug 1788483):

https://launchpadlibrarian.net/391298478/buildlog_ubuntu-
cosmic-i386.mutter_3.30.0-4andersk1_BUILDING.txt.gz

However, the failure seems to have disappeared with today’s updates of
other packages, or maybe the tests are just flaky.  I’ll reopen this if
I see the failure again.

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

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

Title:
  mutter 3.30.0-4 FTBFS

Status in mutter package in Ubuntu:
  Invalid

Bug description:
  mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1).
  A full build log is attached.  The relevant part is these test
  failures.

  ==
 clutter 1.26.1: tests/conform/test-suite.log
  ==

  # TOTAL: 83
  # PASS:  81
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  0
  # XPASS: 0
  # ERROR: 2

  .. contents:: :depth: 2

  ERROR: actor-offscreen-redirect
  ===

  # random seed: R02Sb2875ff7949f70873efba32072c693a6
  1..1
  # Start of actor tests
  **
  Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: 
assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 
<= 2)
  # Start of offscreen tests
  Aborted (core dumped)
  Bail out! 
Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion 
failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2)
  ERROR: actor-offscreen-redirect - Bail out! 
Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion 
failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2)

  ERROR: actor-shader-effect
  ==

  # random seed: R02S35d2b55cc4cd821aa7b19454f0028a03
  1..1
  **
  Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed 
(get_pixel (50, 50) == 0xff): (0 == 16711680)
  # Start of actor tests
  Aborted (core dumped)
  Bail out! Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion 
failed (get_pixel (50, 50) == 0xff): (0 == 16711680)
  ERROR: actor-shader-effect - Bail out! 
Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed 
(get_pixel (50, 50) == 0xff): (0 == 16711680)

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

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

[Desktop-packages] [Bug 1795556] [NEW] mutter 3.30.0-4 FTBFS

[Anders Kaseorg]

Public bug reported:

mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1).
A full build log is attached.  The relevant part is these test failures.

==
   clutter 1.26.1: tests/conform/test-suite.log
==

# TOTAL: 83
# PASS:  81
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 2

.. contents:: :depth: 2

ERROR: actor-offscreen-redirect
===

# random seed: R02Sb2875ff7949f70873efba32072c693a6
1..1
# Start of actor tests
**
Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion 
failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2)
# Start of offscreen tests
Aborted (core dumped)
Bail out! Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: 
assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 
<= 2)
ERROR: actor-offscreen-redirect - Bail out! 
Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion 
failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2)

ERROR: actor-shader-effect
==

# random seed: R02S35d2b55cc4cd821aa7b19454f0028a03
1..1
**
Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed 
(get_pixel (50, 50) == 0xff): (0 == 16711680)
# Start of actor tests
Aborted (core dumped)
Bail out! Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion 
failed (get_pixel (50, 50) == 0xff): (0 == 16711680)
ERROR: actor-shader-effect - Bail out! 
Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed 
(get_pixel (50, 50) == 0xff): (0 == 16711680)

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


** Tags: cosmic

** Attachment added: "mutter_3.30.0-4_amd64.build"
   
https://bugs.launchpad.net/bugs/1795556/+attachment/5195672/+files/mutter_3.30.0-4_amd64.build

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

Title:
  mutter 3.30.0-4 FTBFS

Status in mutter package in Ubuntu:
  New

Bug description:
  mutter 3.30.0-4 fails to build from source (regression from 3.30.0-1).
  A full build log is attached.  The relevant part is these test
  failures.

  ==
 clutter 1.26.1: tests/conform/test-suite.log
  ==

  # TOTAL: 83
  # PASS:  81
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  0
  # XPASS: 0
  # ERROR: 2

  .. contents:: :depth: 2

  ERROR: actor-offscreen-redirect
  ===

  # random seed: R02Sb2875ff7949f70873efba32072c693a6
  1..1
  # Start of actor tests
  **
  Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: 
assertion failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 
<= 2)
  # Start of offscreen tests
  Aborted (core dumped)
  Bail out! 
Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion 
failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2)
  ERROR: actor-offscreen-redirect - Bail out! 
Clutter-Conform:ERROR:actor-offscreen-redirect.c:147:verify_results: assertion 
failed (ABS ((int) expected_color_green - (int) pixel[1]) <= 2): (255 <= 2)

  ERROR: actor-shader-effect
  ==

  # random seed: R02S35d2b55cc4cd821aa7b19454f0028a03
  1..1
  **
  Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed 
(get_pixel (50, 50) == 0xff): (0 == 16711680)
  # Start of actor tests
  Aborted (core dumped)
  Bail out! Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion 
failed (get_pixel (50, 50) == 0xff): (0 == 16711680)
  ERROR: actor-shader-effect - Bail out! 
Clutter-Conform:ERROR:actor-shader-effect.c:233:paint_cb: assertion failed 
(get_pixel (50, 50) == 0xff): (0 == 16711680)

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

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

[Desktop-packages] [Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_t

[Anders Kaseorg]

(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)

** Tags added: patch-accepted-upstream

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message() from
  g_assertion_message_expr("assertion failed: (trap->end_sequence ==
  0)") from gdk_x11_display_error_trap_pop_internal() from
  meta_input_settings_x11_set_tablet_keep_aspect()

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

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/294

  ---

  Crash happened when I tried to use Wacom stylus on Dell 7285
  touchscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Aug 23 03:55:08 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-04-20 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   ?? ()
  Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to cosmic on 2018-04-20 (124 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

(Still waiting on sponsorship, but apparently “In Progress” is the right
status for that.)

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

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Anders Kaseorg (andersk)

** Tags added: patch patch-accepted-upstream

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_t

[Anders Kaseorg]

(Is it really correct to mark this as “In Progress” and assigned to me
when there’s nothing else I can do to move this forward except wait for
a sponsor to pay attention?)

** Patch added: "debdiff adding upstream patch, rebased"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1788483/+attachment/5195604/+files/mutter_3.30.0-4_lp1788483.debdiff

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message() from
  g_assertion_message_expr("assertion failed: (trap->end_sequence ==
  0)") from gdk_x11_display_error_trap_pop_internal() from
  meta_input_settings_x11_set_tablet_keep_aspect()

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

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/294

  ---

  Crash happened when I tried to use Wacom stylus on Dell 7285
  touchscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Aug 23 03:55:08 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-04-20 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   ?? ()
  Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to cosmic on 2018-04-20 (124 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty

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

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

[Desktop-packages] [Bug 1788483] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr("assertion failed: (trap->end_sequence == 0)") from gdk_x11_display_error_t

[Anders Kaseorg]

** Patch added: "debdiff adding upstream patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483/+attachment/5195090/+files/mutter_3.30.0-1_lp1788483.debdiff

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message() from
  g_assertion_message_expr("assertion failed: (trap->end_sequence ==
  0)") from gdk_x11_display_error_trap_pop_internal() from
  meta_input_settings_x11_set_tablet_keep_aspect()

Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/294

  ---

  Crash happened when I tried to use Wacom stylus on Dell 7285
  touchscreen.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  Uname: Linux 4.18.3-041803-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Aug 23 03:55:08 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-04-20 (124 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   ?? ()
  Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to cosmic on 2018-04-20 (124 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

** Patch added: "rebased on 1.12.2-0ubuntu5"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5192582/+files/network-manager_1.12.2-0ubuntu5_lp1792745.debdiff

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

** Patch added: "debdiff adding upstream patch"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5191867/+files/network-manager_1.12.2-0ubuntu4_lp1792745.debdiff

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

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

** Also affects: network-manager via
   https://bugzilla.gnome.org/show_bug.cgi?id=797136
   Importance: Unknown
   Status: Unknown

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

Likewise, nginx does not support PCRE2:
https://trac.nginx.org/nginx/ticket/720

** Bug watch added: trac.nginx.org/nginx/ #720
   http://trac.nginx.org/nginx/ticket/720

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

Note to those filing upstream bugs: probably don’t call the old library
“pcre3” since that’s not a thing outside Debian/Ubuntu.

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

I think that completes the analysis of the current state of things.
Although it seems infeasible to demote PCRE at this time, there’s no
reason that should block the promotion of PCRE2, especially seeing as a
bundled copy of PCRE2 is already in main (18.04 and 18.10) via
libqt5core5a.

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

• pam_mount: no PCRE2 support
• nmap: no PCRE2 support
• postfix: no PCRE2 support, 
http://postfix.1071664.n5.nabble.com/Plans-for-using-PCRE-v2-in-Postfix-td83200.html
• pyScss: no PCRE2 support

** Changed in: libpam-mount (Ubuntu)
   Status: New => Incomplete

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

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

** Changed in: python-pyscss (Ubuntu)
   Status: New => Incomplete

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Confirmed
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

• Quagga: no PCRE2 support
• Rasqal: no PCRE2 support
• S-Lang: no PCRE2 support

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

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

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Confirmed
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

• Aide: no PCRE2 support
• Exim: no PCRE2 support, upstream bug: 
https://bugs.exim.org/show_bug.cgi?id=1878
• FreeRADIUS: no PCRE2 support, mentioned in passing: 
https://github.com/FreeRADIUS/freeradius-server/issues/1865
• GLib: no PCRE2 support
• grep: no PCRE2 support

** Bug watch added: bugs.exim.org/ #1878
   http://bugs.exim.org/show_bug.cgi?id=1878

** Bug watch added: github.com/FreeRADIUS/freeradius-server/issues #1865
   https://github.com/FreeRADIUS/freeradius-server/issues/1865

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

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

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  Incomplete
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

Copying from
https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/163/comments/20,
HAProxy and SELinux upstream support PCRE2.

https://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=f2592b29f13907ddf2bba42d00bc41cb8ee5b69b
https://github.com/SELinuxProject/selinux/commit/50f0910cf05bdc1d10710c7c3fb748a178473387

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

apr-util has a false Build-Depends on libpcre3-dev; it should simply be
dropped.  A corresponding Depends was already dropped in
https://bugs.debian.org/757140.

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  Triaged
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792544] Re: demotion of pcre3 in favor of pcre2

[Anders Kaseorg]

Andreas: No, it’s not a bug.  PCRE2 is a new project that’s not intended
to be compatible with the older PCRE (i.e. what Debian misnamed
“pcre3”).  The API is completely different and this is expected.  See
bug 163 for context, and specifically the PCRE2 release announcement
linked in the bug description:

https://lists.exim.org/lurker/message/20150105.162835.0666407a.en.html

That’s why getting rid of PCRE “in favor of” PCRE2 is a pointless way to
frame the issue.  PCRE2 neither replaces nor conflicts with PCRE, as was
pointed out many times in bug 163.

But since we’re apparently gathering information here: although Apache
2.4.x does not support PCRE2, Apache trunk does support PCRE2 as of
r1773454.  (As you can see, this support was added by creating separate
conditionally compiled code paths for PCRE and PCRE2.)

https://github.com/apache/httpd/commit/b1a3338e011a17ad190fb7f66cf5ca9acf353570

** Bug watch added: Debian Bug tracker #757140
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757140

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

Title:
  demotion of pcre3 in favor of pcre2

Status in aide package in Ubuntu:
  New
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  New
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  New
Status in freeradius package in Ubuntu:
  New
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  New
Status in grep package in Ubuntu:
  New
Status in haproxy package in Ubuntu:
  New
Status in libpam-mount package in Ubuntu:
  New
Status in libselinux package in Ubuntu:
  New
Status in nginx package in Ubuntu:
  Triaged
Status in nmap package in Ubuntu:
  New
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in python-pyscss package in Ubuntu:
  New
Status in quagga package in Ubuntu:
  New
Status in rasqal package in Ubuntu:
  New
Status in slang2 package in Ubuntu:
  New
Status in sssd package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  Triaged
Status in zsh package in Ubuntu:
  Triaged

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

It seems suspicious that cb_data->concheck.curl_ehandle is cleaned up
here despite the comment a few lines above warning that it’s unsafe to
do so.

https://github.com/NetworkManager/NetworkManager/blob/1.12.2/src/nm-
connectivity.c#L190-L213

/* Contrary to what cURL manual claim it is *not* safe to remove
 * the easy handle "at any moment"; specifically not from the
 * write function. Thus here we just dissociate the cb_data from
 * the easy handle and the easy handle will be cleaned up when 
the
 * message goes to CURLMSG_DONE in 
_con_curl_check_connectivity(). */
…
curl_multi_remove_handle (priv->concheck.curl_mhandle, 
cb_data->concheck.curl_ehandle);
curl_easy_cleanup (cb_data->concheck.curl_ehandle);

This cleanup call was added in
https://github.com/NetworkManager/NetworkManager/pull/70.  The comment
was moved by that PR but was present before.

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

Here’s a valgrlind log showing many invalid writes to freed addresses in
cb_data_free → curl_multi_remove_handle and nm_connectivity_check_start
→ curl_multi_add_handle, which could explain the heap corruption.

** Attachment added: "nm.19802.log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792745/+attachment/5189363/+files/nm.19802.log

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1792745] Re: NetworkManager crashed with SIGSEGV in _int_malloc()

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  NetworkManager crashed with SIGSEGV in _int_malloc()

Status in network-manager package in Ubuntu:
  New

Bug description:
  I’m seeing NetworkManager crash several times on startup and on resume
  from suspend. Apport doesn’t catch those for some reason, but this
  happened when I tried to reproduce by manually running NetworkManager
  --debug.

  (Different crash from bug 1792743?  Also apport-retrace didn’t seem to
  like that one.)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  Date: Sat Sep 15 14:04:50 2018
  EcryptfsInUse: Yes
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system.  
Do not edit.
  InstallationDate: Installed on 2016-02-19 (939 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcCmdline: NetworkManager --debug
  SegvAnalysis:
   Segfault happened at: 0x7f79966ea378 <_int_malloc+3352>: cmp
%rcx,0x18(%rdx)
   PC (0x7f79966ea378) ok
   source "%rcx" ok
   destination "0x18(%rdx)" (0x0018) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: network-manager
  StacktraceTop:
   _int_malloc (av=av@entry=0x7f799683ac40 , 
bytes=bytes@entry=4096) at malloc.c:4014
   __libc_calloc (n=, elem_size=) at malloc.c:3420
   g_malloc0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   nlmsg_alloc_size (len=4096) at src/platform/nm-netlink.c:314
   _nl80211_alloc_msg (id=28, ifindex=2, phy=0, cmd=cmd@entry=32, 
flags=flags@entry=768) at src/platform/wifi/wifi-utils-nl80211.c:88
  Title: NetworkManager crashed with SIGSEGV in _int_malloc()
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (29 days ago)
  UserGroups:
   
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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

[Desktop-packages] [Bug 1790992] Re: gnome-shell crashes with SIGABRT when touching stylus to screen, "assertion failed: (trap->end_sequence == 0)" in in gdk_x11_display_error_trap_pop_internal() from

[Anders Kaseorg]

GNOME on Wayland works around the crash.

Based on the apport-retrace results, this is possibly a duplicate of bug
1788483.

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

Title:
  gnome-shell crashes with SIGABRT when touching stylus to screen,
  "assertion failed: (trap->end_sequence == 0)" in in
  gdk_x11_display_error_trap_pop_internal() from
  gdk_x11_display_error_trap_pop() from
  meta_x11_error_trap_pop_with_return() from
  meta_input_settings_x11_set_stylus_button_map()

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

Bug description:
  My Thinkpad Yoga 14 20FY has a builtin stylus pen.  If I touch it to
  the screen, gnome-shell immediately crashes, 100% reproducibly.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.29.90-2ubuntu1
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  5 18:28:08 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-19 (929 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-08-17 (19 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd 
mock plugdev sambashare sbuild sudo wireshark

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

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

[Desktop-packages] [Bug 1780680] Re: Older version in bionic than in xenial

[Anders Kaseorg]

Older versions in bionic than in xenial, as of now:

fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
linux-meta-azure 4.15.0.1021.21 < 4.15.0.1021.27
linux-meta-gcp 4.15.0.1017.19 < 4.15.0.1017.29


** Summary changed:

- Older version in artful than in xenial
+ Older version in bionic than in xenial

** Changed in: snapcraft (Ubuntu)
   Status: New => Fix Released

** Changed in: wireless-regdb (Ubuntu)
   Status: New => Fix Released

** Changed in: python-pyvmomi (Ubuntu)
   Status: New => Invalid

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

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

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

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

Title:
  Older version in bionic than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  Won't Fix
Status in libdrm package in Ubuntu:
  Won't Fix
Status in linux-meta-azure package in Ubuntu:
  New
Status in linux-meta-gcp package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Won't Fix
Status in patch package in Ubuntu:
  Invalid
Status in python-pyvmomi package in Ubuntu:
  Invalid
Status in snapcraft package in Ubuntu:
  Fix Released
Status in wireless-regdb package in Ubuntu:
  Fix Released

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Desktop-packages] [Bug 1780680] Re: Older version in artful than in xenial

[Anders Kaseorg]

** Description changed:

  These packages have an older version in artful than in xenial.
  
  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1
  
  Some of these are older in bionic than in xenial too.
  
- Shouldn’t there be an automated check for this?
+ Shouldn’t there be an automated check for this?  (See also: bug 1780679,
+ bug 1780681.)

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

Title:
  Older version in artful than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in patch package in Ubuntu:
  New
Status in python-pyvmomi package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Desktop-packages] [Bug 1772607] Re: Mesa 18.0.5 stable release

[Anders Kaseorg]

Until this is uploaded to bionic, the version in bionic is older than in
xenial (bug 1780680), which is going to interfere with upgrades.

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

Title:
  Mesa 18.0.5 stable release

Status in libglvnd package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libglvnd source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point 
release of the series.

  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems.

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

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

[Desktop-packages] [Bug 1780680] [NEW] Older version in artful than in xenial

[Anders Kaseorg]

Public bug reported:

These packages have an older version in artful than in xenial.

fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
snapcraft 2.42+17.10 < 2.42.1
wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

Some of these are older in bionic than in xenial too.

Shouldn’t there be an automated check for this?

** Affects: fuse-umfuse-ext2 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

** Affects: python-pyvmomi (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: wireless-regdb (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic

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

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

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

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

** Also affects: python-pyvmomi (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: wireless-regdb (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Older version in artful than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in patch package in Ubuntu:
  New
Status in python-pyvmomi package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Desktop-packages] [Bug 1735912] Re: Firefox reliably crashes on apt upgrade

[Anders Kaseorg]

This happens all the time on my main Ubuntu installation and is not
specific to the live environment. I only demonstrated it in the live
environment for easy reproducibility, and to show it isn’t some crazy
misconfiguration of my specific installation.

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

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

Title:
  Firefox reliably crashes on apt upgrade

Status in firefox package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. kvm -cdrom ubuntu-17.10-desktop-amd64.iso -m 4096
  2. Select “Try Ubuntu”.
  3. Start Firefox.
  4. Start Software Updater; uncheck everything except Firefox Web Browser; 
select “Install Now”.
  5. When update finishes, switch back to Firefox and go to www.google.com.

  Firefox immediately crashes.  (This seems to happen after every recent
  Firefox update, not just 56 to 57.)

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

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

[Desktop-packages] [Bug 1735912] [NEW] Firefox reliably crashes on apt upgrade

[Anders Kaseorg]

Public bug reported:

Steps to reproduce:

1. kvm -cdrom ubuntu-17.10-desktop-amd64.iso -m 4096
2. Select “Try Ubuntu”.
3. Start Firefox.
4. Start Software Updater; uncheck everything except Firefox Web Browser; 
select “Install Now”.
5. When update finishes, switch back to Firefox and go to www.google.com.

Firefox immediately crashes.  (This seems to happen after every recent
Firefox update, not just 56 to 57.)

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


** Tags: artful

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

Title:
  Firefox reliably crashes on apt upgrade

Status in firefox package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. kvm -cdrom ubuntu-17.10-desktop-amd64.iso -m 4096
  2. Select “Try Ubuntu”.
  3. Start Firefox.
  4. Start Software Updater; uncheck everything except Firefox Web Browser; 
select “Install Now”.
  5. When update finishes, switch back to Firefox and go to www.google.com.

  Firefox immediately crashes.  (This seems to happen after every recent
  Firefox update, not just 56 to 57.)

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

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

[Desktop-packages] [Bug 1731694] Re: Ubuntu 17.10 has an older version of ubufox than 14.04, 16.04, 17.04

[Anders Kaseorg]

dino99: This is about the ubufox _source_ package, which is the source
for the xul-ext-ubufox binary package and is not transitional.  The xul-
ext-ubufox binary package has the same problem.

$ rmadison xul-ext-ubufox
 xul-ext-ubufox | 2.0.2-0ubuntu1   | precise  | all
 xul-ext-ubufox | 2.8-0ubuntu1 | trusty   | all
 xul-ext-ubufox | 3.2-0ubuntu0.12.04.1 | precise-security | all
 xul-ext-ubufox | 3.2-0ubuntu0.12.04.1 | precise-updates  | all
 xul-ext-ubufox | 3.2-0ubuntu1 | xenial   | all
 xul-ext-ubufox | 3.2-0ubuntu1 | zesty| all
 xul-ext-ubufox | 3.3-0ubuntu2 | artful   | all
 xul-ext-ubufox | 3.3-0ubuntu2 | bionic   | all
 xul-ext-ubufox | 3.4-0ubuntu0.14.04.1 | trusty-security  | all
 xul-ext-ubufox | 3.4-0ubuntu0.14.04.1 | trusty-updates   | all
 xul-ext-ubufox | 3.4-0ubuntu0.16.04.1 | xenial-security  | all
 xul-ext-ubufox | 3.4-0ubuntu0.16.04.1 | xenial-updates   | all
 xul-ext-ubufox | 3.4-0ubuntu0.17.04.1 | zesty-security   | all
 xul-ext-ubufox | 3.4-0ubuntu0.17.04.1 | zesty-updates| all

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

Title:
  Ubuntu 17.10 has an older version of ubufox than 14.04, 16.04, 17.04

Status in ubufox package in Ubuntu:
  Confirmed

Bug description:
  $ rmadison -asource ubufox
   ubufox | 2.0.2-0ubuntu1   | precise  | source
   ubufox | 2.8-0ubuntu1 | trusty   | source
   ubufox | 3.2-0ubuntu0.12.04.1 | precise-security | source
   ubufox | 3.2-0ubuntu0.12.04.1 | precise-updates  | source
   ubufox | 3.2-0ubuntu1 | xenial   | source
   ubufox | 3.2-0ubuntu1 | zesty| source
   ubufox | 3.3-0ubuntu2 | artful   | source
   ubufox | 3.3-0ubuntu2 | bionic   | source
   ubufox | 3.4-0ubuntu0.14.04.1 | trusty-security  | source
   ubufox | 3.4-0ubuntu0.14.04.1 | trusty-updates   | source
   ubufox | 3.4-0ubuntu0.16.04.1 | xenial-security  | source
   ubufox | 3.4-0ubuntu0.16.04.1 | xenial-updates   | source
   ubufox | 3.4-0ubuntu0.17.04.1 | zesty-security   | source
   ubufox | 3.4-0ubuntu0.17.04.1 | zesty-updates| source

  Apparently 3.4 was never released to artful and bionic.

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

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

[Desktop-packages] [Bug 1731694] [NEW] Ubuntu 17.10 has an older version of ubufox than 14.04, 16.04, 17.04

[Anders Kaseorg]

Public bug reported:

$ rmadison -asource ubufox
 ubufox | 2.0.2-0ubuntu1   | precise  | source
 ubufox | 2.8-0ubuntu1 | trusty   | source
 ubufox | 3.2-0ubuntu0.12.04.1 | precise-security | source
 ubufox | 3.2-0ubuntu0.12.04.1 | precise-updates  | source
 ubufox | 3.2-0ubuntu1 | xenial   | source
 ubufox | 3.2-0ubuntu1 | zesty| source
 ubufox | 3.3-0ubuntu2 | artful   | source
 ubufox | 3.3-0ubuntu2 | bionic   | source
 ubufox | 3.4-0ubuntu0.14.04.1 | trusty-security  | source
 ubufox | 3.4-0ubuntu0.14.04.1 | trusty-updates   | source
 ubufox | 3.4-0ubuntu0.16.04.1 | xenial-security  | source
 ubufox | 3.4-0ubuntu0.16.04.1 | xenial-updates   | source
 ubufox | 3.4-0ubuntu0.17.04.1 | zesty-security   | source
 ubufox | 3.4-0ubuntu0.17.04.1 | zesty-updates| source

Apparently 3.4 was never released to artful and bionic.

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

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

Title:
  Ubuntu 17.10 has an older version of ubufox than 14.04, 16.04, 17.04

Status in ubufox package in Ubuntu:
  New

Bug description:
  $ rmadison -asource ubufox
   ubufox | 2.0.2-0ubuntu1   | precise  | source
   ubufox | 2.8-0ubuntu1 | trusty   | source
   ubufox | 3.2-0ubuntu0.12.04.1 | precise-security | source
   ubufox | 3.2-0ubuntu0.12.04.1 | precise-updates  | source
   ubufox | 3.2-0ubuntu1 | xenial   | source
   ubufox | 3.2-0ubuntu1 | zesty| source
   ubufox | 3.3-0ubuntu2 | artful   | source
   ubufox | 3.3-0ubuntu2 | bionic   | source
   ubufox | 3.4-0ubuntu0.14.04.1 | trusty-security  | source
   ubufox | 3.4-0ubuntu0.14.04.1 | trusty-updates   | source
   ubufox | 3.4-0ubuntu0.16.04.1 | xenial-security  | source
   ubufox | 3.4-0ubuntu0.16.04.1 | xenial-updates   | source
   ubufox | 3.4-0ubuntu0.17.04.1 | zesty-security   | source
   ubufox | 3.4-0ubuntu0.17.04.1 | zesty-updates| source

  Apparently 3.4 was never released to artful and bionic.

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

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

[Desktop-packages] [Bug 1701289] Re: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat()

[Anders Kaseorg]

This may have been fixed by mutter 3.26.1-2 (bug 1722510).  At least I
can no longer reproduce it using the recipe in my duplicate bug 1722709.

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

Title:
  gnome-shell crashed with signal 5 in XIGetClientPointer() from
  gdk_x11_display_get_default_seat()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  cant login to gnome desktop

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 29 16:14:29 2017
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-03-25 (96 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XIGetClientPointer () at /usr/lib/x86_64-linux-gnu/libXi.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1722687] [NEW] ‘env GTK_IM_MODULE=uim gedit’ crashes with SIGSEGV in Wayland

[Anders Kaseorg]

Public bug reported:

Running ‘env GTK_IM_MODULE=uim gedit’ in a Wayland session results in
this crash.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 10 20:50:10 2017
Disassembly: => 0x2:Cannot access memory at address 0x2
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2016-02-19 (599 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
ProcCmdline: gedit
ProcEnviron:
 LANG=en_US.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x2: Cannot access memory at address 0x2
 PC (0x0002) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ()
 XGetModifierMapping () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 im_uim_init_modifier_keys () at 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so
 im_module_init () at 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so
 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gedit crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-05-02 (161 days ago)
UserGroups:

** Affects: gedit (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash artful

** Information type changed from Private to Public

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

Title:
  ‘env GTK_IM_MODULE=uim gedit’ crashes with SIGSEGV in Wayland

Status in gedit package in Ubuntu:
  New

Bug description:
  Running ‘env GTK_IM_MODULE=uim gedit’ in a Wayland session results in
  this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 10 20:50:10 2017
  Disassembly: => 0x2:  Cannot access memory at address 0x2
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gedit
  InstallationDate: Installed on 2016-02-19 (599 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: gedit
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x2:   Cannot access memory at address 0x2
   PC (0x0002) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: gedit
  StacktraceTop:
   ()
   XGetModifierMapping () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   im_uim_init_modifier_keys () at 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so
   im_module_init () at 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gedit crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-05-02 (161 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1721681] Re: gnome-terminal-server crashed with SIGSEGV in XGetModifierMapping()

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  gnome-terminal-server crashed with SIGSEGV in XGetModifierMapping()

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Today’s updates have left me unable to start gnome-terminal inside
  GNOME on Wayland.  It still works in GNOME on X11.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct  5 23:12:55 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2016-02-19 (594 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   XGetModifierMapping () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   im_uim_init_modifier_keys () at 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so
   im_module_init () at 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-uim.so
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_module_use () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-terminal-server crashed with SIGSEGV in XGetModifierMapping()
  UpgradeStatus: Upgraded to artful on 2017-05-02 (156 days ago)
  UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin 
mock plugdev sambashare sbuild sudo wireshark

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

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

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

[Anders Kaseorg]

I’m not sure. Since it’s been a week without any sign of an upload to
artful-proposed, I’m changing this back to Confirmed.

I have a patched build of gnome-shell in my PPA if you need it now:
https://launchpad.net/~andersk/+archive/ubuntu/ppa/+packages
https://launchpadlibrarian.net/339202115/gnome-shell_3.26.0-0ubuntu2_3.26.0-0ubuntu2andersk1.diff.gz

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

** Tags removed: wayland-session
** Tags added: patch patch-accepted-upstream

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

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

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

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

  ---

  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

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

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

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

[Anders Kaseorg]

It seems to be the TopIcons Plus extension that triggers this so often.
I think that’s roughly consistent with the upstream bug report.

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

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

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

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

  ---

  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

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

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

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

[Anders Kaseorg]

This might be triggered by a shell extension.  I haven’t seen any
crashes after turning them all off.  I’ll see if I can bisect which one
it is.

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

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

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

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

  ---

  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

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

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

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

[Anders Kaseorg]

This is happening to me very frequently (several times a day) on both
Wayland and Xorg.  On Wayland, it brings down the entire session.

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

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

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

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

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

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

[Anders Kaseorg]

** Information type changed from Private to Public

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

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

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

[Desktop-packages] [Bug 1713457] [NEW] DNS search domain not removed from resolv.conf on disconnect

[Anders Kaseorg]

Public bug reported:

When I connect to a wireless network that sets a DNS search domain name
via DHCP, the line 'search ' is added to /etc/resolv.conf as
expected.  But if I then disconnect and connect to a different network,
it is not removed from resolv.conf.  If the second network also sets a
search domain name, that one gets appended to resolv.conf along with the
first one, and so on.  Depending on the network, this can cause DNS
leaks, name resolution failures, or other misbehavior.

To be sure this wasn't some kind of user configuration issue, I
reproduced this on the artful daily live image (artful-desktop-
amd64.iso, 2017-08-27), from which I'm writing this report.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CasperVersion: 1.384
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 28 10:34:22 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 172.20.20.1 dev wlp3s0 proto static metric 600
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
 172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
 wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  
/org/freedesktop/NetworkManager/ActiveConnection/2
 enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--   ----
 lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug artful regression-release

** Description changed:

  When I connect to a wireless network that sets a DNS search domain name
- via DHCP, the line 'search domain' is added to /etc/resolv.conf as
+ via DHCP, the line 'search ' is added to /etc/resolv.conf as
  expected.  But if I then disconnect and connect to a different network,
  it is not removed from resolv.conf.  If the second network also sets a
  search domain name, that one gets appended to resolv.conf along with the
  first one, and so on.  Depending on the network, this can cause name
  resolution failures or other misbehavior.
  
  To be sure this wasn't some kind of user configuration issue, I
  reproduced this on the artful daily live image (artful-desktop-
  amd64.iso, 2017-08-27), from which I'm writing this report.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 28 10:34:22 2017
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  IpRoute:
-  default via 172.20.20.1 dev wlp3s0 proto static metric 600 
-  169.254.0.0/16 dev wlp3s0 scope link metric 1000 
-  172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
+  default via 172.20.20.1 dev wlp3s0 proto static metric 600
+  169.254.0.0/16 dev wlp3s0 scope link metric 1000
+  172.20.20.0/24 dev wlp3s0 proto kernel scope link src 172.20.20.20 metric 600
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170827)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
-  DEVICE TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
-  wlp3s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
xfinitywifi  39ffbbfc-1c1e-41c9-b3eb-c513065c3ea6  

[Desktop-packages] [Bug 220263] Re: Bad Firefox integration with dark themes

[Anders Kaseorg]

Firefox 47 worked around this by disabling the dark theme entirely.

Firefox 55 beta supports two new independent about:config settings,
widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark-
theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076).  The
former gets you a dark-themed UI without messing up web page content.

Official PPA for Firefox beta, if you don’t want to wait:
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next

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

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

Title:
  Bad Firefox integration with dark themes

Status in Mozilla Firefox:
  Fix Released
Status in XULRunner:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme.
  Now I see all the input boxes and buttons filled with grey colour.
  This happened even with Firefox 2, but I solved that problem with a
  quick guide under the comment "firefox fix" by Proton at the bottom of
  this page: http://www.gnome-
  look.org/content/show.php/Grey+Neu?content=60824

  In Firefox 3 I can't correct this problem.

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

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

[Desktop-packages] [Bug 1586761] Re: White text on white backgrounds on most sites with Firefox with dark GTK theme

[Anders Kaseorg]

Firefox 47 worked around this by disabling the dark theme entirely.

Firefox 55 beta supports two new independent about:config settings,
widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark-
theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076).  The
former gets you a dark-themed UI without messing up web page content.

Official PPA for Firefox beta, if you don’t want to wait:
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next

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

Title:
  White text on white backgrounds on most sites with Firefox with dark
  GTK theme

Status in Mozilla Firefox:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  When running GNOME 3.18 on Ubuntu GNOME 16.04 I found that on some
  sites the text was black on black so I could only see it through
  highlighting, on other sites like YouTube for instance though I found
  that the text was very light grey on white background, still hard to
  see, but better than having the same colour for the background and the
  text. But now after upgrading to GNOME 3.20 I have found that with all
  themes that on YouTube and many other sites the text is white on white
  background meaning the only way to see it is to highlight it, but in a
  search box this is very annoying as you can imagine. I am running
  Firefox version 46.0.1 and have linked a possibly related upstream
  bug.

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

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

[Desktop-packages] [Bug 1589076] Re: Firefox 47 ignores Global Dark Theme option being enabled

[Anders Kaseorg]

Firefox 55 beta supports two new independent about:config settings,
widget.chrome.allow-gtk-dark-theme and widget.content.allow-gtk-dark-
theme (https://bugzilla.mozilla.org/show_bug.cgi?id=1158076).  The
former gets you a dark-themed UI without messing up web page content.

Official PPA for Firefox beta, if you don’t want to wait:
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next

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

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

Title:
  Firefox 47 ignores Global Dark Theme option being enabled

Status in Mozilla Firefox:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in firefox package in Arch Linux:
  New

Bug description:
  I had Firefox 46.0.1 installed previously which worked fine and when
  having the Global Dark Theme enabled was, well, dark, as I like it.
  However after upgrading to Firefox 47 I have found that Firefox is all
  completely white, it looks as it would if the Global Dark Theme option
  in the gnome-tweak-tool were disabled, which it is not, and it is the
  only application behaving as such. I am running Ubuntu GNOME 16.04
  with GNOME 3.20. I have attached a screenshot of what it looks like
  (though I have blacked out some private stuff).

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

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

[Desktop-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

[Anders Kaseorg]

I have the same problem on a ThinkPad Yoga 14 20FY.  I can reproduce it
with the touchpad disabled as described in this report.  However, I find
it much easier to reproduce (nearly 100% of the time) with the touchpad
enabled, as follows:

1. With my left finger, hold down the trackpoint’s left button.
2. With my right finger, move the pointer with the trackpad.
3. Release my right finger from the trackpad.
4. Release my left finger from the button.  The button has become “stuck” down!
5. Put a finger back on the trackpad.  Now the earlier button release gets 
recognized.

evtest on the trackpoint (ETPS/2 Elantech TrackPoint) shows that the
trackpoint knows the button is pressed at step 1 and released at step 4,
but evtest on the touchpad (ETPS/2 Elantech Touchpad) shows that the
touchpad thinks another copy of the button has been pressed at step 1
and not released until step 5.

The problem is still present in kernel 4.12-rc6 from the mainline
archive.  (I haven’t been able to figure out if enabling the new drivers
in 4.12 is supposed to require manual configuration, but simply booting
into the new kernel didn’t fix it.)

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't
  use same clickpad type touchpad, e.g. T430 or X230. For newer thinkpad
  models (e.g. T460, X260, etc) which uses same clickpad design, same
  issue might exists too (need confirmation though).

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

[Anders Kaseorg]

Martin, was the DNSSEC=allow-downgrade default not switched off for the
17.04 stable release like you said it would?

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Fix Committed

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ 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
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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

[Desktop-packages] [Bug 897302] Re: Screen dims even automatic dimming is turned OFF (when on battery)

[Anders Kaseorg]

** Also affects: gnome-settings-daemon via
   https://bugzilla.gnome.org/show_bug.cgi?id=665073
   Importance: Unknown
   Status: Unknown

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

Title:
  Screen dims even automatic dimming is turned OFF (when on battery)

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

Bug description:
  
  Set:
  System Settings -> Screen -> 
"Dim screen to save power" -> OFF
  and
 Brightness to max.

  Disconnect power cable.

  
  Expected: Brightness stay

  Actual: Brightness lowers
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CheckboxSubmission: 16fcfa228a6401c4bde710ae287e4dc3
  CheckboxSystem: dcc25227c08c2ff167970aa46306308d
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to oneiric on 2011-11-24 (3 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  usr_lib_gnome-control-center: deja-dup 20.1-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

The current location of 24.5+1-7ubuntu1 is zesty-proposed.  I think it
has not migrated to zesty because it failed to build on ppc64el.

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Fix Committed
Status in emacs24 package in Debian:
  Fix Released

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1636320] [NEW] package liblirc-client0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is also in package

[Anders Kaseorg]

Public bug reported:

Selecting previously unselected package liblirc-client0:amd64.
Preparing to unpack .../44-liblirc-client0_0.9.4c-1_amd64.deb ...
Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
Preparing to unpack .../45-liblircclient0_0.9.4c-1_amd64.deb ...
Unpacking liblircclient0 (0.9.4c-1) over (0.9.0-0ubuntu6) ...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblirc-client0 (not installed)
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Mon Oct 24 18:29:50 2016
DuplicateSignature:
 package:liblirc-client0:(not installed)
 Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is also in package 
liblircclient0:amd64 0.9.0-0ubuntu6
InstallationDate: Installed on 2016-02-19 (248 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: lirc
Title: package liblirc-client0 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check package-conflict zesty

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

Title:
  package liblirc-client0 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0',
  which is also in package liblircclient0:amd64 0.9.0-0ubuntu6

Status in lirc package in Ubuntu:
  New

Bug description:
  Selecting previously unselected package liblirc-client0:amd64.
  Preparing to unpack .../44-liblirc-client0_0.9.4c-1_amd64.deb ...
  Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which 
is also in package liblircclient0:amd64 0.9.0-0ubuntu6
  Preparing to unpack .../45-liblircclient0_0.9.4c-1_amd64.deb ...
  Unpacking liblircclient0 (0.9.4c-1) over (0.9.0-0ubuntu6) ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblirc-client0 (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 24 18:29:50 2016
  DuplicateSignature:
   package:liblirc-client0:(not installed)
   Unpacking liblirc-client0:amd64 (0.9.4c-1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-LJoo1m/44-liblirc-client0_0.9.4c-1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which 
is also in package liblircclient0:amd64 0.9.0-0ubuntu6
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is also in package 
liblircclient0:amd64 0.9.0-0ubuntu6
  InstallationDate: Installed on 2016-02-19 (248 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: lirc
  Title: package liblirc-client0 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', which is 
also in package liblircclient0:amd64 0.9.0-0ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

pauljohn: You installed the packages in the wrong order.  Since a
24.5+1-7ubuntu1 package, identical to mine modulo debian/changelog, is
in yakkety-proposed for architectures other than arm64 and ppc64el, the
easiest solution is to enable yakkety-proposed and let apt install them
for you.

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Fix Committed
Status in emacs24 package in Debian:
  Fix Released

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

Adding -no-pie on arm64 doesn’t help.

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Fix Committed
Status in emacs24 package in Debian:
  Fix Released

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

Rebuilding an unchanged 24.5+1-6ubuntu3 also fails on arm64 and ppc64el:

https://launchpadlibrarian.net/287872786/buildlog_ubuntu-yakkety-arm64.emacs24_24.5+1-6ubuntu3_BUILDING.txt.gz
https://launchpadlibrarian.net/287872619/buildlog_ubuntu-yakkety-ppc64el.emacs24_24.5+1-6ubuntu3_BUILDING.txt.gz


** Bug watch added: Debian Bug tracker #837421
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837421

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Fix Committed
Status in emacs24 package in Debian:
  Fix Released

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

The arm64 problem, at least, looks like it could be
https://bugs.debian.org/837421.  Ubuntu has already added -no-pie on
amd64 ppc64el s390x but not yet on arm64.

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Fix Committed
Status in emacs24 package in Debian:
  Fix Released

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

** Tags added: patch-accepted-debian

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Confirmed
Status in emacs24 package in Debian:
  Unknown

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

** Tags added: regression-release

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Confirmed
Status in emacs24 package in Debian:
  Unknown

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

Confirmed that this fixes the toolbar with a test build in ppa:anders-
kaseorg/ppa.  Subscribing sponsors.

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Confirmed
Status in emacs24 package in Debian:
  Unknown

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

This is most straightforwardly solved by merging 24.5+1-7 from Debian,
which pulls in three fixes: one for for this bug, one for malloc
handling with GCC ≥ 5.2, and one for glibc 2.24 support.  We certainly
want all three.  Here is a debdiff from 24.5+1-6ubuntu3.

** Patch added: "emacs24_24.5+1-6ubuntu3_7ubuntu1.debdiff"
   
https://bugs.launchpad.net/debian/+source/emacs24/+bug/1623585/+attachment/4742818/+files/emacs24_24.5+1-6ubuntu3_7ubuntu1.debdiff

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Confirmed
Status in emacs24 package in Debian:
  Unknown

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1623585] Re: Toolbar is blank

[Anders Kaseorg]

** Bug watch added: Debian Bug tracker #828000
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828000

** Also affects: emacs24 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828000
   Importance: Unknown
   Status: Unknown

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

Title:
  Toolbar is blank

Status in emacs24 package in Ubuntu:
  Confirmed
Status in emacs24 package in Debian:
  Unknown

Bug description:
  Emacs 24.5+1-6ubuntu1 in xenial does not display the gtk toolbar
  correctly.  It is just an empty grey space.  This appears to be the
  same issue as https://bugs.archlinux.org/task/48862 which required
  cherry-picking an upstream commit: https://github.com/emacs-
  mirror/emacs/commit/3f4c6d52d34538bc2d4a53246af4c61ef176

  I also tried upgrading to the yakkety packages 24.5+1-6ubuntu3 and
  libpng16-16, but this did not correct the issue.

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

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

[Desktop-packages] [Bug 1591868] Re: fwupd consuming 100% CPU

[Anders Kaseorg]

Also submitted upstream: https://github.com/hughsie/appstream-
glib/pull/129

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

Title:
  fwupd consuming 100% CPU

Status in appstream-glib package in Ubuntu:
  Confirmed
Status in fwupd package in Ubuntu:
  Invalid
Status in libyaml package in Ubuntu:
  Invalid
Status in appstream-glib source package in Xenial:
  Confirmed
Status in fwupd source package in Xenial:
  Invalid
Status in libyaml source package in Xenial:
  Invalid
Status in appstream-glib source package in Yakkety:
  Confirmed
Status in fwupd source package in Yakkety:
  Invalid
Status in libyaml source package in Yakkety:
  Invalid

Bug description:
  fwupd process has been consuming 100% of my CPU for several days now
  (IBM Thinkpad x250 running fully updated 16.04).

  gdb backtrace below.

  Thread 2 (Thread 0x7f3272cf5700 (LWP 4496)):
  #0  0x7f3279b79e8d in poll () at ../sysdeps/unix/syscall-template.S:84
  No locals.
  #1  0x7f327ae9331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f327ae9342c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f327ae93469 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #4  0x7f327aeb9b45 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #5  0x7f3279e4f6fa in start_thread (arg=0x7f3272cf5700) at 
pthread_create.c:333
  __res = 
  pd = 0x7f3272cf5700
  now = 
  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139854651283200, 
418179942412000561, 0, 140731891236207, 
  139854651283904, 0, -312637405101744847, 
-312613451844084431}, mask_was_saved = 0}}, priv = {pad = {
0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
  not_first_call = 
  pagesize_m1 = 
  sp = 
  freesize = 
  __PRETTY_FUNCTION__ = "start_thread"
  #6  0x7f3279b85b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  No locals.

  Thread 1 (Thread 0x7f327c926900 (LWP 4486)):
  #0  0x7f3279e542b7 in __GI___pthread_rwlock_rdlock (rwlock=0x7f3279e43920 
<__libc_setlocale_lock>)
  at pthread_rwlock_rdlock.c:135
  result = 0
  wake = false
  #1  0x7f3279aaf0e9 in __dcigettext (domainname=0x7f327aedee63 "glib20", 
  msgid1=0x7f327b4ca11a "Invalid compressed data", msgid2=0x0, plural=0, 
n=0, category=5) at dcigettext.c:527
  __p = 
  domain = 
  binding = 
  categoryname = 
  categoryvalue = 
  dirname = 
  xdomainname = 
  single_locale = 
  retval = 
  retlen = 93892446493824
  saved_errno = 0
  search = {domainname = 0x7ffeb262bb00 "`\234\353\teU", category = 
166588464, 
localename = 0x556509ededa8 "p\362\355\teU", counter = 166589040, 
domain = 0x23, 
translation = 0x5565fffb , 
translation_length = 93892446493792, msgid = {appended = 
0x7ffeb262bb08 "", 
  ptr = 0x52fb0a5631f15a00 }}
  foundp = 0x0
  localename = 
  domainname_len = 
  #2  0x7f327b44338c in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #3  0x7f327b3e95f9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #4  0x7f327b40d315 in g_input_stream_read () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #5  0x7f327c1ae569 in ?? () from 
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  No symbol table info available.
  #6  0x7f3278c51a15 in ?? () from /usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #7  0x7f3278c51cde in yaml_parser_update_buffer () from 
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #8  0x7f3278c56498 in yaml_parser_fetch_more_tokens () from 
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #9  0x7f3278c5b32f in yaml_parser_parse () from 
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #10 0x7f327c1ae39b in ?? () from 
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  No symbol table info available.
  #11 0x7f327c1ae890 in as_yaml_from_file () from 
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  No symbol table info available.
  #12 0x7f327c1a9231 in ?? () from 
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  No symbol table info available.
  #13 0x7f327c1a9867 in ?? () from 
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  No symbol table info available.
  #14 0x7f327c1a9ee1 in ?? () from 
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8

[Desktop-packages] [Bug 1591868] Re: fwupd consuming 100% CPU

[Anders Kaseorg]

The infinite loop is not in libyaml (yaml_parser_parse), but rather in
its caller in appstream-glib (as_node_yaml_process_layer), which is
ignoring the error code returned by yaml_parser_parse and blindly going
around the loop again.  This patch fixes it.

** Patch added: "appstream-glib_0.5.17-0ubuntu1_lp1591868.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1591868/+attachment/4722986/+files/appstream-glib_0.5.17-0ubuntu1_lp1591868.debdiff

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

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

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

Title:
  fwupd consuming 100% CPU

Status in appstream-glib package in Ubuntu:
  Confirmed
Status in fwupd package in Ubuntu:
  Invalid
Status in libyaml package in Ubuntu:
  Invalid
Status in appstream-glib source package in Xenial:
  New
Status in fwupd source package in Xenial:
  Invalid
Status in libyaml source package in Xenial:
  Invalid
Status in appstream-glib source package in Yakkety:
  Confirmed
Status in fwupd source package in Yakkety:
  Invalid
Status in libyaml source package in Yakkety:
  Invalid

Bug description:
  fwupd process has been consuming 100% of my CPU for several days now
  (IBM Thinkpad x250 running fully updated 16.04).

  gdb backtrace below.

  Thread 2 (Thread 0x7f3272cf5700 (LWP 4496)):
  #0  0x7f3279b79e8d in poll () at ../sysdeps/unix/syscall-template.S:84
  No locals.
  #1  0x7f327ae9331c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f327ae9342c in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f327ae93469 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #4  0x7f327aeb9b45 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #5  0x7f3279e4f6fa in start_thread (arg=0x7f3272cf5700) at 
pthread_create.c:333
  __res = 
  pd = 0x7f3272cf5700
  now = 
  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139854651283200, 
418179942412000561, 0, 140731891236207, 
  139854651283904, 0, -312637405101744847, 
-312613451844084431}, mask_was_saved = 0}}, priv = {pad = {
0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
  not_first_call = 
  pagesize_m1 = 
  sp = 
  freesize = 
  __PRETTY_FUNCTION__ = "start_thread"
  #6  0x7f3279b85b5d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
  No locals.

  Thread 1 (Thread 0x7f327c926900 (LWP 4486)):
  #0  0x7f3279e542b7 in __GI___pthread_rwlock_rdlock (rwlock=0x7f3279e43920 
<__libc_setlocale_lock>)
  at pthread_rwlock_rdlock.c:135
  result = 0
  wake = false
  #1  0x7f3279aaf0e9 in __dcigettext (domainname=0x7f327aedee63 "glib20", 
  msgid1=0x7f327b4ca11a "Invalid compressed data", msgid2=0x0, plural=0, 
n=0, category=5) at dcigettext.c:527
  __p = 
  domain = 
  binding = 
  categoryname = 
  categoryvalue = 
  dirname = 
  xdomainname = 
  single_locale = 
  retval = 
  retlen = 93892446493824
  saved_errno = 0
  search = {domainname = 0x7ffeb262bb00 "`\234\353\teU", category = 
166588464, 
localename = 0x556509ededa8 "p\362\355\teU", counter = 166589040, 
domain = 0x23, 
translation = 0x5565fffb , 
translation_length = 93892446493792, msgid = {appended = 
0x7ffeb262bb08 "", 
  ptr = 0x52fb0a5631f15a00 }}
  foundp = 0x0
  localename = 
  domainname_len = 
  #2  0x7f327b44338c in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #3  0x7f327b3e95f9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #4  0x7f327b40d315 in g_input_stream_read () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  No symbol table info available.
  #5  0x7f327c1ae569 in ?? () from 
/usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
  No symbol table info available.
  #6  0x7f3278c51a15 in ?? () from /usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #7  0x7f3278c51cde in yaml_parser_update_buffer () from 
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #8  0x7f3278c56498 in yaml_parser_fetch_more_tokens () from 
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #9  0x7f3278c5b32f in yaml_parser_parse () from 
/usr/lib/x86_64-linux-gnu/libyaml-0.so.2
  No symbol table info available.
  #10 0x7f327c1ae39b in ?? () from 

[Desktop-packages] [Bug 1537635] [NEW] Reduce zlib compression level for massive performance increase

[Anders Kaseorg]

Public bug reported:

When apport takes a core dump of a large application, it uses 100% CPU
for a _long_ time (often 30 seconds or more) to compress the core dump.
The system is virtually unusable during this time, especially if the
application was the window manager and won’t be restarted until the core
dump is complete.

This is a longstanding known problem; it motivated the switch from bzip2
to zlib level 9 back in apport 0.24. That made it much better, but it’s
still quite bad. So why not switch from zlib level 9 to zlib level 1?

I tested this on a core dump of gnome-shell, and while it increased the
size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased the
needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3 seconds). This
tradeoff seems more than worthwhile for this use case.

** Affects: apport
 Importance: Undecided
 Status: New

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


** Tags: patch

** Patch added: "apport_2.19.3-0ubuntu3_zlib-level-1.debdiff"
   
https://bugs.launchpad.net/bugs/1537635/+attachment/4556055/+files/apport_2.19.3-0ubuntu3_zlib-level-1.debdiff

** Tags added: patch

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

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

Title:
  Reduce zlib compression level for massive performance increase

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  When apport takes a core dump of a large application, it uses 100% CPU
  for a _long_ time (often 30 seconds or more) to compress the core
  dump. The system is virtually unusable during this time, especially if
  the application was the window manager and won’t be restarted until
  the core dump is complete.

  This is a longstanding known problem; it motivated the switch from
  bzip2 to zlib level 9 back in apport 0.24. That made it much better,
  but it’s still quite bad. So why not switch from zlib level 9 to zlib
  level 1?

  I tested this on a core dump of gnome-shell, and while it increased
  the size of the .crash file by 24% (68.5 MB to 85.0 MB), it decreased
  the needed CPU time by a FACTOR OF EIGHT (58.6 seconds to 7.3
  seconds). This tradeoff seems more than worthwhile for this use case.

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

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

[Desktop-packages] [Bug 1533504] [NEW] package fonts-tlwg-kinnari-ttf (not installed) failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/tlwg/Kinnari-Bold.ttf', which is also in

[Anders Kaseorg]

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

Public bug reported:

package fonts-tlwg-kinnari-ttf (not installed) failed to
install/upgrade: trying to overwrite '/usr/share/fonts/truetype/tlwg
/Kinnari-Bold.ttf', which is also in package fonts-tlwg-kinnari
1:0.6.2-1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fonts-tlwg-kinnari-ttf (not installed)
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
Date: Wed Jan 13 01:34:40 2016
DuplicateSignature:
 Unpacking fonts-tlwg-garuda-ttf (1:0.6.2-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/fonts-tlwg-garuda-ttf_1%3a0.6.2-2_all.deb (--unpack):
  trying to overwrite '/usr/share/fonts/truetype/tlwg/Garuda.ttf', which is 
also in package fonts-tlwg-garuda 1:0.6.2-1
ErrorMessage: trying to overwrite 
'/usr/share/fonts/truetype/tlwg/Kinnari-Bold.ttf', which is also in package 
fonts-tlwg-kinnari 1:0.6.2-1
InstallationDate: Installed on 2015-06-02 (224 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.1.10
SourcePackage: fonts-tlwg
Title: package fonts-tlwg-kinnari-ttf (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/fonts/truetype/tlwg/Kinnari-Bold.ttf', which is also in package 
fonts-tlwg-kinnari 1:0.6.2-1
UpgradeStatus: Upgraded to xenial on 2015-10-28 (76 days ago)

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


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

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

Title:
  package fonts-tlwg-kinnari-ttf (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/fonts/truetype/tlwg
  /Kinnari-Bold.ttf', which is also in package fonts-tlwg-kinnari
  1:0.6.2-1

Status in fonts-tlwg package in Ubuntu:
  New

Bug description:
  package fonts-tlwg-kinnari-ttf (not installed) failed to
  install/upgrade: trying to overwrite '/usr/share/fonts/truetype/tlwg
  /Kinnari-Bold.ttf', which is also in package fonts-tlwg-kinnari
  1:0.6.2-1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-tlwg-kinnari-ttf (not installed)
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  Date: Wed Jan 13 01:34:40 2016
  DuplicateSignature:
   Unpacking fonts-tlwg-garuda-ttf (1:0.6.2-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/fonts-tlwg-garuda-ttf_1%3a0.6.2-2_all.deb (--unpack):
trying to overwrite '/usr/share/fonts/truetype/tlwg/Garuda.ttf', which is 
also in package fonts-tlwg-garuda 1:0.6.2-1
  ErrorMessage: trying to overwrite 
'/usr/share/fonts/truetype/tlwg/Kinnari-Bold.ttf', which is also in package 
fonts-tlwg-kinnari 1:0.6.2-1
  InstallationDate: Installed on 2015-06-02 (224 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.1.10
  SourcePackage: fonts-tlwg
  Title: package fonts-tlwg-kinnari-ttf (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/share/fonts/truetype/tlwg/Kinnari-Bold.ttf', which is also in package 
fonts-tlwg-kinnari 1:0.6.2-1
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (76 days ago)

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

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

[Desktop-packages] [Bug 1528728] [NEW] gnome-terminal starts up at 79×23 instead of 80×24

[Anders Kaseorg]

Public bug reported:

Starting gnome-terminal results in a 79×23 window instead of the
standard 80×24, at least in Ubuntu Gnome with the default Adwaita theme
on a high-DPI laptop. This makes it irritating to use some applications
designed for an 80-column terminal.

According to an upstream bug report
(https://bugzilla.gnome.org/show_bug.cgi?id=750559), the problem is
caused by the Ubuntu patch debian/patches/0001-Add-the-style-context-
provider-with-FALLBACK-priorit.patch, which was reverted upstream
(https://bugzilla.gnome.org/show_bug.cgi?id=740123#c6) and in Debian
(https://bugs.debian.org/787104) for this reason. A new version of this
patch (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c9) fixes the
problem for me.

** Affects: vte
 Importance: Unknown
 Status: Unknown

** Affects: vte2.91 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: vte2.91 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: patch

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

Title:
  gnome-terminal starts up at 79×23 instead of 80×24

Status in Gnome Virtual Terminal Emulator:
  Unknown
Status in vte2.91 package in Ubuntu:
  New
Status in vte2.91 package in Debian:
  Unknown

Bug description:
  Starting gnome-terminal results in a 79×23 window instead of the
  standard 80×24, at least in Ubuntu Gnome with the default Adwaita
  theme on a high-DPI laptop. This makes it irritating to use some
  applications designed for an 80-column terminal.

  According to an upstream bug report
  (https://bugzilla.gnome.org/show_bug.cgi?id=750559), the problem is
  caused by the Ubuntu patch debian/patches/0001-Add-the-style-context-
  provider-with-FALLBACK-priorit.patch, which was reverted upstream
  (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c6) and in Debian
  (https://bugs.debian.org/787104) for this reason. A new version of
  this patch (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c9)
  fixes the problem for me.

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

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

[Desktop-packages] [Bug 1528728] Re: gnome-terminal starts up at 79×23 instead of 80×24

[Anders Kaseorg]

** Patch added: "vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1528728/+attachment/4539301/+files/vte2.91_0.42.1-1ubuntu1_lp1528728.debdiff

** Tags added: patch

** Bug watch added: Debian Bug tracker #787104
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787104

** Also affects: vte2.91 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787104
   Importance: Unknown
   Status: Unknown

** Package changed: gnome-terminal (Ubuntu) => vte2.91 (Ubuntu)

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

** Also affects: vte via
   https://bugzilla.gnome.org/show_bug.cgi?id=750559
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-terminal starts up at 79×23 instead of 80×24

Status in Gnome Virtual Terminal Emulator:
  Unknown
Status in vte2.91 package in Ubuntu:
  New
Status in vte2.91 package in Debian:
  Unknown

Bug description:
  Starting gnome-terminal results in a 79×23 window instead of the
  standard 80×24, at least in Ubuntu Gnome with the default Adwaita
  theme on a high-DPI laptop. This makes it irritating to use some
  applications designed for an 80-column terminal.

  According to an upstream bug report
  (https://bugzilla.gnome.org/show_bug.cgi?id=750559), the problem is
  caused by the Ubuntu patch debian/patches/0001-Add-the-style-context-
  provider-with-FALLBACK-priorit.patch, which was reverted upstream
  (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c6) and in Debian
  (https://bugs.debian.org/787104) for this reason. A new version of
  this patch (https://bugzilla.gnome.org/show_bug.cgi?id=740123#c9)
  fixes the problem for me.

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

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

[Desktop-packages] [Bug 1519152] [NEW] unicode-math package results in Undefined control sequence \__um_set_big_operator:nnn

[Anders Kaseorg]

Public bug reported:

The unicode-math LaTeX package no longer works at all in either of its
supported TeX engines (xelatex and lualatex). Downgrading texlive-math-
extra from 2015.20151116-1 to 2015.20150810-1 makes it work again.

$ cat test.tex
\documentclass{article}
\usepackage{unicode-math}
\begin{document}
\end{document}

$ xelatex test.tex
This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Debian) (preloaded 
format=xelatex)
 restricted \write18 enabled.
entering extended mode
…
! Undefined control sequence.
\__um_set_big_operator:nnn ...r_gset_active_eq:nN 
  {#3}\__um_tmpa: \__um_set_...
l.3 \begin{document}

? 

(Same result with lualatex.)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: texlive-math-extra 2015.20151116-1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.19.2-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 23 19:52:51 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-06-02 (174 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: texlive-extra
UpgradeStatus: Upgraded to xenial on 2015-10-28 (26 days ago)

** Affects: texlive-extra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug regression-release xenial

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

Title:
  unicode-math package results in Undefined control sequence
  \__um_set_big_operator:nnn

Status in texlive-extra package in Ubuntu:
  New

Bug description:
  The unicode-math LaTeX package no longer works at all in either of its
  supported TeX engines (xelatex and lualatex). Downgrading texlive-
  math-extra from 2015.20151116-1 to 2015.20150810-1 makes it work
  again.

  $ cat test.tex
  \documentclass{article}
  \usepackage{unicode-math}
  \begin{document}
  \end{document}

  $ xelatex test.tex
  This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Debian) 
(preloaded format=xelatex)
   restricted \write18 enabled.
  entering extended mode
  …
  ! Undefined control sequence.
  \__um_set_big_operator:nnn ...r_gset_active_eq:nN 
{#3}\__um_tmpa: 
\__um_set_...
  l.3 \begin{document}
  
  ? 

  (Same result with lualatex.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: texlive-math-extra 2015.20151116-1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 23 19:52:51 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-02 (174 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  PackageArchitecture: all
  SourcePackage: texlive-extra
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (26 days ago)

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

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

[Desktop-packages] [Bug 1519152] Re: unicode-math package results in Undefined control sequence \__um_set_big_operator:nnn

[Anders Kaseorg]

This can be fixed by merging texlive-base 2015.20151116-1 from Debian
unstable. Here’s a debdiff from 2015.20151116-1 porting the trivial
Ubuntu delta forward.

** Also affects: texlive-base (Ubuntu)
   Importance: Undecided
   Status: New

** Patch added: "texlive-base_2015.20151116-1_1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1519152/+attachment/4524384/+files/texlive-base_2015.20151116-1_1ubuntu1.debdiff

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

Title:
  unicode-math package results in Undefined control sequence
  \__um_set_big_operator:nnn

Status in texlive-base package in Ubuntu:
  New
Status in texlive-extra package in Ubuntu:
  New

Bug description:
  The unicode-math LaTeX package no longer works at all in either of its
  supported TeX engines (xelatex and lualatex). Downgrading texlive-
  math-extra from 2015.20151116-1 to 2015.20150810-1 makes it work
  again.

  $ cat test.tex
  \documentclass{article}
  \usepackage{unicode-math}
  \begin{document}
  \end{document}

  $ xelatex test.tex
  This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Debian) 
(preloaded format=xelatex)
   restricted \write18 enabled.
  entering extended mode
  …
  ! Undefined control sequence.
  \__um_set_big_operator:nnn ...r_gset_active_eq:nN 
{#3}\__um_tmpa: 
\__um_set_...
  l.3 \begin{document}
  
  ? 

  (Same result with lualatex.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: texlive-math-extra 2015.20151116-1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 23 19:52:51 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-06-02 (174 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  PackageArchitecture: all
  SourcePackage: texlive-extra
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (26 days ago)

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

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

[Desktop-packages] [Bug 1512209] Re: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys'

[Anders Kaseorg]

** Bug watch added: Python Roundup #25493
   http://bugs.python.org/issue25493

** Also affects: python via
   http://bugs.python.org/issue25493
   Importance: Unknown
   Status: Unknown

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

** Also affects: pygobject via
   https://bugzilla.gnome.org/show_bug.cgi?id=757184
   Importance: Unknown
   Status: Unknown

** Attachment removed: "CurrentDmesg.txt.txt"
   
https://bugs.launchpad.net/pygobject/+bug/1512209/+attachment/4510908/+files/CurrentDmesg.txt.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/pygobject/+bug/1512209/+attachment/4510912/+files/JournalErrors.txt

** Information type changed from Private to Public

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

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

Title:
  update-manager crashed with SyntaxError in find_cookie(): invalid or
  missing encoding declaration for '/usr/bin/sys'

Status in pygobject:
  Unknown
Status in Python:
  Unknown
Status in pygobject package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  update-manager crashed with SyntaxError in find_cookie(): invalid or
  missing encoding declaration for '/usr/bin/sys'

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: update-manager 1:15.10.3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sun Nov  1 22:34:22 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'813'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'500'
   b'com.ubuntu.update-manager' b'launch-time' b'1445601355'
  InstallationDate: Installed on 2015-06-02 (152 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
  PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']
  SourcePackage: update-manager
  Title: update-manager crashed with SyntaxError in find_cookie(): invalid or 
missing encoding declaration for '/usr/bin/sys'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (4 days ago)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare 
sbuild sudo wireshark

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

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

[Desktop-packages] [Bug 1512209] Re: update-manager crashed with SyntaxError in find_cookie(): invalid or missing encoding declaration for '/usr/bin/sys'

[Anders Kaseorg]

This is a combination of two problems. One is that starting update-
manager results in these warnings:

/usr/bin/update-manager:28: PyGIWarning: Gtk was imported without specifying a 
version first. Use gi.require_version('Gtk', '3.0') before import to ensure 
that the right version gets loaded.
  from gi.repository import Gtk
/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py:26: PyGIWarning: 
GdkX11 was imported without specifying a version first. Use 
gi.require_version('GdkX11', '3.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Gdk, GdkX11
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Dbusmenu was imported without specifying a version first. Use 
gi.require_version('Dbusmenu', '0.4') before import to ensure that the right 
version gets loaded.
  from gi.repository import Dbusmenu, Unity
/usr/lib/python3/dist-packages/UpdateManager/UnitySupport.py:29: PyGIWarning: 
Unity was imported without specifying a version first. Use 
gi.require_version('Unity', '7.0') before import to ensure that the right 
version gets loaded.
  from gi.repository import Dbusmenu, Unity

The other is that when openafs-client is installed, the presence of
/usr/bin/sys causes Python to crash while displaying these warnings (see
linked bugs).

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

Title:
  update-manager crashed with SyntaxError in find_cookie(): invalid or
  missing encoding declaration for '/usr/bin/sys'

Status in pygobject:
  Fix Released
Status in Python:
  Won't Fix
Status in pygobject package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  update-manager crashed with SyntaxError in find_cookie(): invalid or
  missing encoding declaration for '/usr/bin/sys'

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: update-manager 1:15.10.3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.19.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Sun Nov  1 22:34:22 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/update-manager
  GsettingsChanges:
   b'com.ubuntu.update-manager' b'show-details' b'true'
   b'com.ubuntu.update-manager' b'window-height' b'813'
   b'com.ubuntu.update-manager' b'first-run' b'false'
   b'com.ubuntu.update-manager' b'window-width' b'500'
   b'com.ubuntu.update-manager' b'launch-time' b'1445601355'
  InstallationDate: Installed on 2015-06-02 (152 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update 
--no-focus-on-map
  PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']
  SourcePackage: update-manager
  Title: update-manager crashed with SyntaxError in find_cookie(): invalid or 
missing encoding declaration for '/usr/bin/sys'
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (4 days ago)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare 
sbuild sudo wireshark

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

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

[Desktop-packages] [Bug 1237904] Re: Xorg crashed with SIGABRT in OsAbort()

[Anders Kaseorg]

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Freshly booted and logged in, update-notifier signalled a problem, and
  when I clicked "report" caused this cascade of errors.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.3-3ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct  9 14:36:18 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.16, 3.11.0-4-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2207]
  InstallationDate: Installed on 2013-09-27 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130903)
  MachineType: LENOVO 36986DG
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :1 -background none -verbose -auth 
/var/run/gdm/auth-for-gdm-vyFtLi/database -seat seat0 -nolisten tcp vt7
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-4-generic.efi.signed 
root=UUID=d0531e28-c01c-4e90-9c01-43e30e7dea56 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   FatalError ()
   ?? ()
   xf86CloseConsole ()
   ddxGiveUp ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/22/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GFET30WW (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 36986DG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGFET30WW(1.09):bd02/22/2013:svnLENOVO:pn36986DG:pvrThinkPadHelix:rvnLENOVO:rn36986DG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 36986DG
  dmi.product.version: ThinkPad Helix
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Thu Oct 10 11:57:27 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12893 
   vendor AUO
  xserver.version: 2:1.14.3-3ubuntu1

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

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

[Desktop-packages] [Bug 1364741] Re: /lib/udev/rules.d/69-libmtp.rules in libmtp-common is corrupt

[Anders Kaseorg]

This bug was marked Confirmed because it affected multiple users. It is
not a local issue, and in fact it’s still present in trusty, as you can
verify it for yourself by examining the contents of

http://archive.ubuntu.com/ubuntu/pool/main/libm/libmtp/libmtp-
common_1.1.6-20-g1b9f164-1ubuntu2_all.deb


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

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

Title:
  /lib/udev/rules.d/69-libmtp.rules in libmtp-common is corrupt

Status in libmtp package in Ubuntu:
  Confirmed

Bug description:
  I’m seeing these log messages from udev every so often:

  systemd-udevd[416]: invalid key/value pair in file
  /lib/udev/rules.d/69-libmtp.rules on line 1,starting at character 1
  ('n')

  It’s true: the 69-libmtp.rules file distributed in the package
  literally begins with an error message, which makes no sense.

  $ head /lib/udev/rules.d/69-libmtp.rules
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.# UDEV-style hotplug 
map for libmtp
  # Put this file in /etc/udev/rules.d
  …

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libmtp-common 1.1.6-20-g1b9f164-1ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  3 00:20:51 2014
  Dependencies:
   
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-22 (11 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140730)
  PackageArchitecture: all
  SourcePackage: libmtp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1488254] [NEW] clang++ no longer ABI-compatible with g++

[Anders Kaseorg]

Public bug reported:

$ cat foo.cc
#include string
std::string hello = Hello, world!\n;
$ cat bar.cc
#include string
#include iostream
extern std::string hello;
int main() {
std::cout  hello;
return 0;
}
$ g++ -c foo.cc  g++ foo.o bar.cc  ./a.out
Hello, world!
$ clang++ -c foo.cc  clang++ foo.o bar.cc  ./a.out
Hello, world!
$ g++ -c foo.cc  clang++ foo.o bar.cc  ./a.out
/tmp/bar-34fb23.o: In function `main':
bar.cc:(.text+0x14): undefined reference to `hello'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
$ clang++ -c foo.cc  g++ foo.o bar.cc  ./a.out
/tmp/ccqU38Mh.o: In function `main':
bar.cc:(.text+0x5): undefined reference to `hello[abi:cxx11]'
collect2: error: ld returned 1 exit status

In practice, this means that many programs using C++ libraries other
than libstdc++ fail to compile with clang++. For example, mosh fails
with undefined references to google::protobuf::internal::empty_string_,
google::protobuf::MessageLite::InitializationErrorString() const, and
google::protobuf::MessageLite::SerializeAsString() const.

** Affects: llvm
 Importance: Unknown
 Status: Unknown

** Affects: llvm-toolchain-3.6 (Ubuntu)
 Importance: Undecided
 Status: New

** Bug watch added: llvm.org/bugs/ #23529
   http://llvm.org/bugs/show_bug.cgi?id=23529

** Also affects: llvm via
   http://llvm.org/bugs/show_bug.cgi?id=23529
   Importance: Unknown
   Status: Unknown

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

Title:
  clang++ no longer ABI-compatible with g++

Status in LLVM:
  Unknown
Status in llvm-toolchain-3.6 package in Ubuntu:
  New

Bug description:
  $ cat foo.cc
  #include string
  std::string hello = Hello, world!\n;
  $ cat bar.cc
  #include string
  #include iostream
  extern std::string hello;
  int main() {
  std::cout  hello;
  return 0;
  }
  $ g++ -c foo.cc  g++ foo.o bar.cc  ./a.out
  Hello, world!
  $ clang++ -c foo.cc  clang++ foo.o bar.cc  ./a.out
  Hello, world!
  $ g++ -c foo.cc  clang++ foo.o bar.cc  ./a.out
  /tmp/bar-34fb23.o: In function `main':
  bar.cc:(.text+0x14): undefined reference to `hello'
  clang: error: linker command failed with exit code 1 (use -v to see 
invocation)
  $ clang++ -c foo.cc  g++ foo.o bar.cc  ./a.out
  /tmp/ccqU38Mh.o: In function `main':
  bar.cc:(.text+0x5): undefined reference to `hello[abi:cxx11]'
  collect2: error: ld returned 1 exit status

  In practice, this means that many programs using C++ libraries other
  than libstdc++ fail to compile with clang++. For example, mosh fails
  with undefined references to
  google::protobuf::internal::empty_string_,
  google::protobuf::MessageLite::InitializationErrorString() const, and
  google::protobuf::MessageLite::SerializeAsString() const.

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

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

[Desktop-packages] [Bug 1482439] Re: wpa_supplicant crashed with SIGSEGV in get_iface_by_dbus_path()

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  wpa_supplicant crashed with SIGSEGV in get_iface_by_dbus_path()

Status in wpa package in Ubuntu:
  New

Bug description:
  wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: wpasupplicant 2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  Date: Wed Aug  5 00:08:21 2015
  ExecutablePath: /sbin/wpa_supplicant
  InstallationDate: Installed on 2015-06-02 (65 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Release amd64 
(20150422)
  ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f8880818cba __strcmp_sse2_unaligned+26:   movdqu 
(%rdi),%xmm1
   PC (0x7f8880818cba) ok
   source (%rdi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %xmm1 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: wpa
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
  Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
  UpgradeStatus: Upgraded to wily on 2015-06-17 (50 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1484382] [NEW] [firefox-aurora PPA] StartupWMClass=Firefox-dev missing from firefox.desktop

[Anders Kaseorg]

Public bug reported:

Using the firefox package from ppa:ubuntu-mozilla-daily/firefox-aurora,
GNOME Shell fails to match running Firefox windows to the Firefox
launcher icon. This is because the Firefox windows report a WM_CLASS of
‘Firefox-dev’, which GNOME Shell by default tries to match against the
basename of the firefox.desktop file (‘firefox’).

This can be fixed by adding ‘StartupWMClass=Firefox-dev’ to
firefox.desktop for the Aurora packages.

(The firefox-trunk package from ppa:ubuntu-mozilla-daily/ppa is not
affected because its WM_CLASS ‘Firefox-trunk’ matches the basename of
firefox-trunk.desktop.)

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

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

Title:
  [firefox-aurora PPA] StartupWMClass=Firefox-dev missing from
  firefox.desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Using the firefox package from ppa:ubuntu-mozilla-daily/firefox-
  aurora, GNOME Shell fails to match running Firefox windows to the
  Firefox launcher icon. This is because the Firefox windows report a
  WM_CLASS of ‘Firefox-dev’, which GNOME Shell by default tries to match
  against the basename of the firefox.desktop file (‘firefox’).

  This can be fixed by adding ‘StartupWMClass=Firefox-dev’ to
  firefox.desktop for the Aurora packages.

  (The firefox-trunk package from ppa:ubuntu-mozilla-daily/ppa is not
  affected because its WM_CLASS ‘Firefox-trunk’ matches the basename of
  firefox-trunk.desktop.)

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

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

[Desktop-packages] [Bug 1484382] Re: [firefox-aurora PPA] StartupWMClass=Firefox-dev missing from firefox.desktop

[Anders Kaseorg]

Or, I guess, it could alternatively be fixed by renaming the Aurora
packages to firefox-dev with a firefox-dev.desktop. That might be closer
to upstream’s expectations: Aurora tries very hard to coexist with
stable Firefox rather than replace it. (It creates its own separate
Firefox profile ‘dev-edition-default’, and switches back to it on every
launch unless you turn off the “Allow Firefox Developer Edition and
Firefox to run at the same time” setting.)

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

Title:
  [firefox-aurora PPA] StartupWMClass=Firefox-dev missing from
  firefox.desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Using the firefox package from ppa:ubuntu-mozilla-daily/firefox-
  aurora, GNOME Shell fails to match running Firefox windows to the
  Firefox launcher icon. This is because the Firefox windows report a
  WM_CLASS of ‘Firefox-dev’, which GNOME Shell by default tries to match
  against the basename of the firefox.desktop file (‘firefox’).

  This can be fixed by adding ‘StartupWMClass=Firefox-dev’ to
  firefox.desktop for the Aurora packages.

  (The firefox-trunk package from ppa:ubuntu-mozilla-daily/ppa is not
  affected because its WM_CLASS ‘Firefox-trunk’ matches the basename of
  firefox-trunk.desktop.)

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

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

[Desktop-packages] [Bug 1468832] Re: lightdm sources .profile

[Anders Kaseorg]

.xsession is sourced within /bin/sh, not /bin/bash. It wouldn’t make
sense to source .bashrc from it (unless you happened to write a .bashrc
that doesn’t use any bash features).

Also, .bashrc is sourced by _every_ interactive shell, so if you were to add 
things to environment variables from .bashrc, e.g.
  PATH=$HOME/bin:$PATH
then they would show up multiple times in shells launched inside shells. This 
is just an annoyance for $PATH, but it might be an important problem for other 
variables, so you would need to add code to test whether the variable had 
already been changed, etc.

This is why Ubuntu’s default .profile (see /etc/skel/.profile) sets up
$PATH and the default .bashrc (see /etc/skel/.bashrc) does not.

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

Title:
  lightdm sources .profile

Status in lightdm package in Ubuntu:
  New

Bug description:
  It is a bug for any display manager to read .profile--you guys are
  absolutely killing me with this.  The user's .profile is to be read by
  the shell, on interactive shell (i.e. terminal) logins ONLY.  The man
  page for bash explains this in detail; it's also discussed in the dash
  man page.  The problem with display managers reading .profile is that
  it is the place where commands to set up your terminal (i.e. stty) go
  --this is the entire point of differentiating interactive shells from
  non-interactive shells, and it's the reason only interactive shells
  read .profile at all.  Currently, if you have any such commands in
  your .profile, lightdm barfs on them, delaying the login session and
  forcing you to click on a prompt.  This is extremely annoying (and
  wrong)!

  It would be satisfactory to make lightdm not display the errors, but
  that's the wrong solution.  There's already a decades-established
  method of getting X display managers to source your environment
  settings: the .xsession file.  It should be read by ALL display
  managers (or the session file that starts them).  If you have common
  environment settings you want set in all your shells, the correct way
  to handle this is:

  .bashrc:
  # set all common environment vars here
  ENV_VAR=foo
  ...

  .profile:
  # set up terminal
  stty erase
  # BASH already sources .bashrc by default on interactive sessions

  .xsession:
  if [ -f .bashrc ] source .bashrc

  If you're not using BASH, you can still use this method without
  changing anything, except in .profile you need to explicitly source
  the .bashrc file.  Of course you can change the name of the file that
  contains the common settings to reflect that your shell is not BASH;
  since the file is sourced by your other files explicitly, it does not
  matter what the user calls it.

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

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

[Desktop-packages] [Bug 1468832] Re: lightdm sources .profile

[Anders Kaseorg]

No, you misunderstand my comment. It doesn’t matter whether or not your
shell is bash. ~/.xsession file is sourced using /bin/sh, not using your
shell. You cannot expect to be able to source ~/.bashrc from
~/.xsession, no matter what your preferred shell is.

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

Title:
  lightdm sources .profile

Status in lightdm package in Ubuntu:
  New

Bug description:
  It is a bug for any display manager to read .profile--you guys are
  absolutely killing me with this.  The user's .profile is to be read by
  the shell, on interactive shell (i.e. terminal) logins ONLY.  The man
  page for bash explains this in detail; it's also discussed in the dash
  man page.  The problem with display managers reading .profile is that
  it is the place where commands to set up your terminal (i.e. stty) go
  --this is the entire point of differentiating interactive shells from
  non-interactive shells, and it's the reason only interactive shells
  read .profile at all.  Currently, if you have any such commands in
  your .profile, lightdm barfs on them, delaying the login session and
  forcing you to click on a prompt.  This is extremely annoying (and
  wrong)!

  It would be satisfactory to make lightdm not display the errors, but
  that's the wrong solution.  There's already a decades-established
  method of getting X display managers to source your environment
  settings: the .xsession file.  It should be read by ALL display
  managers (or the session file that starts them).  If you have common
  environment settings you want set in all your shells, the correct way
  to handle this is:

  .bashrc:
  # set all common environment vars here
  ENV_VAR=foo
  ...

  .profile:
  # set up terminal
  stty erase
  # BASH already sources .bashrc by default on interactive sessions

  .xsession:
  if [ -f .bashrc ] source .bashrc

  If you're not using BASH, you can still use this method without
  changing anything, except in .profile you need to explicitly source
  the .bashrc file.  Of course you can change the name of the file that
  contains the common settings to reflect that your shell is not BASH;
  since the file is sourced by your other files explicitly, it does not
  matter what the user calls it.

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

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

[Desktop-packages] [Bug 1468832] Re: lightdm sources .profile

[Anders Kaseorg]

Aha, I was confusing ~/.xsessionrc with ~/.xsession. ~/.xsessionrc is
sourced using /bin/sh. A default Ubuntu session does not invoke
~/.xsession at all. Creating one that works correctly with Unity or
GNOME or whatever, as well as configuring LightDM to invoke it it,
requires a very pointy hat.

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

Title:
  lightdm sources .profile

Status in lightdm package in Ubuntu:
  New

Bug description:
  It is a bug for any display manager to read .profile--you guys are
  absolutely killing me with this.  The user's .profile is to be read by
  the shell, on interactive shell (i.e. terminal) logins ONLY.  The man
  page for bash explains this in detail; it's also discussed in the dash
  man page.  The problem with display managers reading .profile is that
  it is the place where commands to set up your terminal (i.e. stty) go
  --this is the entire point of differentiating interactive shells from
  non-interactive shells, and it's the reason only interactive shells
  read .profile at all.  Currently, if you have any such commands in
  your .profile, lightdm barfs on them, delaying the login session and
  forcing you to click on a prompt.  This is extremely annoying (and
  wrong)!

  It would be satisfactory to make lightdm not display the errors, but
  that's the wrong solution.  There's already a decades-established
  method of getting X display managers to source your environment
  settings: the .xsession file.  It should be read by ALL display
  managers (or the session file that starts them).  If you have common
  environment settings you want set in all your shells, the correct way
  to handle this is:

  .bashrc:
  # set all common environment vars here
  ENV_VAR=foo
  ...

  .profile:
  # set up terminal
  stty erase
  # BASH already sources .bashrc by default on interactive sessions

  .xsession:
  if [ -f .bashrc ] source .bashrc

  If you're not using BASH, you can still use this method without
  changing anything, except in .profile you need to explicitly source
  the .bashrc file.  Of course you can change the name of the file that
  contains the common settings to reflect that your shell is not BASH;
  since the file is sourced by your other files explicitly, it does not
  matter what the user calls it.

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

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

[Desktop-packages] [Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90

[Anders Kaseorg]

Every time I press one of these keys, I get the message

(gnome-settings-daemon:7822): GLib-GIO-WARNING **: Dropping signal
AcceleratorActivated of type (ua{sv}) since the type from the expected
interface is (uuu)

This is probably the same thing that happened in LP: #1217196 and LP:
#1376471.

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

Title:
  Media, brightness and volume keys don't work with GNOME 3.15.90

Status in Gnome Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Incomplete
Status in Ubuntu GNOME:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 15.04 Vivid to use GNOME 3.15.90 (by using
  gnome3-team/gnome3, gnome3-team/gnome3-staging ppas) media, brightness
  and volume keys from my laptop keyboard stop to work after working
  some time in a session or after suspending the computer.

  If I restart my computer media keys work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-settings-daemon 3.15.90-0ubuntu1~vivid1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar  3 23:07:33 2015
  InstallationDate: Installed on 2014-10-22 (132 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140923)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90

[Anders Kaseorg]

Here’s a tested patch that reverts the relevant gnome-shell changes to
make it work with gnome-settings-daemon 3.14.x.

** Patch added: gnome-shell_3.16.2-1ubuntu1_lp1427877.debdiff
   
https://bugs.launchpad.net/ubuntu-gnome/+bug/1427877/+attachment/4416604/+files/gnome-shell_3.16.2-1ubuntu1_lp1427877.debdiff

** Tags added: patch

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

Title:
  Media, brightness and volume keys don't work with GNOME 3.15.90

Status in Gnome Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Incomplete
Status in Ubuntu GNOME:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 15.04 Vivid to use GNOME 3.15.90 (by using
  gnome3-team/gnome3, gnome3-team/gnome3-staging ppas) media, brightness
  and volume keys from my laptop keyboard stop to work after working
  some time in a session or after suspending the computer.

  If I restart my computer media keys work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-settings-daemon 3.15.90-0ubuntu1~vivid1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar  3 23:07:33 2015
  InstallationDate: Installed on 2014-10-22 (132 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140923)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90

[Anders Kaseorg]

Specifically, this is caused because gnome-shell 3.16 has
https://git.gnome.org/browse/gnome-shell/commit/?id=2aa4fb02dd9c568038d12fe609252b6934367e76

but gnome-settings-daemon 3.14 does not have
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=46525602364088398eeb3a98d7bcfa64deeddd4e

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

Title:
  Media, brightness and volume keys don't work with GNOME 3.15.90

Status in Gnome Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Incomplete
Status in Ubuntu GNOME:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 15.04 Vivid to use GNOME 3.15.90 (by using
  gnome3-team/gnome3, gnome3-team/gnome3-staging ppas) media, brightness
  and volume keys from my laptop keyboard stop to work after working
  some time in a session or after suspending the computer.

  If I restart my computer media keys work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-settings-daemon 3.15.90-0ubuntu1~vivid1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar  3 23:07:33 2015
  InstallationDate: Installed on 2014-10-22 (132 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140923)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1406189] Re: evolution-addressbook-factory crashed with SIGABRT in g_mutex_clear()

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  evolution-addressbook-factory crashed with SIGABRT in g_mutex_clear()

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

Bug description:
  evolution-addressbook-factory crashed with SIGABRT in g_mutex_clear()

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: evolution-data-server 3.12.9-0ubuntu1
  Uname: Linux 3.18.1-031801-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 29 01:38:19 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory
  InstallationDate: Installed on 2014-08-22 (128 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140730)
  ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libebackend-1.2.so.7
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: evolution-addressbook-factory crashed with SIGABRT in g_mutex_clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare 
sbuild sudo wireshark

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

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

[Desktop-packages] [Bug 1406164] Re: evolution-calendar-factory crashed with SIGABRT in g_mutex_clear()

[Anders Kaseorg]

** Information type changed from Private to Public

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

Title:
  evolution-calendar-factory crashed with SIGABRT in g_mutex_clear()

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

Bug description:
  This happens on every login.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: evolution-data-server 3.12.9-0ubuntu1
  Uname: Linux 3.18.1-031801-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 28 21:09:52 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
  InstallationDate: Installed on 2014-08-22 (128 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140730)
  ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
  Signal: 6
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libebackend-1.2.so.7
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: evolution-calendar-factory crashed with SIGABRT in g_mutex_clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare 
sbuild sudo wireshark

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

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

[Desktop-packages] [Bug 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU

[Anders Kaseorg]

Chrome 40 now sets LIBGL_DRI3_DISABLE=1 automatically on desktop Linux
(https://code.google.com/p/chromium/issues/detail?id=415681).

** Bug watch added: code.google.com/p/chromium/issues #415681
   http://code.google.com/p/chromium/issues/detail?id=415681

** Also affects: chromium-browser via
   http://code.google.com/p/chromium/issues/detail?id=415681
   Importance: Unknown
   Status: Unknown

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

Title:
  Google Chrome crash with mesa 10.3 on Intel GPU

Status in Chromium Browser:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  When I start google-chrome on my Ubuntu 14.10 system the process it
  uses to test for a working GPU crashes and then Chrome falls back to
  software rendering.

  In chrome://gpu/ I get:

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only, hardware acceleration unavailable
  Flash Stage3D: Software only, hardware acceleration unavailable
  Flash Stage3D Baseline profile: Software only, hardware acceleration 
unavailable
  Compositing: Software only, hardware acceleration unavailable
  Multiple Raster Threads: Unavailable
  Rasterization: Software only, hardware acceleration unavailable
  Threaded Rasterization: Unavailable
  Video Decode: Software only, hardware acceleration unavailable
  Video Encode: Software only, hardware acceleration unavailable
  WebGL: Unavailable

  Driver Bug Workarounds
  clear_uniforms_before_first_program_use
  count_all_in_varyings_packing
  disable_ext_occlusion_query
  disable_post_sub_buffers_for_onscreen_surfaces
  scalarize_vec_and_mat_constructor_args

  Problems Detected
  GPU process was unable to boot: GPU access is disabled in chrome://settings.
  Disabled Features: all
  [...]

  In Ubuntu 14.04 (and also previous versions), on the same laptop, the
  exact same Google Chrome used to work perfectly with GPU acceleration.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dri 10.3.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
    * Setting sensors limits   
  [ OK ]
    * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Fri Oct  3 17:48:09 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: kubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:0494]
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Oct  2 13:54:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8685
   vendor AUO
  xserver.version: 2:1.16.0-1ubuntu1

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1387323] [NEW] Merge emacs24 24.4+1-4 from Debian unstable

[Anders Kaseorg]

Public bug reported:

We should merge emacs24 24.4+1-4 from Debian unstable. Note that emacs24
-non-dfsg 24.4+1-2 has already been synced.

(I’m currently preparing this merge in my PPA; I’ll post a debdiff
shortly.)

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

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

Title:
  Merge emacs24 24.4+1-4 from Debian unstable

Status in “emacs24” package in Ubuntu:
  New

Bug description:
  We should merge emacs24 24.4+1-4 from Debian unstable. Note that
  emacs24-non-dfsg 24.4+1-2 has already been synced.

  (I’m currently preparing this merge in my PPA; I’ll post a debdiff
  shortly.)

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

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

[Desktop-packages] [Bug 1387323] Re: Merge emacs24 24.4+1-4 from Debian unstable

[Anders Kaseorg]

** Patch added: emacs24_24.4+1-4_4ubuntu1.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1387323/+attachment/4248445/+files/emacs24_24.4%2B1-4_4ubuntu1.debdiff

** Description changed:

  We should merge emacs24 24.4+1-4 from Debian unstable. Note that emacs24
  -non-dfsg 24.4+1-2 has already been synced.
- 
- (I’m currently preparing this merge in my PPA; I’ll post a debdiff
- shortly.)

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

Title:
  Merge emacs24 24.4+1-4 from Debian unstable

Status in “emacs24” package in Ubuntu:
  New

Bug description:
  We should merge emacs24 24.4+1-4 from Debian unstable. Note that
  emacs24-non-dfsg 24.4+1-2 has already been synced.

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

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

[Desktop-packages] [Bug 493766] Re: Multi_key / compose does not work when XMODIFIERS=@im=SCIM

[Anders Kaseorg]

Merge prepared at bug 1387323.

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

Title:
  Multi_key / compose does not work when XMODIFIERS=@im=SCIM

Status in “emacs23” package in Ubuntu:
  Confirmed
Status in “emacs24” package in Ubuntu:
  Fix Released
Status in “emacs24” package in Debian:
  Fix Released
Status in “emacs23” package in Fedora:
  Unknown

Bug description:
  Binary package hint: emacs23

  Ubuntu 9.10
  emacs23:
Installed: 23.1+1-4ubuntu3.1

  Using X with a configuration for SCIM input methods, environment
  variable XMODIFIERS then contains @im=SCIM

  Start emacs

  Hit Multi_key (aka Compose key, often bound to one of the Windows keys
  depending on keyboard layout and layout options) ' (single quote) e

  You should be getting é (e acute accent)

  Instead, emacs complains that Multi_key is undefined.

  Problem disappears if launching Emacs with XMODIFIERS='

  ProblemType: Bug
  Architecture: i386
  Date: Mon Dec  7 21:56:37 2009
  DistroRelease: Ubuntu 9.10
  Package: emacs (not installed)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
  SourcePackage: emacs22
  Uname: Linux 2.6.31-16-generic i686
  XsessionErrors:
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2548): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2537): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (gnome-panel:2536): Gdk-WARNING **: 
/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a 
pixmap or window

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

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

[Desktop-packages] [Bug 493766] Re: Multi_key / compose does not work when XMODIFIERS=@im=SCIM

[Anders Kaseorg]

The different appearance of 0017-Further-improve-create_frame_xic-
patch.patch is due to the slightly different diff algorithms used by Git
and Bazaar (http://bramcohen.livejournal.com/37690.html); the actual
code change is identical.

If you want to sponsor a merge instead, the one already generated at
https://merges.ubuntu.com/e/emacs24/ has been working for me.

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

Title:
  Multi_key / compose does not work when XMODIFIERS=@im=SCIM

Status in “emacs23” package in Ubuntu:
  Confirmed
Status in “emacs24” package in Ubuntu:
  Confirmed
Status in “emacs24” package in Debian:
  Fix Released
Status in “emacs23” package in Fedora:
  Unknown

Bug description:
  Binary package hint: emacs23

  Ubuntu 9.10
  emacs23:
Installed: 23.1+1-4ubuntu3.1

  Using X with a configuration for SCIM input methods, environment
  variable XMODIFIERS then contains @im=SCIM

  Start emacs

  Hit Multi_key (aka Compose key, often bound to one of the Windows keys
  depending on keyboard layout and layout options) ' (single quote) e

  You should be getting é (e acute accent)

  Instead, emacs complains that Multi_key is undefined.

  Problem disappears if launching Emacs with XMODIFIERS='

  ProblemType: Bug
  Architecture: i386
  Date: Mon Dec  7 21:56:37 2009
  DistroRelease: Ubuntu 9.10
  Package: emacs (not installed)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
  SourcePackage: emacs22
  Uname: Linux 2.6.31-16-generic i686
  XsessionErrors:
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2548): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2537): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (gnome-panel:2536): Gdk-WARNING **: 
/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a 
pixmap or window

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

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