G_IS_DBUS_CONNECTION (connection)' failed

Bug #1770129 reported by John Smallbone on 2018-05-09
This bug affects 7 people
Affects Status Importance Assigned to Milestone
leafpad (Ubuntu)

Bug Description

lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04

Clean install on a new ssd in a HP G3 255 laptop.

Laptop:~$ leafpad
(leafpad:8594): GLib-GIO-CRITICAL **: 10:01:46.306: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

But please note, leafpad does start as expected.

My desktop machine that has upgraded to 18.04 does not show this message.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lxterminal 0.3.1-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed May 9 10:02:56 2018
ExecutablePath: /usr/bin/lxterminal
InstallationDate: Installed on 2018-05-06 (2 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
 PATH=(custom, user)
SourcePackage: lxterminal
UpgradeStatus: No upgrade log present (probably fresh install)

John Smallbone (johnnyoldboy) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lxterminal (Ubuntu):
status: New → Confirmed
Walter Lapchynski (wxl) wrote :

I can confirm it occurs in Bionic. The fact that you have a machine that does not show this message is remarkable to me, as GTK apps tend to be really noisy, showing all sorts of bad looking messages when run from terminal. In fact, I would call that expected behavior. That said, especially given everything otherwise works fine, this is extremely low on the priority list.

affects: lxterminal (Ubuntu) → leafpad (Ubuntu)
Changed in leafpad (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Alberto (elba) wrote :

@Walter Lapchynski
"Everything otherwise works fine"; surely not. For example, the installation program of hplip just crashed with "GLib-GIO-CRITICAL **: 16:14:04.867: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed" after the GUI dialog screen was launched and I pressed <Continue> (the error message was repeated three times and the installation program hanged up). I restarted the installation choosing "interactive" instead of "GUI" (which was the default choice) but I had to uninstall the previous failed installation, which had already written stuff on disk etc.
I would expect that any installation or script that launches a GUI from terminal would be affected.
At any rate, the bug makes for extremely bad publicity for Ubuntu and Linux. It's a CRITICAL error that keeps coming up; as if the aircraft's rocket engines sputtered and stuttered all the time but the crew tried to reassure you by saying, "don't worry, everything otherwise works fine". Some googling shows that quite many people are affected by the bug, both in Ubuntu and in other distributions.
In my opinion, this should be high on the priority list.

Walter Lapchynski (wxl) wrote :

I meant everything works fine.... with leafpad. Note too that few users actually launch graphical applications from the command line, at which point the noisy errors are all but unnoticed.

If you want to make a new bug for hplip, that might make sense.

Alberto (elba) wrote :

OK, I agree that leafpad works fine. However, the present bug is not leafpad specific, leafpad is not even mentioned in the bug description: "G_IS_DBUS_CONNECTION (connection)' failed ". I think that collecting the related bugs under this heading, instead of scattering them into several minor sections, would be more informative and effective. I'd say it makes sense ;)

Walter Lapchynski (wxl) wrote :

No, it doesn't. If hplip shows it and fails and leafpad shows it and succeeds, you have two completely different situations.

Dimitri Koutsouris (timomak) wrote :

Is this finally fixed ?

Dimitri Koutsouris (timomak) wrote :

I confirm this on Lubuntu 18.04.3 kernel 5.0.0

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers