date:20190222

[Ubuntustudio-bugs] [Bug 1817389] Re: GIMP icon sizes small on large and huge setting

2019-02-22 Thread Talib Pierson

I believe these settings are stored at '~/.config/GIMP/2.10/gimprc',
although bug occurs before setting is saved when "OK" is pressed in
Preferences.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to gimp in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1817389

Title:
  GIMP icon sizes small on large and huge setting

Status in gimp package in Ubuntu:
  New

Bug description:
  Description:
  Increasing the icon size setting increases the size on some UI elements, 
while decreasing the size of others. Sizes appear to increase up to a point, 
but once that point is reached, the size reverts to small. This occurs at large 
for most elements, but some get larger and revert at huge instead.

  Reproduce:
  $ gimp
  click: Edit -> Preferences -> Icon theme (under Interface section) -> Custom 
icon size (drop-down menu)
  then the toolbar icons of "Large" and "Huge" settings on the icon size slider 
are smaller than "Medium", being the same size as "Small" instead.

  Where I've reproduced it:
  Short: gimp 2.10.6 and 2.10.8 on Ubuntu 18.10 and Ubuntu 19.
  Long: I've reproduced it in an Ubuntu 18.10 fresh install and a qemu-kvm 
virtual machine. I've reproduced the problem in gimp 2.10.8 (apt) on Ubuntu 19 
(development branch), so it doesn't look like it is fixed in newer versions.

  Where I couldn't reproduce it:
  When I tried to replicate it on Ubuntu 19 (development branch) with the 
flatpak from the gimp website, the bug did not occur. Same for 18.10. Gimp 
version must also be new enough to have icon size setting.

  NOTE:
  I've reported it on https://gitlab.gnome.org/GNOME/gimp/issues/2313 but 
thought that this bug would benefit from the attention of the Ubuntu 
Community/Canonical, given that the bug was reproduced on Ubuntu, but not on 
Debian, where gimp is an earlier version, or using flatpak. The problem may be 
with the apt installation, since flatpak works, and which the GIMP team might 
not be able to fix as easily as Ubuntu.

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ apt-cache policy gimp
  gimp:
Installed: 2.10.6-3
Candidate: 2.10.6-3
Version table:
   *** 2.10.6-3 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status

  What I expected to happen:
  Icon size increases as slider increases through small, medium, large, and huge

  What happened instead:
  Icon sizes revert to small at large setting, other elements change in 
unexpected ways at huge setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gimp 2.10.6-3
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 19:48:01 2019
  ExecutablePath: /usr/bin/gimp-2.10
  InstallationDate: Installed on 2019-02-11 (11 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=screen-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: gimp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Ubuntustudio-bugs] [Bug 1817389] [NEW] GIMP icon sizes small on large and huge setting

2019-02-22 Thread Talib Pierson

Public bug reported:

Description:
Increasing the icon size setting increases the size on some UI elements, while 
decreasing the size of others. Sizes appear to increase up to a point, but once 
that point is reached, the size reverts to small. This occurs at large for most 
elements, but some get larger and revert at huge instead.

Reproduce:
$ gimp
click: Edit -> Preferences -> Icon theme (under Interface section) -> Custom 
icon size (drop-down menu)
then the toolbar icons of "Large" and "Huge" settings on the icon size slider 
are smaller than "Medium", being the same size as "Small" instead.

Where I've reproduced it:
Short: gimp 2.10.6 and 2.10.8 on Ubuntu 18.10 and Ubuntu 19.
Long: I've reproduced it in an Ubuntu 18.10 fresh install and a qemu-kvm 
virtual machine. I've reproduced the problem in gimp 2.10.8 (apt) on Ubuntu 19 
(development branch), so it doesn't look like it is fixed in newer versions.

Where I couldn't reproduce it:
When I tried to replicate it on Ubuntu 19 (development branch) with the flatpak 
from the gimp website, the bug did not occur. Same for 18.10. Gimp version must 
also be new enough to have icon size setting.

NOTE:
I've reported it on https://gitlab.gnome.org/GNOME/gimp/issues/2313 but thought 
that this bug would benefit from the attention of the Ubuntu 
Community/Canonical, given that the bug was reproduced on Ubuntu, but not on 
Debian, where gimp is an earlier version, or using flatpak. The problem may be 
with the apt installation, since flatpak works, and which the GIMP team might 
not be able to fix as easily as Ubuntu.

$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

$ apt-cache policy gimp
gimp:
  Installed: 2.10.6-3
  Candidate: 2.10.6-3
  Version table:
 *** 2.10.6-3 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
100 /var/lib/dpkg/status

What I expected to happen:
Icon size increases as slider increases through small, medium, large, and huge

What happened instead:
Icon sizes revert to small at large setting, other elements change in 
unexpected ways at huge setting.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gimp 2.10.6-3
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 22 19:48:01 2019
ExecutablePath: /usr/bin/gimp-2.10
InstallationDate: Installed on 2019-02-11 (11 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=screen-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: gimp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to gimp in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1817389

Title:
  GIMP icon sizes small on large and huge setting

Status in gimp package in Ubuntu:
  New

Bug description:
  Description:
  Increasing the icon size setting increases the size on some UI elements, 
while decreasing the size of others. Sizes appear to increase up to a point, 
but once that point is reached, the size reverts to small. This occurs at large 
for most elements, but some get larger and revert at huge instead.

  Reproduce:
  $ gimp
  click: Edit -> Preferences -> Icon theme (under Interface section) -> Custom 
icon size (drop-down menu)
  then the toolbar icons of "Large" and "Huge" settings on the icon size slider 
are smaller than "Medium", being the same size as "Small" instead.

  Where I've reproduced it:
  Short: gimp 2.10.6 and 2.10.8 on Ubuntu 18.10 and Ubuntu 19.
  Long: I've reproduced it in an Ubuntu 18.10 fresh install and a qemu-kvm 
virtual machine. I've reproduced the problem in gimp 2.10.8 (apt) on Ubuntu 19 
(development branch), so it doesn't look like it is fixed in newer versions.

  Where I couldn't reproduce it:
  When I tried to replicate it on Ubuntu 19 (development branch) with the 
flatpak from the gimp website, the bug did not occur. Same for 18.10. Gimp 
version must also be new enough to have icon size setting.

  NOTE:
  I've reported it on https://gitlab.gnome.org/GNOME/gimp/issues/2313 but 
thought that this bug would benefit from the attention of the Ubuntu 
Community/Canonical, given that the bug was reproduced on Ubuntu, but not on 
Debian, where gimp is an earlier version, or using flatpak. The problem may be 
with the apt installation, since flatpak works, and which the GIMP team might 
not be able to fix as easily as Ubuntu.

  $ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  $ apt-cache policy gimp
  gimp:
Installed: 2.10.6-3
Candidate: 2.10.6-3
Version table:
   *** 2.10.6-3 500

[Ubuntustudio-bugs] [Bug 305901] Re: Intrepid gcc -O2 breaks string appending with sprintf(), due to fortify source patch

2019-02-22 Thread Bug Watch Updater

** Changed in: glibc
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacious-plugins in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/305901

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FORTIFY_SOURCE).

  One might argue that this usage of sprintf() is questionable.  I had
  been under the impression that it is valid, and found many web pages
  that agree with me, though I was not able to find an authoritative
  statement either way citing the C specification.  I decided to
  investigate how common this pattern is in real source code.

  You can search a source file for instances of it with this regex:
pcregrep -M 'sprintf\s*\(\s*([^,]*)\s*,\s*"%s[^"]*"\s*,\s*\1\s*,'

  To determine how common the pattern is, I wrote a script to track down 
instances using Google Code Search, and found 2888 matches:

  (For the curious: the script uses a variant of the regex above.  I had to use 
a binary search to emulate backreferences, which aren’t supported by Code 
Search, so the script makes 46188 queries and takes a

[Ubuntustudio-bugs] [Bug 305901]

2019-02-22 Thread Siddhesh-n

There was a pretty lengthy discussion on this late last year:

https://sourceware.org/ml/libc-alpha/2018-12/msg00838.html

where the behaviour breakage was introduced in the non-fortified path
and then reverted.  It might be a good idea to resume that discussion
for the fortified case as well.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacious-plugins in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/305901

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FORTIFY_SOURCE).

  One might argue that this usage of sprintf() is questionable.  I had
  been under the impression that it is valid, and found many web pages
  that agree with me, though I was not able to find an authoritative
  statement either way citing the C specification.  I decided to
  investigate how common this pattern is in real source code.

  You can search a source file for instances of it with this regex:
pcregrep -M 'sprintf\s*\(\s*([^,]*)\s*,\s*"%s[^"]*"\s*,\s*\1\s*,'

  To determine how common the pattern is, I wrote a script to track down 
instances using Google Code Search, and found 2888 matches:

[Ubuntustudio-bugs] [Bug 305901]

2019-02-22 Thread Kees Cook

So I'd like to bring this back up and reiterate the issue: there is no
benefit to the early truncation, and it actively breaks lots of existing
software (which is why Debian and Ubuntu have had this fix for 10 years
now).

What is the _benefit_ of early truncation that justifies breaking so
many existing cases?

Can glibc please take this patch? http://paste.ubuntu.com/p/CbrxmSfKD4/

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacious-plugins in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/305901

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FORTIFY_SOURCE).

  One might argue that this usage of sprintf() is questionable.  I had
  been under the impression that it is valid, and found many web pages
  that agree with me, though I was not able to find an authoritative
  statement either way citing the C specification.  I decided to
  investigate how common this pattern is in real source code.

  You can search a source file for instances of it with this regex:
pcregrep -M 'sprintf\s*\(\s*([^,]*)\s*,\s*"%s[^"]*"\s*,\s*\1\s*,'

  To determine how common the pattern is, I wrote a script to track down

[Ubuntustudio-bugs] [Bug 305901]

2019-02-22 Thread Siddhesh-n

It might be a good idea to take this discussion to the libc-alpha
mailing list.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacious-plugins in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/305901

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FORTIFY_SOURCE).

  One might argue that this usage of sprintf() is questionable.  I had
  been under the impression that it is valid, and found many web pages
  that agree with me, though I was not able to find an authoritative
  statement either way citing the C specification.  I decided to
  investigate how common this pattern is in real source code.

  You can search a source file for instances of it with this regex:
pcregrep -M 'sprintf\s*\(\s*([^,]*)\s*,\s*"%s[^"]*"\s*,\s*\1\s*,'

  To determine how common the pattern is, I wrote a script to track down 
instances using Google Code Search, and found 2888 matches:

  (For the curious: the script uses a variant of the regex above.  I had to use 
a binary search to emulate backreferences, which aren’t supported by Code 
Search, so the script makes 46188

[Ubuntustudio-bugs] [Bug 305901]

2019-02-22 Thread Kees Cook

It's not defined in POSIX, but it has worked a certain way in glibc for
decades. There's no _reason_ to break it for _FORTIFY_SOURCE. Pre-
truncating just silently breaks programs and does weird stuff. If you
want to expose it with _FORITFY_SOURCE then have vsprintf notice that
the target and first format argument are the same variable, and refuse
to build.

Either pretruncation should be eliminated, or the undefined behavior
should be explicitly detected and dealt with. Just having programs lose
data while running with no indication of the cause seems like a terrible
user experience.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacious-plugins in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/305901

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FORTIFY_SOURCE).

  One might argue that this usage of sprintf() is questionable.  I had
  been under the impression that it is valid, and found many web pages
  that agree with me, though I was not able to find an authoritative
  statement either way citing the C specification.  I decided to
  investigate how common this pattern is in real source code.

  You can

[Ubuntustudio-bugs] [Bug 305901]

2019-02-22 Thread Andreas Schwab

The point of _FORTIFY_SOURCE is to expose undefined behaviour.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacious-plugins in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/305901

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FORTIFY_SOURCE).

  One might argue that this usage of sprintf() is questionable.  I had
  been under the impression that it is valid, and found many web pages
  that agree with me, though I was not able to find an authoritative
  statement either way citing the C specification.  I decided to
  investigate how common this pattern is in real source code.

  You can search a source file for instances of it with this regex:
pcregrep -M 'sprintf\s*\(\s*([^,]*)\s*,\s*"%s[^"]*"\s*,\s*\1\s*,'

  To determine how common the pattern is, I wrote a script to track down 
instances using Google Code Search, and found 2888 matches:

  (For the curious: the script uses a variant of the regex above.  I had to use 
a binary search to emulate backreferences, which aren’t supported by Code 
Search, so the script makes 46188 queries and takes a

[Ubuntustudio-bugs] [Bug 305901]

2019-02-22 Thread Kees Cook

I'd still like to have this patch applied -- while we can claim the
behavior is "undefined", it is not, in fact, undefined. It behaves one
way without -D_FORTIFY_SOURCE=2, and differently with it. And that
difference doesn't need to exist. Ubuntu carried this patch for quite a
while.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to audacious-plugins in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs, ubuntustudio-bugs: blender
https://bugs.launchpad.net/bugs/305901

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FORTIFY_SOURCE).

  One might argue that this usage of sprintf() is questionable.  I had
  been under the impression that it is valid, and found many web pages
  that agree with me, though I was not able to find an authoritative
  statement either way citing the C specification.  I decided to
  investigate how common this pattern is in real source code.

  You can search a source file for instances of it with this regex:
pcregrep -M 'sprintf\s*\(\s*([^,]*)\s*,\s*"%s[^"]*"\s*,\s*\1\s*,'

  To determine how common the pattern is, I wrote a script to track down 
instances using Google Code Search, and found 2888 matches:

[Ubuntustudio-bugs] [Bug 1817264] Re: [needs-packaging] Upload Carla as a replacement for jack-rack

2019-02-22 Thread Brian Murray

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

- Upload Carla as a replacement for jack-rack
+ [needs-packaging] Upload Carla as a replacement for jack-rack

** Changed in: ubuntustudio-meta (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817264

Title:
  [needs-packaging] Upload Carla as a replacement for jack-rack

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As Debian in in the Buster freeze now, it is not possible to get Carla
  uploaded to Debian in time for Ubuntu Studio 1904.

  I will upload it there eventually (Debian RFP bug):
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804235

  It would be good to get this uploaded to Ubuntu in the meantime.

  Erich has the package working in our Ubuntu Studio autobuilder. I am
  in the process of tidying up the packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817264/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for jack-rack

2019-02-22 Thread Erich Eickmeyer

Just one thing to add: The version I packaged is 1.9.13 (2.0-RC3).
falktx hopes to get 2.0-RC4 soon, and has given himself a rough deadline
for a 2.0 release for the end of March. Depending on the timing, it
would be good to get 2.0 (final) in for either an FFe or SRU, depending
on the timing.

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817264

Title:
  Upload Carla as a replacement for jack-rack

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As Debian in in the Buster freeze now, it is not possible to get Carla
  uploaded to Debian in time for Ubuntu Studio 1904.

  I will upload it there eventually (Debian RFP bug):
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804235

  It would be good to get this uploaded to Ubuntu in the meantime.

  Erich has the package working in our Ubuntu Studio autobuilder. I am
  in the process of tidying up the packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817264/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for jackrack

2019-02-22 Thread Erich Eickmeyer

jack-rack, sorry for the wrong package name.

** Summary changed:

- Upload Carla as a replacement for jackrack
+ Upload Carla as a replacement for jack-rack

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817264

Title:
  Upload Carla as a replacement for jack-rack

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As Debian in in the Buster freeze now, it is not possible to get Carla
  uploaded to Debian in time for Ubuntu Studio 1904.

  I will upload it there eventually (Debian RFP bug):
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804235

  It would be good to get this uploaded to Ubuntu in the meantime.

  Erich has the package working in our Ubuntu Studio autobuilder. I am
  in the process of tidying up the packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817264/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for jackrack

2019-02-22 Thread Erich Eickmeyer

A little change in plans. len-ovenwerks and I discovered that, as it
turns out, Patchage is still in active development despite not having a
release in >3 years.

Either way, Carla is a more intuitive and technologically plugin host
than Jackrack, so that should be what is replaced.

** Summary changed:

- Upload Carla as a replacement for Jackrack
+ Upload Carla as a replacement for jackrack

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817264

Title:
  Upload Carla as a replacement for jack-rack

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As Debian in in the Buster freeze now, it is not possible to get Carla
  uploaded to Debian in time for Ubuntu Studio 1904.

  I will upload it there eventually (Debian RFP bug):
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804235

  It would be good to get this uploaded to Ubuntu in the meantime.

  Erich has the package working in our Ubuntu Studio autobuilder. I am
  in the process of tidying up the packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817264/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1817262] Re: Drop Patchage from Ubuntu Studio seeds once Carla is uploaded

2019-02-22 Thread Erich Eickmeyer

A little change in plans. len-ovenwerks and I discovered that, as it
turns out, Patchage is still in active development despite not having a
release in >3 years.

Either way, Carla is a more intuitive and technologically superior
plugin host than jack-rack, so that should be what is replaced.

** Summary changed:

- Drop Patchage from Ubuntu Studio seeds once Carla is uploaded
+ Drop jack-rack from Ubuntu Studio seeds once Carla is uploaded

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817262

Title:
  Drop jack-rack from Ubuntu Studio seeds once Carla is uploaded

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As discussed on the mailing list:
  
https://lists.ubuntu.com/archives/ubuntu-studio-devel/2019-February/009069.html

  Patchage is not maintained upstream, and Carla can manage the plugin
  patches instead.

  THerefore we should drop patchage from the seeds and add carla instead
  (once it is available).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817262/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for Jackrack

2019-02-22 Thread Len Ovens

** Summary changed:

- Upload Carla as a replacement for patchage 
+ Upload Carla as a replacement for Jackrack

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817264

Title:
  Upload Carla as a replacement for jack-rack

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As Debian in in the Buster freeze now, it is not possible to get Carla
  uploaded to Debian in time for Ubuntu Studio 1904.

  I will upload it there eventually (Debian RFP bug):
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804235

  It would be good to get this uploaded to Ubuntu in the meantime.

  Erich has the package working in our Ubuntu Studio autobuilder. I am
  in the process of tidying up the packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817264/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour

2019-02-22 Thread Kai-Heng Feng

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0-rc7 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc7/

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to The Ubuntu Studio Project.
Matching subscriptions: Ubuntu Studio Bugs, UbuntuStudio Bugs
https://bugs.launchpad.net/bugs/1787857

Title:
  USB mouse cursor lags after random time of correct behaviour

Status in Ubuntu Studio:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in rtirq package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I 
noticed the following behaviour:
  after havig logged in, my USB mouse works normally for about ten seconds, 
then the cursor starts lagging a lot which makes the mouse pretty much unusable.
  The last dmesg always contain lines these: (more in attached file)

  [<9e659b0c>] irq_default_primary_handler threaded 
[] usb_hcd_irq
  [<9e659b0c>] irq_default_primary_handler threaded 
[] _rtl_pci_interrupt [rtl_pci]
  Disabling IRQ #18

  Out of frustration & curiosity I disabled most autostart apps
  (Settings > Session ... > Autostart) and re-enabled them after
  rebooting. Since then I rarely encounter the lagging cursor. If I open
  Settings > Mouse & Touchpad and toggle any option on/off the cursor
  starts lagging.

  How can make the cursor work reliably?
  Some comment in dmesg mentions "irqpoll" boot option

  Ubuntu Studio 18.04.1
  4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT

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

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

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for patchage

2019-02-22 Thread Ross Gammon

** Tags added: needs-packaging

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817264

Title:
  Upload Carla as a replacement for patchage

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As Debian in in the Buster freeze now, it is not possible to get Carla
  uploaded to Debian in time for Ubuntu Studio 1904.

  I will upload it there eventually (Debian RFP bug):
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804235

  It would be good to get this uploaded to Ubuntu in the meantime.

  Erich has the package working in our Ubuntu Studio autobuilder. I am
  in the process of tidying up the packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817264/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1817262] [NEW] Drop Patchage from Ubuntu Studio seeds once Carla is uploaded

2019-02-22 Thread Ross Gammon

Public bug reported:

As discussed on the mailing list:
https://lists.ubuntu.com/archives/ubuntu-studio-devel/2019-February/009069.html

Patchage is not maintained upstream, and Carla can manage the plugin
patches instead.

THerefore we should drop patchage from the seeds and add carla instead
(once it is available).

** Affects: ubuntustudio-meta (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817262

Title:
  Drop Patchage from Ubuntu Studio seeds once Carla is uploaded

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As discussed on the mailing list:
  
https://lists.ubuntu.com/archives/ubuntu-studio-devel/2019-February/009069.html

  Patchage is not maintained upstream, and Carla can manage the plugin
  patches instead.

  THerefore we should drop patchage from the seeds and add carla instead
  (once it is available).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817262/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1817264] [NEW] Upload Carla as a replacement for patchage

2019-02-22 Thread Ross Gammon

Public bug reported:

As Debian in in the Buster freeze now, it is not possible to get Carla
uploaded to Debian in time for Ubuntu Studio 1904.

I will upload it there eventually (Debian RFP bug):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804235

It would be good to get this uploaded to Ubuntu in the meantime.

Erich has the package working in our Ubuntu Studio autobuilder. I am in
the process of tidying up the packaging.

** Affects: ubuntustudio-meta (Ubuntu)
 Importance: Undecided
 Assignee: Ross Gammon (rosco2)
 Status: New

** Changed in: ubuntustudio-meta (Ubuntu)
 Assignee: (unassigned) => Ross Gammon (rosco2)

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/1817264

Title:
  Upload Carla as a replacement for patchage

Status in ubuntustudio-meta package in Ubuntu:
  New

Bug description:
  As Debian in in the Buster freeze now, it is not possible to get Carla
  uploaded to Debian in time for Ubuntu Studio 1904.

  I will upload it there eventually (Debian RFP bug):
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804235

  It would be good to get this uploaded to Ubuntu in the meantime.

  Erich has the package working in our Ubuntu Studio autobuilder. I am
  in the process of tidying up the packaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1817264/+subscriptions

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

[Ubuntustudio-bugs] [Bug 1817389] Re: GIMP icon sizes small on large and huge setting

[Ubuntustudio-bugs] [Bug 1817389] [NEW] GIMP icon sizes small on large and huge setting

[Ubuntustudio-bugs] [Bug 305901] Re: Intrepid gcc -O2 breaks string appending with sprintf(), due to fortify source patch

[Ubuntustudio-bugs] [Bug 305901]

[Ubuntustudio-bugs] [Bug 305901]

[Ubuntustudio-bugs] [Bug 305901]

[Ubuntustudio-bugs] [Bug 305901]

[Ubuntustudio-bugs] [Bug 305901]

[Ubuntustudio-bugs] [Bug 305901]

[Ubuntustudio-bugs] [Bug 1817264] Re: [needs-packaging] Upload Carla as a replacement for jack-rack

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for jack-rack

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for jackrack

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for jackrack

[Ubuntustudio-bugs] [Bug 1817262] Re: Drop Patchage from Ubuntu Studio seeds once Carla is uploaded

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for Jackrack

[Ubuntustudio-bugs] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour

[Ubuntustudio-bugs] [Bug 1817264] Re: Upload Carla as a replacement for patchage

[Ubuntustudio-bugs] [Bug 1817262] [NEW] Drop Patchage from Ubuntu Studio seeds once Carla is uploaded

[Ubuntustudio-bugs] [Bug 1817264] [NEW] Upload Carla as a replacement for patchage

19 matches

Site Navigation

Mail list logo

Footer information