[Bug 1627901] [NEW] /lib/systemd/systemd-journald:6:server_read_dev_kmsg:source_dispatch:sd_event_dispatch:sd_event_run:main

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding systemd.  This problem was most recently seen with version
229-4ubuntu8, the problem page at
https://errors.ubuntu.com/problem/b36dbf417b25f2ad6c8f3e648c98a253db6f4f65
contains more details.

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


** Tags: vivid wily xenial

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

Title:
  /lib/systemd/systemd-
  
journald:6:server_read_dev_kmsg:source_dispatch:sd_event_dispatch:sd_event_run:main

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1612240] Re: [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

[Launchpad Bug Tracker]

This bug was fixed in the package zmqpp - 4.1.2-0ubuntu1

---
zmqpp (4.1.2-0ubuntu1) yakkety; urgency=medium

  * New upstream release
  * debian/copyright:
- Follow up on the license change to MPLv2
  * debian/watch:
- Point to the new upstream location
  * debian/patches/support_use_fd_option.diff:
- Support for ZMQ_USE_FD (LP: #1612240)
  * debian/patches/fix_ftbfs_new_boost.diff:
- Fix FTBFS on yakkety due to boost1.61
  * debian/control:
- Bump the libzmq3-dev dependency for the new required features in zeromq
- Add the libsodium-dev build-dep for the test libs
- Rename package to libzmqpp4 as the ABI changed and the soname was bumped
- Bump the standards version to 3.9.7
  * debian/rules:
- Remove the unneeded statically linked library archive
  * Drop debian/patches/mkdir_before_install.diff
  * Drop debian/patches/fix_1256886.diff

 -- Łukasz 'sil2100' Zemczak   Thu, 11 Aug
2016 17:15:27 +0200

** Changed in: zmqpp (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627304] Re: User locking problems - guest login crashing

[Tyler Hicks]

Marking the apparmor task as invalid since the changes will likely need
to be made to the profile shipped by lightdm.

** Changed in: apparmor (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

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

Title:
  User locking problems - guest login crashing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627304] Re: User locking problems - guest login crashing

[Tyler Hicks]

Thanks, I gave it a shot (after putting the profile into complain mode)
and here are the unique denials that I see when starting the guest
session:

operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1295/fd/2" pid=1295 comm="lightdm-session" requested_mask="c" 
denied_mask="c" fsuid=998 ouid=998
operation="mknod" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1297/fd/2" pid=1297 comm="lightdm-session" requested_mask="c" 
denied_mask="c" fsuid=998 ouid=998
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1446 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"
operation="file_perm" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1293 
comm="upstart" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive" denied_mask="send" addr="@/com/ubuntu/upstart-session/998/1293" 
peer_addr=none peer="unconfined"
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1709 
comm="unity-panel-ser" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"

and when logging out of the guest session:

operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2042 
comm="dbus-send" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"
operation="file_perm" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1293 
comm="upstart" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive" denied_mask="send" addr="@/com/ubuntu/upstart-session/998/1293" 
peer_addr=none peer="unconfined"
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2046 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=1709 
comm="unity-panel-ser" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/1293" peer_addr=none peer="unconfined"

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

Title:
  User locking problems - guest login crashing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1597439] Re: [MIR] zeromq3

[Steve Langasek]

Override component to main
zeromq3 4.1.5-2 in yakkety: universe/libs -> main
libzmq3-dev 4.1.5-2 in yakkety amd64: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety arm64: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety armhf: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety i386: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety powerpc: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety ppc64el: universe/libdevel/optional/100% -> main
libzmq3-dev 4.1.5-2 in yakkety s390x: universe/libdevel/optional/100% -> main
libzmq5 4.1.5-2 in yakkety amd64: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety arm64: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety armhf: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety i386: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety powerpc: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety ppc64el: universe/libs/optional/100% -> main
libzmq5 4.1.5-2 in yakkety s390x: universe/libs/optional/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety amd64: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety arm64: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety armhf: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety i386: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety powerpc: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety ppc64el: universe/debug/extra/100% -> main
libzmq5-dbg 4.1.5-2 in yakkety s390x: universe/debug/extra/100% -> main
22 publications overridden.


** Changed in: zeromq3 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] zeromq3

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1574576] Re: [MIR] network-manager-openvpn

[Steve Langasek]

Override component to main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety: universe/net -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety amd64: 
universe/net/optional/100% -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety arm64: 
universe/net/optional/100% -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety armhf: 
universe/net/optional/100% -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety i386: 
universe/net/optional/100% -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety powerpc: 
universe/net/optional/100% -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety ppc64el: 
universe/net/optional/100% -> main
network-manager-openvpn 1.1.93-1ubuntu1 in yakkety s390x: 
universe/net/optional/100% -> main
network-manager-openvpn-gnome 1.1.93-1ubuntu1 in yakkety amd64: 
universe/net/optional/100% -> main
network-manager-openvpn-gnome 1.1.93-1ubuntu1 in yakkety arm64: 
universe/net/optional/100% -> main
network-manager-openvpn-gnome 1.1.93-1ubuntu1 in yakkety armhf: 
universe/net/optional/100% -> main
network-manager-openvpn-gnome 1.1.93-1ubuntu1 in yakkety i386: 
universe/net/optional/100% -> main
network-manager-openvpn-gnome 1.1.93-1ubuntu1 in yakkety powerpc: 
universe/net/optional/100% -> main
network-manager-openvpn-gnome 1.1.93-1ubuntu1 in yakkety ppc64el: 
universe/net/optional/100% -> main
network-manager-openvpn-gnome 1.1.93-1ubuntu1 in yakkety s390x: 
universe/net/optional/100% -> main
15 publications overridden.


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

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

Title:
  [MIR] network-manager-openvpn

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1588994] Re: Location not working since OTA-11 on BQ 4.5

[Saif Ahmed]

On my bq e4.5 it had not been working since OTA-12. but after OTA-13 it
worked briefly (for 3 days).  Sensor status app indicates "back-end
found" and "Active", but not able to deliver any location data.  Nearby
scope says please enable location services.  Location  detection is on.
some diagnostic tests would be nice.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1588994

Title:
  Location not working since OTA-11 on BQ 4.5

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627304] Re: User locking problems - guest login crashing

[flocculant]

Sep 23 21:42:38 wolf-wolf kernel: [   69.411731] audit: type=1400
audit(1474663358.636:31): apparmor="DENIED" operation="connect"
profile="/usr/lib/lightdm/lightdm-guest-session" pid=3713 comm="initctl"
family="unix" sock_type="stream" protocol=0 requested_mask="send receive
accept" denied_mask="send accept" addr="@/com/ubuntu/upstart-
session/999/3321" peer_addr=none peer="unconfined"

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

Title:
  User locking problems - guest login crashing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627304] Re: User locking problems - guest login crashing

[Iain Lane]

I think this is an issue with the lightdm(-guest-session) apparmor
profiles.

In dmesg:

laney@yakkety-vm:~$ dmesg | grep DENIED
[  142.273990] audit: type=1400 audit(1474905574.718:125): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/sys/kernel/osrelease" pid=2167 comm="pkill" requested_mask="r" 
denied_mask="r" fsuid=998 ouid=0
[  142.274396] audit: type=1400 audit(1474905574.718:126): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274428] audit: type=1400 audit(1474905574.718:127): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/2/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274457] audit: type=1400 audit(1474905574.718:128): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/3/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274484] audit: type=1400 audit(1474905574.718:129): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/4/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274513] audit: type=1400 audit(1474905574.718:130): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/5/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274542] audit: type=1400 audit(1474905574.718:131): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/6/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274569] audit: type=1400 audit(1474905574.718:132): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/7/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274598] audit: type=1400 audit(1474905574.718:133): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/8/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  142.274626] audit: type=1400 audit(1474905574.718:134): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9/cmdline" pid=2167 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.434462] audit: type=1400 audit(1474905579.878:282): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2843 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/2526" peer_addr=none peer="unconfined"
[  147.450970] audit: type=1400 audit(1474905579.894:283): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2855 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/2526" peer_addr=none peer="unconfined"
[  147.494563] audit: type=1400 audit(1474905579.938:284): apparmor="DENIED" 
operation="connect" profile="/usr/lib/lightdm/lightdm-guest-session" pid=2871 
comm="initctl" family="unix" sock_type="stream" protocol=0 requested_mask="send 
receive accept" denied_mask="send accept" 
addr="@/com/ubuntu/upstart-session/998/2526" peer_addr=none peer="unconfined"
[  147.511922] audit: type=1400 audit(1474905579.954:285): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/sys/kernel/osrelease" pid=2879 comm="pkill" requested_mask="r" 
denied_mask="r" fsuid=998 ouid=0
[  147.512279] audit: type=1400 audit(1474905579.958:286): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cmdline" pid=2879 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.512303] audit: type=1400 audit(1474905579.958:287): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/2/cmdline" pid=2879 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.512322] audit: type=1400 audit(1474905579.958:288): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/3/cmdline" pid=2879 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.512340] audit: type=1400 audit(1474905579.958:289): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/4/cmdline" pid=2879 comm="pkill" requested_mask="r" denied_mask="r" 
fsuid=998 ouid=0
[  147.512356] audit: type=1400 audit(1474905579.958:290): apparmor="DENIED" 
operation="open" 

[Bug 1627304] Re: User locking problems - guest login crashing

[Iain Lane]

(The security team will look soon)

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  User locking problems - guest login crashing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627304] Re: User locking problems - guest login crashing

[Tyler Hicks]

Hi - are there any AppArmor denials in the syslog? To check, you can
trigger this bug and then look in /var/log/syslog for lines that contain
'apparmor="DENIED"'.  Thanks!

** Changed in: apparmor (Ubuntu)
   Importance: Critical => Undecided

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

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

Title:
  User locking problems - guest login crashing

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1101986] Re: gvfsd-mtp crashed with SIGSEGV in on_uevent()

[Apport retracing service]

** Tags added: yakkety

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627727] Re: gvfsd-mtp crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1101986
   gvfsd-mtp crashed with SIGSEGV in on_uevent()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627641] Re: Backport netplan to xenial

[Martin Pitt]

We need to backport a networkd fix:
https://github.com/systemd/systemd/commit/6fc2549711 . This will clean
up old addresses from interfaces when restarting networkd, so that
changed netplan configuration will actually reflect reality.

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

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

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

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  Backport netplan to xenial

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1626627] [NEW] FFe: Build e-d-s with libphonenumber support

[Iain Lane]

On Thu, Sep 22, 2016 at 03:52:51PM -, Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug by Jeremy Bicha (jbicha):
> 
> Debian builds evolution-data-server with libphonenumber support. Ubuntu
> doesn't because libphonenumber was in main. Now that libphonenumber is
> approved to be in main ( bug 1618178 ), I am requesting permission to
> build evolution-data-server with libphonenumber.

Yes, that's a good idea. Please do.

 status confirmed

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


** Changed in: evolution-data-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  FFe: Build e-d-s with libphonenumber support

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1614050] Re: Window depth order messed up

[Alberts Muktupāvels]

I hope that finally we can close this bug. :) Please test 
1:3.18.7-0ubuntu0.1ppa1 version from my PPA:
https://launchpad.net/~albertsmuktupavels/+archive/ubuntu/metacity-3-18

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

Title:
  Window depth order messed up

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1365296] Re: No 'recent' files shown until a file is opened (due to gmenumodel changes)

[Theodore Vasiloudis]

> This is not an issue in 16.04 as evince opens to a populated recent
documents screen

I disagree with this, one of the main points of the feature is to open
files while you are reading other ones.

This is an important user facing feature and I can't see why it's listed
a 'low' priority.

We've waited 2 years for an LTS upgrade from 14.04 to 16.04 for evince,
and it seems like we'll have to wait two more for a basic feature.

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

Title:
  No 'recent' files shown until a file is opened (due to gmenumodel
  changes)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1535575] Re: evince recent menu is empty

[Theodore Vasiloudis]

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

** This bug has been marked a duplicate of bug 1365296
   No 'recent' files shown until a file is opened (due to gmenumodel changes)

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

Title:
  evince recent menu is empty

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627637] [NEW] bad alloc on large (but not too large) image

[Jeff Abrahamson]

Public bug reported:

For this example, I've created an entirely white png (attached to the
bug report) with size 2400 x 36000.  I saved it at compression level 9
(or whatever gimp means by that) and in 8-bit RGB.  I would expect eog
to be able to display this because 2400 * 36000 * 4 colours is 330 MB,
which is vastly less than the available RAM on my machine.  While X
represents window dimensions with 16 bit values, which may perhaps be
signed (I didn't check my host's type definitions), I don't expect eog
to allocate a pixel-to-pixel window for the image.  My screen's size is
ample.

This arose because of a real image of the same dimensions, but which I
can't attach here.  The behaviour is the same.


jeff@starshine:data_2016-09-01 $ eog /tmp/2400x36000.png 

** (eog:26198): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-3UXmMLd2Wv: Connection refused

(eog:26198): Gdk-ERROR **: The program 'eog' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 415 error_code 11 request_code 130 (MIT-SHM) minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)
133, jeff@starshine:data_2016-09-01 $ ubuntu-bug eog

** (apport-gtk:27057): WARNING **: Couldn't connect to accessibility bus: 
Failed to connect to socket /tmp/dbus-3UXmMLd2Wv: Connection refused
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without 
specifying a version first. Use gi.require_version('Wnck', '3.0') before import 
to ensure that the right version gets loaded.
  from gi.repository import GLib, Wnck, GdkX11, Gdk
jeff@starshine:data_2016-09-01 $

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: eog 3.18.2-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: i3
Date: Mon Sep 26 10:24:34 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-12-17 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: eog
UpgradeStatus: Upgraded to xenial on 2016-05-15 (133 days ago)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "Opening this image with eog results in a bad allocation 
error."
   
https://bugs.launchpad.net/bugs/1627637/+attachment/4748707/+files/2400x36000.png

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

Title:
  bad alloc on large (but not too large) image

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1584280] Re: Using menu causes nautilus to freeze the desktop

[Erik Moldtmann]

Have this bug also on Ubuntu-Gnome 16.04 with Nautilus 3.14.3.

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

** No longer affects: nautilus (Ubuntu)

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

Title:
  Using menu causes nautilus to freeze the desktop

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1609009] Re: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)

[Bug Watch Updater]

** Changed in: vte
   Status: Confirmed => Won't Fix

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

Title:
  gnome-terminal should allow the disabling of text wrapping (so that
  there is a scroll bar at the bottom instead)

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1627612] [NEW] systemctl restart xxx* does not restart inactive services

[Jake Yip]

Public bug reported:

Man pages of systemctl indicates that the start, restart, status takes
in [PATTERN], which accepts wildcard.

However, for an inactive service, it does not work UNLESS --all is
provided, which does not make sense for a command like restart. If one
wants to restart only if service is active, there is the try-restart
command.

To replicate

1. Stop a service. `systemctl stop sysstat.service`
2. Restart with wildcard. `systemctl restart sysstat*`
3. Check service status. It should still be inactive.
4. Restart with --all wildcard. `systemctl restart --all sysstat*`
5. Check again, service should have been started.

More logs below

root@notifications-m:~# systemctl status sysstat.service 
● sysstat.service - LSB: Start/stop sysstat's sadc
   Loaded: loaded (/etc/init.d/sysstat; bad; vendor preset: enabled)
   Active: active (exited) since Mon 2016-09-26 16:22:02 AEST; 48min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 3607 ExecStop=/etc/init.d/sysstat stop (code=exited, 
status=0/SUCCESS)
  Process: 3809 ExecStart=/etc/init.d/sysstat start (code=exited, 
status=0/SUCCESS)
Tasks: 0
   Memory: 0B
  CPU: 0

Sep 26 16:22:02 notifications-m systemd[1]: Starting LSB: Start/stop sysstat's 
sadc...
Sep 26 16:22:02 notifications-m systemd[1]: Started LSB: Start/stop sysstat's 
sadc.
root@notifications-m:~# systemctl stop sysstat.service 
root@notifications-m:~# systemctl status sysstat.service 
● sysstat.service - LSB: Start/stop sysstat's sadc
   Loaded: loaded (/etc/init.d/sysstat; bad; vendor preset: enabled)
   Active: inactive (dead) since Mon 2016-09-26 17:10:16 AEST; 1s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 8228 ExecStop=/etc/init.d/sysstat stop (code=exited, 
status=0/SUCCESS)
  Process: 3809 ExecStart=/etc/init.d/sysstat start (code=exited, 
status=0/SUCCESS)

Sep 26 16:22:02 notifications-m systemd[1]: Starting LSB: Start/stop sysstat's 
sadc...
Sep 26 16:22:02 notifications-m systemd[1]: Started LSB: Start/stop sysstat's 
sadc.
Sep 26 17:10:16 notifications-m systemd[1]: Stopping LSB: Start/stop sysstat's 
sadc...
Sep 26 17:10:16 notifications-m systemd[1]: Stopped LSB: Start/stop sysstat's 
sadc.
(reverse-i-search)`restar': systemctl ^Cstart --all 
ceilometer-agent-notification*
root@notifications-m:~# systemctl restart sysstat*
root@notifications-m:~# systemctl status sysstat.service 
● sysstat.service - LSB: Start/stop sysstat's sadc
   Loaded: loaded (/etc/init.d/sysstat; bad; vendor preset: enabled)
   Active: inactive (dead) since Mon 2016-09-26 17:10:16 AEST; 16s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 8228 ExecStop=/etc/init.d/sysstat stop (code=exited, 
status=0/SUCCESS)
  Process: 3809 ExecStart=/etc/init.d/sysstat start (code=exited, 
status=0/SUCCESS)

Sep 26 16:22:02 notifications-m systemd[1]: Starting LSB: Start/stop sysstat's 
sadc...
Sep 26 16:22:02 notifications-m systemd[1]: Started LSB: Start/stop sysstat's 
sadc.
Sep 26 17:10:16 notifications-m systemd[1]: Stopping LSB: Start/stop sysstat's 
sadc...
Sep 26 17:10:16 notifications-m systemd[1]: Stopped LSB: Start/stop sysstat's 
sadc.
root@notifications-m:~# systemctl restart --all sysstat*
root@notifications-m:~# systemctl status sysstat.service 
● sysstat.service - LSB: Start/stop sysstat's sadc
   Loaded: loaded (/etc/init.d/sysstat; bad; vendor preset: enabled)
   Active: active (exited) since Mon 2016-09-26 17:10:39 AEST; 1s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 8228 ExecStop=/etc/init.d/sysstat stop (code=exited, 
status=0/SUCCESS)
  Process: 8250 ExecStart=/etc/init.d/sysstat start (code=exited, 
status=0/SUCCESS)

Sep 26 17:10:39 notifications-m systemd[1]: Starting LSB: Start/stop sysstat's 
sadc...
Sep 26 17:10:39 notifications-m systemd[1]: Started LSB: Start/stop sysstat's 
sadc.

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

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

Title:
  systemctl restart xxx* does not restart inactive services

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs