kde-info2html exits with error (perl compatibility problem) -> info browsing fails "Cannot Initiate the info Protocol"

Bug #1659257 reported by Carsten Jacobi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde-runtime (Ubuntu)
New
Undecided
Unassigned

Bug Description

On can't browse info pages with konqueror on Ubuntu-Xenial. Issue is already known and fixed:

https://bugs.kde.org/show_bug.cgi?id=359015

It seems the fix just haven't made it into Xenial yet (and this is perl, so it'll also affect other platforms and not just mine)
Here is my version of the package:

jacobi@Jacobis-G5:~$ apt-cache policy kde-runtime-data
kde-runtime-data:
  Installiert: 4:15.12.3-0ubuntu1
  Installationskandidat: 4:15.12.3-0ubuntu1
  Versionstabelle:
 *** 4:15.12.3-0ubuntu1 500
        500 http://de.ports.ubuntu.com/ubuntu-ports xenial/universe powerpc Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: kde-runtime-data 4:15.12.3-0ubuntu1 [modified: usr/share/kde4/apps/kio_info/kde-info2html]
ProcVersionSignature: Ubuntu 4.4.0-59.80-powerpc64-smp 4.4.35
Uname: Linux 4.4.0-59-powerpc64-smp ppc64
NonfreeKernelModules: openafs
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: powerpc
CurrentDesktop: KDE
Date: Wed Jan 25 11:46:44 2017
InstallationDate: Installed on 2016-08-05 (172 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: kde-runtime
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Carsten Jacobi (jacobi-de) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.