[Ubuntustudio-bugs] [Bug 1334056] Re: LibreOffice opens a TCP port on localhost and doesn't start if the port is blocked

2014-06-24 Thread Seth Arnold
Thanks for this report; I'm unmarking the 'security' flag after a quick
inspection of the changes introduced in the most recent update show
significant reworking of bluetooth connectivity including some work for
remotecontrol devices. It seems more likely to me that requiring a TCP
port to localhost is from these than a mistaken debug mode.

Thanks

** Information type changed from Private Security to Public

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

Title:
  LibreOffice opens a TCP port on localhost and doesn't start if the
  port is blocked

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  I am on Kubuntu 14.04 amd64 with latest packages of everything
  (libreoffice-core = Version: 1:4.2.4-0ubuntu2).

  LibreOffice was working fine until about 2014-06-22 - thats the modification 
date of the last file which I edited with it.
  Somewhere between 2014-06-22 and 2014-06-24, a package was auto-updated and 
now it won't start anymore. 
  It hangs at the splash screen.

  I've figured out the reason: LibreOffice opens a random TCP port on 127.0.0.1 
and tries to connect to it. Because I have blocked connections to localhost in 
my firewall, the connection fails, resulting in the hang. If I open the port, 
it works.
  I cannot add a firewall rule to fix this permanently though because the port 
is chosen randomly.
  And why does a text editor need a TCP port anyway?

  Please do one of the following:
  - Check whether this is debug functionality which has accidentally been left 
in. It might be a security issue, so I filed this as security. Please remove 
the flag if it is not.
  - Add a way of configuring it to disable the TCP stuff.
  - Add a way of configuring which port is used .

  Please do not tell me that denying access to localhost is nonsense:
  There are certain daemons which do not provide authentication
  mechanisms, and there are multiuser machines. If I want to protect
  those daemons on a multiuser machine I need to deny localhost
  connections by default and work with whitelisting allowed types of
  connections.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1334056/+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 1433879] Re: package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

2015-03-18 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libav package in Ubuntu:
  New

Bug description:
  I have no idea

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libavcodec-extra 6:9.18-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Thu Mar 19 06:27:41 2015
  DuplicateSignature: package:libavcodec-extra:6:9.18-0ubuntu0.14.04.1:package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-04-24 (328 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: libav
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  Title: package libavcodec-extra 6:9.18-0ubuntu0.14.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-04-28 (324 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1433879/+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 1574282] Re: package libaudgui3 (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/lib/x86_64-linux-gnu/libaudgui.so.3" presente anche nel pacchetto li

2016-04-25 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libaudgui3 (not installed) failed to install/upgrade: tentata
  sovrascrittura di "/usr/lib/x86_64-linux-gnu/libaudgui.so.3" presente
  anche nel pacchetto libaudcore3:amd64 3.7.2-1~webupd8~xenial0

Status in audacious package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libaudgui3 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun Apr 24 16:14:59 2016
  ErrorMessage: tentata sovrascrittura di 
"/usr/lib/x86_64-linux-gnu/libaudgui.so.3" presente anche nel pacchetto 
libaudcore3:amd64 3.7.2-1~webupd8~xenial0
  InstallationDate: Installed on 2016-03-15 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: audacious
  Title: package libaudgui3 (not installed) failed to install/upgrade: tentata 
sovrascrittura di "/usr/lib/x86_64-linux-gnu/libaudgui.so.3" presente anche nel 
pacchetto libaudcore3:amd64 3.7.2-1~webupd8~xenial0
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1574282/+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 1662513] Re: Update to 9.21 in Trusty

2017-02-07 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is available, members of the security team will review it and
publish the package. See the following link for more information:
https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures

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

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

Title:
  Update to 9.21 in Trusty

Status in libav package in Ubuntu:
  Incomplete

Bug description:
  version 9.21:
  - mpeg12: move setting first_field to mpeg_field_start() (libav/999)
  - mpeg12: avoid signed overflow in bitrate calculation (libav/981)
  - mpegvideo_parser: avoid signed overflow in bitrate calculation (libav/981)
  - avformat/output-example: Declare link dependency on libswscale in the 
Makefile
  - build: output-example: Add avutil to ELIBS in link command

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1662513/+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 1626783] Re: shotwell crashed with SIGSEGV

2016-09-22 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  shotwell crashed with SIGSEGV

Status in shotwell package in Ubuntu:
  New

Bug description:
  pressed Esc when viewing an image

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Sep 23 01:16:16 2016
  ExecutablePath: /usr/bin/shotwell
  ProcCmdline: shotwell 
/media/username/VERBATIM_HD/FOTOS_2015/SONY_DSLR-A700/11550817/_DSC5546.ARW
  SegvAnalysis:
   Segfault happened at: 0x7fd0fcbf8828:mov0x30(%rax),%rax
   PC (0x7fd0fcbf8828) ok
   source "0x30(%rax)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: shotwell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgee-0.8.so.2
   ()
   photo_get_prefetched_copy ()
   photo_get_pixbuf_with_options ()
   ()
  Title: shotwell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse kvm 
libvirtd lpadmin netdev plugdev pulse sambashare saned tape vboxusers video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1626783/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

2016-12-21 Thread Seth Arnold
William, as far as I know the next LTS is still intended to be 18.04.

Our current LTS releases are 12.04, 14.04, and 16.04.

If you wish to upgrade to 14.04 note that Apache2's authentication and
authorization changed drastically. If you wish to upgrade to 16.04 note
that php is now version 7, and many applications aren't yet updated for
php7. Be sure to check the release notes for details of larger changes:
https://wiki.ubuntu.com/Releases

Thanks

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

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/libav/+bug/1643467/+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 1692487] Re: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package fonts-lmodern is not ready for configuration cannot configure (current status 'half-installed')

2017-05-22 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package fonts-lmodern 2.004.5-1 failed to install/upgrade: package
  fonts-lmodern is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in lmodern package in Ubuntu:
  New

Bug description:
  dpkg: error processing package fonts-lmodern (--configure):
   package fonts-lmodern is not ready for configuration
   cannot configure (current status 'half-installed')
  Errors were encountered while processing:
   fonts-lmodern

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-lmodern 2.004.5-1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   fonts-lmodern: Configure
   lmodern: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 12:44:31 2017
  DpkgTerminalLog:
   dpkg: error processing package fonts-lmodern (--configure):
package fonts-lmodern is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package fonts-lmodern is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2015-07-25 (666 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lmodern
  Title: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package 
fonts-lmodern is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to xenial on 2017-05-21 (0 days ago)
  modified.conffile..etc.fonts.conf.avail.65-fonts-lmodern.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lmodern/+bug/1692487/+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 1692487] Re: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package fonts-lmodern is not ready for configuration cannot configure (current status 'half-installed')

2017-05-22 Thread Seth Arnold
Hello,

I suggest trying:

sudo apt-get -f install
sudo dpkg --configure -a

Thanks

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

Title:
  package fonts-lmodern 2.004.5-1 failed to install/upgrade: package
  fonts-lmodern is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in lmodern package in Ubuntu:
  New

Bug description:
  dpkg: error processing package fonts-lmodern (--configure):
   package fonts-lmodern is not ready for configuration
   cannot configure (current status 'half-installed')
  Errors were encountered while processing:
   fonts-lmodern

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fonts-lmodern 2.004.5-1
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   fonts-lmodern: Configure
   lmodern: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Mon May 22 12:44:31 2017
  DpkgTerminalLog:
   dpkg: error processing package fonts-lmodern (--configure):
package fonts-lmodern is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package fonts-lmodern is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2015-07-25 (666 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: lmodern
  Title: package fonts-lmodern 2.004.5-1 failed to install/upgrade: package 
fonts-lmodern is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to xenial on 2017-05-21 (0 days ago)
  modified.conffile..etc.fonts.conf.avail.65-fonts-lmodern.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lmodern/+bug/1692487/+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 1726014] Re: gimp-2.8 crashed with SIGSEGV in printf_positional()

2017-10-23 Thread Seth Arnold
** Information type changed from Private Security to Public

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

Title:
  gimp-2.8 crashed with SIGSEGV in printf_positional()

Status in gimp package in Ubuntu:
  New

Bug description:
  I opened a photo in gimp. Tryed to cut a part og photo. Trhen tryed to
  revert, but gimp was crushed and after that couldn't opened a gimp.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gimp 2.8.20-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 15:34:51 2017
  ExecutablePath: /usr/bin/gimp-2.8
  ProcCmdline: gimp-2.8
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=hr_HR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7ff703418416 <__strlen_sse2+38>: movdqu 
(%rax),%xmm4
   PC (0x7ff703418416) ok
   source "(%rax)" (0x0009) not located in a known VMA region (needed 
readable region)!
   destination "%xmm4" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gimp
  StacktraceTop:
   printf_positional (s=s@entry=0x7fffaa0609a0, 
format=format@entry=0x7ff707c4a4fb , readonly_format=readonly_format@entry=0, 
ap=ap@entry=0x7fffaa060b30, ap_savep=ap_savep@entry=0x7fffaa060548, done=22, 
nspecs_done=1, lead_str_end=, work_buffer=, 
save_errno=, grouping=, thousands_sep=) at vfprintf.c:2023
   _IO_vfprintf_internal (s=s@entry=0x7fffaa0609a0, format=, 
format@entry=0x7ff707c4a4fb , ap=ap@entry=0x7fffaa060b30) at vfprintf.c:1688
   __GI___vasprintf_chk (result_ptr=0x7fffaa060af0, flags=1, 
format=0x7ff707c4a4fb , 
args=0x7fffaa060b30) at vasprintf_chk.c:66
   g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gimp-2.8 crashed with SIGSEGV in printf_positional()
  UpgradeStatus: Upgraded to artful on 2017-10-19 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1726014/+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 1759859] Re: hydrogen crashed with SIGSEGV in H2Core::InstrumentComponent::get_layer()

2018-03-29 Thread Seth Arnold
By the way, check your CPU fan, your CPU is overheating.

Thanks

** Information type changed from Private Security to Public

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

Title:
  hydrogen crashed with SIGSEGV in
  H2Core::InstrumentComponent::get_layer()

Status in hydrogen package in Ubuntu:
  New

Bug description:
  Hydrogen keeps crashing when run with OBS

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: hydrogen 0.9.7-6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Mar 29 13:13:01 2018
  ExecutablePath: /usr/bin/hydrogen
  InstallationDate: Installed on 2018-03-28 (1 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  ProcCmdline: /usr/bin/hydrogen
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x56511cbdad92 
<_ZN6H2Core7Sampler13__render_noteEPNS_4NoteEjPNS_4SongE+594>:  mov
0x18(%rax),%r11
   PC (0x56511cbdad92) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%r11" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: hydrogen
  StacktraceTop:
   H2Core::Sampler::__render_note(H2Core::Note*, unsigned int, H2Core::Song*) ()
   H2Core::Sampler::process(unsigned int, H2Core::Song*) ()
   H2Core::audioEngine_process(unsigned int, void*) ()
   H2Core::alsaAudioDriver_processCaller(void*) ()
   start_thread (arg=0x7fa8ee37d700) at pthread_create.c:463
  Title: hydrogen crashed with SIGSEGV in H2Core::Sampler::__render_note()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hydrogen/+bug/1759859/+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 1831154] Re: [needs-packaging] ubuntustudio-menu-add

2019-06-18 Thread Seth Arnold
Consider it a goal to remove all the uses of subprocess except exo-
desktop-item-edit, and to replace the string-based execution there with
an array-based execution as seen in the documentation:
https://docs.python.org/3/library/subprocess.html#subprocess.run

For the rm and cp commands:

https://docs.python.org/3/library/os.html#os.unlink
https://docs.python.org/3/library/shutil.html#shutil.copyfile

Thanks

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

Title:
  [needs-packaging] ubuntustudio-menu-add

Status in Ubuntu Studio:
  In Progress
Status in Ubuntu Studio Menu Add:
  In Progress
Status in Ubuntu:
  New

Bug description:
  New native package for Ubuntu Studio. From the description:

   Utility for creating a menu item within the XDG menu for
   a user. It allows adding a script or other application to
   the XDG menu. It can also modify a menu item by creating
   a new version for the user. This utility does not change
   any of the system menu files.

  Please sponsor package. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1831154/+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 1867734] Re: GIMP Speicherzugriffsfehler

2020-04-06 Thread Seth Arnold
I didn't spot anything private in here, I'll open this so others can see
it.

Thanks

** Information type changed from Private Security to Public Security

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

Title:
  GIMP Speicherzugriffsfehler

Status in gimp package in Ubuntu:
  Incomplete

Bug description:
  ```
  GNU Image Manipulation Program version 2.10.14
  git-describe: GIMP_2_10_12-511-ga4f55d6c7e
  C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
9.2.1-17ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none,hsa --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 9.2.1 20191102 (Ubuntu 9.2.1-17ubuntu1) 

  using babl version 0.1.74 (compiled against version 0.1.72)
  using GEGL version 0.4.18 (compiled against version 0.4.18)
  using GLib version 2.64.0 (compiled against version 2.62.1)
  using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
  using GTK+ version 2.24.32 (compiled against version 2.24.32)
  using Pango version 1.44.7 (compiled against version 1.42.3)
  using Fontconfig version 2.13.1 (compiled against version 2.13.1)
  using Cairo version 1.16.0 (compiled against version 1.16.0)

  ```
  > fatal error: Speicherzugriffsfehler

  Stack trace:
  ```

  # Stack traces obtained from PID 11823 - Thread 11823 #

  [New LWP 11826]
  [New LWP 11827]
  [New LWP 11828]
  [New LWP 11829]
  [New LWP 11830]
  [New LWP 11831]
  [New LWP 11832]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  __libc_read (nbytes=256, buf=0x7ffe146d5390, fd=16) at 
../sysdeps/unix/sysv/linux/read.c:26
Id   Target Id  Frame 
  * 1Thread 0x7f4b2ebf1e00 (LWP 11823) "gimp-2.10"  __libc_read 
(nbytes=256, buf=0x7ffe146d5390, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f4b2e363700 (LWP 11826) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f4b2db62700 (LWP 11827) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7f4b2d361700 (LWP 11828) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7f4b1700 (LWP 11829) "gmain"  0x7f4b2fbe99bf 
in __GI___poll (fds=0x55f5856fdfd0, nfds=1, timeout=3639) at 
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7f4b1f7fe700 (LWP 11830) "gdbus"  0x7f4b2fbe99bf 
in __GI___poll (fds=0x55f5857160a0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7f4b11450700 (LWP 11831) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7f4b10c4f700 (LWP 11832) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

  Thread 8 (Thread 0x7f4b10c4f700 (LWP 11832)):
  #0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  No locals.
  #1  0x7f4b2fedf586 in g_cond_wait_until () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #2  0x7f4b2fe62561 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #3  0x7f4b2fe62b86 in g_async_queue_timeout_pop () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #4  0x7f4b2febc259 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #5  0x7f4b2febb911 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  No symbol table info available.
  #6  0x7f4b2fcd1609 in start_thread (arg=) at 
pthread_create.c:477
  ret = 
  pd = 
  unwind_buf = 

[Ubuntustudio-bugs] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-02-14 Thread Seth Arnold
Scarlett, Simon and I had discussed preparing a small program that could
prepare a wrapper profile: given a path to an appimage, it could emit a
small profile to /etc/apparmor.d/ for the file, with the right
attachment path and then load the profile.

As I understand our new strategy, it would probably also have to include
whatever capabilities that appimage uses as part of setting up the new
namespaces -- ideally, it'd be the same capabilities from appimage to
appimage.

If there's some reasonable restraints on appimages, like using
XDG_SOMETHING for user data storage, that might be nice, too. But that's
harder to do.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2046844

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  In Progress
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Fix Released
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kgeotag package in Ubuntu:
  In Progress
Status in kiwix package in Ubuntu:
  Confirmed
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in plasma-welcome package in Ubuntu:
  In Progress
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Fix Released

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 2055220] Re: mypaint

2024-02-29 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  mypaint

Status in mypaint package in Ubuntu:
  Invalid

Bug description:
  As soon as I start drawing a line, it always crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: mypaint 2.0.1-10
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 27 22:38:46 2024
  ExecutablePath: /usr/bin/mypaint
  InstallationDate: Installed on 2024-01-07 (52 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  InterpreterPath: /usr/bin/python3.12
  ProcCmdline: /usr/bin/python3 /usr/bin/mypaint
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 
3.12.1-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x4df4fe:  mov0x10(%rcx),%rcx
   PC (0x004df4fe) ok
   source "0x10(%rcx)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: mypaint
  StacktraceTop:
   ?? ()
   PyObject_GetAttrString ()
   _PyObject_CallMethod_SizeT ()
   ?? () from /usr/lib/mypaint/lib/_mypaintlib.cpython-312-x86_64-linux-gnu.so
   process_tile_internal () from /lib/x86_64-linux-gnu/libmypaint-1.5.so.1
  Title: mypaint crashed with SIGSEGV in PyObject_GetAttrString()
  UpgradeStatus: Upgraded to noble on 2024-01-12 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users vboxusers
  separator:

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