nspluginviewer crashed with SIGSEGV in XChangeProperty()

Bug #349351 reported by Javier Adrian Rojas
36
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gtk+2.0 (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: kdebase

I just work in kmail and kmess when this message get out.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/nspluginviewer
NonfreeKernelModules: nvidia
Package: konqueror-nsplugins 4:4.2.1-0ubuntu6
ProcCmdline: /usr/bin/nspluginviewer -dbusservice org.kde.nspluginviewer-3706
ProcEnviron:
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
 LANGUAGE=
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 XChangeProperty () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_cclosure_marshal_VOID__VOID ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: nspluginviewer crashed with SIGSEGV in XChangeProperty()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Javier Adrian Rojas (javieradrianr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:XChangeProperty (dpy=0x0, w=0, property=0, type=0, format=32, mode=0,
xembed_set_info (window=<value optimized out>, flags=0)
gtk_plug_realize (widget=0x9483188)
IA__g_cclosure_marshal_VOID__VOID (closure=0x9444788,
g_type_class_meta_marshal (closure=0x9444788,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in kdebase:
importance: Undecided → Medium
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Looks like a crash in GTK.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

Changed in gtk+2.0 (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Incomplete
visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in gtk+2.0 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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