compiz crashed with SIGSEGV in __pthread_mutex_lock()

StacktraceTop:
 __pthread_mutex_lock (mutex=0x894c02fa8328ec8b)
 g_source_unref_internal (source=0x7fe9e18d38e0,

Very similar to
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/191174

Semms still not fixed :(

I'm affected by this bug. Anyway, I tried to "unity --reset" and it crashed Compiz.

This bug affect me as well. I get the same symptoms as discussed in the initial bug report. What can I do to assist?

Affect me while in Gnome, not Unity. In the middle of the session, pretty lot time from log in.

The issue is still there using compiz 0.9.4 and unity 3.4.6:

"#1 0x004d4ab4 in g_source_unref_internal () from /lib/libglib-2.0.so.0
No symbol table info available.
#2 0x00d06bd0 in Glib::Source::unreference() const () from /usr/lib/libglibmm-2.4.so.1
No symbol table info available.
#3 0x080709f5 in ~RefPtr (this=0x8a51540, __in_chrg=<value optimised out>) at /usr/include/glibmm-2.4/glibmm/refptr.h:207
No locals.
#4 PrivateScreen::~PrivateScreen (this=0x8a51540, __in_chrg=<value optimised out>) at /build/buildd/compiz-0.9.4/src/screen.cpp:4776
No locals.
#5 0x08070cc2 in PrivateScreen::~PrivateScreen (this=0x8a51540, __in_chrg=<value optimised out>) at /build/buildd/compiz-0.9.4/src/screen.cpp:4778
No locals.
#6 0x0806f858 in CompScreen::~CompScreen (this=0x8a514b8, __in_chrg=<value optimised out>) at /build/buildd/compiz-0.9.4/src/screen.cpp:4683
        p = <value optimised out>
#7 0x0806f962 in CompScreen::~CompScreen (this=0x8a514b8, __in_chrg=<value optimised out>) at /build/buildd/compiz-0.9.4/src/screen.cpp:4686
No locals.
#8 0x080663c1 in CompManager::fini (this=0xbf9c1bbc) at /build/buildd/compiz-0.9.4/src/main.cpp:259
No locals.
#9 0x08066bb0 in main (argc=1, argv=0xbf9c1c94) at /build/buildd/compiz-0.9.4/src/main.cpp:287"

bug #684991 seems similar to this crasher

I get this when I login and I get it again every time I restart compiz. I don't use unity, I prefer classic desktop.

I talked to Murray Cummings about this one - apparantly it is a bug in Glibmm where sources are auto unref'd when they are first disconnected and also on the parent class destructors. In any case, this crash only seems to happen when compiz is actually exiting, so the real issue is that compiz is failing to start. I'd like to see why this is, since there are very few cases where shutDown is true except where *two* instances of compiz are started. And in that case it is a gnome-session bug.

Hrm, ok, looking into this further it seems like g-s restarts compiz because we miss a timeout. Except that it can't because the first compiz cant be restarted yet.

Could someone please attach their .xsession-errors ?

@Sam, a .xsession-errors file is attached to the duplicate bug #717652 : https://launchpadlibrarian.net/64134992/XsessionErrors.txt .

I've been directed here from the duplicate bug Bug #750127. I'm running Natty beta

Compiz seems to load fine and operates as normal until I start matlab and then it crashes every time as reported for Bug #750127.

Let me know if you need more information.

Platform i386
Affects me too.
I could provide more info if needed (just told me which one)

This bug was fixed in the package unity - 3.8.6-0ubuntu1

---------------
unity (3.8.6-0ubuntu1) natty; urgency=low

  * New upstream release.
    - compiz crashed with SIGABRT in raise() (LP: #748163)
    - System freezes when maximize button is clicked (LP: #754063)
    - compiz crashed with SIGSEGV in QuicklistView::IsMenuItemSeperator()
      (LP: #754302)
    - compiz crashed with SIGSEGV in std::_List_node_base::_M_hook()
      (LP: #754235)
    - compiz crashed with SIGSEGV in ubus_server_pump_message_queue()
      (LP: #754657)
    - drag from dash to launcher (LP: #662616)
    - Add a test case for unity-decorator regressions (LP: #736878)
    - the files place category combo has empty space (LP: #741641)
    - panel superposition (LP: #742859)
    - Unity Launcher stops autohiding and is not responsive (LP: #744325)
    - Unity Launcher stops autohiding and is not responsive (LP: #744325)
    - [FFE] Need API to set urgency from background process (LP: #747677)
    - Launcher - Escape from 'drag behind the Launcher' interaction
      (LP: #750298)
    - Launcher needs to be desaturated when Dash is open, not transparent.
      (LP: #750358)
    - compiz crashed with SIGSEGV in free() (LP: #752293)
    - migrate_favorites.py crashed with ImportError in __main__: No module
      named gconf (LP: #752176)
    - compiz crashed with SIGSEGV in PluginClassHandler<DecorWindow,
      CompWindow, 0>::get() (LP: #743807)
    - cannot close the dash by clicking on the bfb (LP: #753914)
    - Animation for Grid Previews is broken (LP: #754088)
    - compiz crashed with SIGSEGV in PanelMenuView::OnPlaceViewShown()
      (LP: #754585)
    - Pressing F10 then "left arrow" wit Unity on Natty makes the system
      unusable (LP: #756867)
    - compiz crashed with SIGSEGV in __pthread_mutex_lock() (LP: #711231)
    - Tooltips and Dash Font Problems (LP: #741605)
    - Title elipisising incorrect. Type “Shotwell” for a good example
      (LP: #750350)
    - compiz crashed with SIGSEGV in Launcher::Launcher() (LP: #748096)
    - BFB - Turn top left corner blue rather than Ubuntu logo (LP: #755286)
    - launcher appears and gets stuck when resizing windows with mouse
      (LP: #754690)
    - Wrong item gets dragged out (LP: #729796)
    - Launcher - when the launcher is folded, the bottom icon partially falls
      off the end of the screen (LP: #731869)
    - unity-window-decorator: Resize padding: Tiny focused windows lose resize
      padding and shadow when <69 pixels wide (LP: #737707)
    - Deinstalling an application with launcher entry leaves orphaned shortcut
      (LP: #748107)
    - Two Nautilus windows open when clicked on a device icon on Launcher
      (started after 3.8.2) (LP: #748299)
    - compiz crashed with SIGSEGV in Launcher::AnimationTimeout()
      (LP: #749890)
  * debian/control:
    - build-dep on latest nux (ABI break)
  * debian/unity-common.install:
    - install the desktop file for the new capplet
 -- Didier Roche <email address hidden> Mon, 11 Apr 2011 12:42:33 +0200

affects me too , but not 'sometimes' , Its always !

I use ubuntu 11.04 beta 1

my video card is intel g828 and compiz was working good in ubuntu 10.04

Increasing priority due to number of duplicates.

This bug can be reproduced by running "metacity --replace" while compiz is running.

This is a bug in glibmm (https://bugzilla.gnome.org/show_bug.cgi?id=561885) we tried to workaround in Compiz by never returning false in the event source callback. It appeared to be problematic with some people experiencing infinite loops. There's a patch in bugzilla we should try and maybe improve.

This happens to me on every boot now as of yesterday's updates. Video card is a Radeon 3850, but compiz still appears to be running, just without the Unity environment. There's just Nautilus on the desktop, and startup items do load. To get anything done, I have to start apps with DISPLAY=:0 from another login.

It appears the problem was, in my case, related to a misconfiguration on the
gnome-launcher.
The default session launched was 'unity', due to a previous installation of
ubuntu netbook-edition. By setting the default session to 'ubuntu' , unity
start correctly with X.
On Apr 20, 2011 5:12 PM, "Geoffrey Pursell" <email address hidden> wrote:
> This happens to me on every boot now as of yesterday's updates. Video
> card is a Radeon 3850, but compiz still appears to be running, just
> without the Unity environment. There's just Nautilus on the desktop,
> and startup items do load. To get anything done, I have to start apps
> with DISPLAY=:0 from another login.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (759791).
> https://bugs.launchpad.net/bugs/711231
>
> Title:
> compiz crashed with SIGSEGV in __pthread_mutex_lock()
>
> Status in Unity:
> Triaged
> Status in “compiz” package in Ubuntu:
> Triaged
> Status in “unity” package in Ubuntu:
> Fix Released
> Status in “compiz” source package in Natty:
> Triaged
> Status in “unity” source package in Natty:
> Fix Released
>
> Bug description:
> Binary package hint: compiz
>
> When logging in, sometimes Unity does not finish loading. No
> indicators appear but the desktop icons will. I can't interact with
> anything because compiz will have crashed.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.04
> Package: compiz-core 1:0.9.2.1+glibmainloop4-0ubuntu8
> ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
> Uname: Linux 2.6.38-1-generic x86_64
> Architecture: amd64
> CrashCounter: 1
> DRM.card0.DP.1:
> status: disconnected
> enabled: disabled
> dpms: Off
> modes:
> edid-base64:
> DRM.card0.HDMI.A.1:
> status: disconnected
> enabled: disabled
> dpms: Off
> modes:
> edid-base64:
> DRM.card0.LVDS.1:
> status: connected
> enabled: enabled
> dpms: On
> modes: 1366x768
> edid-base64:
AP///////wAwZAMJAQEBASMTAQOAHRF4CoWVmVdPjyYhUFQAAAABAQEBAQEBAQEBAQEBAQEBux1W6lAAGTAjcFoAJ6YQAAAYAAAADwAC0ALQAAUBBUzUAg4AAAAA/gBUTURJU1BMQVkKICAgAAAA/gBMVDEzM0VFMDkxMDAKALI=
> DRM.card0.VGA.1:
> status: disconnected
> enabled: disabled
> dpms: Off
> modes:
> edid-base64:
> Date: Tue Feb 1 08:03:58 2011
> DistUpgraded: Yes, recently upgraded Log time: 2010-08-25 06:21:49.797653
> DistroCodename: natty
> DistroVariant: ubuntu
> ExecutablePath: /usr/bin/compiz
> GraphicsCard: Subsystem: CLEVO/KAPOK Computer Device [1558:3100]
> MachineType: System76, Inc. Lemur UltraThin
> ProcCmdline: compiz
> ProcEnviron:
> LANGUAGE=en_US:en
> PATH=(custom, user)
> LANG=en_GB.utf8
> LC_MESSAGES=en_US.utf8
> SHELL=/bin/bash
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic
root=UUID=625ed789-1cb3-4081-9c7e-f812810b5126 ro quiet splash vt.handoff=7
> SegvAnalysis:
> Segfault happened at: 0x7fe9e2bd2394 <__pthread_mutex_lock+4>: mov
0x10(%rdi),%esi
> PC (0x7fe9e2bd2394) ok
> source "0x10(%rdi)" (0x894c02fa8328ec9b) not located in a known VMA region
(needed readable region)!
> destination "%esi" ok
> SegvReason: reading unknown VMA
> Signal: 11
> SourcePackage: compiz
> StacktraceTop:
> __pthread_mutex_lock (mutex=0x894c02fa8328ec8b) at pthread_mutex_lock.c:50
> g_source_unref...

Avignon: I had no previous installation of netbook edition, but I had switched to the "Ubuntu Classic" session once Unity stopped working. Switching back to the "Ubuntu" session makes Unity work again. Fantastic!

My bug #765072 was duped to this one. I've used only a straight-up Unity session since installing beta 1 and have experienced this crash. If unrelated, both mine and the more popular bug #740897 should be un-duped from this bug report.

The bug still be there...

Last Natty 64-bit, and Gnome

I have the same issue with ATI/xorg driver and AMD official driver.

the bug is still here after the final release please help !!

For those who are still having problems with Compiz, particularly if you cannot get the titlebar to appear on your windows, I suggest using Metacity. This will give you a working desktop environment until a fix is released:

metacity --replace

The other thing you can do is select "Ubuntu Classic (No Effects)" as your desktop session when you log in.

I confirm taht the bug is still here.
I have installed Natty in two machines (Lenovo T61 and Lenovo ThinkCengtre 8810-AA5) and on both the leak can be easily reproduced: just minimize and restore an gnome-terminal window, for example. Or just drag a window to the top until touching the gnome-panel on the top.
It seems that any graphic operation (minimize, maximize, open, etc.) makes that compiz leak memory.

We should really try to fix the problem in GLibmm improving the patch attached in that bug report https://bugzilla.gnome.org/show_bug.cgi?id=561885.

I recommend to not consider this bug for an SRU anymore, and wll update the milestone accordingly.

Rationale:
- the only potential fix for the problem has proved to have widespread and critical side-effects when used on compiz (and was reverted as a consequence)
- the issue occurs only under special conditions and doesn't impact users in regular daily usage

The bug is moved to the backlog though, as it is still something we'd like to get rid of for the next version.

I have this problen on oneric i cant see anything in my desktop

The source unreffing has been fixed upstream and in the oneiric branch. I'd love to know if this is still happening.

sorry for the wrong status, now changed to incomplete per Tim's comment.

Might be fixed since a while, as the latest duplicate report was also about "natty"