[Desktop-packages] [Bug 1359715] Re: Ghostscript runaway memory consumption during font search

[Vlad Orlov]

Marking as fixed according to the latest comments here

** Changed in: ghostscript (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Ghostscript runaway memory consumption during font search

Status in ghostscript package in Ubuntu:
  Fix Released

Bug description:
  Linux Mint 17 (Qiana), Cinnamon 64-bit, kernel 3.13.0-24-generic #47-Ubuntu 
SMP x86_64 x86_64 x86_64 GNU/Linux
  Ghostscript version 9.10

  When Ghostscript searches for a specified font, if that font is not
  found in the Fontmap file, memory consumption shoots up, the system
  starts swapping and hangs.

  Tested on system (see above) with ~ 2GB memory.

  A simple way to reproduce, is to use the following procedure to
  attempt to display a font:

  1) Invoke ghostscript on 'prfont.ps'

  $ gs /usr/share/ghostscript/9.10/lib/prfont.ps
  GPL Ghostscript 9.10 (2013-08-30)
  Copyright (C) 2013 Artifex Software, Inc.  All rights reserved.
  This software comes with NO WARRANTY: see the file PUBLIC for details.
  Loading NimbusRomNo9L-Regu font from 
/usr/share/fonts/type1/gsfonts/n021003l.pfb... 3896292 2355421 3853784 2540955 
1 done.
  GS>

  2) At Ghostscript prompt, specify a random fontname - which we know
  does not exist - to 'DoFont':

  GS>/Somefont DoFont
  Can't find (or can't open) font file 
/usr/share/ghostscript/9.10/Resource/Font/Somefont.
  Can't find (or can't open) font file Somefont.
  Querying operating system for font files...

  Result: memory usage maxes out, system swaps and hangs.

  I expected Ghostscript to conclude the font search (without
  exhausating system resources!) and to report failure to locate the
  specified font.

  This problem always occurs, and affects any other program which
  invokes ghostscript and triggers a font search.

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


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

[Desktop-packages] [Bug 1560722] Re: repositórios sumiram

[Vlad Orlov]

** Changed in: glib2.0 (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/1560722

Title:
  repositórios sumiram

Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  repositórios sumiram não sei o que fiz de errado.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: mate-notification-daemon 1.12.1-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 22 19:41:03 2016
  ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
  InstallationDate: Installed on 2016-03-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
  Signal: 5
  SourcePackage: mate-notification-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
   ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
  Title: mate-notification-daemon crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


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

[Desktop-packages] [Bug 1360225] Re: gnome-mahjongg has outdated website link in the package description in Mint 17/Ubuntu 14.04

[Vlad Orlov]

Fixed in version 1:3.14.1-1, according to git:

https://salsa.debian.org/gnome-team/gnome-
mahjongg/-/commit/04d2e96e8894b340e47b72e9f4bd29c0e2a32b72

** Changed in: gnome-mahjongg (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  gnome-mahjongg has outdated website link in the package description in
  Mint 17/Ubuntu 14.04

Status in gnome-mahjongg package in Ubuntu:
  Fix Released

Bug description:
  The Software Manager (mintInstall 7.5.7) shows an outdated link for the 
gnome-mahjongg package. 
  The link shown is 

  https://live.gnome.org/Mahjongg

  but it should be

  https://wiki.gnome.org/Apps/Mahjongg

  Not the end of the world, I know, but still a bug.

  My system: Mint 17 64-bit XFCE, dist-upgraded to current.

  Cheers
  --Knut

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

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

[Desktop-packages] [Bug 1549653] Re: Disks utility doesn't remove previous record in /etc/fstab

[Vlad Orlov]

** Bug watch added: gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #43
   https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/43

** Changed in: gnome-disk-utility
   Importance: Medium => Unknown

** Changed in: gnome-disk-utility
   Status: Expired => Unknown

** Changed in: gnome-disk-utility
 Remote watch: GNOME Bug Tracker #762718 => 
gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues #43

** Bug watch removed: GNOME Bug Tracker #762718
   https://gitlab.gnome.org/762718

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

Title:
  Disks utility doesn't remove previous record in /etc/fstab

Status in GNOME Disks:
  Unknown
Status in gnome-disk-utility package in Ubuntu:
  Triaged

Bug description:
  How to reproduce:
  1. delete an NTFS partition on secondary disk (rewrite with zeroes).
  2. put there EXT4 partition instead.
  3. reboot computer
  => ubuntu doesn't boot, allows only single-user mode.

  By checking system log, I found out system was trying to mount the old
  NTFS partition and hanged on it, even though that is not at all a
  necessary partition. Then I checked /etc/fstab and found out the GUI
  tool did NOT remove the original record, when it deleted the partition
  on the drive.

  By commenting it out I was able to get into the GUI again.

  Ubuntu 15.10
  pkg: gnome-disk-utility 3.16.2-0ubuntu2 0

  The original line, that was left behind:
  UUID=52D09468D09453D7 /backup ntfsdefaults,umask=007,gid=46 0 
  0

  The new line that the tool created:
  /dev/disk/by-uuid/414e95a1-fb40-45a6-9b90-487a45337fdd /extdata auto 
nosuid,nodev,nofail,x-gvfs-show 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-disk-utility 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 25 08:34:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-24 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1586716] Re: yelp crashed with SIGSEGV in g_str_equal()

[Vlad Orlov]

** Bug watch added: gitlab.gnome.org/GNOME/yelp/-/issues #116
   https://gitlab.gnome.org/GNOME/yelp/-/issues/116

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

** Changed in: yelp
   Status: Expired => Unknown

** Changed in: yelp
 Remote watch: GNOME Bug Tracker #778553 => 
gitlab.gnome.org/GNOME/yelp/-/issues #116

** Bug watch removed: GNOME Bug Tracker #778553
   https://gitlab.gnome.org/778553

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

Title:
  yelp crashed with SIGSEGV in g_str_equal()

Status in Ubuntu GNOME:
  Triaged
Status in Yelp:
  Unknown
Status in yelp package in Ubuntu:
  Triaged

Bug description:
  No idea, just saw the error.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: yelp 3.20.1-1ubuntu1~xenial1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  Uname: Linux 4.6.0-040600-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Sun May 29 03:03:21 2016
  ExecutablePath: /usr/bin/yelp
  InstallationDate: Installed on 2014-02-04 (844 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203)
  ProcCmdline: yelp file:///usr/share/doc/pspp/pspp.xml#ONEWAY
  SegvAnalysis:
   Segfault happened at: 0x7f497638eb5a <__strcmp_sse2_unaligned+26>:   movdqu 
(%rdi),%xmm1
   PC (0x7f497638eb5a) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: yelp
  StacktraceTop:
   g_str_equal () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libyelp.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libyelp.so.0
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: yelp crashed with SIGSEGV in g_str_equal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo 
vboxusers
  XsessionErrors:
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to create 
device: failed to obtain org.freedesktop.color-manager.create-device auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to obtain 
org.freedesktop.color-manager.create-profile auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: failed to obtain 
org.freedesktop.color-manager.create-profile auth
   (cinnamon-settings-daemon:3255): color-plugin-WARNING **: could not find 
device: property match 'XRANDR_name'='eDP1' does not exist

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

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

[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

Sorry, completely forgot about it... :-/

So bug 1828639 is now fixed. I guess no need to fix gconf triggers now?

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1846890] Re: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonload

[Vlad Orlov]

** Attachment added: "Debdiff to fix Python 2 loader name"
   
https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+attachment/5294753/+files/libpeas-debdiff-eoan

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

Title:
  Pluma: unable to enable plugins External tools, Python Console, Quick
  Open, Snippets) because of missed /usr/lib/x86_64-linux-
  gnu/libpeas-1.0/loaders/libpythonloader.so

Status in libpeas package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.10
  2. Launch Pluma
  3. Go to Edit -> Preferences, switch to Plugins tab
  4. Try enable all plugins by checking their checkmarks

  Expected results:
  * all plugins are enabled without errors or warnings;

  Actual results:
  * plugin(s) are not enabled, show the following errors in `pluma`'s terminal:

  ```
  $ pluma

  (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module
  'pythonloader': /usr/lib/x86_64-linux-
  gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object
  file: No such file or directory

  (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 
'python'
  ```

  Note: in previous releases the `libpythonloader.so` was located in
  libpeas-1.0-python2loader package (see
  
https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so
  ) but this file is missed in 19.10 repository.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pluma 1.22.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct  5 19:23:02 2019
  InstallationDate: Installed on 2019-10-05 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1846890] Re: Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so

[Vlad Orlov]

** Package changed: pluma (Ubuntu) => libpeas (Ubuntu)

** Summary changed:

- Unable to enable plugins External tools, Python Console, Quick Open, 
Snippets) because of missed 
/usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so
+ Pluma: unable to enable plugins External tools, Python Console, Quick Open, 
Snippets) because of missed 
/usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so

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

Title:
  Pluma: unable to enable plugins External tools, Python Console, Quick
  Open, Snippets) because of missed /usr/lib/x86_64-linux-
  gnu/libpeas-1.0/loaders/libpythonloader.so

Status in libpeas package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 19.10
  2. Launch Pluma
  3. Go to Edit -> Preferences, switch to Plugins tab
  4. Try enable all plugins by checking their checkmarks

  Expected results:
  * all plugins are enabled without errors or warnings;

  Actual results:
  * plugin(s) are not enabled, show the following errors in `pluma`'s terminal:

  ```
  $ pluma

  (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module
  'pythonloader': /usr/lib/x86_64-linux-
  gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object
  file: No such file or directory

  (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 
'python'
  ```

  Note: in previous releases the `libpythonloader.so` was located in
  libpeas-1.0-python2loader package (see
  
https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so
  ) but this file is missed in 19.10 repository.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pluma 1.22.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct  5 19:23:02 2019
  InstallationDate: Installed on 2019-10-05 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)

[Vlad Orlov]

Cosmic is EOL since July 18, therefore the tag is removed

https://lists.ubuntu.com/archives/ubuntu-security-
announce/2019-July/004996.html

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  From duplicate bug 1720364 report.

  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher in mate-control-center
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ---
  Original description below:

  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions

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

[Desktop-packages] [Bug 1835376] Re: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1828639
   Unlooping all the trigger loops!

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

Title:
  package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers
  looping, abandoned

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  failed when i tried to do a partial upgrade because last upgrade
  already failed.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: libvlc-bin:amd64 3.0.6-1
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Thu Jul  4 10:16:45 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-04-06 (88 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: N/A
  SourcePackage: vlc
  Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1835376/+subscriptions

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

[Desktop-packages] [Bug 1836651] Re: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1828639
   Unlooping all the trigger loops!

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

Title:
  package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade:
  triggers looping, abandoned

Status in texinfo package in Ubuntu:
  New

Bug description:
  error during update

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: install-info 6.5.0.dfsg.1-4build1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Jul 15 14:25:23 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-12-26 (201 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.1
  SourcePackage: texinfo
  Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1761913] Re: gnome-software crashed with SIGABRT in g_assertion_message_error → ensure_surface_for_gicon → gtk_icon_helper_load_surface → gtk_icon_helper_ensure_surface → gtk_i

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1627564
   Crash due to assertion failure in ensure_surface_for_gicon 
[gtkiconhelper.c:493] (when png loader is missing/during upgrades)

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

Title:
  gnome-software crashed with SIGABRT in g_assertion_message_error →
  ensure_surface_for_gicon → gtk_icon_helper_load_surface →
  gtk_icon_helper_ensure_surface → gtk_icon_helper_ensure_surface →
  _gtk_icon_helper_get_size → gtk_image_get_content_size

Status in gnome-software package in Ubuntu:
  New

Bug description:
  testing ubuntu 18.04, this error popped up while NOT using gnome-
  software...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  7 11:52:45 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-04-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-software
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-software crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1819079] Re: /usr/lib/gcr/gcr-prompter:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1627564
   Crash due to assertion failure in ensure_surface_for_gicon 
[gtkiconhelper.c:493] (when png loader is missing/during upgrades)

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

Title:
  /usr/lib/gcr/gcr-
  
prompter:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface

Status in gcr package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1400036] Re: libvte9 shouldn't depend on libpango1.0-0 as it's a transitional package

[Vlad Orlov]

** No longer affects: vte (Debian)

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

Title:
  libvte9 shouldn't depend on libpango1.0-0 as it's a transitional
  package

Status in vte package in Ubuntu:
  Fix Released

Bug description:
  libvte9 should depend on libpango-1.0-0 instead of libpango1.0-0

  libpango1.0-0 is a transitional package.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libvte9 1:0.28.2-5ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec  7 02:39:58 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-11-01 (766 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: vte
  UpgradeStatus: Upgraded to trusty on 2014-09-04 (94 days ago)

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

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

[Desktop-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached

[Vlad Orlov]

Fixed in 2.56

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  various apps abort on assertion - g_file_monitor_source_handle_event:
  code should not be reached

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  I was opening "War Thunder"- Steam game and when I changed settings in
  game and it restarted I saw also in desktop error-message. I do not
  remember did I have anything from "nautilus" open.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu10
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 11 22:00:01 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-09-11 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910)
  ProcCmdline: nautilus -n
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_file_monitor_source_handle_event () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo

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

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

[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

Oh, nice. Maybe then gconf patches won't be needed. (Still need to fix
FTBFS in Bionic, bug 1834211.)

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1298534] Re: Mint 16 / 64-bit unable to mount via usb DROID Mini

[Vlad Orlov]

Fixed in 1.1.7 upstream, so 1.1.10-2ubuntu1 in Ubuntu 16.04 has the fix.

** Project changed: linuxmint => libmtp (Ubuntu)

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

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

Title:
  Mint 16 / 64-bit unable to mount via usb DROID Mini

Status in libmtp package in Ubuntu:
  Fix Released

Bug description:
  Installed 'mtp-tools' following instructions for "MTP' device recognition as 
listed on http://www.linuxmint.com/.  Have created file 
'etc/udev/rules.d/51-android.rules which contains:
  SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e67", MODE="0666"
  ownership is root:root and permissions 775

  DROID mini still doesn't mount and am returned with:

  noname@nonameM-A:~ > mtp-detect
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

  Listing raw device(s)
  Device 0 (VID=22b8 and PID=2e67) is UNKNOWN.
  **
  Please report this VID/PID and the device model to the libmtp development team
  **
 Found 1 device(s):
 22b8:2e67 @ bus 1, dev 11
  Attempting to connect device(s)
  ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  Android device detected, assigning default bug flags
  Error 1: Get Storage information failed.
  Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get 
object handles.
  Error 2: Error 02fe: PTP: Protocol error, data expected
  USB low-level info:
 bcdUSB: 512
 bDeviceClass: 0
 bDeviceSubClass: 0
 bDeviceProtocol: 0
 idVendor: 22b8
 idProduct: 2e67
 IN endpoint maxpacket: 512 bytes
 OUT endpoint maxpacket: 512 bytes
 Raw device info:
Bus location: 1
Device number: 11
Device entry info:
   Vendor: (null)
   Vendor id: 0x22b8
   Product: (null)
   Vendor id: 0x2e67
   Device flags: 0x08008106
  Configuration 0, interface 0, altsetting 0:
 Interface description contains the string "MTP"
 Device recognized as MTP, no further probing.
  Device info:
 Manufacturer: motorola
 Model: XT1030
 Device version: 1.0
 Serial number: TA6260EEFY
 Vendor extension ID: 0x0006
 Vendor extension description: microsoft.com: 1.0; android.com: 1.0; 
mot-mobility.com/DSU: 1.2
 Detected object size: 64 bits
 Extensions:
  microsoft.com: 1.0
  android.com: 1.0
  Supported operations:
 1001: get device info
 1002: Open session
 1003: Close session
 1004: Get storage IDs
 1005: Get storage info
 1006: Get number of objects
 1007: Get object handles
 1008: Get object info
 1009: Get object
 100a: Get thumbnail
 100b: Delete object
 100c: Send object info
 100d: Send object
 1014: Get device property description
 1015: Get device property value
 1016: Set device property value
 1017: Reset device property value
 101b: Get partial object
 9801: Get object properties supported
 9802: Get object property description
 9803: Get object property value
 9804: Set object property value
 9805: Get object property list
 9810: Get object references
 9811: Set object references
 95c1: Get Partial Object (64bit Offset)
 95c2: Send Partial Object
 95c3: Truncate Object
 95c4: Begin Edit Object
 95c5: End Edit Object
 9001: Unknown (9001)
 9002: Unknown (9002)
 9003: Unknown (9003)
 9004: Unknown (9004)
 9005: Unknown (9005)
 9006: Unknown (9006)
 9007: Unknown (9007)
 9008: Unknown (9008)
 9009: Unknown (9009)
 900a: Unknown (900a)
 900b: Unknown (900b)
 900c: Unknown (900c)
  Events supported:
 0x4002
 0x4003
 0x4004
 0x4005
  Device Properties Supported:
 0xd401: Synchronization Partner
 0xd402: Friendly Device Name
 0x5003: Image Size
  Playable File (Object) Types and Object Properties Supported:
 3000: Undefined Type
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM 

[Desktop-packages] [Bug 1529999] Re: reporting per mtp-detect: droid razr hd not recognized

[Vlad Orlov]

Fixed in Ubuntu 16.04 which has 1.1.10-2ubuntu1

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

Title:
  reporting per mtp-detect: droid razr hd not recognized

Status in libmtp package in Ubuntu:
  Fix Released

Bug description:
  On Ubuntu 12.04lts, mtp-detect reporst the following about a USB-
  connected Verizon DROID MAXX HD smartphone.  Request that this be
  fixed.

  Device 0 (VID=22b8 and PID=2e62) is UNKNOWN.
  Please report this VID/PID and the device model to the libmtp development team
  PTP_ERROR_IO: failed to open session, trying again after resetting USB 
interface
  LIBMTP libusb: Attempt to reset device
  libmtp version: 1.1.3

  Listing raw device(s)
 Found 1 device(s):
 22b8:2e62 @ bus 2, dev 10
  Attempting to connect device(s)
  Android device detected, assigning default bug flags
  USB low-level info:
 Interface has a kernel driver attached.
 bcdUSB: 512
 bDeviceClass: 0
 bDeviceSubClass: 0
 bDeviceProtocol: 0
 idVendor: 22b8
 idProduct: 2e62
 IN endpoint maxpacket: 512 bytes
 OUT endpoint maxpacket: 512 bytes
 Raw device info:
Bus location: 2
Device number: 10
Device entry info:
   Vendor: (null)
   Vendor id: 0x22b8
   Product: (null)
   Vendor id: 0x2e62
   Device flags: 0x08008106
  Configuration 0, interface 0, altsetting 0:
 Interface description contains the string "MTP"
 Device recognized as MTP, no further probing.
  Device info:
 Manufacturer: motorola
 Model: DROID RAZR HD
 Device version: 1.0
 Serial number: 
 Vendor extension ID: 0x0006
 Vendor extension description: microsoft.com: 1.0; android.com: 1.0; 
mot-mobility.com/DSU: 1.2
 Detected object size: 64 bits
 Extensions:
  microsoft.com: 1.0
  android.com: 1.0
  Supported operations:
 1001: get device info
 1002: Open session
 1003: Close session
 1004: Get storage IDs
 1005: Get storage info
 1006: Get number of objects
 1007: Get object handles
 1008: Get object info
 1009: Get object
 100a: Get thumbnail
 100b: Delete object
 100c: Send object info
 100d: Send object
 1014: Get device property description
 1015: Get device property value
 1016: Set device property value
 1017: Reset device property value
 101b: Get partial object
 9801: Get object properties supported
 9802: Get object property description
 9803: Get object property value
 9804: Set object property value
 9805: Get object property list
 9810: Get object references
 9811: Set object references
 95c1: Unknown (95c1)
 95c2: Unknown (95c2)
 95c3: Unknown (95c3)
 95c4: Unknown (95c4)
 95c5: Unknown (95c5)
 9001: Unknown (9001)
 9002: Unknown (9002)
 9003: Unknown (9003)
 9004: Unknown (9004)
 9005: Unknown (9005)
 9006: Unknown (9006)
 9007: Unknown (9007)
 9008: Unknown (9008)
 9009: Unknown (9009)
 900a: Unknown (900a)
 900b: Unknown (900b)
 900c: Unknown (900c)
  Events supported:
 0x4002
 0x4003
 0x4004
 0x4005
  Device Properties Supported:
 0xd401: Synchronization Partner
 0xd402: Friendly Device Name
 0x5003: Image Size
  Playable File (Object) Types and Object Properties Supported:
 3000: Undefined Type
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
 3001: Association/Directory
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
 3004: Text
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: 

[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

It could be that Debian won't need this change. Looks like all the
triggers are now processed near the end of upgrade, due to changes in
dpkg itself.

Possibly related entry from dpkg 1.19.3 changelog:

  * dpkg: Introduce a new dependency try level for trigger processing. This
completely defers trigger processing until after the dependency cycle
breaking level, so to avoid generating artificial trigger cycles, when we
end up trying to process triggers with yet unsatisifiable dependencies.
Closes: #810724, #854478, #911620

https://bugs.debian.org/810724

And from dpkg 1.19.7 changelog:

  * dpkg: Split the trigger dependtry into two, the second of which will be
the one checking trigger cycles when deferring trigger processing due to
unsatisfiable dependencies. Closes: #928429

https://bugs.debian.org/928429

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

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

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

No, Debian package doesn't have this change. As for the bug reports, I
only found a mention of this issue in a report for dpkg:
https://bugs.debian.org/774794

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

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

** Description changed:

- When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
+ [Impact]
+ 
+ During system upgrades, triggers for gconf2 might activate too early,
+ while some of its dependencies aren't configured yet. This happens
+ several times in a loop and stops the upgrade in the end.
+ 
+ The attached debdiffs fix this issue by changing interest to interest-
+ noawait in debian/gconf2.triggers file. The triggers will now activate
+ near the end of upgrade.
+ 
+ In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
+ 1834211).
+ 
+ [Test Case]
+ 
+ Triggers for gconf2 are usually activated on changes in
+ /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
+ GNOME) is most suitable for reproducing the issue. To reproduce it,
+ install that edition, apply all updates, then try upgrading to the next
+ release.
+ 
+ [Regression Potential]
+ 
+ None, interest-noawait trigger is known to work well in other packages
+ (comment 31).
+ 
+ [Other Info]
+ 
+ Even if Cosmic goes EOL next month, the fix for it might be worth it for
+ release upgrades.
+ 
+ [Original Description]
+ 
+ When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1
-  apt  1.2.3
+  dpkg 1.18.4ubuntu1
+  apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

** Summary changed:

- package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
+ [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

** Tags added: bionic cosmic disco

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

Title:
  [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  During system upgrades, triggers for gconf2 might activate too early,
  while some of its dependencies aren't configured yet. This happens
  several times in a loop and stops the upgrade in the end.

  The attached debdiffs fix this issue by changing interest to interest-
  noawait in debian/gconf2.triggers file. The triggers will now activate
  near the end of upgrade.

  In addition, the debdiff for Bionic also contains a fix for FTBFS (bug
  1834211).

  [Test Case]

  Triggers for gconf2 are usually activated on changes in
  /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with
  GNOME) is most suitable for reproducing the issue. To reproduce it,
  install that edition, apply all updates, then try upgrading to the
  next release.

  [Regression Potential]

  None, interest-noawait trigger is known to work well in other packages
  (comment 31).

  [Other Info]

  Even if Cosmic goes EOL next month, the fix for it might be worth it
  for release upgrades.

  [Original Description]

  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome.
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post 

[Desktop-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic

[Vlad Orlov]

These fixes are also added to combined debdiff in bug 1551623.

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

Title:
  [SRU] gconf FTBFS in Bionic

Status in gconf package in Ubuntu:
  New

Bug description:
  [Impact]

  Two issues make gconf FTBFS in Bionic:

  - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
  - missing dh-python in B-D

  The debdiff attached below fixes these issues and makes gconf build
  properly.

  [Test Case]

  Just install the needed build dependencies and try to build gconf. It
  will fail with an error from gtk-doc.make. Second issue: if gtk-
  doc.make is patched, the build will fail if dh-python isn't installed.

  [Regression Potential]

  None, you can't break it more than FTBFS :)

  [Other Info]

  Fixes are backported from Cosmic.

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

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

[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

Fix for 18.04 + build fix (bug 1834211)

this can go into bionic-proposed in one diff

** Attachment added: "Debdiff with the fix for Bionic + build fix (bug 1834211)"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273780/+files/gconf-debdiff-bionic

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

For 18.04, a build fix is required first (bug 1834211).

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

Fix for 18.10

** Attachment added: "Debdiff with the fix for Cosmic"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273779/+files/gconf-debdiff-cosmic

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

Fix for 19.04

** Attachment added: "Debdiff with the fix for Disco"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273778/+files/gconf-debdiff-disco

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

This is similar to what happened in the past with:

- dbus (https://bugs.debian.org/771989)
- cracklib-runtime (https://bugs.debian.org/854554)
- shared-mime-info (https://bugs.debian.org/864953)

It can be fixed the same way as those. I'll post the debdiffs with the
fixes later.

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

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

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

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, 
alongside many others related to systemd and gnome. 
  Notice that despite all warnings and errors, finally, the system remained 
functional.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Tue Mar  1 09:21:15 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-10-04 (148 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1733733] Re: portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estad

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1509043
   package gconf2-common 3.2.6-3ubuntu5 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 Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1733733

Title:
  portable apps crash while installing package gconf2-common
  3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-
  installation instalado retornou estado de saída de erro 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I installed orbital apps then it crashed, i changed to unity environment then 
tried to install again. I'm in need for portable apps for ubuntu.
  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: gconf2-common 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Tue Nov 21 21:44:08 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 128
  InstallationDate: Installed on 2017-09-05 (77 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 128
  UpgradeStatus: Upgraded to artful on 2017-11-18 (4 days ago)

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

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

[Desktop-packages] [Bug 1645384] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida d

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1509043
   package gconf2-common 3.2.6-3ubuntu5 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 Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1645384

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 128

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  el problema se genero cuando intentaba descargar unos programas, no se
  completo la descarga  y la tuve que reiniciar y posterior al reinicio
  aparecio el  mensaje de error.

  ProblemType: Package
  DistroRelease: elementary 0.4
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Nov 28 09:10:05 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 128
  InstallationDate: Installed on 2016-11-26 (1 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1698612] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1509043
   package gconf2-common 3.2.6-3ubuntu5 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 Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1698612

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: telepítve post-installation parancsfájl alfolyamat
  128 hibakóddal kilépett

Status in gconf package in Ubuntu:
  New

Bug description:
  this problem comes up after aech booting

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue May 23 18:21:04 2017
  ErrorMessage: telepítve post-installation parancsfájl alfolyamat 128 
hibakóddal kilépett
  InstallationDate: Installed on 2017-05-22 (26 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 
hibakóddal kilépett
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1711472] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sorti

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1509043
   package gconf2-common 3.2.6-3ubuntu5 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 Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711472

Title:
  package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to
  install/upgrade: le sous-processus script post-installation installé a
  retourné une erreur de sortie d'état 128

Status in gconf package in Ubuntu:
  New

Bug description:
  Hello,
  i want you say what this problem isn't today.
  I had this problem with ubuntu16.10
  And today i have this problem with this new system based on ubuntu.
  I wish what you resolved this problem.
  Jo

  ProblemType: Package
  DistroRelease: elementary 0.4.1
  Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug 17 23:53:18 2017
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 128
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to 
install/upgrade: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic

[Vlad Orlov]

** Attachment added: "Debdiff with the fix for Bionic"
   
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+attachment/5273159/+files/gconf-debdiff-bionic

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

Title:
  [SRU] gconf FTBFS in Bionic

Status in gconf package in Ubuntu:
  New

Bug description:
  [Impact]

  Two issues make gconf FTBFS in Bionic:

  - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
  - missing dh-python in B-D

  The debdiff attached below fixes these issues and makes gconf build
  properly.

  [Test Case]

  Just install the needed build dependencies and try to build gconf. It
  will fail with an error from gtk-doc.make. Second issue: if gtk-
  doc.make is patched, the build will fail if dh-python isn't installed.

  [Regression Potential]

  None, you can't break it more than FTBFS :)

  [Other Info]

  Fixes are backported from Cosmic.

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

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

[Desktop-packages] [Bug 1834211] [NEW] [SRU] gconf FTBFS in Bionic

[Vlad Orlov]

Public bug reported:

[Impact]

Two issues make gconf FTBFS in Bionic:

- outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
- missing dh-python in B-D

The debdiff attached below fixes these issues and makes gconf build
properly.

[Test Case]

Just install the needed build dependencies and try to build gconf. It
will fail with an error from gtk-doc.make. Second issue: if gtk-doc.make
is patched, the build will fail if dh-python isn't installed.

[Regression Potential]

None, you can't break it more than FTBFS :)

[Other Info]

Fixes are backported from Cosmic.

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


** Tags: bionic ftbfs

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

Title:
  [SRU] gconf FTBFS in Bionic

Status in gconf package in Ubuntu:
  New

Bug description:
  [Impact]

  Two issues make gconf FTBFS in Bionic:

  - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26
  - missing dh-python in B-D

  The debdiff attached below fixes these issues and makes gconf build
  properly.

  [Test Case]

  Just install the needed build dependencies and try to build gconf. It
  will fail with an error from gtk-doc.make. Second issue: if gtk-
  doc.make is patched, the build will fail if dh-python isn't installed.

  [Regression Potential]

  None, you can't break it more than FTBFS :)

  [Other Info]

  Fixes are backported from Cosmic.

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

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

[Desktop-packages] [Bug 1574029] Re: Upgrade failed

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1550292
   package shared-mime-info 1.5-2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed

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

Title:
  Upgrade failed

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  At the end of the upgrade, a dialog box appeared "The upgrade has
  aborted. Your system could be in an unstable state. A recovery will
  run now (dpkg -configure - a). Nothing happened after closing the
  dialog box.

  
  After shutdown, boot up failed after grub tries to load something with this 
message "Starting up", then after 10 seconds this message "Gave up waiting 
for root device., common problems:.ALERT! UUID = 2476e..does not exist.

  The the boot process stopped at the initramfs prompt.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Apr 23 17:34:29 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-11-12 (162 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1568572] Re: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

Fixed in Xenial on 2016-07-18 by using interest-noawait in
debian/bamfdaemon.triggers file. More info at bug 1589097.

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

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

Title:
  package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in bamf package in Ubuntu:
  Fix Released

Bug description:
  I submitted this bug report because Ubuntu advised me to do so during
  an upgrade to Xenial from Wily.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1
  Uname: Linux 4.0.3-bisect-test-01-0559366f72c86288c8d3dc5cae91dfc2f6e26ad9 
x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Apr 10 19:23:53 2016
  DuplicateSignature: 
package:bamfdaemon:0.5.2~bzr0+15.10.20150627.1-0ubuntu1:dependency problems - 
leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-10 (0 days ago)

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

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

[Desktop-packages] [Bug 1574123] Re: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1568572
   package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed

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

Title:
  package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in bamf package in Ubuntu:
  Confirmed

Bug description:
  during upgrade bamfdaemon was noch possible to install. Now it seems
  to be missiong? how to install it now? via packet-installer or
  terminal?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Sat Apr 23 20:17:09 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-08-21 (246 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3~bzr0+16.04.20160415-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1599846] Re: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1568572
   package bamfdaemon 0.5.2~bzr0+15.10.20150627.1-0ubuntu1 failed to 
install/upgrade: dependency problems - leaving triggers unprocessed

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

Title:
  package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to
  install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

Status in bamf package in Ubuntu:
  New

Bug description:
  Update failed while upgrading from xenial to yakkety.

  mahowi@T60:~$ lsb_release -rd
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

  mahowi@T60:~$ apt-cache policy bamfdaemon
  bamfdaemon:
Installiert:   0.5.3~bzr0+16.10.20160705-0ubuntu1
Installationskandidat: 0.5.3~bzr0+16.10.20160705-0ubuntu1
Versionstabelle:
   *** 0.5.3~bzr0+16.10.20160705-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
  Uname: Linux 4.4.0-30-generic i686
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: i386
  Date: Thu Jul  7 13:39:38 2016
  ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  InstallationDate: Installed on 2016-07-06 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu1
   apt  1.3~exp1
  SourcePackage: bamf
  Title: package bamfdaemon 0.5.3~bzr0+16.10.20160705-0ubuntu1 failed to 
install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  UpgradeStatus: Upgraded to yakkety on 2016-07-07 (0 days ago)

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

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

[Desktop-packages] [Bug 1615116] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  beroendeproblem - lämnar utlösare obehandlade

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  Error received when upgrading from 16.04 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug 19 18:49:10 2016
  ErrorMessage: beroendeproblem - lämnar utlösare obehandlade
  InstallationDate: Installed on 2016-02-08 (193 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu2
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: 
beroendeproblem - lämnar utlösare obehandlade
  UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1669632] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Mar  2 20:56:22 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-04-10 (326 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-03-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1634151] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade:
  vereistenproblemen - triggers blijven onbehandeld

Status in gconf package in Ubuntu:
  New

Bug description:
  Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system
  the message occured

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 17 13:29:10 2016
  ErrorMessage: vereistenproblemen - triggers blijven onbehandeld
  InstallationDate: Installed on 2016-05-04 (166 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: 
vereistenproblemen - triggers blijven onbehandeld
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago)

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

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

[Desktop-packages] [Bug 1681137] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  while upgrading from 16.04 to 16.10,
  it gave me this bug..

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Sun Apr  9 01:01:29 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-01 (250 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-04-08 (0 days ago)

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

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

[Desktop-packages] [Bug 1632415] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  error after updating from 16.04.1 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Oct 11 22:08:46 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-25 (78 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago)

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

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

[Desktop-packages] [Bug 1741658] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  System upgrage to Ubuntu 16.04 failed. During upgrade many packets were not 
installed:
  I wrote down the Dutch remarks "Kan gconf2 niet installeren" and many others. 
Translated:
  Failed to install during the systemupgrade:
  ==
  gconf2  (+ "gconf2 will possibly not work")
  gnupg-agent
  gnupg2
  libgdata22
  gvfs-backends
  adwaita-icon-theme-full
  libgail-3-0
  gstreamer1.0-plugins-bad
  gstreamer0.10-plugins-good
  gstreamer1.10-plugins-good
  libgssdp-1.0-3
  libupnp-1.0-4
  libupnp-igd-1.0-4
  libnice10
  gstreamer1.0-nice
  libfarstream-0.2-5
  libpurple0
  gnome-keyring
  libgpgme11
  libgmime-2.6-0
  libwebkitgtk-3.0-0
  geary
  gnome-icon-theme
  ===
  Hope the list is complete :-))
  Since then only logging-out is possible, but the menu items: "Close the 
system" ("Afsluiten" in Dutch)  nor "Restart" gave any effect. Caption of this 
menu is:

 Lubuntu
Session Zorin-OS-lite 16.04

  Best regards!
  Dirk De Backer
  mailto:debacker.d...@worldonline.be

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Jan  6 15:32:06 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2015-12-19 (748 days ago)
  InstallationMedia: Zorin 9 trusty - Release i386 (20140811)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2018-01-06 (0 days ago)

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

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

[Desktop-packages] [Bug 1636962] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 26 23:42:05 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-04-27 (181 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-10-26 (0 days ago)

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

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

[Desktop-packages] [Bug 1656553] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug is no longer a duplicate of bug 1645117
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Error during partial update from 16.04 LTS to 16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic i686
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: i386
  Date: Sat Jan 14 15:46:26 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-12-14 (31 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1645117] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  --

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  Date: Sun Nov 27 21:29:34 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-03 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-11-27 (0 days ago)

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

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

[Desktop-packages] [Bug 1651222] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  upgrade done with fail to install package gconf2 3.2.6ubuntu7

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Mon Dec 19 13:13:09 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-11-19 (29 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1698600] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  upgrading from 16.04 to 17.04  failed to install

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Sat Jun 17 18:19:27 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-13 (277 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-06-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1701447] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug is no longer a duplicate of bug 1632415
   package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  The bugs being reported were generated automatically (without any of
  my input) when I allowed the system to upgrade itself from 16.04 to
  16.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Thu Jun 29 21:58:13 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-11-27 (214 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2017-06-30 (0 days ago)
  mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 
2017-01-03T13:15:58.771330

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

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

[Desktop-packages] [Bug 1698478] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  would load but with errors

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 16 17:22:13 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-06-16 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2017-06-16 (0 days ago)

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

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

[Desktop-packages] [Bug 1618364] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com
  dependências - a deixar triggers por processar

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from xenial to yakkety

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  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
  Date: Tue Aug 30 09:34:31 2016
  ErrorMessage: problemas com dependências - a deixar triggers por processar
  InstallationDate: Installed on 2016-02-15 (196 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com 
dependências - a deixar triggers por processar
  UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago)

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

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

[Desktop-packages] [Bug 1610029] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  when upgrading from 14.04 LTS to 16.04 LTS this error came up during
  the upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Aug  3 23:57:59 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago)

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

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

[Desktop-packages] [Bug 1618492] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con
  le dipendenze - trigger non elaborati

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  crash

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 30 14:35:15 2016
  ErrorMessage: problemi con le dipendenze - trigger non elaborati
  InstallationDate: Installed on 2016-08-27 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con 
le dipendenze - trigger non elaborati
  UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago)

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

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

[Desktop-packages] [Bug 1573662] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade:
  Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  error occured during regular "do-release-upgrade". System remains in
  unstable condition. dpkg --configure -a / apt-get -f install continues
  the process (still running).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Fri Apr 22 17:05:44 2016
  DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:Abhängigkeitsprobleme - 
Trigger bleiben unverarbeitet
  ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  InstallationDate: Installed on 2016-03-17 (35 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: 
Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1576539] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Triaged

Bug description:
  bug happened while i'm upgrading ubuntu version from 15.10 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 29 08:16:36 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-03-05 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago)

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

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

[Desktop-packages] [Bug 1743975] Re: "Power Statistics" UI become grey and have no respond after launch it about 30 seconds

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1721282
   upowerd/gnome-power-statistics crash; high CPU, memory consumption

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

Title:
  "Power Statistics" UI become grey and have no respond after launch it
  about 30 seconds

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  Install Ubuntu 16.04 and launch Power Statistics,
  After the application launched for a while(about 30 sec),
  the UI become gray and has no response.

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

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

[Desktop-packages] [Bug 1796804] Re: webkit2gtk-4.0-dev 依赖关系不完整(dependence wrong)

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1795901
   libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h

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

Title:
  webkit2gtk-4.0-dev 依赖关系不完整(dependence wrong)

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Proccess:
  apt install libwebkit2gtk-4.0-dev golang-go
  go get -v github.com/sourcegraph/go-webkit2/webkit2

  
  Will report error:
  # github.com/sourcegraph/go-webkit2/webkit2
  In file included from /usr/include/webkitgtk-4.0/webkit2/webkit2.h:54:0,
   from 
../../github.com/sourcegraph/go-webkit2/webkit2/settings.go:3:
  /usr/include/webkitgtk-4.0/webkit2/WebKitJavascriptResult.h:28:10: fatal 
error: jsc/jsc.h: No such file or directory
   #include 
^~~
  compilation terminated.

  
  Because: there is no "jsc.h"

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

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

[Desktop-packages] [Bug 1795901] Re: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h

[Vlad Orlov]

Thanks, Atril builds fine now.

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

Title:
  libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h

Status in WebKit:
  Unknown
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in webkit2gtk source package in Bionic:
  Fix Released
Status in webkit2gtk package in Debian:
  Unknown

Bug description:
  2.22.2-0ubuntu0.18.04.1, just like https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=906519

  /usr/include/webkitgtk-4.0/webkit2/WebKitJavascriptResult.h:28:10: fatal 
error: jsc/jsc.h: No such file or directory
   #include 
    ^~~

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit-open-source/+bug/1795901/+subscriptions

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

[Desktop-packages] [Bug 1795901] Re: libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h

[Vlad Orlov]

Also it's impossible to build Atril, MATE's document viewer.

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

Title:
  libjavascriptcoregtk-4.0-dev: missing jsc/jsc.h

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

Bug description:
  2.22.2-0ubuntu0.18.04.1, just like https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=906519

  /usr/include/webkitgtk-4.0/webkit2/WebKitJavascriptResult.h:28:10: fatal 
error: jsc/jsc.h: No such file or directory
   #include 
    ^~~

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

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

[Desktop-packages] [Bug 1721282] Re: upowerd/gnome-power-statistics crash; high CPU, memory consumption

[Vlad Orlov]

** Tags added: bionic xenial

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

Title:
  upowerd/gnome-power-statistics crash; high CPU, memory consumption

Status in gnome-power-manager package in Ubuntu:
  Confirmed

Bug description:
  Not sure if necessary here since same bug is already on:
  https://bugzilla.redhat.com/show_bug.cgi?id=1427621
  https://bugs.freedesktop.org/show_bug.cgi?id=100626
  https://bugzilla.gnome.org/show_bug.cgi?id=781088

  Tested on Ubuntu 16.04.3, 4.12.0-041200rc3-generic

  Steps to reproduce:
  1. have a system with a recent kernel (4.10.x or later)
  2. start gnome-power-statistics
  3. go to Pprocessor tab
  4. have a look at gnome-system-monitor or htop

  Result:
  - On Processor section, Wakeups tab: "Processor wakeups pers second: 
GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats."
  - High CPU usage of /usr/lib/upower/upowerd
  - Crash gnome-power-statistics

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

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

[Desktop-packages] [Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)

[Vlad Orlov]

** Package changed: mate-desktop (Ubuntu) => ubuntu-mate

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

Title:
  nm-applet symbol not displayed on mate (18.04)

Status in ubuntu-mate:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 18.04, the network manager applet symbol
  isn't displayed any longer. The other functionality (asking for
  credentials) is working. I also see other symbols.

  
  aptitude show network-manager-gnome
  Paket: network-manager-gnome
  Version: 1.8.10-2ubuntu1
  Neu: ja
  Zustand: Installiert

  
  stdout/stderr:
  Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

  ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
  accessibility bus: Did not receive a reply. Possible causes include:
  the remote application did not send a reply, the message bus security
  policy blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
  information for modem at /org/freedesktop/ModemManager1/Modem/6: No
  ModemManager support

  (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
  not available for modem at /org/freedesktop/ModemManager1/Modem/6

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on
  widget which has a parent

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Mar  8 21:27:56 2018
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WpaSupplicantLog:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1613363] Re: /usr/bin/engrampa:11:g_type_check_instance_is_fundamentally_a:g_object_get_qdata:detach_from_style:clear_cache:ensure_cache_up_to_date

[Vlad Orlov]

** Package changed: engrampa (Ubuntu) => gtk+2.0 (Ubuntu)

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

Title:
  
/usr/bin/engrampa:11:g_type_check_instance_is_fundamentally_a:g_object_get_qdata:detach_from_style:clear_cache:ensure_cache_up_to_date

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding engrampa.  This problem was most recently seen with version
  1.12.0-2, the problem page at
  https://errors.ubuntu.com/problem/2f8bf782a90fe3ab90595f0ab71cdafa82f08b7f
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1613363/+subscriptions

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

[Desktop-packages] [Bug 1569068] Re: /usr/bin/mate-settings-daemon:ERROR:pulse/glib-mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)

[Vlad Orlov]

** Package changed: mate-settings-daemon (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  /usr/bin/mate-settings-daemon:ERROR:pulse/glib-
  mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-settings-daemon.  This problem was most recently seen
  with version 1.12.1-2build1, the problem page at
  https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7
  contains more details.

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

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

[Desktop-packages] [Bug 580958] Re: nautilus crashed with signal 7

[Vlad Orlov]

** Package changed: nautilus (Ubuntu) => gvfs (Ubuntu)

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

Title:
  nautilus crashed with signal 7

Status in Nautilus:
  Expired
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  Nautilus crashes if it has not been used for some time (I don't now
  the exact time but maybe 15 minutes). If it is already started it
  crashes and if I start it it crashes. But it works if I start it a
  second time, but crashes again when it has been idle for 15 minutes.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.30.1-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: openafs nvidia
  Architecture: i386
  CrashCounter: 1
  Date: Sat May 15 15:15:29 2010
  ExecutablePath: /usr/bin/nautilus
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=sv_SE:sv:en_GB:en
   PATH=(custom, no user)
   LANG=sv_SE.utf8
   SHELL=/bin/bash
  Signal: 7
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
   ?? () from /usr/lib/gio/modules/libgvfsdbus.so
  Title: nautilus crashed with signal 7
  UserGroups: admin audio plugdev pulse

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

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

[Desktop-packages] [Bug 1620708] Re: /usr/bin/caja:7:meta_tree_needs_rereading:meta_tree_refresh:meta_tree_lookup_by_name:meta_lookup_cache_lookup_path:g_daemon_vfs_local_file_add_info

[Vlad Orlov]

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

** Package changed: caja (Ubuntu) => gvfs (Ubuntu)

** This bug has been marked a duplicate of bug 580958
   nautilus crashed with signal 7

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

Title:
  
/usr/bin/caja:7:meta_tree_needs_rereading:meta_tree_refresh:meta_tree_lookup_by_name:meta_lookup_cache_lookup_path:g_daemon_vfs_local_file_add_info

Status in gvfs package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding caja.  This problem was most recently seen with version
  1.12.7-1, the problem page at
  https://errors.ubuntu.com/problem/acdafa3ef66918969b8aa8b7b780f5bf9f61e934
  contains more details.

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

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

[Desktop-packages] [Bug 1670898] Re: crash after spi_cache_foreach from impl_GetItems

[Vlad Orlov]

** Summary changed:

- 
/usr/bin/mate-settings-daemon:11:g_type_check_instance_is_fundamentally_a:g_object_ref:g_hash_table_foreach:spi_cache_foreach:impl_GetItems
+ crash after spi_cache_foreach from impl_GetItems

** Package changed: mate-settings-daemon (Ubuntu) => at-spi2-atk
(Ubuntu)

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

Title:
  crash after spi_cache_foreach from impl_GetItems

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-settings-daemon.  This problem was most recently seen with package version 
1.12.1-2build1, the problem page at 
https://errors.ubuntu.com/problem/f507ea21d5337991672738917ae190e6e86f76e2 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1670898/+subscriptions

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

[Desktop-packages] [Bug 1555331] Re: crash in g_slist_remove_all from gtk_rc_clear_realized_style

[Vlad Orlov]

** Summary changed:

- mate-panel crashed with SIGSEGV in g_slist_remove_all()
+ crash in g_slist_remove_all from gtk_rc_clear_realized_style

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

Title:
  crash in g_slist_remove_all from gtk_rc_clear_realized_style

Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Won't Fix

Bug description:
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: mate-panel 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4
  Uname: Linux 4.4.0-11-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Mar  9 22:49:55 2016
  ExecutablePath: /usr/bin/mate-panel
  InstallationDate: Installed on 2016-02-25 (12 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160224)
  ProcCmdline: mate-panel
  SegvAnalysis:
   Segfault happened at: 0x7f4fa6439b1c :cmp
%rbp,(%rdi)
   PC (0x7f4fa6439b1c) ok
   source "%rbp" ok
   destination "(%rdi)" (0x160016) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-panel
  StacktraceTop:
   g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  Title: mate-panel crashed with SIGSEGV in g_slist_remove_all()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1555331/+subscriptions

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

[Desktop-packages] [Bug 1535944] Re: /usr/lib/mate-panel/wnck-applet:11:g_type_check_instance_cast:pager_update:display_workspace_names_changed:g_cclosure_marshal_VOID__STRINGv:_g_closure_invoke_va

[Vlad Orlov]

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

Random crash after display_workspace_names_changed, fixed as bug
1555993.

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

** Changed in: mate-panel (Ubuntu)
   Status: Invalid => Fix Released

** This bug has been marked a duplicate of bug 1555993
   wnck-applet (window list, workspace switcher) crashes on moving/removing 
applet

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

Title:
  /usr/lib/mate-panel/wnck-
  
applet:11:g_type_check_instance_cast:pager_update:display_workspace_names_changed:g_cclosure_marshal_VOID__STRINGv:_g_closure_invoke_va

Status in libwnck package in Ubuntu:
  Invalid
Status in mate-panel package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.10.1+gfdl1-1, the problem page at
  https://errors.ubuntu.com/problem/ccf5af49f1c8672b263e1bb5e90d637a8c027758
  contains more details.

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

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

[Desktop-packages] [Bug 1617552] Re: mate-notification-daemon crashed with SIGABRT in __assert_fail_base()

[Vlad Orlov]

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

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** This bug has been marked a duplicate of bug 1598142
   mate-notification-daemon assert failure: mate-notification-daemon: 
../../../../src/cairo.c:305: cairo_destroy: Assertion 
`CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed.

** This bug is no longer a duplicate of bug 1598142
   mate-notification-daemon assert failure: mate-notification-daemon: 
../../../../src/cairo.c:305: cairo_destroy: Assertion 
`CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed.

** Package changed: ubuntu => mate-notification-daemon (Ubuntu)

** This bug has been marked a duplicate of bug 1598142
   mate-notification-daemon assert failure: mate-notification-daemon: 
../../../../src/cairo.c:305: cairo_destroy: Assertion 
`CAIRO_REFERENCE_COUNT_HAS_REFERENCE (>ref_count)' failed.

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

Title:
  mate-notification-daemon crashed with SIGABRT in __assert_fail_base()

Status in mate-notification-daemon package in Ubuntu:
  New

Bug description:
  Just popped out of nowhere.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: mate-notification-daemon 1.14.1-1build1
  ProcVersionSignature: Ubuntu 4.4.0-9134.53-powerpc64-smp 4.4.15
  Uname: Linux 4.4.0-9134-powerpc64-smp ppc64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: powerpc
  CurrentDesktop: MATE
  Date: Sat Aug 27 13:10:34 2016
  ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
  InstallationDate: Installed on 2016-03-26 (153 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta powerpc 
(20160326)
  ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=de_AT:de
   LANG=de_AT.UTF-8
  Signal: 6
  SourcePackage: mate-notification-daemon
  StacktraceTop:
   raise () from /lib/powerpc-linux-gnu/libc.so.6
   abort () from /lib/powerpc-linux-gnu/libc.so.6
   ?? () from /lib/powerpc-linux-gnu/libc.so.6
   __assert_fail () from /lib/powerpc-linux-gnu/libc.so.6
   cairo_destroy () from /usr/lib/powerpc-linux-gnu/libcairo.so.2
  Title: mate-notification-daemon crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1617552/+subscriptions

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

[Desktop-packages] [Bug 1071155] Re: nautilus crashed with signal 5 in gdk_flush from make_root_pixmap from gnome_bg_create_surface

[Vlad Orlov]

** Summary changed:

- nautilus crashed with signal 5 in _XReply()
+ nautilus crashed with signal 5 in gdk_flush from make_root_pixmap from 
gnome_bg_create_surface

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

Title:
  nautilus crashed with signal 5 in gdk_flush from make_root_pixmap from
  gnome_bg_create_surface

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Unity was being glitchy so I ran "$ unity --replace". Nautilus then
  crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 25 17:36:13 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'958x502+0+548'"
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcCmdline: nautilus -n
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   gdk_flush () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (6 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1726661] Re: nautilus-desktop crashed with signal 5 in gnome_bg_create_surface()

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1071155
   nautilus crashed with signal 5 in _XReply()

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

Title:
  nautilus-desktop crashed with signal 5 in gnome_bg_create_surface()

Status in nautilus package in Ubuntu:
  New

Bug description:
  This crash happened just after the system booted. I had installed a
  bunch of themes from Github previous to that. I also have nemo 3
  installed from noobslab.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 07:12:23 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2017-10-19 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: nautilus-desktop
  Signal: 5
  SourcePackage: nautilus
  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
   XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   gdk_flush () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus-desktop crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1580686] Re: scp-dbus-service.py crashed with signal 5 in _XReply()

[Vlad Orlov]

** Package changed: system-config-printer (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- scp-dbus-service.py crashed with signal 5 in _XReply()
+ crash in XTranslateCoordinates from gdk_window_x11_get_root_coords

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

Title:
  crash in XTranslateCoordinates from gdk_window_x11_get_root_coords

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Printed 3 copys of one document with setting 2 pages on 1 sheet. Job
  printed normally but crash report appeared afterwards.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: system-config-printer-gnome 1.5.7+20160212-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog: E [11/May/2016:18:27:44 +0200] [cups-deviced] PID 13760 
(gutenprint52+usb) stopped with status 1!
  CurrentDesktop: XFCE
  Date: Wed May 11 18:32:16 2016
  ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py
  InstallationDate: Installed on 2016-04-30 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterpreterPath: /usr/bin/python3.5
  Lpstat: device for FS-1010: usb://Kyocera/FS-1010?serial=XAL4584303
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: FS-1010: Kyocera Mita FS-1010
  ProcCmdline: /usr/bin/python3 
/usr/share/system-config-printer/scp-dbus-service.py
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=6d707d68-42fe-492a-8d56-5bd131334069 ro quiet splash vt.handoff=7
  Signal: 5
  SourcePackage: system-config-printer
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gtk_tooltip_trigger_tooltip_query () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: scp-dbus-service.py crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare sudo video
  dmi.bios.date: 03/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B150-HD3P-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd03/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1580686/+subscriptions

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

[Desktop-packages] [Bug 1718543] Re: gnome-shell-extension-prefs crashed with SIGABRT in g_assertion_message_expr() "assertion failed: (destination)" from ensure_surface_for_gicon()

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  gnome-shell-extension-prefs crashed with SIGABRT in
  g_assertion_message_expr() "assertion failed: (destination)" from
  ensure_surface_for_gicon()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crashed when changing Dash to Dock settings

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep 20 00:56:33 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2017-06-01 (110 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-shell-extension-prefs dash-to-d...@micxgx.gmail.com
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gnome-shell-extension-prefs crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: Upgraded to artful on 2017-06-10 (101 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1752533] Re: zenity (6) g_assertion_message → g_assertion_message_error → ensure_surface_for_gicon → gtk_icon_helper_load_surface → gtk_icon_helper_ensure_surface

[Vlad Orlov]

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

** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  zenity (6) g_assertion_message → g_assertion_message_error →
  ensure_surface_for_gicon → gtk_icon_helper_load_surface →
  gtk_icon_helper_ensure_surface

Status in zenity package in Ubuntu:
  Confirmed

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

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

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

[Desktop-packages] [Bug 1752506] Re: zenity crashed with SIGABRT in g_assertion_message()

[Vlad Orlov]

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

** This bug is no longer a duplicate of bug 1752533
   zenity (6) g_assertion_message → g_assertion_message_error → 
ensure_surface_for_gicon → gtk_icon_helper_load_surface → 
gtk_icon_helper_ensure_surface
** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  zenity crashed with SIGABRT in g_assertion_message()

Status in zenity package in Ubuntu:
  New

Bug description:
  no idea, just asked to submit the error report

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: zenity 3.27.90-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Thu Mar  1 02:21:03 2018
  ExecutablePath: /usr/bin/zenity
  InstallationDate: Installed on 2015-03-19 (1077 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: zenity --warning --text The\ system\ is\ running\ in\ 
low-graphics\ mode\\n\\nYour\ screen,\ graphics\ card,\ and\ input\ 
device\ settings\\ncould\ not\ be\ detected\ correctly.\ \ You\ will\ need\ to\ 
configure\ these\ yourself.
  Signal: 6
  SourcePackage: zenity
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_error () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: zenity crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1594609] Re: /usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func

[Vlad Orlov]

** Package changed: mate-panel (Ubuntu) => gtk+2.0 (Ubuntu)

** Summary changed:

- 
/usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func
+ crash due to assertion in get_icon_fallback from 
gtk_recent_chooser_menu_create_item

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

Title:
  crash due to assertion in get_icon_fallback from
  gtk_recent_chooser_menu_create_item

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mate-panel.  This problem was most recently seen with
  version 1.12.2-1, the problem page at
  https://errors.ubuntu.com/problem/96ae198a578de2353a3cc778896a83a10ab7d131
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1594609/+subscriptions

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

[Desktop-packages] [Bug 1627564] Re: was doing an upgrade and this created a trouble report

[Vlad Orlov]

** Package changed: lightdm-gtk-greeter (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- was doing an upgrade and this created a trouble report
+ crash due to assertion in ensure_surface_for_gicon

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

Title:
  crash due to assertion in ensure_surface_for_gicon

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  bubble opened up indicating there was a failure during the latest
  update.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.4.0-9136-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Sun Sep 25 20:37:06 2016
  ExecutablePath: /usr/sbin/lightdm-gtk-greeter
  InstallationDate: Installed on 2016-08-04 (52 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
  ProcCmdline: /usr/sbin/lightdm-gtk-greeter
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: lightdm-gtk-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
   [greeter]
   theme-name = Lubuntu-dark-panel
  mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 
2016-08-14T22:33:57.293011

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1627564/+subscriptions

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

[Desktop-packages] [Bug 1678693] Re: mate-notification-daemon crashed with SIGABRT in g_assertion_message()

[Vlad Orlov]

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

** Package changed: mate-notification-daemon (Ubuntu) => gtk+3.0
(Ubuntu)

** This bug has been marked a duplicate of bug 1627564
   crash due to assertion in ensure_surface_for_gicon

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

Title:
  mate-notification-daemon crashed with SIGABRT in g_assertion_message()

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  occurred while installing packages

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-notification-daemon 1.18.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  2 23:04:26 2017
  ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon
  InstallationDate: Installed on 2017-04-01 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_US
   LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: mate-notification-daemon
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-notification-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1678693/+subscriptions

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

[Desktop-packages] [Bug 1427332] Re: nautilus crashed with signal 5 in _XReply()

[Vlad Orlov]

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- nautilus crashed with signal 5 in _XReply()
+ crash in XGetWindowProperty from gdk_check_wm_state_changed

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

Title:
  crash in XGetWindowProperty from gdk_check_wm_state_changed

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  Date: Mon Mar  2 16:17:00 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-10-24 (129 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: nautilus
  ProcEnviron:
   LANGUAGE=es_UY:es
   PATH=(custom, no user)
   LANG=es_UY.UTF-8
   SHELL=/bin/bash
   TERM=unknown
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to vivid on 2015-01-05 (56 days ago)
  UserGroups:
   
  usr_lib_nautilus:
   brasero3.12.0-0ubuntu2
   evince 3.14.1-0ubuntu5
   file-roller3.14.2-0ubuntu4
   gnome-terminal 3.14.2-0ubuntu2
   nautilus-share 0.7.3-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1427332/+subscriptions

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

[Desktop-packages] [Bug 1201854] Re: gnome-settings-daemon crashed with signal 5 in _XReply()

[Vlad Orlov]

** Package changed: gnome-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- gnome-settings-daemon crashed with signal 5 in _XReply()
+ crash in XGetWindowProperty from read_settings from 
gdk_xsettings_manager_window_filter

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

Title:
  crash in XGetWindowProperty from read_settings from
  gdk_xsettings_manager_window_filter

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  This happened immediately after a reboot for updates. Immediately
  after I checked for more updates and there were some, meaning this bug
  might already be fixed. About the updates, I noticed that a few
  'failed to download' but running sudo apt-get upgrade they installed
  fine. I don't know if this is related but it might be. This has
  probably happened several times, but I don't think it's a regular
  pattern. Running 13.10 Alpha. Otherwise seems to be pretty stable so
  far despite the minor bugs.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.6.4-0ubuntu15
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Fri Jul 12 23:43:27 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ExecutableTimestamp: 1372327096
  InstallationDate: Installed on 2013-06-14 (28 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
  ProcCwd: /home/karatekid
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to saucy on 2013-07-12 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1201854/+subscriptions

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

[Desktop-packages] [Bug 1751948] Re: /usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event

[Vlad Orlov]

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

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1201854
   crash in XGetWindowProperty from read_settings from 
gdk_xsettings_manager_window_filter

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

Title:
  
/usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event

Status in gtk+3.0 package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1751948/+subscriptions

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

[Desktop-packages] [Bug 1744744] Re: /usr/bin/mate-settings-daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_

[Vlad Orlov]

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

** Package changed: mate-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1427332
   crash in XGetWindowProperty from gdk_check_wm_state_changed

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

Title:
  /usr/bin/mate-settings-
  
daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event

Status in gtk+3.0 package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1744744/+subscriptions

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

[Desktop-packages] [Bug 1359308] Re: crash due to assertion in gail_focus_notify_when_idle: code should not be reached

[Vlad Orlov]

** Summary changed:

- mate-panel crashed when using window list
+ crash due to assertion in gail_focus_notify_when_idle: code should not be 
reached

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

Title:
  crash due to assertion in gail_focus_notify_when_idle: code should not
  be reached

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  On an Ubuntu MATE utopic amd64 system, mate-panel 1.8.0+dfsg1-2
  crashed when I clicked on an item in the window list (located in the
  bottom panel). The panel reappeared and continued working correctly.
  This happened while apt-get was upgrading packages, but mate-panel was
  not one of the packages being upgraded.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: mate-panel 1.8.0+dfsg1-2
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  Date: Wed Aug 20 13:21:43 2014
  ExecutablePath: /usr/bin/mate-panel
  InstallationDate: Installed on 2014-08-19 (1 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731)
  ProcCmdline: mate-panel
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1359308/+subscriptions

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

[Desktop-packages] [Bug 1745815] Re: [patch] screen-resolution-extra should depend on polkit-1-auth-agent instead of policykit-1-gnome

[Vlad Orlov]

Thanks for uploading, that was fast :)

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

Title:
  [patch] screen-resolution-extra should depend on polkit-1-auth-agent
  instead of policykit-1-gnome

Status in screen-resolution-extra package in Ubuntu:
  Fix Released
Status in screen-resolution-extra source package in Bionic:
  Fix Released

Bug description:
  System: Ubuntu MATE 18.04
  Package version: 0.17.1

  Expected behavior:

  Package screen-resolution-extra should depend on polkit-1-auth-agent.
  This would allow installing it in desktop environments that provide
  their own PolicyKit authentication agents, like MATE which has mate-
  polkit. All these agents provide polkit-1-auth-agent (which is a
  virtual package).

  Actual behavior:

  Package screen-resolution-extra depends on policykit-1-gnome. In MATE
  desktop it leads to installation of both mate-polkit and
  policykit-1-gnome, which is not needed.

  Additional info:

  Package screen-resolution-extra is used by nvidia-settings tool,
  therefore the problem affects everyone who uses proprietary nvidia
  drivers.

  The debdiff that is attached below makes screen-resolution-extra
  depend on polkit-1-auth-agent, fixing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+subscriptions

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

[Desktop-packages] [Bug 1745815] Re: [patch] screen-resolution-extra should depend on polkit-1-auth-agent instead of policykit-1-gnome

[Vlad Orlov]

Oops, I forgot to add that link to LP...

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

Title:
  [patch] screen-resolution-extra should depend on polkit-1-auth-agent
  instead of policykit-1-gnome

Status in screen-resolution-extra package in Ubuntu:
  Fix Released
Status in screen-resolution-extra source package in Bionic:
  Fix Released

Bug description:
  System: Ubuntu MATE 18.04
  Package version: 0.17.1

  Expected behavior:

  Package screen-resolution-extra should depend on polkit-1-auth-agent.
  This would allow installing it in desktop environments that provide
  their own PolicyKit authentication agents, like MATE which has mate-
  polkit. All these agents provide polkit-1-auth-agent (which is a
  virtual package).

  Actual behavior:

  Package screen-resolution-extra depends on policykit-1-gnome. In MATE
  desktop it leads to installation of both mate-polkit and
  policykit-1-gnome, which is not needed.

  Additional info:

  Package screen-resolution-extra is used by nvidia-settings tool,
  therefore the problem affects everyone who uses proprietary nvidia
  drivers.

  The debdiff that is attached below makes screen-resolution-extra
  depend on polkit-1-auth-agent, fixing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+subscriptions

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

[Desktop-packages] [Bug 1745815] Re: [patch] screen-resolution-extra should depend on polkit-1-auth-agent instead of policykit-1-gnome

[Vlad Orlov]

Ok, here goes the corrected debdiff.

** Attachment added: "Debdiff with the fix for Bionic, version 2"
   
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+attachment/5052420/+files/screen-resolution-extra-debdiff-bionic-v2

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

Title:
  [patch] screen-resolution-extra should depend on polkit-1-auth-agent
  instead of policykit-1-gnome

Status in screen-resolution-extra package in Ubuntu:
  New
Status in screen-resolution-extra source package in Bionic:
  New

Bug description:
  System: Ubuntu MATE 18.04
  Package version: 0.17.1

  Expected behavior:

  Package screen-resolution-extra should depend on polkit-1-auth-agent.
  This would allow installing it in desktop environments that provide
  their own PolicyKit authentication agents, like MATE which has mate-
  polkit. All these agents provide polkit-1-auth-agent (which is a
  virtual package).

  Actual behavior:

  Package screen-resolution-extra depends on policykit-1-gnome. In MATE
  desktop it leads to installation of both mate-polkit and
  policykit-1-gnome, which is not needed.

  Additional info:

  Package screen-resolution-extra is used by nvidia-settings tool,
  therefore the problem affects everyone who uses proprietary nvidia
  drivers.

  The debdiff that is attached below makes screen-resolution-extra
  depend on polkit-1-auth-agent, fixing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+subscriptions

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

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

[Vlad Orlov]

Ok... what to do about upstream now?

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

Title:
  [SRU] intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Released
Status in intltool source package in Xenial:
  Fix Released
Status in intltool source package in Artful:
  Fix Released

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

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

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

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

[Desktop-packages] [Bug 1745815] Re: [patch] screen-resolution-extra should depend on polkit-1-auth-agent instead of policykit-1-gnome

[Vlad Orlov]

policykit-1-gnome provides polkit-1-auth-agent, should be ok

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

Title:
  [patch] screen-resolution-extra should depend on polkit-1-auth-agent
  instead of policykit-1-gnome

Status in screen-resolution-extra package in Ubuntu:
  New
Status in screen-resolution-extra source package in Bionic:
  New

Bug description:
  System: Ubuntu MATE 18.04
  Package version: 0.17.1

  Expected behavior:

  Package screen-resolution-extra should depend on polkit-1-auth-agent.
  This would allow installing it in desktop environments that provide
  their own PolicyKit authentication agents, like MATE which has mate-
  polkit. All these agents provide polkit-1-auth-agent (which is a
  virtual package).

  Actual behavior:

  Package screen-resolution-extra depends on policykit-1-gnome. In MATE
  desktop it leads to installation of both mate-polkit and
  policykit-1-gnome, which is not needed.

  Additional info:

  Package screen-resolution-extra is used by nvidia-settings tool,
  therefore the problem affects everyone who uses proprietary nvidia
  drivers.

  The debdiff that is attached below makes screen-resolution-extra
  depend on polkit-1-auth-agent, fixing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+subscriptions

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

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

[Vlad Orlov]

Testing in Xenial...

- upgraded intltool to 0.51.0-2ubuntu1.16.04.1 from xenial-proposed
- repeated the same tarball making process for mate-desktop package,
  the only difference being the git branch (1.12 instead of master)
- the process completed successfully, the distcheck didn't break

Good to go in Xenial as well.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  [SRU] intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Released
Status in intltool source package in Xenial:
  Fix Committed
Status in intltool source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

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

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

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

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

[Vlad Orlov]

Testing in Artful...

- upgraded intltool to 0.51.0-4ubuntu1.17.04.1 from artful-proposed
- repeated the tarball making process for mate-desktop package, exactly
  as described above in the Test Case
- the process completed successfully, the distcheck didn't break

Good to go.

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  [SRU] intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Released
Status in intltool source package in Xenial:
  Fix Committed
Status in intltool source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

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

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

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

[Desktop-packages] [Bug 1745815] [NEW] [patch] screen-resolution-extra should depend on polkit-1-auth-agent instead of policykit-1-gnome

[Vlad Orlov]

Public bug reported:

System: Ubuntu MATE 18.04
Package version: 0.17.1

Expected behavior:

Package screen-resolution-extra should depend on polkit-1-auth-agent.
This would allow installing it in desktop environments that provide
their own PolicyKit authentication agents, like MATE which has mate-
polkit. All these agents provide polkit-1-auth-agent (which is a virtual
package).

Actual behavior:

Package screen-resolution-extra depends on policykit-1-gnome. In MATE
desktop it leads to installation of both mate-polkit and
policykit-1-gnome, which is not needed.

Additional info:

Package screen-resolution-extra is used by nvidia-settings tool,
therefore the problem affects everyone who uses proprietary nvidia
drivers.

The debdiff that is attached below makes screen-resolution-extra depend
on polkit-1-auth-agent, fixing the problem.

** Affects: screen-resolution-extra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic patch

** Patch added: "Debdiff with the fix for Bionic"
   
https://bugs.launchpad.net/bugs/1745815/+attachment/5044398/+files/screen-resolution-extra-debdiff-bionic

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

Title:
  [patch] screen-resolution-extra should depend on polkit-1-auth-agent
  instead of policykit-1-gnome

Status in screen-resolution-extra package in Ubuntu:
  New

Bug description:
  System: Ubuntu MATE 18.04
  Package version: 0.17.1

  Expected behavior:

  Package screen-resolution-extra should depend on polkit-1-auth-agent.
  This would allow installing it in desktop environments that provide
  their own PolicyKit authentication agents, like MATE which has mate-
  polkit. All these agents provide polkit-1-auth-agent (which is a
  virtual package).

  Actual behavior:

  Package screen-resolution-extra depends on policykit-1-gnome. In MATE
  desktop it leads to installation of both mate-polkit and
  policykit-1-gnome, which is not needed.

  Additional info:

  Package screen-resolution-extra is used by nvidia-settings tool,
  therefore the problem affects everyone who uses proprietary nvidia
  drivers.

  The debdiff that is attached below makes screen-resolution-extra
  depend on polkit-1-auth-agent, fixing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+subscriptions

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

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

[Vlad Orlov]

Yes, I meant the upstream entry here. I was just wondering, wasn't going
to mark it (I don't actually have the rights for that).

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

Title:
  [SRU] intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Released
Status in intltool source package in Xenial:
  Fix Committed
Status in intltool source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

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

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

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

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

[Vlad Orlov]

** Tags removed: zesty

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

Title:
  [SRU] intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Committed
Status in intltool source package in Xenial:
  Fix Committed
Status in intltool source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

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

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

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

[Desktop-packages] [Bug 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

[Vlad Orlov]

** Tags removed: yakkety

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

Title:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: atril 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Oct 22 09:43:08 2016
  ExecutablePath: /usr/bin/atril-thumbnailer
  InstallationDate: Installed on 2016-05-14 (160 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: atril-thumbnailer -s 128 
file:///home/username/Documents/jedi_complaint.pdf 
/tmp/.mate_desktop_thumbnail.8JDPPY
  SegvAnalysis:
   Segfault happened at: 0x7fdcb0258990 : mov
0x50(%rdi),%eax
   PC (0x7fdcb0258990) ok
   source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: atril
  StacktraceTop:
   cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2
   GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () 
from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
   Page::loadThumb(unsigned char**, int*, int*, int*) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
  Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark

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

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

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

[Vlad Orlov]

Not sure if the upstream entry should be wontfix or not, it seems
unmaintained.

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

Title:
  intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Committed
Status in intltool source package in Xenial:
  New
Status in intltool source package in Artful:
  New

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

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

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

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

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

[Vlad Orlov]

Thanks :)

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

Title:
  intltool confused by separate build-dir

Status in intltool:
  Confirmed
Status in intltool package in Ubuntu:
  Fix Committed
Status in intltool source package in Xenial:
  New
Status in intltool source package in Artful:
  New

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

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

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

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

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

[Vlad Orlov]

Is anything else needed to get the fix into Bionic before it's released
in April?

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

Title:
  intltool confused by separate build-dir

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

Bug description:
  [Impact]

  An old bug in intltool breaks out-of-tree builds, including "make
  distcheck", in a lot of intltool-using projects when automake version
  is 1.15 or newer.

  The fix for this issue (by Aleksander Morgado) is provided in the
  debdiffs attached to the report.

  It's a long-standing bug which is present in all current Ubuntu releases,
  starting from Xenial. Would be really nice to get it finally fixed. The 
developers have to patch their intltool locally just to have a working 
distcheck target (which is used when making release tarballs).

  [Test Case]

  Try making release tarball for some upstream package. For example, it
  can be mate-desktop, a base project for various MATE components.

  $ sudo apt-get build-dep mate-desktop
  $ git clone https://github.com/mate-desktop/mate-desktop
  $ cd mate-desktop
  $ ./autogen.sh --enable-gtk-doc --enable-deprecated --disable-strict
  $ make -j5 && make dist -j5 && make distcheck -j5

  This will build the project, make release tarball and check it by
  unpacking it into a new directory and building (again) in it. The last
  step will fail:

  ---

  srcdir=../../../po /usr/bin/intltool-update -m
  The following files contain translations and are currently not in use. Please
  consider adding these to the POTFILES.in file, located in the po/ directory.

  sub/mate-about/mate-about.desktop.in
  sub/tools/mate-color-select.desktop.in

  If some of these files are left out on purpose then please add them to
  POTFILES.skip instead of POTFILES.in. A file 'missing' containing this list
  of left out files has been written in the current directory.
  Please report to https://github.com/mate-desktop/mate-desktop/
  if [ -r missing -o -r notexist ]; then \
exit 1; \
  fi
  Makefile:179: recipe for target 'check' failed

  ---

  The out-of-tree build breaks here.

  [Regression Potential]

  None. This is a fix for a broken feature, it doesn't affects other ones.
  Also the fix had been tested by MATE developers in various distros, including 
Debian, Ubuntu and Fedora.

  [Original Description]

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

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

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

[Desktop-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

[Vlad Orlov]

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

Forgot to mention that 016_no_offscreen_widgets_grabbing.patch had never
been accepted upstream, as I learned in the discussion at
https://bugzilla.gnome.org/607668.

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mate-terminal package in Ubuntu:
  Invalid

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

[Vlad Orlov]

** Package changed: gnome-terminal (Ubuntu) => gtk+3.0 (Ubuntu)

** Summary changed:

- gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
+ gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts

** Tags removed: vivid
** Tags added: bionic xenial

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

Title:
  gnome-terminal-server and mate-terminal crash when setting keyboard
  shortcuts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  I put my laptop to sleep for an hour or so; when I restored it, gnome-
  terminal had crashed. It did not do this the previous time I suspended
  my laptop today, so I doubt that's immediately related.

  This crash can be reproduced by setting a shortcut in preferences.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-terminal 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 30 00:19:43 2015
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2014-02-03 (419 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f98e2afbf1f :
testb  $0x4,0x16(%rax)
   PC (0x7f98e2afbf1f) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0xbcae) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel (widget=0x2580c30) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382
   window_group_cleanup_grabs (group=, 
window=window@entry=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110
   gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169
   gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at 
/build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134
  Title: gnome-terminal-server crashed with SIGSEGV in 
g_type_check_instance_is_a()
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare 
sbuild sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1438014/+subscriptions

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

[Desktop-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts

[Vlad Orlov]

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

Surprise, it's been affecting gnome-terminal for years: bug 1438014.

** This bug has been marked a duplicate of bug 1438014
   gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()

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

Title:
  mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() -
  while editing Keyboard Shortcuts

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mate-terminal package in Ubuntu:
  Invalid

Bug description:
  1) 
  $ lsb_release -rd
  Description:  Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64

  2) 
  $ apt-cache policy mate-terminal
  mate-terminal:
Installed: 1.17.0-0ubuntu1
Candidate: 1.17.0-0ubuntu1
  3) 
  Open mate-terminal
  Select "Edit" -> "Keyboard Shortcuts"
  Select "Help"->"Contents", click on default shortcut key "F1" to change
  Try to set it to various key sequences. Sometimes bug is triggered by 
pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting 
Ctrl-Shift-W / Crtl-Shift-Alt-W
  Expected: changed keyboard shortcut for "Help"->"Contents"

  4) Abort and closed mate-terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: mate-terminal 1.17.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 23 09:33:19 2017
  ExecutablePath: /usr/bin/mate-terminal
  ExecutableTimestamp: 1484233434
  InstallationDate: Installed on 2017-02-22 (1 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  ProcCmdline: mate-terminal
  ProcCwd: /home/user
  SegvAnalysis:
   Segfault happened at: 0x7f883e41c321 :
testb  $0x4,0x16(%rax)
   PC (0x7f883e41c321) ok
   source "$0x4" ok
   destination "0x16(%rax)" (0x7001e) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: mate-terminal
  StacktraceTop:
   g_type_check_instance_is_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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