[Touch-packages] [Bug 1885313] Re: evince crashes when opening rfc8798.pdf

[Erik Auerswald]

The tested snaps indeed use the same libpoppler version as found in
18.04.

I have created a 20.04 boot medium and tested evince using the "try
Ubuntu without installation". This did indeed work, so I stand corrected
that the bug is fixed in current Ubuntu releases.

The evince version in 20.04 is 3.36.0 (older than the latest/candidate
snap), libpoppler and poppler-utils are version 0.86.1 (newer than in
the snaps, or in Debian). So this does look like a poppler rather than
evince problem.

Thanks.

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

Title:
  evince crashes when opening rfc8798.pdf

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler package in Debian:
  New

Bug description:
  evince reproducabely crashes when opening the file rfc8798.pdf from
  https://www.rfc-editor.org/rfc/rfc8798.pdf:

  $ evince --version
  GNOME Document Viewer 3.28.4
  $ evince rfc8798.pdf
  Segmentation fault (core dumped)
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

  Required information:

  1) Ubuntu release info:
  $ lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  2) Package version info:
  $ apt-cache policy evince
  evince:
Installed: 3.28.4-0ubuntu1.2
Candidate: 3.28.4-0ubuntu1.2
Version table:
   *** 3.28.4-0ubuntu1.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) Expected outcome:
  I expected evince to successfully open the PDF, allowing me to read the 
document.

  4) Observed behavior:
  The default PDF reader of Ubuntu, evince, crashed (reporting a "segmentation 
fault".

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

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

[Touch-packages] [Bug 932133] Re: upowerd crash when plugging in iPhone

[Erik Auerswald]

Since this has not occurred on 18.04 for me, this bug seems to actually
be fixed, with the fix released in 18.04 LTS (ignoring development
versions of Ubuntu).

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

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

Title:
  upowerd crash when plugging in iPhone

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  upowerd crashed when I plugged in my iPhone 3GS. This is reproducible
  in 12.04 on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: upower 0.9.15-1
  ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
  Uname: Linux 3.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Tue Feb 14 10:43:29 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to precise on 2012-02-13 (0 days ago)

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

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

[Touch-packages] [Bug 1885313] Re: evince crashes when opening rfc8798.pdf

[Erik Auerswald]

The Debian bug report clearly shows that current unstable still exhibits
the bug.

Since Ubuntu is based on unstable, every Ubuntu version, released or in
development, still exhibits this bug.

As before, the bug is closed as "fixed", but it is not fixed.

The first possible fix in an LTS release is in 22.04 LTS, if upstream
picks the problem up and really fixes it. But since this report seems to
show that it already is fixed, they might be lured into thinking it is
fixed already. It is not.

Even if we assume that the bug was fixed in 19.10 and then re-appeared,
and possibly fixed in some experimental code base, just closing this bug
is the surest way to have it re-appear again, because it was never
diagnosed and knowingly fixed, but rather happened to not show itself in
some random version of the software.

This is very frustrating, and one of the reasons many people still think
commercial proprietary software is of better quality than free software
(as evidenced, e.g., in the IETF mailing list thread[1]). :-(

[1] https://mailarchive.ietf.org/arch/msg/tools-
discuss/vIR4w4Qgj796wcTkiNtK6ljMxss/

The poppler-using xpdf in 18.04 does not have this issue. The tools from
poppler-utils work fine with the PDF documents in question. So is it
really an issue in poppler? Or rather in the way evince uses poppler? I
am not familiar with either code base, so I have no idea.

The GNOME Document Viewer "evince" stands out as the only PDF viewer
that actually crashes on those PDFs. Others display the PDFs, with some
(e.g., MuPDF and gv) producing warning and/or error messages (but still
correctly displaying the document). It also stands out as the default
PDF viewer in Ubuntu.

It is not a problem of PDF attachments not working in poppler based PDF
viewers, because (using, e.g., pdftk) it is possible to take the
problematic PDFs, extract the attachment, create a new PDF without
attachment, but otherwise the same contents, and then (re-)attach the
file extracted in the first step. The result works fine in evince (and
does not produce error nor warning messages in MuPDF).

I am sorry for venting my frustration.

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

Title:
  evince crashes when opening rfc8798.pdf

Status in poppler package in Ubuntu:
  Fix Released
Status in evince package in Debian:
  New

Bug description:
  evince reproducabely crashes when opening the file rfc8798.pdf from
  https://www.rfc-editor.org/rfc/rfc8798.pdf:

  $ evince --version
  GNOME Document Viewer 3.28.4
  $ evince rfc8798.pdf
  Segmentation fault (core dumped)
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

  Required information:

  1) Ubuntu release info:
  $ lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  2) Package version info:
  $ apt-cache policy evince
  evince:
Installed: 3.28.4-0ubuntu1.2
Candidate: 3.28.4-0ubuntu1.2
Version table:
   *** 3.28.4-0ubuntu1.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) Expected outcome:
  I expected evince to successfully open the PDF, allowing me to read the 
document.

  4) Observed behavior:
  The default PDF reader of Ubuntu, evince, crashed (reporting a "segmentation 
fault".

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

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

[Touch-packages] [Bug 932133] Re: upowerd crash when plugging in iPhone

[Erik Auerswald]

The problem has not occured for me on Ubuntu 18.04 yet, it might be
fixed in the latest LTS release.

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

Title:
  upowerd crash when plugging in iPhone

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  upowerd crashed when I plugged in my iPhone 3GS. This is reproducible
  in 12.04 on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: upower 0.9.15-1
  ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
  Uname: Linux 3.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Tue Feb 14 10:43:29 2012
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to precise on 2012-02-13 (0 days ago)

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

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

[Touch-packages] [Bug 1841654] Re: Consider replacing mawk with gawk in main

[Erik Auerswald]

I would prefer to have a current mawk in Ubuntu, but if that does not
happen, replacing mawk with gawk would be appreciated.

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

Title:
  Consider replacing mawk with gawk in main

Status in mawk package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  For POSIX compatibility reasons Ubuntu ships with mawk ("Mike's awk" =
  mawk) in main. There is an awk-symlink to mawk, thus mawk is the
  official awk implementation in Ubuntu.

  == Reasons against keeping mawk ==

  *The mawk package is synced from debian and it is heavily
  undermaintained: Debian (and thus Ubuntu) still ships version
  1.3.3-17, the same version at least since oldoldstable:
  https://packages.debian.org/search?searchon=names=mawk

  *maintainer Thomas E. Dickey (https://invisible-island.net/mawk/)
  called officially out that Debian "neglected" mawk in 2014 ("As noted,
  mawk has been neglected by some packagers (see for example this
  http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=mawk)". And
  Debian (and Ubuntu) still ship the same version five years later

  *Most other distributions ship mawk at least in its last official
  incarnation 1.3.4 in their repositories. Dickey lists AIX, Fedora,
  FinkPorts (Mac OS X), FreeBSD port, Gentoo, HPUX, MacPorts (Mac OS X),
  NetBSD pkgsrc/lang, OpenCSW (Solaris). That version is from 2014 but
  updated snapshots are released in regular intervals. The current
  snapshot is from February 2019: https://github.com/ThomasDickey/mawk-
  snapshots/blob/ab13a164013940e90c0b1ad36a039feae06a0b65/CHANGES

  *A planned rewrite mawk2 was planned by original author Mike Brennan
  in 2016 but obviously came to nothing:
  https://github.com/ploxiln/mawk-2/commits/master

  *Thus mawk sits in Ubuntu main in a version published upstream in 2009
  and celebrates its 10th anniversary of negligence. In a state that
  Debian was called out for 5 years ago.

  *This year it is 10 years unmaintained and largely untouched. At the
  end of the next LTS-support-cycle we can celebrate 15 years of not
  supporting it.

  *awk is included in Linux for POSIX standard compliance. Mawk is known
  to be fast and small but it is the implementation that is farthest
  from being POSIX compliant, missing things like named character
  classes like [[:space:]] within its EREs.

  == Reasons for gawk as a replacement ==

  *It is the official GNU awk implementation and known to work well with
  the rest of the GNU userland.

  *It is actively maintained with the last version 5.01 shipping in
  June, 2019 (even if Ubuntu will obviously still ship 4.2 for Eoan).

  *It is mostly compliant with the POSIX standard.

  *Most other distributions ship it as the standard POSIX
  implementation, with a awk symlink. So it had security reviews already
  by Red Hat and others.

  == Possible problems with switching to gawk in time for Ubuntu 20.4 ==

  - It might need to be MIRed by the Ubuntu security team and a review
  might take some time. So I filed this bug early with Eoan not yet out
  of the door.

  - It is much larger than mawk, the Ubuntu package is 1600 kB in size,
  while mawk is only about 190KB. Thus some might want to split out some
  basic functionality to save size. Like what is vim-tiny to vim. To
  start gawk in --traditional or --posix mode and disable the extensions
  at compile time might be a good start to reduce the size. See:
  https://www.gnu.org/software/gawk/manual/html_node/Additional-
  Configuration-Options.html#Additional-Configuration-Options

  =

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mawk 1.3.3-17ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 20:12:11 2019
  Dependencies:
   gcc-9-base 9.1.0-2ubuntu2~19.04
   libc6 2.29-0ubuntu2
   libgcc1 1:9.1.0-2ubuntu2~19.04
   libidn2-0 2.0.5-1
   libunistring2 0.9.10-1ubuntu2
  InstallationDate: Installed on 2018-02-23 (550 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: mawk
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Erik Auerswald]

For what it is worth, since the powers that be have deemed the bug
"fixed"...

iPhone handling on Ubuntu 14.04 LTS is quite broken. You plug in an
iPhone, upowerd crashes. You plug it out, then back in, and you get an
error message that the iPhone is already mounted. You unplug the iPhone,
reboot, and upowerd crashes. Not nice. :-(

The patch from comment #7 is obviously correct. It has been accepted
upstream. It is very small. Pretty please with sugar on top, backport
this fix (i.e. just apply the patch and rebuild the package!) for
14.04LTS.

Thanks.

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 932133] Re: upowerd crash when plugging in iPhone

[Erik Auerswald]

This problem still exists with 14.04 and an iPhone 4s.

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

Title:
  upowerd crash when plugging in iPhone

Status in upower package in Ubuntu:
  Confirmed

Bug description:
  upowerd crashed when I plugged in my iPhone 3GS. This is reproducible
  in 12.04 on my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: upower 0.9.15-1
  ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
  Uname: Linux 3.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Tue Feb 14 10:43:29 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to precise on 2012-02-13 (0 days ago)

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

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