apport-bug unable to init server, dumps core

Bug #1723272 reported by Paul
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After upgrading to 17.10, apport-bug fails with the follow error:

# apport-bug
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
Segmentation fault (core dumped)

Calling apport-cli directly works just fine. The problem seems to be a general Xwayland permission issue, since nothing can connect to the display server if sudo/su is used:

$ sudo xclock
No protocol specified
Error: Can't open display: :0
$ xauth list
xauth: file /home/user/.Xauthority does not exist

If that's the way things are going to be in Ubuntu from now on, we need to make apport-bug a bit smarter in the way it decides whether to use the GUI version or not.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashReports: 640:0:119:7137742:2017-10-13 09:46:22.546417474 +1100:2017-10-13 09:46:23.546417474 +1100:/var/crash/_usr_share_apport_apport-gtk.0.crash
Date: Fri Oct 13 09:49:17 2017
InstallationDate: Installed on 2016-12-02 (313 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
SourcePackage: apport
UpgradeStatus: Upgraded to artful on 2017-10-12 (0 days ago)

Revision history for this message
Paul (i41bktob-launchpad-net) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

This looks like a duplicate of bug 1713313 but LP keeps timing out when I try to mark it as one.

Revision history for this message
Paul (i41bktob-launchpad-net) wrote :

Interesting. According to that ticket, applications require changes to PolicyKit and ultimately maybe their architecture (separation into non-graphical and graphical components) in order to run as root on Wayland. So it looks like you have two options:

1. Put your foot down and refuse to make those changes in apport-bug
2
. Decide to re-architect apport-bug to work under Wayland

Keep this ticket open in the latter case.

Revision history for this message
Norbert (nrbrtx) wrote :

Thanks for reporting. It's already known - see bug 1713313.
Please mark as duplicate (I got timeout issue).

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Paul (i41bktob-launchpad-net) wrote :

@nrbrtx Yeah, Launchpad has had some timeout issue for over a week now. However ...

This bug isn't a duplicate of bug 1713313. That bug is filed against Wayland in general, and odds on it won't get fixed because this feature/misfeature is intentional in Wayland's architecture. Other distros are sticking to it. See https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1713313/comments/44

This bug is filed against apport-bug itself, which is where changes will need to be made if/when bug 1713313 is Wontfixed.

Norbert (nrbrtx)
tags: removed: artful
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.