Pidgin crashing - _gtk_text_btree_tag assertion failed

This started today after running a system upgrade and doing some cleanup. At first swiftdove started crashing but then I realised that the build I was using was no longer in the aur. I uninstalled it and installed a new version (also from AUR).
Pidgin crashes as I send out a message. Ive confirmed that the messages do actually get sent out.
Is anyone else getting this same crash?
/var/log/pacman.log
[2009-07-16 20:20] upgraded perl (5.10.0-4 -> 5.10.0-5)
[2009-07-16 20:20] warning: /etc/ssl/openssl.cnf installed as /etc/ssl/openssl.cnf.pacnew
[2009-07-16 20:20] upgraded openssl (0.9.8k-2 -> 0.9.8k-4)
[2009-07-16 20:20] upgraded run-parts (2.31-1 -> 3.1.3-1)
[2009-07-16 20:20] Updating certificates in /etc/ssl/certs... 4 added, 0 removed; done.
[2009-07-16 20:20] Running hooks in /etc/ca-certificates/update.d....done.
[2009-07-16 20:20] upgraded ca-certificates (20080809-5 -> 20090709-1)
[2009-07-16 20:20] upgraded libmysqlclient (5.1.35-2 -> 5.1.36-1)
[2009-07-16 20:20] upgraded mysql-clients (5.1.35-2 -> 5.1.36-1)
[2009-07-16 20:20] upgraded mysql (5.1.35-2 -> 5.1.36-1)
[2009-07-16 20:26] removed swiftdove-nocona (2.0.0.16-1)
[2009-07-16 20:27] installed libgnomecanvas (2.26.0-1)
[2009-07-16 20:27] installed gnome-mime-data (2.18.0-3)
[2009-07-16 20:27] installed gnome-vfs (2.24.1-2)
[2009-07-16 20:27] installed libbonobo (2.24.1-1)
[2009-07-16 20:27] installed libgnome (2.26.0-2)
[2009-07-16 20:27] installed libbonoboui (2.24.1-1)
[2009-07-16 20:27] installed gnome-keyring (2.26.3-1)
[2009-07-16 20:27] installed libgnomeui (2.24.1-1)
[2009-07-16 20:29] installed swiftdove-intel64-pgo (2.0.0.21-1)
[2009-07-16 21:33] synchronizing package lists
[2009-07-16 21:33] starting full system upgrade
[2009-07-16 21:55] synchronizing package lists
[2009-07-16 21:55] synchronizing package lists
[2009-07-16 21:56] starting full system upgrade
[2009-07-16 21:56] synchronizing package lists
[2009-07-16 21:56] starting full system upgrade
[2009-07-16 21:59] synchronizing package lists
[2009-07-16 22:00] starting full system upgrade
[2009-07-16 22:02]  > Rebuilding xdg icon database ... DONE
[2009-07-16 22:02] removed kdemod-kdeartwork-kworldclock (4.1.3-1)
[2009-07-16 22:03] removed nforce-utils (1.0.0310-1)
[2009-07-16 22:31] installed intltool (0.40.6-1)
[2009-07-16 22:39] upgraded pidgin (2.5.8-1 -> 2.5.8-1)
[ brendan@watricky : 23:15:30 : ~ ]
tail plog.1.txt
(23:11:28) util: Writing file blist.xml to directory /home/brendan/.purple
(23:11:28) util: Writing file /home/brendan/.purple/blist.xml
(23:11:29) msn: C: NS 000: PNG
(23:11:29) msn: S: NS 000: QNG 43
(23:11:32) pidgin-encryption: send_msg: [email protected]
(23:11:32) pidgin-encryption: Outgoing Msg::<font color="#000a8e">that's always happened</font>::
(23:11:32) jabber: Unable to find caps: nothing known about buddy
(23:11:32) jabber: Sending (ssl): <message type='chat' id='purple8ad93196' to='identity@protected'><x xmlns='jabber:x:event'><composing/></x><body>that&apos;s always happened</body><html xmlns='http://jabber.org/protocol/xhtml-im'><body xmlns='http://www.w3.org/1999/xhtml'><span style='color: #000a8e;'>that&apos;s always happened</span></body></html></message>
Gtk:ERROR:gtktextbtree.c:1885:_gtk_text_btree_tag: assertion failed: (seg != indexable_seg)

Seems to have been resolved by changing my gtk theme to match the KDE theme using kdemod-extragear-gtk-qt-engine. tsk. Ive never even changed themes before.
My guess is that swiftdove's "depending on the gnome-related packaged messed with the GTK settings.

Similar Messages

  • CVI crashes - event log shows [FATAL] [LW_UAE_Handler] [..\jeff\i386\except.c:161] Assertion failed: 0.

    Hello,
    When calling lua_error(L) (pushing a Lua error in an embedded lua interpreter in my CVI code), I have been encountering a complete crash.  Not only does my code stop running, but the full CVI 9.1.1 IDE crashes without even an error message.  When I look in the windows xp event log I find the following:
    The description for Event ID ( 0 ) in Source ( CVI ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [16:45:30.768] [FATAL] [LW_UAE_Handler] [..\jeff\i386\except.c:161] Assertion failed: 0.
    When I recompile my project with visual studio, the identical code does not crash or cause any problems.  Any insite on this problem would be greatly appreciated.
    thanks,
    Alex Corwin

    Hello Alex,
    Could you try to generate a crash dump? Also, here is a community example of code using an embedded interpreter LUA in a LabWindows/CVI Project.
    Regards,
    Jeff L.
    Applications Engineer | National Instruments

  • Powerpoint Crash:  "Assertion Failed"

    I'm experiencing repeated crashes while audio editing in Presenter.
    When it crashes, I get a pop-up message that reads as follows:
    "Assertion Failed!
    Program:  Files/MicrosoftOffice\Office14\POWERPNT.EXE
    File: .\Source\Mp3AudioReader.cpp
    Line: 126
    Expression: bufSize > 0
    For information on how your program can cause an assertion failure, see the VisualC++ documentation on asserts
    (Press Retry to debug the application – JIT must be enabled)"
    After the above message, I receive a message noting that the Adobe Presenter add-in caused Powerpoint to crasn and prompting me to uninstall Presenter.
    I'm using Windows 7, Powerpoint 2010, and Presenter 7.0.6 build 7604.
    Anyone know how to fix this?  I'm under deadline and need a fix soon.
    Thanks in advace to any gurus who have a fixit.

    I'm experiencing repeated crashes while audio editing in Presenter.
    When it crashes, I get a pop-up message that reads as follows:
    "Assertion Failed!
    Program:  Files/MicrosoftOffice\Office14\POWERPNT.EXE
    File: .\Source\Mp3AudioReader.cpp
    Line: 126
    Expression: bufSize > 0
    For information on how your program can cause an assertion failure, see the VisualC++ documentation on asserts
    (Press Retry to debug the application – JIT must be enabled)"
    After the above message, I receive a message noting that the Adobe Presenter add-in caused Powerpoint to crasn and prompting me to uninstall Presenter.
    I'm using Windows 7, Powerpoint 2010, and Presenter 7.0.6 build 7604.
    Anyone know how to fix this?  I'm under deadline and need a fix soon.
    Thanks in advace to any gurus who have a fixit.

  • Assert Failed:  Flashfarm

    I am having a problem on intel macs with a crash after an
    assert is tripped
    Assert failed:
    /flashfarm/depot/main/player/branches/FlashPlayer/FlashPlayer8_MacIntel_Integrated/platfo rm/mac/plugins/../mpi_player.cpp:5445
    this is with 8.0r27 (is there a later one for intel mac)
    my code dumps har after this any word on why this assert
    fails?

    Yes, there is now a Flash Player 9 Beta for Intel-based
    Macintosh computers:
    http://www.adobe.com/products/flashplayer/public_beta/

  • Updated to Adobe Muse CC 2014, 2 days ago and I CANT even open it! It keeps on displaying the same ASSERTION FAILED IN FILE error.

    I love muse and have been using for years now. A couple of days ago I was really exited that they had a new version the  ADOBE MUSE CC 2014 so I updated it in my laptop. Now it wont even open. I had spent the last 3 days uninstalling and reinstalling MUSE CC 2014 thinking that it would help. But nothing works. I keep on having the same ASSERTION FAILED IN FILE error. At this point I am pretty much desperate and do not know really what to do and to make matters worse I have freelance work that needs to be done and update. If anyone can help I would really appreciated it.
    In addition, if anyone from the MUSE CC SUPPORT TEAM is reading this, please work on making access to you guys easier. I honestly could not find a way to talk to anyone from the ADOBE MUSE CC support team about this problem.

    I had the same problem but good news is I found the reason of problem and solution;
    I was using Windows 7 in English with timezone setting for Turkey. Adobe Muse was in English and had same problem, to solve this issue I even installed new Windows but it happened again.
    Solution is easy, I just changed Muse language settings from English to Turkish and so far so good i never had any crash or problem.
    Cheers!

  • Assert failed in /modules/streams/flv/TCFLVData.cpp

    Hi,
    We're running FMS 3.5.2 r654 on RHEL 5.2 and we're getting tons of errors like this:
    "2009-08-31      10:47:43        11394   (e)2581279      Assert failed in /modules/streams/flv/TCFLVData.cpp line 2033   -"
    Always the same line number.
    Can we safely ignore this error? What does it mean?
    We're only getting this since 3.5.2. We were running FMS 3.5.1 before, and weren't getting this error, but upgraded to get rid of the occasional "core experienced [x] failures"-crashes.
    Kind regards,
    Pieter Barrezeele

    thanks patrick for your interest.
    we're using the 2.0.3.
    this error code was never traced in the log file of the 2.0.2

  • I get Assertion Failed open report with CR viewer 2.0.23

    Post Author: gionnyDeep
    CA Forum: General
    any help?
    Assertion Failed: java.lang.Throwable        at com.crystaldecisions.reports.common.j.b.a(Unknown Source)        at com.crystaldecisions.reports.common.j.b.a(Unknown Source)        at com.crystaldecisions.reports.queryengine.b0.char(Unknown Source)        at com.crystaldecisions.reports.queryengine.b0.else(Unknown Source)        at com.crystaldecisions.reports.queryengine.b0.else(Unknown Source)        at com.crystaldecisions.reports.queryengine.b0.d(Unknown Source)        at com.crystaldecisions.reports.queryengine.b0.dt(Unknown Source)        at com.crystaldecisions.reports.queryengine.b0.dD(Unknown Source)        at com.crystaldecisions.reports.queryengine.b9.int(Unknown Source)        at com.crystaldecisions.reports.queryengine.b9.for(Unknown Source)        at com.crystaldecisions.reports.queryengine.b9.int(Unknown Source)        at com.crystaldecisions.reports.queryengine.b9.for(Unknown Source)        at com.crystaldecisions.reports.queryengine.b9.int(Unknown Source)        at com.crystaldecisions.reports.queryengine.b9.case(Unknown Source)        at com.crystaldecisions.reports.queryengine.b9.if(Unknown Source)        at com.crystaldecisions.reports.queryengine.b9.c(Unknown Source)        at com.crystaldecisions.reports.queryengine.b0.d(Unknown Source)        at com.crystaldecisions.reports.queryengine.b0.dt(Unknown Source)        at com.crystaldecisions.reports.reportdefinition.datainterface.l.a(Unknown Source)        at com.crystaldecisions.reports.dataengine.j.j(Unknown Source)        at com.crystaldecisions.reports.dataengine.j.i(Unknown Source)        at com.crystaldecisions.reports.dataengine.j.a7(Unknown Source)        at com.crystaldecisions.reports.dataengine.j.a9(Unknown Source)        at com.crystaldecisions.reports.dataengine.j.char(Unknown Source)        at com.crystaldecisions.reports.dataengine.n.a(Unknown Source)        at com.crystaldecisions.reports.dataengine.a5.a(Unknown Source)        at com.crystaldecisions.reports.dataengine.a5.Z(Unknown Source)        at com.crystaldecisions.reports.dataengine.a5.<init>(Unknown Source)        at com.crystaldecisions.reports.dataengine.a5.<init>(Unknown Source)        at com.crystaldecisions.reports.dataengine.a5.<init>(Unknown Source)        at com.crystaldecisions.reports.dataengine.a5.a(Unknown Source)        at com.crystaldecisions.reports.formatter.formatter.objectformatter.bn.<init>(Unknown Source)        at com.crystaldecisions.reports.formatter.formatter.objectformatter.bn.if(Unknown Source)        at com.crystaldecisions.reports.formatter.formatter.d.k.<init>(Unknown Source)        at com.crystaldecisions.reports.formatter.formatter.d.o.<init>(Unknown Source)        at com.crystaldecisions.reports.formatter.formatter.d.o.a(Unknown Source)        at com.crystaldecisions.reports.reportengineinterface.g.if(Unknown Source)        at com.crystaldecisions.reports.reportengineinterface.g.do(Unknown Source)        at com.crystaldecisions.reports.reportengineinterface.JPEReportSource.getPage(Unknown Source)        at com.businessobjects.crystalreports.viewer.core.rs.b.if(Unknown Source)        at com.businessobjects.crystalreports.viewer.core.aw.a(Unknown Source)        at com.businessobjects.crystalreports.viewer.core.aw.run(Unknown Source)        at java.lang.Thread.run(Thread.java:619)

    Sorry, but you have to define "viewer just crashed". To different people this means different things; error, viewer never shows up, application terminates, etc., etc., etc....
    If the issue is only 10% of computers then it is not
    Re. "...could be caused by:"
    - previous installation of CR8.5 (or earlier) runtime (how to cleanup it correctly?)
    possibly - see below
    - OS configuration (what we need to ajust?)
    probably not - as long as it's the same OS and SPs
    - something missing in our code (but why it works in 90% cases?)
    -no
    - something wrong with CRXI runtime (but we a using latest available MSMs, and again, this works in 90% ...)
    possibly see below.
    I would approach the issue by running [Modules|https://smpdl.sap-ag.de/~sapidp/012002523100006252802008E/modules.zip] and comparing the dlls loading on a computer that works and one that "crashes"...
    Your second utility is [Process Monitor|http://technet.microsoft.com/en-ca/sysinternals/bb896645.aspx] but ProcMon creates large and difficult to read files.
    Oh, and get the powers that be to start to consider moving away from this legacy "stuff". Like I said, PE APIs have been gone since version 9 of CR and RDC has been retired in CR XI R2 (11.5). Neither product is supported anymore.
    - Ludek

  • Lightroom 4 - "assertion Failed" error after install

    I recently upgraded from 3.6 to 4.  Previously, I attempted to install Lightoom 4 beta and tried to open a 3.6 catalog.  When it did not work, I simply uninstalled that Lightroom 4 beta.
    Now, when I installed Lightroom 4(Upgrade version), installation was uneventful.  However, I cannot open the program without crashing.  The error message is "assertion failed"   Additional detail on the error shows the following.
    Problem signature:
      Problem Event Name:          APPCRASH
      Application Name:          lightroom.exe
      Application Version:          4.0.0.10
      Application Timestamp:          4f45ddd8
      Fault Module Name:          ntdll.dll
      Fault Module Version:          6.1.7601.17725
      Fault Module Timestamp:          4ec4aa8e
      Exception Code:          c015000f
      Exception Offset:          000000000006fd5c
      OS Version:          6.1.7601.2.1.0.256.48
      Locale ID:          1033
    I assume this has something to do with remnants of my previous Lightroom 4 beta installation(which was subsequently uninstalled prior to full Lightroom 4 installation).  Does anyone know where the catalog resides by default and whether I can fix this problem by deleting/renaming the catalog(if that is what the problem is).
    Thanks

    Ok it is fixed now.  Locating the Lightroom 3 catalog file and opening it in Lightroom 4 ( right click and choose program...) prompted me to upgrade the catalog.  This fixed the issue

  • Oops! An untagged string (assertion failed!) got thrown far enough that we display it to the user. T

    After installing the latest update to Lightroom 5, I started getting this message when I started Lightroom:
    Adobe Photoshop Lightroom 5[4407]: Oops! An untagged string (assertion failed!) got thrown far enough that we display it to the user. This shouldn't happen.
    From what I've found through searches, plugins may be related to the problem.
    The problem I'm having here is the lack of any information - no crash log, no reference to what caused this - in any log file.  I've taken the most recently installed or updated pugins and moved them elsewhere to test and am still getting this message.
    I assume that when I see "This shouldn't happen" as a message from the software, that it's a significant warning.  What can go wrong / is going wrong as a result of the related problem?  Is my data in danger?
    All help gratefully appreciated.

    Off.line wrote:
    Thanks for your thoughts, Rob.
    You're welcome .
    Off.line wrote:
    The few times I wrote something like this, I dumped as much data as I could somewhere to facilitate the debugging process and it's a bit dissappointing that there seems to be no such output.
    No such output enabled for users. I'm sure the developers have some way of debugging..
    Off.line wrote:
    I wonder what the output of the -tracebacks switch would be.
    It shows the error in context (I've done it before, but it was a long time ago) - what Lr was doing when error occurred. For example, if plugin was executing, it would show that.
    Off.line wrote:
    I'm not familiar with the .agprefs file
    It's where Lr stores preferences - see your presets folder (location is accessible via a button in Lr preferences dialog box: "Show Lightroom Presets Folder..."). Look in 'Preferences' subfolder. It's the source of some aberrant behavior sometimes..
    Off.line wrote:
    my catalog is backed up in two places, on two separate devices.  But if there's corruption within the catalog, then the backups are bad, too.
    If you've been using Lightroom's built-in catalog backup feature, then it creates a new backup each time, so old backups, if not yet deleted, may not have same problem as newer backups. But I think we're getting ahead of ourselves now.
    Rob

  • HELP Assertion failed!

    Just this evening LR2 crashed on me while processing a wedding shoot. I can now not get back into LR2, all I get is a dialogue proclaiming "Assertion failed".
    I have uninstalled and re-installed but to no avail. I am still getting this same message and I have lost my catalogue and prefs etc into the bargain.
    Can anyone please help?
    regards Ian

    Try uninstalling the program, run a registry cleaner, and reinstall.
    Jim

  • Assertion failed: t- numPointers == 0, ....

    I develop software on true64 Unix 5.0 and use JDK1.3.1 beta 2 (Fast VM) , I found exception like this
    Assertion failed: t->numPointers == 0, file ../../../src/share/native/sun/awt/font/t2k/tsimem.c, line 92
    exception system: exiting due to multiple internal errors:
    exception dispatch or unwind stuck in infinite loop
    exception dispatch or unwind stuck in infinite loop
    Had anyone ever met this exception before , what is it wrong , and how can i solve it ?

    Hi -
    We also came across this problem. It seems to be related to using anti aliased text in a drawString() call. Interestingly it happens on the second call using a particular font.
    Test case code is pasted below, which will crash the JVM on the second run through the main loop - i.e. the second time iterating through all the fonts.
    This code was cannibalised from another example posted here a while ago.
    Chris Davey
    ===========
    import java.awt.*;
    import java.awt.font.*;
    import java.awt.image.*;
    class Test {
    public static void main(String[] argv) {
    FontMetrics fm = null;
    String strings [] ={""," "," ","a","test string"};
    int iaBITypes [] = {BufferedImage.TYPE_3BYTE_BGR ,BufferedImage.TYPE_4BYTE_ABGR ,
                                BufferedImage.TYPE_4BYTE_ABGR_PRE ,BufferedImage.TYPE_BYTE_BINARY ,
                                BufferedImage.TYPE_BYTE_GRAY ,BufferedImage.TYPE_BYTE_INDEXED ,
                                BufferedImage.TYPE_INT_ARGB ,BufferedImage.TYPE_INT_ARGB_PRE ,
                                BufferedImage.TYPE_INT_BGR ,BufferedImage.TYPE_INT_RGB ,
                                BufferedImage.TYPE_USHORT_555_RGB ,BufferedImage.TYPE_USHORT_565_RGB ,
                                BufferedImage.TYPE_USHORT_GRAY };
    Toolkit t = Toolkit.getDefaultToolkit();
    System.out.println("hi");
    for (int idx = 0; idx < 100; idx++){
    Font fonts [] = GraphicsEnvironment.getLocalGraphicsEnvironment().getAllFonts();
    for (int ff=0;ff<fonts.length;ff++) {  // Try all fonts
    for (int iBIType = 0; iBIType < iaBITypes.length; iBIType++){
    BufferedImage bi = new BufferedImage(1000,1000,iaBITypes[iBIType]);
    Graphics2D g= (Graphics2D) bi.getGraphics();
    //FontRenderContext frc = g.getFontRenderContext();
    //XXX Problem Here - if
    //2nd Param (anti - aliasing ) is TRUE, then This
    //will crash on True 64 Unix - with either Sun or
    //Compaq JVM, on 2nd pass through
    FontRenderContext frc2 = new FontRenderContext(null,true,false);
    //TextLayout tl = new TextLayout("test-string",fonts[ff],frc);
    TextLayout tl2 = new TextLayout("test-string",fonts[ff],frc2);
    g.setFont(fonts[ff]);
    for (float a = -1000; a < 2000; a+=200)
    g.drawString("test",a,a);
    System.out.println("dumping threads: " );
    Thread ath[] = new Thread[512];
    Thread.currentThread().enumerate(ath);
    for (int i=0; i < ath.length; i++){
    if (ath[i] != null)
    System.out.println("\tThread: " + i + " " + ath);
    Keywords: Tru64 tsimem.c assert true64 crash

  • Assertion failed: (CGFloatIsValid(x)

    iPhoto crashed a couple of times while editing a couple of different pictures, and now everytime it starts up, an assert is firing and killing the App.  In iOS developer documentation, Apple requests that apps never "just die" when they encounter an error, and this is certainly a case that looks to be unrelated to the photo content, in that the stack trace points at some window decoration drawing it seems to me.   What can I do to stop this from happening so that I can open iPhoto again?  The bezierPath fill should not be using photo data, so what gives?
    Application Specific Information:
    Assertion failed: (CGFloatIsValid(x) && CGFloatIsValid(y)), function void CGPathAddLineToPoint(CGMutablePathRef, const CGAffineTransform *, CGFloat, CGFloat), file Paths/CGPath.cc, line 224.
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib                  0x948d6922 __pthread_kill + 10
    1   libsystem_pthread.dylib                 0x938c41bc pthread_kill + 101
    2   libsystem_c.dylib                       0x96a623a8 abort + 155
    3   libsystem_c.dylib                       0x96a2d4a6 __assert_rtn + 347
    4   com.apple.CoreGraphics                  0x9517972c CGPathAddLineToPoint + 164
    5   com.apple.CoreGraphics                  0x951c7bb9 CGContextAddLineToPoint + 148
    6   com.apple.AppKit                        0x92f2c5ae -[NSBezierPath fill] + 210
    7   com.apple.iPhoto                        0x00576591 0xb9000 + 4969873
    8   com.apple.iPhoto                        0x001cbbce 0xb9000 + 1125326
    9   com.apple.AppKit                        0x92ed62ed -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inContext:topView:] + 1034
    10  com.apple.AppKit                        0x934af73d __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 223
    11  com.apple.AppKit                        0x92ed5bee -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 2085
    12  com.apple.AppKit                        0x92ed5307 -[NSView(NSLayerKitGlue) drawLayer:inContext:] + 115
    13  com.apple.AppKit                        0x93179f9a -[_NSViewBackingLayer drawInContext:] + 383
    14  com.apple.QuartzCore                    0x999755b6 backing_callback(CGContext*, void*) + 96
    15  com.apple.QuartzCore                    0x9984ccca CABackingStoreUpdate_ + 3412
    16  com.apple.QuartzCore                    0x9997554e ___ZN2CA5Layer8display_Ev_block_invoke + 93
    17  com.apple.QuartzCore                    0x9999f593 x_blame_allocations + 88
    18  com.apple.QuartzCore                    0x9984b9b0 CA::Layer::display_() + 1552
    19  com.apple.QuartzCore                    0x9984b39b -[CALayer _display] + 20
    20  com.apple.QuartzCore                    0x9984b37c CA::Layer::display() + 186
    21  com.apple.QuartzCore                    0x9984b2ba -[CALayer display] + 20
    22  com.apple.AppKit                        0x9366301b _NSBackingLayerDisplay + 105
    23  com.apple.AppKit                        0x93662fad -[_NSBackingLayer display] + 26
    24  com.apple.AppKit                        0x931798ff -[_NSViewBackingLayer display] + 1788
    25  com.apple.QuartzCore                    0x9984b1e4 CA::Layer::display_if_needed(CA::Transaction*) + 690
    26  com.apple.QuartzCore                    0x9984aa6c CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 38
    27  com.apple.QuartzCore                    0x9983fab0 CA::Context::commit_transaction(CA::Transaction*) + 292
    28  com.apple.QuartzCore                    0x9983f849 CA::Transaction::commit() + 393
    29  com.apple.QuartzCore                    0x9983f64f CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 75
    30  com.apple.CoreFoundation                0x9459c09e __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 30
    31  com.apple.CoreFoundation                0x9459bfef __CFRunLoopDoObservers + 399
    32  com.apple.CoreFoundation                0x945757ca CFRunLoopRunSpecific + 666
    33  com.apple.CoreFoundation                0x9457551b CFRunLoopRunInMode + 123
    34  com.apple.HIToolbox                     0x96686931 RunCurrentEventLoopInMode + 259
    35  com.apple.HIToolbox                     0x966866ad ReceiveNextEventCommon + 526
    36  com.apple.HIToolbox                     0x967ec678 _BlockUntilNextEventMatchingListInModeWithFilter + 92
    37  com.apple.AppKit                        0x92d506d9 _DPSNextEvent + 1602
    38  com.apple.AppKit                        0x92d4fc00 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
    39  com.apple.AppKit                        0x92d46e1c -[NSApplication run] + 727
    40  com.apple.AppKit                        0x92cecc18 NSApplicationMain + 1165
    41  com.apple.iPhoto                        0x000c90b9 0xb9000 + 65721
    42  com.apple.iPhoto                        0x000c8705 0xb9000 + 63237

    Does this involve iPhoto for Mac in some way? If so, a full description of the issue is best:
    - What version of iPhoto.
    - What version of the Operating System.
    - Details. As full a description of the problem as you can. For instance: 'iPhoto won't export' is best explained by describing how you are trying to export, and so on.
    - History: Is this going on long? Has anything been installed or deleted?
    - Are there error messages?
    - What steps have you tried already to solve the issue.
    - Anything unusual about your set up? Or how you use iPhoto?
    Anything else you can think of that might help someone understand the problem you have.

  • Assertion Failed : Lot of Application say the same thing :(

    Hello , in a first part , sorry for my english , I'm French and I'm not very good in English.
    so now , the problem :
    When I launch an application which need to write something ( like SpotLight ) or a Browser ( I have test with Google Chrome and Safari )  , I have the text :
                  Application Specific Information
                   obj[966]: garbage collector is OFF
                   Assertion Failed: (stat(path,&stat_data) == 0 ) ,
                   function _open_and_mmap_for_reading ,
                   file /SourceCache/LanguageIdentifier/LanguageIdentifier-106/LanguageIdentifier.c , line 550
    and the error log go away...
    So I search the file in Terminal, and the directory "SourceCache" doesn't exist ... so the rest doesn't exist too ...
    And it's why the assertion comes.
    So I demand , how can I fix this problem ?
    My Configuration is :
    a MacBook Pro 13"
    Mac OS X Lion
    Thanks for your help

    Please post the whole crash report.

  • SQL error: Internal database error *** ERROR *** Assertion failed: 201501 (10.0.1.3415)

    A SQLA10 production database has been crashing at a customer site.
    Here's the error which displayed when I tried to unload the database...
    Unloading "DBA"."schedule_profile" into C:\resq\resqprod2\db\unload\719.dat (relative to server)
    Unloading "DBA"."schedules" into C:\resq\resqprod2\db\unload\720.dat (relative to server)
    ***** SQL error: Internal database error *** ERROR *** Assertion failed: 201501 (10.0.1.3415)
    Page for requested record not a table page or record not present on page -- transaction rolled back
    The database 'C:\resq\resqprod2\db\resqprod2.db' could not be unloaded.
    The database 'C:\resq\resqprod2\db\resqprod2.db' could not be unloaded.
    I think that backups may also have this error.
    Can the database be salvaged?
    Thank you,
    Doug

    Hi Doug,
    The error seems to be saying that a pointer is pointing to an invalid page.
    Actually, the assertion message is suggesting that we were scanning for a row (record) on a particular page where we expected to find it, and didn't - the table page is likely corrupt.
    Does a utility exist which would eliminate all pointers to invalid pages?
    No. If the database is corrupted, it is best to move to your database recovery procedure from a valid backup. See KBA 1959391 - How can a SQL Anywhere (stand alone) database be restored from a full or incremental backup?
    If you do not have a valid database backup but can still start and connect to the corrupted database (and it seems that you can), you can attempt to salvage the data out of the corrupted database tables manually to extract it to a new database (as Jinwoo suggested). See KBA 1959030 - How To Salvage Data When There are Corrupt Pages in the Database. Using -e to skip tables is appropriate and then trying to select the data that is not contained on invalid pages via the KBA instructions is your best option in this case.
    Does sap/sybase offer a recovery service?
    No, there is no such "recovery service" underneath SAP and any previous mentions of salvages were one-off contracts underneath Sybase Professional Services, and not a technical support service. These contracts are not available at SAP.
    This topic was discussed thoroughly on the SQL Anywhere forum ( http://sqlanywhere-forum.sap.com/ ) previously here and here.
    The prevention for this situation is to have properly validated backups, preferably in multiple backup generations to provide many opportunities for recovery. See: http://wiki.scn.sap.com/wiki/x/3QNcFg
    Regards,
    Jeff Albion
    SAP Active Global Support

  • Uttsc assertion failed

    Dear all,
    I'm running Solaris 10.4, SRSS 4.0 and Sun Ray Connector 1.1; until I tried using the Sun Ray Connector, everything was working very well and I was very happy with it all.
    If I run:
    $ /opt/SUNWuttsc/bin/uttsc <a windows server>
    I have the following error returned to me:
    Assertion failed: 0 && "Invalid mode value", file admin.c, line 354
    /opt/SUNWuttsc.bin/utsc[137]: 13753 Abort
    What am I doing wrong? Any help would be greatly appreciated; my googles have yet to turn up anything that resolves this.
    Thanks in advance

    An assertion failure means that the program has encountered a situation that should never occur and that the program logic can not handle in any sensible way. The program has deliberately crashed itself rather than taking the risk of proceeding and perhaps causing damage to your data. The failure might mean that there is a bug in the program or it might mean that the RDP traffic stream has been corrupted, but in any case it's very unlikely that you can do anything to fix the problem. You should open a support call with Sun and give them as many details as you can about your environment and what was happening at the time this failure happened. If the program left a file named "core" behind then send that to Sun too. It contains a snapshot of the memory of the process at the time it failed.
    It's possible that you could work around (hide, not fix) the problem by changing some of the RDP or Sun Ray settings that are being used for this session, but I don't know enough about the Windows Connector to make any suggestions. If you decide to try this then please make a note of what the settings are now, before you change anything, so that you can describe your current configuration correctly to Sun. This will give them the maximum chance of being able to reproduce and then fix the real problem.

Maybe you are looking for