calling "x2goclient --help" segfaults

Bug #1301099 reported by Reinhard Tartler on 2014-04-02
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
x2goclient (Ubuntu)
Low
Unassigned

Bug Description

triggered by "x2goclient --help"

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: x2goclient 4.0.1.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 1 21:58:38 2014
ExecutablePath: /usr/bin/x2goclient
ProcCmdline: x2goclient --help
SegvAnalysis:
 Segfault happened at: 0x7ff9b786ab68 <_ZN15QSystemTrayIcon10setVisibleEb+8>: mov 0x8(%rdi),%rbx
 PC (0x7ff9b786ab68) ok
 source "0x8(%rdi)" (0x6e00000075) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: x2goclient
StacktraceTop:
 QSystemTrayIcon::setVisible(bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 ?? ()
 ?? ()
 QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
 QMainWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4
Title: x2goclient crashed with SIGSEGV in QSystemTrayIcon::setVisible()
UpgradeStatus: Upgraded to trusty on 2014-03-30 (2 days ago)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sbuild sudo

Reinhard Tartler (siretart) wrote :

StacktraceTop:
 data (this=0x6e00000075) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
 qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2467
 d_func (this=0x6e0000006d) at util/qsystemtrayicon.h:120
 QSystemTrayIcon::setVisible (this=0x6e0000006d, visible=false) at util/qsystemtrayicon.cpp:267
 hide (this=<optimized out>) at /usr/include/qt4/QtGui/qsystemtrayicon.h:109

Changed in x2goclient (Ubuntu):
importance: Undecided → Medium
summary: - x2goclient crashed with SIGSEGV in QSystemTrayIcon::setVisible()
+ x2goclient crashed with SIGSEGV in data()
tags: removed: need-amd64-retrace
information type: Private → Public

Interestingly, this crash is not reproducible with the same source built in debian/unstable.

Is this maybe because of different compilation options? In any case, this only happens after the help message was successfully printed, so lowering the severity.

Changed in x2goclient (Ubuntu):
importance: Medium → Low
status: New → Confirmed
summary: - x2goclient crashed with SIGSEGV in data()
+ calling "x2goclient --help" segfaults
Reinhard Tartler (siretart) wrote :

btw, I've tried stripping Bsymbolic functions, but this did not help :-(

dpkg-source: Warnung: unsigniertes Quellpaket wird extrahiert (/tmp/x2go/x2goclient_4.0.1.1-1ubuntu3.dsc)
diff -Nru x2goclient-4.0.1.1/debian/changelog x2goclient-4.0.1.1/debian/changelog
--- x2goclient-4.0.1.1/debian/changelog 2014-05-14 07:52:15.000000000 -0400
+++ x2goclient-4.0.1.1/debian/changelog 2014-05-17 17:59:29.000000000 -0400
@@ -1,3 +1,9 @@
+x2goclient (4.0.1.1-1ubuntu3) trusty; urgency=medium
+
+ * Remove -Bsymbolic-functions from linker flags, LP: #1301099
+
+ -- Reinhard Tartler <email address hidden> Sat, 17 May 2014 17:59:03 -0400
+
 x2goclient (4.0.1.1-1ubuntu2) trusty; urgency=low

   * Bugfix: x2goclient using high cpu, LP: #1288631
diff -Nru x2goclient-4.0.1.1/debian/rules x2goclient-4.0.1.1/debian/rules
--- x2goclient-4.0.1.1/debian/rules 2013-09-11 08:34:38.000000000 -0400
+++ x2goclient-4.0.1.1/debian/rules 2014-05-17 18:12:53.000000000 -0400
@@ -3,7 +3,7 @@
 export CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS)
 export CFLAGS:=$(shell dpkg-buildflags --get CFLAGS)
 export CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS)
-export LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS)
+export LDFLAGS := $(filter-out %-Bsymbolic-functions,$(shell dpkg-buildflags --get LDFLAGS))

 %:
  dh $@ --parallel --with apache2
zsh: exit 1 debdiff x2goclient_4.0.1.1-1ubuntu{2,3}.dsc

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

Other bug subscribers