pinentry-qt4 crashed with SIGABRT in qt_message_output()

Bug #927167 reported by mbel on 2012-02-05
64
This bug affects 19 people
Affects Status Importance Assigned to Milestone
ibus
Unknown
Unknown
ibus-qt (Ubuntu)
Medium
Harald Sitter

Bug Description

what I did
1. executed in console "eval $(gpg-agent --daemon)"
2. started tcl script which called "gpg --sign --use-agent $<dome file name>"
I saw KDE password prompt window for a second, then crash report

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: pinentry-qt4 0.8.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic-pae 3.0.13
Uname: Linux 3.0.0-15-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sun Feb 5 18:49:58 2012
ExecutablePath: /usr/bin/pinentry-qt4
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: pinentry --display :0
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LC_MESSAGES=ru_RU.UTF-8
 LANG=ru_RU.UTF-8
 LANGUAGE=ru:en_US:en
Signal: 6
SourcePackage: pinentry
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 qt_message_output(QtMsgType, char const*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/i386-linux-gnu/libQtCore.so.4
Title: pinentry-qt4 crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to oneiric on 2012-01-05 (31 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

mbel (mbel) wrote :

StacktraceTop:
 qt_message_output (msgType=QtFatalMsg, buf=0x9a13d48 "ASSERT failure in QList<T>::operator[]: \"index out of range\", file /usr/include/qt4/QtCore/qlist.h, line 464") at global/qglobal.cpp:2315
 qt_message (msgType=QtFatalMsg, msg=0xb76fefb8 "ASSERT failure in %s: \"%s\", file %s, line %d", ap=0xbf84e6b4 "+\232\237\263\030\232\237\263\370\231\237\263\320\001") at global/qglobal.cpp:2361
 qFatal (msg=0xb76fefb8 "ASSERT failure in %s: \"%s\", file %s, line %d") at global/qglobal.cpp:2544
 qt_assert_x (where=0xb39f9a2b "QList<T>::operator[]", what=0xb39f9a18 "index out of range", file=0xb39f99f8 "/usr/include/qt4/QtCore/qlist.h", line=464) at global/qglobal.cpp:2047
 QList<QString>::operator[](int) () from /tmp/tmp2o8CRO/usr/lib/libibus-qt.so.1

Changed in pinentry (Ubuntu):
importance: Undecided → Medium
summary: - pinentry-qt4 crashed with SIGABRT in __kernel_vsyscall()
+ pinentry-qt4 crashed with SIGABRT in qt_message_output()
tags: removed: need-i386-retrace
Jonathan Thomas (echidnaman) wrote :

It appears to be ibus-qt trying to access an out of range index on a list.

visibility: private → public
affects: pinentry (Ubuntu) → ibus-qt (Ubuntu)
Changed in ibus-qt (Ubuntu):
status: New → Triaged
Alex Wauck (awauck) wrote :

This still happens on 12.04.

Alex Wauck (awauck) wrote :

Removing ibus-qt4 and libibus-qt1 (probably only needed to remove libibus-qt1) seems to fix this, and it didn't force me to remove kubuntu-desktop as I had feared. Of course, for those who need ibus, that's hardly a viable solution.

Peter Wu (lekensteyn) wrote :

Test-case is mentioned in upstream report.
Upstream report: http://code.google.com/p/ibus/issues/detail?id=1504

tags: added: amd64 patch precise

The attachment "0001-Do-not-crash-on-missing-invalid-DISPLAY-envvar.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: kubuntu
Changed in ibus-qt (Ubuntu):
assignee: nobody → Harald Sitter (apachelogger)
milestone: none → ubuntu-13.10
status: Triaged → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ibus-qt - 1.3.1-2.1ubuntu3

---------------
ibus-qt (1.3.1-2.1ubuntu3) saucy; urgency=low

  * Add upstream_DISPLAY_crash_fix.diff preventing a crash when -display
    was passed but no DISPLAY environment variable is actually defined
    (LP: #927167)
 -- Harald Sitter <email address hidden> Wed, 25 Sep 2013 11:58:46 +0200

Changed in ibus-qt (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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