Caught a segmentation fault while loading plugin file: /usr/lib/gstreamer-0.10/libgstclutter.so

Bug #971613 reported by Thiago Belem
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Pidgin
New
Undecided
Unassigned
pidgin (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

After upgrading to Ubuntu Precise (12.04) I can't start Pidgin..

When running from command line I get the following error:

"ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.10/libgstclutter.so"

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: pidgin 1:2.10.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Mon Apr 2 09:03:04 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: pidgin
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Thiago Belem (thiago.belem) wrote :
Revision history for this message
Jon (sailias) wrote :

Same problem here:

fixed with:

sudo apt-get install gstreamer-tools
gst-inspect

Revision history for this message
Eugen Paraschiv (hanriseldon) wrote :

That fixed the issue, thanks.
Is there an issue for this in the Pidgin trac?
Thanks.
Eugen.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in pidgin (Ubuntu):
status: New → Confirmed
Revision history for this message
Cd-MaN (panther79) wrote :

This just started to happen to me after updating some packages yesterday. I installed 12.04 in the weekend, fully updated it and pidgin worked. After yesterdays update it failed on me with the same error mesage. The solution fom comment #2 worked.

Revision history for this message
Majestyx (majestyx) wrote :

i have Pidgin 2.10.3 (libpurple 2.10.3) @12.04 - and all works fine... i close this bug....

Changed in pidgin (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Daniel O'Connor (daniel-oconnor) wrote :

This isn't fixed/released afaict, and the workaround doesn't function anymore.

Oddly, this was functional on Friday, it's only having done an apt-get upgrade that this has resurfaced.

clockwerx@clockwerx-laptop:~/uofa/res_prof$ sudo apt-get install gstreamer-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  gstreamer-tools
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,018 B of archives.
After this operation, 741 kB of additional disk space will be used.
Get:1 http://au.archive.ubuntu.com/ubuntu/ precise/main gstreamer-tools amd64 0.10.36-1ubuntu1 [8,018 B]
Fetched 8,018 B in 0s (18.7 kB/s)
Selecting previously unselected package gstreamer-tools.
(Reading database ... 208087 files and directories currently installed.)
Unpacking gstreamer-tools (from .../gstreamer-tools_0.10.36-1ubuntu1_amd64.deb) ...
Setting up gstreamer-tools (0.10.36-1ubuntu1) ...

clockwerx@clockwerx-laptop:~/uofa/res_prof$ pidgin
The program 'Pidgin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 37 error_code 1 request_code 154 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.10/libgstclutter.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap --gst-disable-registry-fork and debug.

clockwerx@clockwerx-laptop:~/uofa/res_prof$ dpkg -l | grep pidgin
ii indicator-status-provider-pidgin 0.6.0-0ubuntu1 indicator-messages status provider for pidgin
ii pidgin 1:2.10.3-0ubuntu1 graphical multi-protocol instant messaging client for X
ii pidgin-data 1:2.10.3-0ubuntu1 multi-protocol instant messaging client - data files
ii pidgin-libnotify 0.14-4ubuntu10 display notification bubbles in pidgin

Revision history for this message
Daniel O'Connor (daniel-oconnor) wrote :

Related:
https://bbs.archlinux.org/viewtopic.php?id=140287
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667499

The suggestion in those threads that this relates to a mangled setup of display drives seems likely, having installed the restricted drivers recently (gnome-shell is also unhappy at me, for what I suspect is the same reason)

Revision history for this message
James Taylor (barrkins) wrote :

same issue. after upgrading to ubuntu 12.04 pidgin does not start anymore.

Pidgin 2.10.3 (libpurple 2.10.3)

The program 'Pidgin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 37 error_code 1 request_code 154 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Revision history for this message
mustangtyson (tysonsmith) wrote :

ran into this on ubuntu 13.04 after upgrade

pidgin
Xlib: extension "RANDR" missing on display ":0.0".
Xlib: extension "RANDR" missing on display ":0.0".
Xlib: extension "RANDR" missing on display ":0.0".

ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/x86_64-linux-gnu/gstreamer-0.10/libgstclutter.so

Please either:
- remove it and restart.
- run with --gst-disable-segtrap --gst-disable-registry-fork and debug.

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.