[Touch-packages] [Bug 1863148] Re: RFE: update libjson-c-dev to 0.13

[stsp]

But are you sure the API was changed
rather than extended? Are there any
evidences that the transition will be
needed?

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

Title:
  RFE: update libjson-c-dev to 0.13

Status in json-c package in Ubuntu:
  Fix Released
Status in json-c source package in Precise:
  Won't Fix
Status in json-c source package in Trusty:
  Won't Fix
Status in json-c source package in Xenial:
  Won't Fix
Status in json-c source package in Bionic:
  Won't Fix

Bug description:
  All versions of libjson-c-dev prior to 0.13
  lack the json_pointer API. As the result, libjson-c-dev
  is only useful since Eoan, which is very disappointing.
  Please update json-c to 0.13 on every supported distro
  prior to Eoan (Disco, Bionic, Xenial etc).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1863148/+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 1863148] [NEW] RFE: update libjson-c-dev to 0.13

[stsp]

Public bug reported:

All versions of libjson-c-dev prior to 0.13
lack the json_pointer API. As the result, libjson-c-dev
is only useful since Eoan, which is very disappointing.
Please update json-c to 0.13 on every supported distro
prior to Eoan (Disco, Bionic, Xenial etc).

** Affects: json-c (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  RFE: update libjson-c-dev to 0.13

Status in json-c package in Ubuntu:
  New

Bug description:
  All versions of libjson-c-dev prior to 0.13
  lack the json_pointer API. As the result, libjson-c-dev
  is only useful since Eoan, which is very disappointing.
  Please update json-c to 0.13 on every supported distro
  prior to Eoan (Disco, Bionic, Xenial etc).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1863148/+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 1832417] [NEW] wrong soundfont path

[stsp]

Public bug reported:

libfliudsynth provides an API to locate the default
soundfonts. Its like below:

ret = fluid_settings_dupstr(settings, "synth.default-soundfont", );
if (ret == 0 || access(sfont, R_OK) != 0) {
ret = fluid_synth_sfload(synth, sfont, TRUE);
}

Under ubuntu it returns
/usr/share/soundfonts/default.sf2
but its unclear what package provides this,
if any. At least not fluid-soundfont-gm.

This font path can be specified during fluidsynth
build. The valid one under ubuntu seems to be
/usr/share/sounds/sf2/FluidR3_GM.sf2
But as this font may not be installed, I would
suggest fluidsynth to check against the pre-defined
list of pathes, and return error if nothing is found.

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

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

Title:
  wrong soundfont path

Status in fluidsynth package in Ubuntu:
  New

Bug description:
  libfliudsynth provides an API to locate the default
  soundfonts. Its like below:

  ret = fluid_settings_dupstr(settings, "synth.default-soundfont", );
  if (ret == 0 || access(sfont, R_OK) != 0) {
  ret = fluid_synth_sfload(synth, sfont, TRUE);
  }

  Under ubuntu it returns
  /usr/share/soundfonts/default.sf2
  but its unclear what package provides this,
  if any. At least not fluid-soundfont-gm.

  This font path can be specified during fluidsynth
  build. The valid one under ubuntu seems to be
  /usr/share/sounds/sf2/FluidR3_GM.sf2
  But as this font may not be installed, I would
  suggest fluidsynth to check against the pre-defined
  list of pathes, and return error if nothing is found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/1832417/+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 1749443] [NEW] ioctl FBIOPUT_VSCREENINFO: Invalid argument

[stsp]

Public bug reported:

$ fbset 768x576-75
ioctl FBIOPUT_VSCREENINFO: Invalid argument

And the same happens with all other modes
defined in /etc/fb.modes

The problem seems to be that KMS fbcon does
not accept the pixclock parameter, which is
the first parameter in a "timings" string.
Changing it to 0 for all modes makes them to
work, albeit w/o actual resizing. The image
then just occupies the upper-left corner of
the screen. But its still better than the
complete failure.
I suppose also other timing params are not
supported. At least if you run fbset w/o
parameters, it will display all timing params
set to zero.
So I think zeroing "timings" for all modes
in /etc/fb.modes will help with KMS.

Additionally, please add the 1920x1080 mode,
its currently missing.

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

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

Title:
  ioctl FBIOPUT_VSCREENINFO: Invalid argument

Status in fbset package in Ubuntu:
  New

Bug description:
  $ fbset 768x576-75
  ioctl FBIOPUT_VSCREENINFO: Invalid argument

  And the same happens with all other modes
  defined in /etc/fb.modes

  The problem seems to be that KMS fbcon does
  not accept the pixclock parameter, which is
  the first parameter in a "timings" string.
  Changing it to 0 for all modes makes them to
  work, albeit w/o actual resizing. The image
  then just occupies the upper-left corner of
  the screen. But its still better than the
  complete failure.
  I suppose also other timing params are not
  supported. At least if you run fbset w/o
  parameters, it will display all timing params
  set to zero.
  So I think zeroing "timings" for all modes
  in /etc/fb.modes will help with KMS.

  Additionally, please add the 1920x1080 mode,
  its currently missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fbset/+bug/1749443/+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 1315755] Re: /init: line 327: egrep: not found

[stsp]

This is a problem in Trusty too, if
BUSYBOX=n
in /etc/initramfs-tools/initramfs.conf.
Neither grep nor egrep seems to be added, so
the same error message appears.

** Changed in: initramfs-tools (Ubuntu Trusty)
   Status: Invalid => Confirmed

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

Title:
  /init: line 327: egrep: not found

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Confirmed
Status in initramfs-tools source package in Utopic:
  Fix Released

Bug description:
  I'm using Ubuntu 14.10 dev with upstart 1.12.1-0ubuntu4 and on every
  boot I'm seeing the message "/init: line 327: egrep: not found" but
  egrep is installed on  my system:

  sworddragon@ubuntu:~$ egrep -V
  egrep (GNU grep) 2.18
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Mike Haertel and others, see
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1315755/+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