[Touch-packages] [Bug 1719287] [NEW] libnss-resolve causes gnome-shell to hang when there's a high rate of getaddrinfo() calls

2017-09-25 Thread Chow Loong Jin 
Public bug reported:

I've been running a locust[1]-based web load test on my Ubuntu machine
running GNOME Shell (wayland). When starting a new test with a client
spawn rate of ~500/s, it issues a huge amount of getaddrinfo() calls.
When using libnss-resolve, this causes a huge number of NameOwnerChanged
events on the system bus:


signal time=1506335482.865950 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=227290 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.190697"
   string ""
   string ":1.190697"
signal time=1506335482.868601 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=227291 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.190697"
   string ":1.190697"
   string ""
signal time=1506335483.305614 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=227292 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.190698"
   string ""
   string ":1.190698"
signal time=1506335483.310873 sender=org.freedesktop.DBus -> destination=(null 
destination) serial=227293 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.190698"
   string ":1.190698"
   string ""

This in turn causes gnome-shell to spend a huge amount of CPU churning
through these events, and if sufficiently starved of CPU (those load
testing scripts also consume quite a bit) when interacting with Google
Chome, it goes into key repeat runaway (similar to [2]).

I'm not completely certain, but there were quite a number of other
processes affected by this, and all of them start fighting over CPU time
to handle these NameOnwerChanged events.

As a workaround, disabling libnss-resolve in /etc/nsswitch.conf and just
using the stub resolver fixes things.


[1] https://locust.io
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1459692

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1719287

Title:
  libnss-resolve causes gnome-shell to hang when there's a high rate of
  getaddrinfo() calls

Status in systemd package in Ubuntu:
  New

Bug description:
  I've been running a locust[1]-based web load test on my Ubuntu machine
  running GNOME Shell (wayland). When starting a new test with a client
  spawn rate of ~500/s, it issues a huge amount of getaddrinfo() calls.
  When using libnss-resolve, this causes a huge number of
  NameOwnerChanged events on the system bus:

  
  signal time=1506335482.865950 sender=org.freedesktop.DBus -> 
destination=(null destination) serial=227290 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
 string ":1.190697"
 string ""
 string ":1.190697"
  signal time=1506335482.868601 sender=org.freedesktop.DBus -> 
destination=(null destination) serial=227291 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
 string ":1.190697"
 string ":1.190697"
 string ""
  signal time=1506335483.305614 sender=org.freedesktop.DBus -> 
destination=(null destination) serial=227292 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
 string ":1.190698"
 string ""
 string ":1.190698"
  signal time=1506335483.310873 sender=org.freedesktop.DBus -> 
destination=(null destination) serial=227293 path=/org/freedesktop/DBus; 
interface=org.freedesktop.DBus; member=NameOwnerChanged
 string ":1.190698"
 string ":1.190698"
 string ""

  This in turn causes gnome-shell to spend a huge amount of CPU churning
  through these events, and if sufficiently starved of CPU (those load
  testing scripts also consume quite a bit) when interacting with Google
  Chome, it goes into key repeat runaway (similar to [2]).

  I'm not completely certain, but there were quite a number of other
  processes affected by this, and all of them start fighting over CPU
  time to handle these NameOnwerChanged events.

  As a workaround, disabling libnss-resolve in /etc/nsswitch.conf and
  just using the stub resolver fixes things.

  
  [1] https://locust.io
  [2] https://bugzilla.redhat.com/show_bug.cgi?id=1459692

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

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

2017-07-13 Thread Chow Loong Jin 
Tested and verified on xenial, yakkety and zesty.

** Tags removed: verification-needed verification-needed-xenial 
verification-needed-yakkety verification-needed-zesty
** Tags added: verification-done verification-done-xenial 
verification-done-yakkety verification-done-zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1693850

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Fix Committed
Status in libzen source package in Yakkety:
  Fix Committed
Status in libzen source package in Zesty:
  Fix Committed
Status in libzen source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

2017-07-06 Thread Chow Loong Jin 
Yeah I tested it using mediainfo on a large file in chroots of the
target distributions without rebuilding mediainfo.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1693850

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Triaged
Status in libzen source package in Yakkety:
  Triaged
Status in libzen source package in Zesty:
  Triaged
Status in libzen source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

2017-05-29 Thread Chow Loong Jin 
Whoops, uploaded with a wrong version number (0.4.34-1ubuntu0.16.04.1)
to zesty. I've fixed it with another upload (0.4.34-1ubuntu0.17.04.1).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1693850

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Triaged
Status in libzen source package in Yakkety:
  Triaged
Status in libzen source package in Zesty:
  Triaged
Status in libzen source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

2017-05-28 Thread Chow Loong Jin 
** Description changed:

- The switch to cmake caused two compilation flags to be accidentally dropped: 
+ The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64
  
  This causes all file-handling operations in zenlib to fail to work with
- large files. This affects the following reverse-dependencies:
+ large files on 32-bit machines. This affects the following reverse-
+ dependencies:
  
   - libmediainfo
   - mediainfo
   - mediaconch
  
  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.
+ 
+ [Test Case]
+ 
+ Run `mediainfo $filename` where $filename is a file that is larger than
+ 4.2GB. Output will be missing if this bug is present.
+ 
+ [Regression Potential]
+ 
+ Quite low, since the only thing that's changed here are some -D
+ compilation flags that aren't even directly referenced in the codebase.

** Description changed:

+ [Impact]
+ 
  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64
  
  This causes all file-handling operations in zenlib to fail to work with
  large files on 32-bit machines. This affects the following reverse-
  dependencies:
  
   - libmediainfo
   - mediainfo
   - mediaconch
  
  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.
  
  [Test Case]
  
  Run `mediainfo $filename` where $filename is a file that is larger than
  4.2GB. Output will be missing if this bug is present.
  
  [Regression Potential]
  
  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the codebase.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1693850

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Triaged
Status in libzen source package in Yakkety:
  Triaged
Status in libzen source package in Zesty:
  Triaged
Status in libzen source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The switch to cmake caused two compilation flags to be accidentally dropped:
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files on 32-bit machines. This affects the following
  reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

  [Test Case]

  Run `mediainfo $filename` where $filename is a file that is larger
  than 4.2GB. Output will be missing if this bug is present.

  [Regression Potential]

  Quite low, since the only thing that's changed here are some -D
  compilation flags that aren't even directly referenced in the
  codebase.

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

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

2017-05-26 Thread Chow Loong Jin 
** Also affects: libzen (Ubuntu Artful)
   Importance: Undecided
 Assignee: Chow Loong Jin (hyperair)
   Status: Fix Released

** Also affects: libzen (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: libzen (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1693850

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released
Status in libzen source package in Xenial:
  Triaged
Status in libzen source package in Yakkety:
  Triaged
Status in libzen source package in Zesty:
  Triaged
Status in libzen source package in Artful:
  Fix Released

Bug description:
  The switch to cmake caused two compilation flags to be accidentally dropped: 
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files. This affects the following reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

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

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

[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support

2017-05-26 Thread Chow Loong Jin 
This bug was fixed in the package libzen - 0.4.35-1

---
libzen (0.4.35-1) experimental; urgency=medium

  * [015b0fa] Imported Upstream version 0.4.35

 -- Chow Loong Jin <hyper...@debian.org>  Tue, 04 Apr 2017 00:39:46
+0800

** Changed in: libzen (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1693850

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released

Bug description:
  The switch to cmake caused two compilation flags to be accidentally dropped: 
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files. This affects the following reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

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

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

[Touch-packages] [Bug 1693850] [NEW] libzen wasn't compiled with large file support

2017-05-26 Thread Chow Loong Jin 
Public bug reported:

The switch to cmake caused two compilation flags to be accidentally dropped: 
-D_LARGE_FILES -D_FILE_OFFSET_BITS=64

This causes all file-handling operations in zenlib to fail to work with
large files. This affects the following reverse-dependencies:

 - libmediainfo
 - mediainfo
 - mediaconch

This has been fixed in
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

** Affects: libzen (Ubuntu)
 Importance: Undecided
 Assignee: Chow Loong Jin (hyperair)
 Status: Fix Released


** Tags: patch

** Description changed:

- The switch to cmake caused two compilation flags to be accidentally
- dropped: -D_LARGE_FILES -D_FILE_OFFSET_BITS=64
+ The switch to cmake caused two compilation flags to be accidentally dropped: 
+ -D_LARGE_FILES -D_FILE_OFFSET_BITS=64
  
  This causes all file-handling operations in zenlib to fail to work with
  large files. This affects the following reverse-dependencies:
  
-  - libmediainfo
-  - mediainfo
-  - mediaconch
+  - libmediainfo
+  - mediainfo
+  - mediaconch
  
  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

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

** Changed in: libzen (Ubuntu)
   Status: Fix Released => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1693850

Title:
  libzen wasn't compiled with large file support

Status in libzen package in Ubuntu:
  Fix Released

Bug description:
  The switch to cmake caused two compilation flags to be accidentally dropped: 
  -D_LARGE_FILES -D_FILE_OFFSET_BITS=64

  This causes all file-handling operations in zenlib to fail to work
  with large files. This affects the following reverse-dependencies:

   - libmediainfo
   - mediainfo
   - mediaconch

  This has been fixed in
  
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.

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

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

[Touch-packages] [Bug 1619932] Re: FFe: Sync libmediainfo 0.7.88-1 (universe) from Debian unstable (main)

2016-09-07 Thread Chow Loong Jin 
This bug was fixed in the package libmediainfo - 0.7.88-1

---
libmediainfo (0.7.88-1) unstable; urgency=medium

  * [4017389] Imported Upstream version 0.7.88

 -- Chow Loong Jin <hyper...@debian.org>  Thu, 01 Sep 2016 23:06:29
+0800

libmediainfo (0.7.87-1) unstable; urgency=medium

  * [36d49df] Imported Upstream version 0.7.87

 -- Chow Loong Jin <hyper...@debian.org>  Sun, 28 Aug 2016 20:09:22
+0800

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmediainfo in Ubuntu.
https://bugs.launchpad.net/bugs/1619932

Title:
  FFe: Sync libmediainfo 0.7.88-1 (universe) from Debian unstable (main)

Status in libmediainfo package in Ubuntu:
  Fix Released

Bug description:
  Please sync libmediainfo 0.7.88-1 (universe) from Debian unstable
  (main)

  Explanation of FeatureFreeze exception:

  Upstream wishes to deprecate versions before 0.7.88, as there were some bugs
  fixed in between 0.7.85 and 0.7.88.

  Changelog entries since current yakkety version 0.7.85-1build2:

  libmediainfo (0.7.88-1) unstable; urgency=medium

* [4017389] Imported Upstream version 0.7.88

   -- Chow Loong Jin <hyper...@debian.org>  Thu, 01 Sep 2016 23:06:29
  +0800

  libmediainfo (0.7.87-1) unstable; urgency=medium

* [36d49df] Imported Upstream version 0.7.87

   -- Chow Loong Jin <hyper...@debian.org>  Sun, 28 Aug 2016 20:09:22
  +0800

  
  Upstream changelog since 0.7.85:

  Version 0.7.88, 2016-08-31
  --
  + MediaInfo distributed with HTTP/HTTPS support: support of Amazon S3 with 
Signature Version 4
  + FFV1: parsing speed slight improvement
  x Duration: fixed regression in last release, sometimes duration was 
displayed with only count of minutes

  Version 0.7.87, 2016-06-30
  --
  + Refactoring of the trace feature, for better performance and some bug fixes
  - Visual C++ 2012 project files removed
  x Review of symbols display, now using standard display (e.g. "k" instead of 
"K", " min" instead of "mn"...)
  x XML output: revert to old versioning method (version is MediaInfo software 
version)
  x I63, EBUCore/FIMS outputs: typo correction about WritingLibrary and 
WritingApplication
  x Matroska: files with CodecPrivate element before CodecID element where not 
always correctly parsed
  x OGG: crash/incoherent behavior with some buggy OGG streams having invalid 
chunk sizes

  Version 0.7.86, 2016-05-31
  --
  + FFV1 parsing optimization, avoiding by default a too verbose trace
  + Matroska: more elements support and typo fixes in the trace
  + #I172, Trace feature: provide the name of the main parser in the media 
element
  + Matroska: consider all values below 0x10 EBML names as 1-byte junk
  + --HTTPS=0 option for using HTTP in XML outputs
  x Matroska: better support (including speed improvement) of huge lossless 
frames (e.g. 20 MB FFV1 4K)
  x #I144, Python binding: Python 2 on Linux does not automatically provide the 
locale to the shared object
  x HTML output: don't escape carriage returns from the input file
  x FFV1: some streams were rejected despite the fact they are valid
  x Python binding: some errors during call of Get() API with Python3 on 
Linux/Mac

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

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

[Touch-packages] [Bug 1619932] [NEW] FFe: Sync libmediainfo 0.7.88-1 (universe) from Debian unstable (main)

2016-09-03 Thread Chow Loong Jin 
Public bug reported:

Please sync libmediainfo 0.7.88-1 (universe) from Debian unstable (main)

Explanation of FeatureFreeze exception:

Upstream wishes to deprecate versions before 0.7.88, as there were some bugs
fixed in between 0.7.85 and 0.7.88.

Changelog entries since current yakkety version 0.7.85-1build2:

libmediainfo (0.7.88-1) unstable; urgency=medium

  * [4017389] Imported Upstream version 0.7.88

 -- Chow Loong Jin <hyper...@debian.org>  Thu, 01 Sep 2016 23:06:29
+0800

libmediainfo (0.7.87-1) unstable; urgency=medium

  * [36d49df] Imported Upstream version 0.7.87

 -- Chow Loong Jin <hyper...@debian.org>  Sun, 28 Aug 2016 20:09:22
+0800


Upstream changelog since 0.7.85:

Version 0.7.88, 2016-08-31
--
+ MediaInfo distributed with HTTP/HTTPS support: support of Amazon S3 with 
Signature Version 4
+ FFV1: parsing speed slight improvement
x Duration: fixed regression in last release, sometimes duration was displayed 
with only count of minutes

Version 0.7.87, 2016-06-30
--
+ Refactoring of the trace feature, for better performance and some bug fixes
- Visual C++ 2012 project files removed
x Review of symbols display, now using standard display (e.g. "k" instead of 
"K", " min" instead of "mn"...)
x XML output: revert to old versioning method (version is MediaInfo software 
version)
x I63, EBUCore/FIMS outputs: typo correction about WritingLibrary and 
WritingApplication
x Matroska: files with CodecPrivate element before CodecID element where not 
always correctly parsed
x OGG: crash/incoherent behavior with some buggy OGG streams having invalid 
chunk sizes

Version 0.7.86, 2016-05-31
--
+ FFV1 parsing optimization, avoiding by default a too verbose trace
+ Matroska: more elements support and typo fixes in the trace
+ #I172, Trace feature: provide the name of the main parser in the media element
+ Matroska: consider all values below 0x10 EBML names as 1-byte junk
+ --HTTPS=0 option for using HTTP in XML outputs
x Matroska: better support (including speed improvement) of huge lossless 
frames (e.g. 20 MB FFV1 4K)
x #I144, Python binding: Python 2 on Linux does not automatically provide the 
locale to the shared object
x HTML output: don't escape carriage returns from the input file
x FFV1: some streams were rejected despite the fact they are valid
x Python binding: some errors during call of Get() API with Python3 on Linux/Mac

** Affects: libmediainfo (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: libmediainfo (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmediainfo in Ubuntu.
https://bugs.launchpad.net/bugs/1619932

Title:
  FFe: Sync libmediainfo 0.7.88-1 (universe) from Debian unstable (main)

Status in libmediainfo package in Ubuntu:
  New

Bug description:
  Please sync libmediainfo 0.7.88-1 (universe) from Debian unstable
  (main)

  Explanation of FeatureFreeze exception:

  Upstream wishes to deprecate versions before 0.7.88, as there were some bugs
  fixed in between 0.7.85 and 0.7.88.

  Changelog entries since current yakkety version 0.7.85-1build2:

  libmediainfo (0.7.88-1) unstable; urgency=medium

    * [4017389] Imported Upstream version 0.7.88

   -- Chow Loong Jin <hyper...@debian.org>  Thu, 01 Sep 2016 23:06:29
  +0800

  libmediainfo (0.7.87-1) unstable; urgency=medium

* [36d49df] Imported Upstream version 0.7.87

   -- Chow Loong Jin <hyper...@debian.org>  Sun, 28 Aug 2016 20:09:22
  +0800

  
  Upstream changelog since 0.7.85:

  Version 0.7.88, 2016-08-31
  --
  + MediaInfo distributed with HTTP/HTTPS support: support of Amazon S3 with 
Signature Version 4
  + FFV1: parsing speed slight improvement
  x Duration: fixed regression in last release, sometimes duration was 
displayed with only count of minutes

  Version 0.7.87, 2016-06-30
  --
  + Refactoring of the trace feature, for better performance and some bug fixes
  - Visual C++ 2012 project files removed
  x Review of symbols display, now using standard display (e.g. "k" instead of 
"K", " min" instead of "mn"...)
  x XML output: revert to old versioning method (version is MediaInfo software 
version)
  x I63, EBUCore/FIMS outputs: typo correction about WritingLibrary and 
WritingApplication
  x Matroska: files with CodecPrivate element before CodecID element where not 
always correctly parsed
  x OGG: crash/incoherent behavior with some buggy OGG streams having invalid 
chunk sizes

  Version 0.7.86, 2016-05-31
  --
  + FFV1 parsing optimization, avoiding by default a too verbose trace
  + Matroska: more elements support and typo fixes in the trace
  + #I172, Trace feature: provide the name of the main parser in the media 
element
  + Matroska: consider all values below 0x10 EBML name

[Touch-packages] [Bug 1287322] Re: ctrl+super keybindings broken in trusty

2015-02-11 Thread Chow Loong Jin 
Still happens in 14.10.

** Changed in: unity (Ubuntu)
   Status: Expired = New

** Changed in: unity
   Status: Expired = New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1287322

Title:
  ctrl+super keybindings broken in trusty

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
   affects unity
   status new

  Unity's handling of Ctrl+Super+X keybindings has regressed in trusty -- 
Control
  must be pressed before Super is pressed, or Unity hijacks the keybinding
  instead.

  For example:
  1. Press and hold Control
  2. Press and hold Super
  3. Press 1

  This activates the Ctrl+Super+1 keybinding, which for me is Zoom reset
  (from the ezoom plugin).

  However, if you reverse steps 1 and 2, so that Super is held down before
  Control, then the keybinding for Super+1 is activated instead, i.e. the first
  item in the launcher gets activated.

  This bug used to be present in older versions of Unity, but was fixed in 
Saucy,
  and reappeared in Trusty.

  -- 
  Kind regards,
  Loong Jin

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

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

Re: [Touch-packages] [Bug 1401238] Re: bump to new 0.4.30 version

2015-01-08 Thread Chow Loong Jin 
On Thu, Jan 08, 2015 at 08:45:32AM -, Ivan Romanov wrote:
 Look at package in Fedora 
 http://pkgs.fedoraproject.org/cgit/libzen.git/tree/?id=de88f55ad00bef4c79595f69c8e71066cfc20eff
 You can use the same patch.

Hmm, could you forward it upstream if you haven't done so already?
Thanks.

-- 
Kind regards,
Loong Jin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1401238

Title:
  bump to new 0.4.30 version

Status in libzen package in Ubuntu:
  New

Bug description:
  Please update to the latest upstream release.
  Also manually add missed cmake files. Then rebuild with cmake. It is need to 
have cmake config modules for ZenLib.
  Look at Fedora package for example. 
http://pkgs.fedoraproject.org/cgit/libzen.git/commit/?id=de88f55ad00bef4c79595f69c8e71066cfc20eff

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

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

Re: [Touch-packages] [Bug 1401238] Re: bump to new 0.4.30 version

2015-01-08 Thread Chow Loong Jin 
On Thu, Jan 08, 2015 at 03:14:02PM +0800, Chow Loong Jin wrote:
 On Wed, Jan 07, 2015 at 08:08:15AM -, Ivan Romanov wrote:
  Was:
  libzen.so - libzen.so.0.0.0
  libzen.so.0 - libzen.so.0.0.0
  libzen.so.0.0.0
  
  Now:
  libzen.so - libzen.so.0
  libzen.so.0 - libzen.so.0.4.30
  libzen.so.0.4.30
 
 Oh, it actually did that? Hmm, let me give it another go.

Meh, missing files. I'm starting to think upstream didn't mean for the cmake
bits to be used with the tarball releases.

dh_auto_configure -DProject/CMake
-- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Error: File /«PKGBUILDDIR»/Project/CMake/cmake_uninstall.cmake.in does not
exist.
CMake Error at CMakeLists.txt:139 (configure_file):
  configure_file Problem configuring file


CMake Error: File /«PKGBUILDDIR»/Project/CMake/libzen.pc.in does not exist.
CMake Error at CMakeLists.txt:146 (configure_file):
  configure_file Problem configuring file


CMake Error: File /«PKGBUILDDIR»/Project/CMake/ZenLibConfig.cmake.in does not
exist.
CMake Error at /usr/share/cmake-3.0/Modules/CMakePackageConfigHelpers.cmake:298 
(configure_file):
  configure_file Problem configuring file
Call Stack (most recent call first):
  CMakeLists.txt:155 (configure_package_config_file)


-- Configuring incomplete, errors occurred!
See also /«PKGBUILDDIR»/obj-x86_64-linux-gnu/CMakeFiles/CMakeOutput.log.

-- 
Kind regards,
Loong Jin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1401238

Title:
  bump to new 0.4.30 version

Status in libzen package in Ubuntu:
  New

Bug description:
  Please update to the latest upstream release.
  Also manually add missed cmake files. Then rebuild with cmake. It is need to 
have cmake config modules for ZenLib.
  Look at Fedora package for example. 
http://pkgs.fedoraproject.org/cgit/libzen.git/commit/?id=de88f55ad00bef4c79595f69c8e71066cfc20eff

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

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

Re: [Touch-packages] [Bug 1401238] Re: bump to new 0.4.30 version

2015-01-07 Thread Chow Loong Jin 
On Wed, Jan 07, 2015 at 08:08:15AM -, Ivan Romanov wrote:
 Was:
 libzen.so - libzen.so.0.0.0
 libzen.so.0 - libzen.so.0.0.0
 libzen.so.0.0.0
 
 Now:
 libzen.so - libzen.so.0
 libzen.so.0 - libzen.so.0.4.30
 libzen.so.0.4.30

Oh, it actually did that? Hmm, let me give it another go.

-- 
Kind regards,
Loong Jin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1401238

Title:
  bump to new 0.4.30 version

Status in libzen package in Ubuntu:
  New

Bug description:
  Please update to the latest upstream release.
  Also manually add missed cmake files. Then rebuild with cmake. It is need to 
have cmake config modules for ZenLib.
  Look at Fedora package for example. 
http://pkgs.fedoraproject.org/cgit/libzen.git/commit/?id=de88f55ad00bef4c79595f69c8e71066cfc20eff

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

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

Re: [Touch-packages] [Bug 1401238] Re: bump to new 0.4.30 version

2015-01-06 Thread Chow Loong Jin 
On Sun, Dec 21, 2014 at 07:50:32PM -, Ivan Romanov wrote:
 I would say that it's very very strange ))).
 Thanks for explanations. I will do.

No, don't bother. I'm the Debian maintainer, and have seen this bug.

In fact, I saw this bug before making the zenlib update, but decided against
switching to the CMake build system because it doesn't handle the library
SOVERSIOn properly. The autotools build system looks very much better maintained
than the CMake build system so I will stick with that.

On the other hand, the missing .cmake file in the -dev package is a valid
concern, so I'll just work on getting that file installed.

-- 
Kind regards,
Loong Jin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1401238

Title:
  bump to new 0.4.30 version

Status in libzen package in Ubuntu:
  New

Bug description:
  Please update to the latest upstream release.
  Also manually add missed cmake files. Then rebuild with cmake. It is need to 
have cmake config modules for ZenLib.
  Look at Fedora package for example. 
http://pkgs.fedoraproject.org/cgit/libzen.git/commit/?id=de88f55ad00bef4c79595f69c8e71066cfc20eff

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

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

[Touch-packages] [Bug 1392588] [NEW] whoopsie's postinst fails when systemd is running and report_crashes=false in /etc/default/whoopsie

2014-11-13 Thread Chow Loong Jin 
Public bug reported:

Here's the output of systemctl status whoopsie

whoopsie.service - crash report submission daemon
   Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled)
   Active: failed (Result: start-limit) since Fri 2014-11-14 12:51:17 SGT; 
11min ago
  Process: 29535 ExecStartPre=/bin/grep -sqi report_crashes=true 
/etc/default/whoopsie (code=exited, status=1/FAILURE)

As you can see, ExecStartPre intentionally fails the starting of
whoopsie.service when report_crashes=true is not found. This is fine,
and done even during the upstart days.

However, the postinst doesn't seem to handle it so well. I added set -x
to /var/lib/dpkg/info/whoopsie.postinst, and found the following output:

Setting up whoopsie (0.2.39ubuntu0.1) ...
+ [ configure = configure ]
+ getent passwd whoopsie
+ mkdir -p -m 3777 /var/crash
+ chmod g+s /var/crash
+ chgrp whoopsie /var/crash
+ chgrp whoopsie /var/crash/whoopsie.0.crash
+ chmod 0640 /var/crash/whoopsie.0.crash
+ mkdir -p -m 3777 /var/metrics
+ chmod g+s /var/metrics
+ chgrp whoopsie /var/metrics
+ deb-systemd-helper unmask whoopsie.service
+ deb-systemd-helper --quiet was-enabled whoopsie.service
+ deb-systemd-helper enable whoopsie.service
+ [ -x /etc/init.d/whoopsie ]
+ [ -x /etc/init.d/whoopsie ]
+ [ -e /etc/init/whoopsie.conf ]
+ invoke-rc.d whoopsie start
Job for whoopsie.service failed. See 'systemctl status whoopsie.service' and 
'journalctl -xn' for details.
invoke-rc.d: initscript whoopsie, action start failed.
+ exit 1
dpkg: error processing package whoopsie (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 whoopsie


The affected section in the postinst looks like this:
# Automatically added by dh_installinit
if [ -x /etc/init.d/whoopsie ]; then
update-rc.d whoopsie defaults /dev/null
fi
if [ -x /etc/init.d/whoopsie ] || [ -e /etc/init/whoopsie.conf ]; then
invoke-rc.d whoopsie start || exit $?
fi
# End automatically added section

I'm not sure if the packaging of whoopsie is at fault, or dh_installinit
is at fault here. In the first place, is it right to fail a package
upgrade just because the service refuses to launch?

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: whoopsie 0.2.39ubuntu0.1
Uname: Linux 3.16.2-hyper1 x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashReports: 640:0:154:278767:2014-11-14 09:48:15.120531913 +0800:2014-11-14 
09:48:14.926532689 +0800:/var/crash/whoopsie.0.crash
CurrentDesktop: Unity
Date: Fri Nov 14 12:57:19 2014
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: Upgraded to utopic on 2014-10-23 (21 days ago)
modified.conffile..etc.default.whoopsie:
 [General]
 report_crashes=false
 report_metrics=false
mtime.conffile..etc.default.whoopsie: 2014-11-14T09:52:54.378414

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

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


** Tags: amd64 apport-bug autoreport-false utopic

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1392588

Title:
  whoopsie's postinst fails when systemd is running and
  report_crashes=false in /etc/default/whoopsie

Status in “debhelper” package in Ubuntu:
  New
Status in “whoopsie” package in Ubuntu:
  New

Bug description:
  Here's the output of systemctl status whoopsie

  whoopsie.service - crash report submission daemon
 Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled)
 Active: failed (Result: start-limit) since Fri 2014-11-14 12:51:17 SGT; 
11min ago
Process: 29535 ExecStartPre=/bin/grep -sqi report_crashes=true 
/etc/default/whoopsie (code=exited, status=1/FAILURE)

  As you can see, ExecStartPre intentionally fails the starting of
  whoopsie.service when report_crashes=true is not found. This is fine,
  and done even during the upstart days.

  However, the postinst doesn't seem to handle it so well. I added set
  -x to /var/lib/dpkg/info/whoopsie.postinst, and found the following
  output:

  Setting up whoopsie (0.2.39ubuntu0.1) ...
  + [ configure = configure ]
  + getent passwd whoopsie
  + mkdir -p -m 3777 /var/crash
  + chmod g+s /var/crash
  + chgrp whoopsie /var/crash
  + chgrp whoopsie /var/crash/whoopsie.0.crash
  + chmod 0640 /var/crash/whoopsie.0.crash
  + mkdir -p -m 3777 /var/metrics
  + chmod g+s /var/metrics
  + chgrp whoopsie /var/metrics
  + deb-systemd-helper unmask whoopsie.service
  + deb-systemd-helper --quiet was-enabled whoopsie.service
  + deb-systemd-helper enable whoopsie.service
  + [ -x /etc/init.d/whoopsie ]
  + [ -x /etc/init.d/whoopsie ]
  + [ -e /etc/init/whoopsie.conf ]
  + invoke-rc.d whoopsie start
  Job for whoopsie.service failed. See 'systemctl status whoopsie.service'

[Touch-packages] [Bug 1392588] Re: whoopsie's postinst fails when systemd is running and report_crashes=false in /etc/default/whoopsie

2014-11-13 Thread Chow Loong Jin 
Setting report_crashes=true in /etc/default/whoopsie at least allows
dpkg to complete:

Setting up whoopsie (0.2.39ubuntu0.1) ...
+ [ configure = configure ]
+ getent passwd whoopsie
+ mkdir -p -m 3777 /var/crash
+ chmod g+s /var/crash
+ chgrp whoopsie /var/crash
+ chgrp whoopsie /var/crash/whoopsie.0.crash
+ chmod 0640 /var/crash/whoopsie.0.crash
+ mkdir -p -m 3777 /var/metrics
+ chmod g+s /var/metrics
+ chgrp whoopsie /var/metrics
+ deb-systemd-helper unmask whoopsie.service
+ deb-systemd-helper --quiet was-enabled whoopsie.service
+ deb-systemd-helper enable whoopsie.service
+ [ -x /etc/init.d/whoopsie ]
+ [ -x /etc/init.d/whoopsie ]
+ [ -e /etc/init/whoopsie.conf ]
+ invoke-rc.d whoopsie start
+ [ -d /run/systemd/system ]
+ systemctl --system daemon-reload
+ deb-systemd-invoke start whoopsie.service
+ dpkg-maintscript-helper rm_conffile /etc/cron.daily/whoopsie 0.1.25 -- 
configure 0.2.39
+ exit 0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1392588

Title:
  whoopsie's postinst fails when systemd is running and
  report_crashes=false in /etc/default/whoopsie

Status in “debhelper” package in Ubuntu:
  New
Status in “whoopsie” package in Ubuntu:
  New

Bug description:
  Here's the output of systemctl status whoopsie

  whoopsie.service - crash report submission daemon
 Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled)
 Active: failed (Result: start-limit) since Fri 2014-11-14 12:51:17 SGT; 
11min ago
Process: 29535 ExecStartPre=/bin/grep -sqi report_crashes=true 
/etc/default/whoopsie (code=exited, status=1/FAILURE)

  As you can see, ExecStartPre intentionally fails the starting of
  whoopsie.service when report_crashes=true is not found. This is fine,
  and done even during the upstart days.

  However, the postinst doesn't seem to handle it so well. I added set
  -x to /var/lib/dpkg/info/whoopsie.postinst, and found the following
  output:

  Setting up whoopsie (0.2.39ubuntu0.1) ...
  + [ configure = configure ]
  + getent passwd whoopsie
  + mkdir -p -m 3777 /var/crash
  + chmod g+s /var/crash
  + chgrp whoopsie /var/crash
  + chgrp whoopsie /var/crash/whoopsie.0.crash
  + chmod 0640 /var/crash/whoopsie.0.crash
  + mkdir -p -m 3777 /var/metrics
  + chmod g+s /var/metrics
  + chgrp whoopsie /var/metrics
  + deb-systemd-helper unmask whoopsie.service
  + deb-systemd-helper --quiet was-enabled whoopsie.service
  + deb-systemd-helper enable whoopsie.service
  + [ -x /etc/init.d/whoopsie ]
  + [ -x /etc/init.d/whoopsie ]
  + [ -e /etc/init/whoopsie.conf ]
  + invoke-rc.d whoopsie start
  Job for whoopsie.service failed. See 'systemctl status whoopsie.service' and 
'journalctl -xn' for details.
  invoke-rc.d: initscript whoopsie, action start failed.
  + exit 1
  dpkg: error processing package whoopsie (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   whoopsie

  
  The affected section in the postinst looks like this:
  # Automatically added by dh_installinit
  if [ -x /etc/init.d/whoopsie ]; then
update-rc.d whoopsie defaults /dev/null
  fi
  if [ -x /etc/init.d/whoopsie ] || [ -e /etc/init/whoopsie.conf ]; then
invoke-rc.d whoopsie start || exit $?
  fi
  # End automatically added section

  I'm not sure if the packaging of whoopsie is at fault, or
  dh_installinit is at fault here. In the first place, is it right to
  fail a package upgrade just because the service refuses to launch?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: whoopsie 0.2.39ubuntu0.1
  Uname: Linux 3.16.2-hyper1 x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CrashReports: 640:0:154:278767:2014-11-14 09:48:15.120531913 +0800:2014-11-14 
09:48:14.926532689 +0800:/var/crash/whoopsie.0.crash
  CurrentDesktop: Unity
  Date: Fri Nov 14 12:57:19 2014
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: Upgraded to utopic on 2014-10-23 (21 days ago)
  modified.conffile..etc.default.whoopsie:
   [General]
   report_crashes=false
   report_metrics=false
  mtime.conffile..etc.default.whoopsie: 2014-11-14T09:52:54.378414

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

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

Re: [Touch-packages] [Bug 474514] Re: Banshee very slow when interacting with track lists

2014-10-26 Thread Chow Loong Jin 
On Sun, Oct 26, 2014 at 10:04:12PM -, Si Dedman wrote:
 Hi Chow, all,
 I'm getting what I think is a similar thing: 100% use of one CPU core after
 saving any tags edits (2.4ghz dual core E6600); generally sluggish
 performance. I've turned BPM detection off  podcast support off. I just ran
 the debug command as per your advice to Myk, made one tag edit, saved, waited
 til the CPU dropped back to idle (~15 seconds) then closed  pasted the
 (visible) terminal to a file. The file makes no mention of the file I tagged
 though, which seems odd?

Why don't you attach the output and let me see?

 Banshee v2.62 on xubuntu 14.10 (was the same on 14.04).
 
 p.s. is there a daily PPA?

Yes there is, but it's disabled for now -- there's been a migration from Gtk2 to
Gtk3, and that's not been done for some of the intermediate libraries in the
dependency chain (libgpod).

-- 
Kind regards,
Loong Jin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sqlite3 in Ubuntu.
https://bugs.launchpad.net/bugs/474514

Title:
  Banshee very slow when interacting with track lists

Status in “banshee” package in Ubuntu:
  Fix Released
Status in “sqlite3” package in Ubuntu:
  Invalid
Status in “banshee” package in Debian:
  Invalid
Status in “sqlite3” package in Debian:
  Invalid

Bug description:
  Binary package hint: banshee

  Banshee's great, but since I've added a few more songs it's become
  unbearably slow.

  Scrolling up and down the library is ok, provided it's settled for a
  while, However, whenever a song finishes playing or I rate a track or
  skip a track there's a delay whist 2 of my 8 CPU cores are maxed out.
  The UI takes an age to redraw or respond to clicks. The delay can be
  just half a second, or sometimes around 5. This usually coincides with
  some network activity.

  It makes interacting with the application nearly unbearable. Don't
  want to go back to Rhythmbox, but might have to :(

  I have:
  * Banshee 1.6 Beta 2 (1.5.1)
  * about 5,300 songs in the library
  * Ubuntu 9.10 Karmic 64bit
  * 6Gb of memory and an i7 920 processor

  Banshee extensions running:
  * Audio CD Support
  * Bookmarks
  * Cover Art Fetching
  * DAAP
  * Digital Media Player Support
  * IPod Support
  * Karma Support
  * Mass Storage Media Player Support
  * MTP Media Player Support
  * File System Queue
  * Internet Radio
  * Last.fm Radio  Scrobbling
  * Multimedia Keys
  * Play Queue
  * Importers for Amarok  Rhythmbox
  * Podcasts

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

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

Re: [Touch-packages] [Bug 1374249] Re: Scrolling works erratically when sound center balance is off-center

2014-10-02 Thread Chow Loong Jin 
On Wed, Oct 01, 2014 at 02:55:25PM -, Lars Uebernickel wrote:
 Indeed, good catch. The sound menu always manipulated the left channel.
 
 I've attached a branch fixes most of the problem by making it handle
 channels in the same way that system settings does. Changing the volume
 to 0 still resets the balance to center, though (same as in system
 settings).

I'm not sure it should reset the balance to center. Shouldn't it recall the last
balance setting and try to preserve that? FWIW, the system settings also
functions a little weirdly -- if you try to click and drag the volume control
around in the system settings, it starts jumping around like it wants to reduce
its volume instead of following your cursor. Scrolling seems to work as expected
in the system settings though.

-- 
Kind regards,
Loong Jin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1374249

Title:
  Scrolling works erratically when sound center balance is off-center

Status in “indicator-sound” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Triaged

Bug description:
  When the center balance is adjusted to the right, scrolling on the
  volume icon in the panel produces erratic results. The same thing
  happens when trying to adjust the volume in the sound menu. The volume
  buttons still function correctly though.

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

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

[Touch-packages] [Bug 1374249] Re: Scrolling works erratically when sound center balance is off-center

2014-09-25 Thread Chow Loong Jin 
Dragging the handle on the sound menu seems to indicate that it keeps
trying to go down instead of following the mouse. Also, when it hits 0,
the sound center balance is reset to 0 (right in the center).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1374249

Title:
  Scrolling works erratically when sound center balance is off-center

Status in “indicator-sound” package in Ubuntu:
  New

Bug description:
  When the center balance is adjusted to the right, scrolling on the
  volume icon in the panel produces erratic results. The same thing
  happens when trying to adjust the volume in the sound menu. The volume
  buttons still function correctly though.

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

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

[Touch-packages] [Bug 1369369] [NEW] → and ← characters overlap with the next character

2014-09-14 Thread Chow Loong Jin 
Public bug reported:

When using Ubuntu Mono in gnome-terminal, → and ← characters overlap
into the next character. This is somewhat fine if they are surrounded by
spaces, but it's hard to read when someone does a→b with no spaces
around the arrow.

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

** Affects: ubuntu-font-family-sources (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-font-family-sources
in Ubuntu.
https://bugs.launchpad.net/bugs/1369369

Title:
  → and ← characters overlap with the next character

Status in “gnome-terminal” package in Ubuntu:
  New
Status in “ubuntu-font-family-sources” package in Ubuntu:
  New

Bug description:
  When using Ubuntu Mono in gnome-terminal, → and ← characters overlap
  into the next character. This is somewhat fine if they are surrounded
  by spaces, but it's hard to read when someone does a→b with no spaces
  around the arrow.

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

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

[Touch-packages] [Bug 1369369] Re: → and ← characters overlap with the next character

2014-09-14 Thread Chow Loong Jin 
Okay, seeing how it appears to render fine in Chromium, this might be
more of a gnome-terminal issue and less of a font issue.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-font-family-sources
in Ubuntu.
https://bugs.launchpad.net/bugs/1369369

Title:
  → and ← characters overlap with the next character

Status in “gnome-terminal” package in Ubuntu:
  New
Status in “ubuntu-font-family-sources” package in Ubuntu:
  New

Bug description:
  When using Ubuntu Mono in gnome-terminal, → and ← characters overlap
  into the next character. This is somewhat fine if they are surrounded
  by spaces, but it's hard to read when someone does a→b with no spaces
  around the arrow.

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

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

[Touch-packages] [Bug 1369369] Re: → and ← characters overlap with the next character

2014-09-14 Thread Chow Loong Jin 
-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-font-family-sources
in Ubuntu.
https://bugs.launchpad.net/bugs/1369369

Title:
  → and ← characters overlap with the next character

Status in “gnome-terminal” package in Ubuntu:
  New
Status in “ubuntu-font-family-sources” package in Ubuntu:
  New

Bug description:
  When using Ubuntu Mono in gnome-terminal, → and ← characters overlap
  into the next character. This is somewhat fine if they are surrounded
  by spaces, but it's hard to read when someone does a→b with no spaces
  around the arrow.

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

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

[Touch-packages] [Bug 1369369] Re: → and ← characters overlap with the next character

2014-09-14 Thread Chow Loong Jin 
** Attachment added: Screenshot showing gnome-terminal, emacs (X11), and urxvt 
rendering the same text
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1369369/+attachment/4204093/+files/screenshot19.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-font-family-sources
in Ubuntu.
https://bugs.launchpad.net/bugs/1369369

Title:
  → and ← characters overlap with the next character

Status in “gnome-terminal” package in Ubuntu:
  New
Status in “ubuntu-font-family-sources” package in Ubuntu:
  New

Bug description:
  When using Ubuntu Mono in gnome-terminal, → and ← characters overlap
  into the next character. This is somewhat fine if they are surrounded
  by spaces, but it's hard to read when someone does a→b with no spaces
  around the arrow.

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

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

Re: [Touch-packages] [Bug 1340349] Re: [Precision WorkStation T3500, Analog Devices AD1984A, Green Headphone Out, Front] equalizer problem

2014-07-17 Thread Chow Loong Jin 
On Thu, Jul 17, 2014 at 06:33:12PM -, Dave wrote:
 Sorry for the slow reply.  I installed libgstreamer dbg as above, and
 already had libc6-dbg.  I did the sysctl, but it had no effect.  My
 /usr/bin/banshee is owned by root:root, so as suggested in the output
 above I ran it as sudo banshee --debug, but it no longer recognized my
 CD player.  I fired up a random podcast instead, and caused the crash
 once more by simply bringing up the Equalizer with Ctrl-E, seeing that
 was already set to Classical and Enabled, turned off Enabled and turned
 it on again.  Dump attached.
 
 
 ** Attachment added: output from   sudo banshee --debug 21 | tee 
 bansheeCrash.txt

 https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1340349/+attachment/4154906/+files/bansheeCrash.txt

Okay, I'm not really sure what's going on here. Let's just add a gstreamer1.0
task to this bug.

  affects ubuntu/gstreamer1.0
  affects ubuntu/gst-plugins-good1.0

-- 
Kind regards,
Loong Jin


** Also affects: gstreamer1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gst-plugins-good1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [Precision WorkStation T3500, Analog Devices AD1984A, Green Headphone
  Out, Front] equalizer problem

Status in “banshee” package in Ubuntu:
  Incomplete
Status in “gst-plugins-good1.0” package in Ubuntu:
  New
Status in “gstreamer1.0” package in Ubuntu:
  New

Bug description:
  Running Banshee and listening to a CD, hit Ctrl-E to bring up the
  equalizer, changed it from Rock to Classical, and then clicked the
  checkbox to Enable it ... and Banshee locked, then crashed.  Music
  stopped the instant I clicked enable.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dscheele   1949 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 10 13:57:15 2014
  InstallationDate: Installed on 2011-11-17 (966 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: Volume slider, or mixer problems
  Title: [Precision WorkStation T3500, Analog Devices AD1984A, Green Headphone 
Out, Front] volume slider problem
  UpgradeStatus: Upgraded to trusty on 2014-07-08 (2 days ago)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 09KPNV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd04/20/2011:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T3500
  dmi.sys.vendor: Dell Inc.

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

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