[Bug 1200950] Re: gnome-keyring-daemon crashed with SIGABRT in _g_log_abort()

[Daniel]

Hey guys, I got exactly the same error message.. :(
Are there any solutions or workaround for the bug?


OS: Xubuntu 16.10 (amd64)
Kernel: Ubuntu 4.8.0-46.49-generic 4.8.17
Keyring-Version: gnome-keyring 3.20.0-2ubuntu4

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

Title:
  gnome-keyring-daemon crashed with SIGABRT in _g_log_abort()

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

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

[Bug 1689702] [NEW] Cannot create a disk partition image on a mounted external usb hard drive

[Steve Singer]

Public bug reported:

Package:
gnome-disk-utility-3.10.0_1ubuntu3_i386

OS:
LiveDVD Ubuntu 14.04.1 ubuntu 3.13.0-32 i686

Hardware:
Dell Dimension 4550 4mB Pentium 4
Seagate Backup Plus 1TB


I tried to create a disk image of the primary disk's boot partition on an 
external USB backup drive.


>From a terminal window:

ubuntu@ubuntu:~$ gnome-disks
   or
ubuntu@ubuntu:~$ sudo gnome-disks


The partition to be imaged was not mounted.
The permissions for the destination directory were 'drwxrwxrwxt' [1777]

When I tried to create the image, the error message:

   "Error allocating space for disk image file: Invalid argument (g-io-
error-quark, 13)"

appeared.

In the terminal window from which gnome-disks was invoked, there was a
repeating error message until the error dialog was dismissed:

   "(gnome-disks:6765): GLib-GIO-CRITICAL **: g_dbus_interface_get_object:
 assertion 'G_IS_DBUS_INTERFACE (interface_)' failed"

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

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

Title:
  Cannot create a disk partition image on a mounted external usb hard
  drive

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

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

[Bug 1685178] Re: /usr/bin/gnome-software:11:as_format_get_kind:as_store_add_app:as_store_load_yaml_file:as_store_from_file_internal:as_store_watch_source_added

[Launchpad Bug Tracker]

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

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

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

Title:
  /usr/bin/gnome-
  
software:11:as_format_get_kind:as_store_add_app:as_store_load_yaml_file:as_store_from_file_internal:as_store_watch_source_added

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

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

[Bug 1689678] Re: Update gnome-calendar to 3.24.2

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-calendar - 3.24.1-0ubuntu2

---
gnome-calendar (3.24.1-0ubuntu2) artful; urgency=medium

  * New upstream release (LP: #1689678)
- Fix crash in active-date logic (LP: #1688414)

 -- Jeremy Bicha   Tue, 09 May 2017 19:24:41 -0400

** Changed in: gnome-calendar (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-calendar to 3.24.2

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

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

[Bug 1688414] Re: /usr/bin/gnome-calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-calendar - 3.24.1-0ubuntu2

---
gnome-calendar (3.24.1-0ubuntu2) artful; urgency=medium

  * New upstream release (LP: #1689678)
- Fix crash in active-date logic (LP: #1688414)

 -- Jeremy Bicha   Tue, 09 May 2017 19:24:41 -0400

** Changed in: gnome-calendar (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

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

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

[Bug 1686077] Re: Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too

[Jeremy Bicha]

** Description changed:

  Impact
  ==
  This bugfix enabled gnome-settings-daemon's multimedia key support to work 
according to what the API has said for years (in addition to the way it's been 
commonly used).
  
  https://git.gnome.org/browse/gnome-settings-
  daemon/commit/?h=gnome-3-24&id=42f75ed4cdc86498d6e02e511a1314b8916bd4aa
  
  https://mail.gnome.org/archives/desktop-devel-
  list/2017-April/msg00069.html
  
  The SRU justification is that newer versions of apps will be switching
  to the D-Bus name in the API documentation. If someone installs the
  newer version from a PPA or a Flatpak or Snap, the multimedia key
  support should continue working.
  
  Test Case
  =
- ?
+ Install this update on Ubuntu GNOME.
+ Reboot
+ Install d-feet then run d-feet
+ Switch to the session tab.
+ Type 'settings' into the search box.'
+ In the list of results there should be both org.gnome.SettingsDaemon and 
org.gnome.SettingsDaemon.MediaKeys with cmd: 
/usr/lib/gnome-settings-daemon/gsd-media-keys
  
  Regression Potential
  
  This should just make gnome(unity)-settings-daemon own both the commonly used 
D-Bus name and the one actually defined in the API docs.

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

Title:
  Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too

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

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

[Bug 1688414] Re: /usr/bin/gnome-calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

[Jeremy Bicha]

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

** Changed in: gnome-calendar (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: gnome-calendar (Ubuntu Zesty)
   Status: New => Triaged

** Description changed:

+ Impact
+ --
+ A crash has been reported in gnome-calendar 3.24.1.
+ 
+ Test Case
+ -
+ Check the errors site to see if this error has been reported in 3.24.2
+ 
+ Regression Potential
+ 
+ This particular fix is a one-character logic bug fix! But it's bundled with 
3.24.2 so see LP: #1689678 for more details about that.
+ 
+ Original Report
+ ---
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
3.24.1-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/6d4cc768a146ab0f6ae401d9cb62adf1efb89b2c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

Title:
  /usr/bin/gnome-
  
calendar:11:get_start_of_week:update_unchanged_events:gcal_week_header_set_date:gcal_week_view_set_date:update_active_date

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

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

[Bug 1689678] [NEW] Update gnome-calendar to 3.24.2

[Jeremy Bicha]

Public bug reported:

Impact
--
This is a new bugfix release in the stable 3.24 series.

https://git.gnome.org/browse/gnome-calendar/tree/NEWS?h=gnome-3-24
https://git.gnome.org/browse/gnome-calendar/log?h=gnome-3-24

This should fix crash bug LP: #1688414

gnome-calendar is in the default Ubuntu, Ubuntu Budgie, and Ubuntu GNOME
installs.

Test Case
-
Install the update.

Run the app and make sure it works without crashing.

Regression Potential

This is a smaller update than 3.24.1 and the commits sound sensible. All GNOME 
3.24 distros will be packaging this update.

Other Info
--
Waiting to upload until the 3.24.1 SRU is promoted to zesty-updates.

** Affects: gnome-calendar (Ubuntu)
 Importance: Medium
 Status: Fix Committed

** Affects: gnome-calendar (Ubuntu Zesty)
 Importance: Medium
 Status: Triaged


** Tags: upgrade-software-version zesty

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

** Changed in: gnome-calendar (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: gnome-calendar (Ubuntu Zesty)
   Status: New => Triaged

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

Title:
  Update gnome-calendar to 3.24.2

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

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

[Bug 1689660] [NEW] systemd-fsckd busy spawning fsck

[Olaf Dietsche]

Public bug reported:

I rebooted my laptop after a crash.

Fsck couldn't repair the /var partition, so I was greeted with "Welcome
to Emergency!" and the request to look at `journalctl -xb`.

After logging in, and journalctl telling me about the broken /var
partition, I tried

fsck /dev/mapper/vg0-var

which immediately returned with a message stating that /dev/mapper/vg0-var is 
busy.
Looking at the processes with `ps aux | grep fsck` gave

- systemd-fsckd
- /sbin/fsck /dev/mapper/vg0-var
- fsck.ext2 /dev/mapper/vg0-var

Trying to kill `fsck.ext2` or `fsck` was futile, because `fsck` was
dying and restarting faster, than I could look at the process list.
Killing `systemd-fsckd` finally ended the busy loop.

But still, I couldn't check my /var partition, because now systemd has
mounted my /var partition, even though it told me before, it was in need
of repair.

After unmounting /var, I could finally do the much needed `fsck
/dev/mapper/vg0-var`.

---

I would expect

1. systemd-fsck stop restarting fsck, when it was aware, that it must be 
checked manually
2. systemd *not* mount an unchecked file system, especially when systemd-fsckd 
stopped with an error or was killed

---

Description:Ubuntu 16.04 LTS
Release:16.04

---

systemd:
  Installed: 229-4ubuntu10
  Candidate: 229-4ubuntu16
  Version table:
 229-4ubuntu16 500
500 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 *** 229-4ubuntu10 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

---

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

Title:
  systemd-fsckd busy spawning fsck

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

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

[Bug 1689344] Re: print of __glib_assert_msg not returning a message

[Brian Murray]

I tested the yakkety core file and binary with a xenial version of gdb
and didn't still received the cannot access memory error, so I don't
think its a gdb bug.

** Package changed: gdb (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  print of __glib_assert_msg not returning a message

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

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

[Bug 1689344] [NEW] print of __glib_assert_msg not returning a message

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

apport's test test_add_gdb_info_abort_glib has been failing for a bit,
since zesty(?), now. Digging into this matter I discovered that using
gdb to "print __glib_assert_msg" is resulting in different behavior.

With the generated binary, it used to return the following:

$2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)"

However, now I am seeing:

(gdb) print __glib_assert_msg 
$1 = 1332592064
(gdb) print (char*) __glib_assert_msg 
$2 = 0x4f6dbdc0 

This seems to be a regression in gdb itself, I've added an apport task
though to track the disabling of the autopkgtest which utilizes this
command.

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
print of __glib_assert_msg not returning a message
https://bugs.launchpad.net/bugs/1689344
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to glib2.0 in Ubuntu.

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

[Bug 1683445] Re: E6430 brightness control not working

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-settings-daemon -
3.24.2-0ubuntu1

---
gnome-settings-daemon (3.24.2-0ubuntu1) artful; urgency=medium

  * New upstream release (LP: #1689610)
- Fix brightness control in some dual-GPU computers (LP: #1683445)
- Disable GNOME's rfkill handling which basically reverts this to
  how it worked or didn't in 16.04 LTS. Hopefully, a more thorough
  rework will be done in time for 3.26.
  * Drop patches applied in new release:
- git_fix-gdm-plugins.patch
- media-keys-Fix-mmkeys-D-Bus-API-to-match-API-docs.patch

 -- Jeremy Bicha   Tue, 09 May 2017 13:17:44 -0400

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  E6430 brightness control not working

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

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

[Bug 1689555] Re: Scrolling + "Terminal bell" crashes pulseaudio

[Egmont Koblinger]

I have seen frequent pulseaudio crashes in 17.04, see bug #1675892.
(Maybe this one is a dupe of that.)

gnome-terminal causing pulseaudio crash most definitely does not belong
to gnome-terminal but to pulseaudio.

** Package changed: gnome-terminal (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  Scrolling + "Terminal bell" crashes pulseaudio

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

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

[Bug 1689610] Re: Update gnome-settings-daemon to 3.24.2

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-settings-daemon -
3.24.2-0ubuntu1

---
gnome-settings-daemon (3.24.2-0ubuntu1) artful; urgency=medium

  * New upstream release (LP: #1689610)
- Fix brightness control in some dual-GPU computers (LP: #1683445)
- Disable GNOME's rfkill handling which basically reverts this to
  how it worked or didn't in 16.04 LTS. Hopefully, a more thorough
  rework will be done in time for 3.26.
  * Drop patches applied in new release:
- git_fix-gdm-plugins.patch
- media-keys-Fix-mmkeys-D-Bus-API-to-match-API-docs.patch

 -- Jeremy Bicha   Tue, 09 May 2017 13:17:44 -0400

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update gnome-settings-daemon to 3.24.2

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

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

[Bug 1681910] Re: gnome-terminal constantly logs "Unable to load blank_cursor from the cursor theme" under gnome/wayland

[Jamie Strandboge]

This bug is *super* annoying. Here is a workaround to make rsyslog
discard this messages:

Create /etc/rsyslog.d/49-lp1681910.conf with:
# workaround LP: #1681910
:msg,contains,"Unable to load blank_cursor from the cursor theme" ~
& stop

Restart rsyslog: sudo service rsyslog restart

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

Title:
  gnome-terminal constantly logs "Unable to load blank_cursor from the
  cursor theme" under gnome/wayland

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

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

[Bug 1685035] Re: GDM login doesn't scale on Hi-DPI display

[Jeremy Bicha]

** Description changed:

- Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800,
- login screen is too tiny to read. GDM login screen doesn't reflect
- changes to org.gnome.desktop.interface scaling-factor or text-scaling-
- factor.
+ Impact
+ --
+ GDM's login screen was being start with no gnome-settings-daemons plugins. In 
particular, this broke Hi-DPI support in the login screen
+ 
+ Test Case
+ -
+ - Install the update on a computer running Ubuntu GNOME 17.04 with a Hi-DPI 
display (ideally one that worked well with Ubuntu GNOME 16.10).
+ - Restart your computer.
+ - The login screen should automatically show at the right scale.
+ 
+ Regression Potential
+ 
+ See the other 3.24.2 bugs but this commit is a simple typo fix.
+ 
+ Original Bug Report
+ ---
+ Ubuntu gnome 17.04, gnome 3.24. On high resolution display, 3200x1800, login 
screen is too tiny to read. GDM login screen doesn't reflect changes to 
org.gnome.desktop.interface scaling-factor or text-scaling-factor.
  
  Eg:
  xhost +SI:localuser:gdm
  sudo su gdm -s /bin/bash
  gsettings set org.gnome.desktop.interface scaling-factor 2
  gsettings set org.gnome.desktop.interface text-scaling-factor 2.0
  
  no effect.
  
  Creating a gdm user under /etc/dconf and running dconf update has no
  effect either. Scaling-factor seems to scale the mouse cursor, but
  nothing else.

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  GDM login doesn't scale on Hi-DPI display

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

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

[Bug 1683445] Re: E6430 brightness control not working

[Jeremy Bicha]

** Description changed:

- The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open
- Source Nouveau driver shows the brightness slider moving but does not
- affect the brightness.
+ Impact
+ --
+ It looks like GNOME's brightness control simply used the first backlight 
device it saw instead of one currently in use. This meant that the brightness 
control would not work on some computers with multiple GPUs.
+ 
+ Test Case
+ -
+ From Ubuntu GNOME 17.04 on a dual-GPU computer, install the update.
+ Restart.
+ Does the brightness control now work correctly?
+ 
+ Regression Potential
+ 
+ This looks like a minimal fix for this issue. It was accepted as part of 
gnome-settings-daemon 3.24.2 which all GNOME 3.24 distros  will be upgrading to.
+ 
+ Original Bug Report
+ ---
+ The Dell E6430 with Nvidia Optimus enables in BIOS, using the Open Source 
Nouveau driver shows the brightness slider moving but does not affect the 
brightness.
  
  When using the kernel boot option acpi_backlight=vendor , the brightness
  control works.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 2081 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Mon Apr 17 20:00:56 2017
  HibernationDevice: RESUME=UUID=66528b53-0f42-4043-9ff8-da8f86036be6
  InstallationDate: Installed on 2017-04-10 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Latitude E6430
  ProcFB:
-  0 nouveaufb
-  1 inteldrmfb
+  0 nouveaufb
+  1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=4e08c33d-f8cf-4159-a559-a0463d67b96c ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.10.0-19-generic N/A
-  linux-backports-modules-4.10.0-19-generic  N/A
-  linux-firmware 1.164
+  linux-restricted-modules-4.10.0-19-generic N/A
+  linux-backports-modules-4.10.0-19-generic  N/A
+  linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0H3MT5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd01/18/2016:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6430
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  E6430 brightness control not working

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

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

[Bug 1686077] Re: Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too

[Jeremy Bicha]

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too

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

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

[Bug 1689610] Re: Update gnome-settings-daemon to 3.24.2

[Jeremy Bicha]

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: Triaged => In Progress

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

Title:
  Update gnome-settings-daemon to 3.24.2

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

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

[Bug 1689610] Re: Update gnome-settings-daemon to 3.24.2

[Jeremy Bicha]

** Also affects: gnome-settings-daemon (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Importance: Undecided => Medium

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

Title:
  Update gnome-settings-daemon to 3.24.2

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

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

[Bug 1683445] Re: E6430 brightness control not working

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu

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

Title:
  E6430 brightness control not working

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

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

[Bug 1689610] Re: Update gnome-settings-daemon to 3.24.2

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu

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

Title:
  Update gnome-settings-daemon to 3.24.2

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

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

[Bug 1689610] [NEW] Update gnome-settings-daemon to 3.24.2

[Jeremy Bicha]

Public bug reported:

Impact
--
gnome-settings-daemon 3.24.2 is a bugfix release in the stable 3.24 series.

https://git.gnome.org/browse/gnome-settings-daemon/log?h=gnome-3-24
https://git.gnome.org/browse/gnome-settings-daemon/tree/NEWS?h=gnome-3-24

gnome-settings-daemon itself is used by Ubuntu Budgie and Ubuntu GNOME.
The schemas are also used by Ubuntu, Ubuntu Kylin and Ubuntu MATE. And Ubuntu 
Touch.

This also fixes Hi-DPI in GDM (LP: #1685035), the brightness control in
some dual-GPU computers (LP: #1683445), and adds a D-Bus API to match
the mediakeys documentation (LP: #1686077)

Test Case
-
After installing the update, reboot and log into GNOME

Regression Potential

There was a minimal fix for rfkill handling (to revert GNOME's behavior back to 
how it worked in Ubuntu 16.04 LTS), but because this ends up causing 
regressions for some other people, I have reverted this commit since it's 
better not to introduce a new bug into a stable release. See 
https://bugzilla.gnome.org/760517 if you want more details.

The other changes look like minimal bugfixes. Schemas shouldn't be
affected in this update.

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Medium
 Status: Fix Committed


** Tags: upgrade-software-version zesty

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

Title:
  Update gnome-settings-daemon to 3.24.2

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

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

[Bug 1683445] Re: E6430 brightness control not working

[Jeremy Bicha]

I am closing the 'linux' portion of this bug because this apparently can
be fixed in gnome-settings-daemon and unity-settings-daemon.

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

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Fix Committed

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity-settings-daemon (Ubuntu)
   Importance: Undecided => Medium

** Changed in: unity-settings-daemon (Ubuntu)
   Status: New => Triaged

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: gnome-settings-daemon (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: unity-settings-daemon (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: New => Triaged

** No longer affects: linux (Ubuntu Zesty)

** Changed in: unity-settings-daemon (Ubuntu Zesty)
   Status: New => Triaged

** Changed in: unity-settings-daemon (Ubuntu Zesty)
   Importance: Undecided => Medium

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

Title:
  E6430 brightness control not working

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

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

[Bug 1576341] Re: systemd in degraded state on startup in LXD containers

[Nish Aravamudan]

lvm2 fix is in 2.02.168-2ubuntu1 in artful.

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

** Changed in: open-iscsi (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  systemd in degraded state on startup in LXD containers

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

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

[Bug 1689565] Re: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1689565/+subscriptions

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

[Bug 1689410] Re: nplan with networkd + resolvconf without resolved, results in no DNS resolution

[Dimitri John Ledkov]

 slangasek: xnox: re DNS for netplan/networkd ;  on xenial , there is 
a unit watch placed on /run/systemd/netif/state which will trigger a call to 
systemd-network-resolvconf-update.service, which exec's some shell code to 
extract any DNS values from networkd state and the respective interfaces and 
invokes resolvconf program ;  
 rharper, hm, that's what i was thinking should be happening I did 
not notice such watch. Where is it exactly, and does one have to activate it 
manually?
* xnox commented to the same effect on the bug i filed, that it seemed to me 
that networkd <-> resolvconf integration was non existant.
 you do not have to activate it manually;  
/lib/systemd/system/resovlconf.service.wants/systemd-networkd-resolvconf-update.path
 is the trigger for 
/lib/systemd/system/systemd-networkd-resolconf-update.service 
 ./resolvconf.service.wants/systemd-networkd-resolvconf-update.path
 xnox: you probably want to add a symlink to 
/lib/systemd/system/systemd-networkd-wait-online.service in 
/etc/systemd/system/network-online.target.wants  
 which bug?
 https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1689410
 Bug #1689410: nplan with networkd + resolvconf without resolved, results 
in no DNS resolution
  

 30 seconds is a long time to get DNS settings right
 for some reason, my /run/systemd/netif/state had DNS, yet i did not have 
namespace resolution =(
 but i may have stopped resolvconf =(
 and hence ConditionPathExists=/run/resolvconf/enable-updates was not 
satisfied.
 thus a bug in my image.
 I can look at the bug, but it doesn't take 30 seconds when things are 
configured properly or things like network via cloud-init early would fail to 
resolve the snappy store, etc; 
 yeah, things did fail to resolve snappy store, ubuntu ntp, etc.
 the bug is not very descriptive.
 right, I think if you add the systemd-networkd-wait-online link to 
the network-online.target.wants 
 that should ensure it runs at the right time.
 nplan does that out of the box.
 only if 1) you have yaml in /etc/netplan/
 cloud-init invokes netplan generate 
 but on first boot we are doing it half way during the boot (as 
cloud-init is running) thus it may not be part of the initial transaction.
 but since that's not called by a systemd-generator, it does not add 
the link 
  cloud-init generates yaml into /etc/netplan.
 (when i force network generator to netplan, as I have in my xenial 
image, when experimenting to use nplan by default for this cloud)
 it does create the yaml and call generate, but it's not sufficient to 
create the symlink IIRC due to the code in netplan which doesn't generate the 
symlinks in /run if it;s not invoked as a genartor 
 (via cloud.cfg.d)
 ah, fun.
 no 
 this was not fun in any sense of the words
 I've picked this apart too many times;  we've got the set of changes 
needed documented and staged for ubuntu-core 
 so i had symlinks in originally; then i removed them, because i noticed 
that nplan generates them; but did not realise that it's /sometimes/ generates, 
rather than always.
 so this isn't new ground
 but it's not landed in xenial for cloud-init proper due to not 
wanting to foist networkd onto xenial users at this time 
 (well, not new to me at least) 
 right.
 based on the above, i think i need to do a retest of my nplan based 
cloud image.

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

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

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

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

Title:
  nplan with networkd + resolvconf without resolved, results in no DNS
  resolution

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

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

[Bug 1689565] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Adam Al Haris]

Public bug reported:

Says that "usr" is full, though I should have space. I've fixed broken
packages but I can't install anything.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue May  9 18:21:21 2017
DpkgTerminalLog:
 Setting up shared-mime-info (1.5-2ubuntu0.1) ...
 I/O error : No space left on device
 Failed to write XML file; For permission problems, try rerunning as root
 dpkg: error processing package shared-mime-info (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-04-18 (21 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1689565/+subscriptions

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

[Bug 1685683] Re: Update evolution to 3.24.1

[Launchpad Bug Tracker]

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

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

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

Title:
  Update evolution to 3.24.1

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

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

[Bug 1685683] Re: Update evolution to 3.24.1

[Launchpad Bug Tracker]

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

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

Title:
  Update evolution to 3.24.1

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

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

[Bug 1685683] Re: Update evolution to 3.24.1

[Jeremy Bicha]

** Description changed:

  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.
  
  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages
  
  I made a few packaging changes we should review with Debian. e-d-s is
  looking good now, here's some Evolution remaining questions/issues:
  
  1. I dropped
  https://sources.debian.net/src/evolution/unstable/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not directly
  apply to cmake and it doesn't seem needed. The soname hasn't been bumped
  in 5 years. I had to have libevolution Breaks/Replaces evolution-dev
  since there are no .so symlinks any more.
  
  2. I disabled
  
https://sources.debian.net/src/evolution/unstable/debian/patches/02_nss_paths.patch/
  since it didn't seem to be needed.
  
- 3. Maybe related to #1 is that evolution now no longer has an automatic
- dependency on libevolution.
+ 3. Maybe related to #1 is that packages like evolution no longer have an
+ automatic dependency on libevolution.
  
- 4. Also lintian is complaining about rpaths. The rpath fix I used with
- e-d-s did not work for Evolution.
+ 4. Lintian is complaining about rpaths. The rpath fix I used with e-d-s
+ did not work for Evolution.

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

Title:
  Update evolution to 3.24.1

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

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

[Bug 1685683] Re: Update evolution to 3.24.1

[Jeremy Bicha]

** Description changed:

  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.
  
  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages
  
- I made a few packaging changes we should review with Debian.
+ I made a few packaging changes we should review with Debian. e-d-s is
+ looking good now, here's some Evolution remaining questions/issues:
  
- 1. I dropped https://sources.debian.net/src/evolution-data-
- server/unstable/debian/patches/01-noinst-libedbus-private.patch/ and
- added a libedbus-private0 package and had all the e-d-s libraries depend
- on it.
- 
- 2. I dropped
+ 1. I dropped
  https://sources.debian.net/src/evolution/unstable/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not directly
  apply to cmake and it doesn't seem needed. The soname hasn't been bumped
  in 5 years. I had to have libevolution Breaks/Replaces evolution-dev
  since there are no .so symlinks any more.
  
- 3. I disabled
+ 2. I disabled
  
https://sources.debian.net/src/evolution/unstable/debian/patches/02_nss_paths.patch/
  since it didn't seem to be needed.
  
- To Do
- =
- 4. Hook up the new installed-tests packages to be ran as autopkgtests
+ 3. Maybe related to #1 is that evolution now no longer has an automatic
+ dependency on libevolution.
+ 
+ 4. Also lintian is complaining about rpaths. The rpath fix I used with
+ e-d-s did not work for Evolution.

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

Title:
  Update evolution to 3.24.1

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

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

[Bug 1689555] [NEW] Scrolling + "Terminal bell" crashes pulseaudio

[Anders Trier Olesen]

Public bug reported:

If "Terminal bell" is enabled (in "Profile Preferences" > "General"),
and I scroll fast in the output of e.g less to cause the "alert sound"
to be played repeatably very fast, pulseaudio crashes.

>From /var/log/syslog:
May  9 15:05:13 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
May  9 15:05:15 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default sink
May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Unable to get default 
source
May  9 15:05:16 ubuntu-laptop unity-settings-[2940]: Failed to connect context: 
Connection refused
May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Failed to connect context: 
Connection refused
May  9 15:05:16 ubuntu-laptop unity-control-c[5557]: Unable to find stream for 
bar '(null)'
May  9 15:05:17 ubuntu-laptop indicator-sound[2948]: 
volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files
May  9 15:06:01 ubuntu-laptop indicator-sound[2948]: message repeated 22 times: 
[ volume-control-pulse.vala:735: unable to get pulse unix socket: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 
was not provided by any .service files]

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Tue May  9 14:58:51 2017
InstallationDate: Installed on 2017-05-01 (7 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Scrolling + "Terminal bell" crashes pulseaudio

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

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

[Bug 1689410] Re: nplan with networkd + resolvconf without resolved, results in no DNS resolution

[Dimitri John Ledkov]

I guess that a .path unit can be setup to parse the private
/run/systemd/netif/state file (or similar), which would then kick off
and feed the DNS entries to resolfconf.

** Also affects: resolvconf (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/1689410

Title:
  nplan with networkd + resolvconf without resolved, results in no DNS
  resolution

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

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

[Bug 1689239] Re: Headerbar used as toolbars in unity are missing proper css classes

[Bug Watch Updater]

** Changed in: gnome-software
   Status: In Progress => Fix Released

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

Title:
  Headerbar used as toolbars in unity are missing proper css classes

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

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

[Bug 1689528] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

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

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 #1688721, 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.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

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

[Bug 1689528] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Walter]

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

Public bug reported:

hello.

When I try to install google chrome on my ubuntu 17 PC, it fail to
install.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue May  9 03:51:17 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-09 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

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

[Bug 581618] Re: Restart session unexpected 10.04

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

Please upgrade to the latest version and re-test.

** Changed in: gnome-session (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/581618

Title:
  Restart session unexpected 10.04

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

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

[Bug 1679831] Re: pygobject FTBFS on all arches during zesty test rebuild

[Michael Hudson-Doyle]

This will end up blocking the enablement of python 3.6 as a supported
version. Any idea who might know how to fix this?

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

Title:
  pygobject FTBFS on all arches during zesty test rebuild

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

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