Crash Caused by GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close()

Bug #517295 reported by z0man
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: f-spot

Xubuntu Karmic
--------------------
Description: Ubuntu 9.10
Release: 9.10

 Package details
-------------------------
f-spot:
  Installed: 0.6.1.5-0ubuntu1
  Candidate: 0.6.1.5-0ubuntu1
  Version table:
 *** 0.6.1.5-0ubuntu1 0
        500 http://gb.archive.ubuntu.com karmic-updates/main Packages
        100 /var/lib/dpkg/status
     0.6.1.3-2 0
        500 http://gb.archive.ubuntu.com karmic/main Packages

What I did to get this
----------------------------
This is on a newly installed system. I connected my camera and nothing happened
I then checked the docs and found I had to install F-Spot in order for auto "Import" auto run to work
I installed F-Spot and then connected the camera, still nothing happened
I then just clicked the "+" sign and saw that the camera was being detected.
When I click "Import Button in the Import window, it died.
I ran Fspot in terminal mode and scanned the output and found that this line

GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close()

Followed by

(/usr/lib/f-spot/f-spot.exe:1745): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
item ImportCommand+SourceItem
Stacktrace:

  at (wrapper managed-to-native) GdkGlx.Context.glXDestroyContext (intptr,System.Runtime.InteropServices.HandleRef) <0x00004>
  at (wrapper managed-to-native) GdkGlx.Context.glXDestroyContext (intptr,System.Runtime.InteropServices.HandleRef) <0xffffffff>
  at GdkGlx.Context.Destroy () <0x0005d>
  at FSpot.Widgets.PhotoImageView.OnUnrealized () <0x00034>
  at Gtk.Widget.unrealized_cb (intptr) <0x0004e>
  ...
Please attached log for full stacktrace

My Camera
----------------
Canon IXY Digital (Canon PC1209)

Additional
-------------
My camera did not appear in the File System

Revision history for this message
z0man (z0manifest) wrote :
Revision history for this message
z0man (z0manifest) wrote :

Apologizes for the duplicate entry and the minor grammar "Please attached log for full stacktrace",

 Ubuntu LaunchedPad looked like it halted, I'm a first time bug submitter. And the correct grammar is "Please see attached log".

Revision history for this message
z0man (z0manifest) wrote :

Eek I said, "LaunchedPad"...

Ok I did another two tests and found that "Importing Folders" does the same thing.

I have attached another log file for that enviornment.

(/usr/lib/f-spot/f-spot.exe:2572): GdkPixbuf-WARNING **: GdkPixbufLoader finalized without calling gdk_pixbuf_loader_close() - this is not allowed. You must explicitly end the data stream to the loader before dropping the last reference.
item ImportCommand+SourceItem
cleanup context
cleanup context
Stopping
Stacktrace:

  at (wrapper managed-to-native) GdkGlx.Context.glXDestroyContext (intptr,System.Runtime.InteropServices.HandleRef) <0x00004>
  at (wrapper managed-to-native) GdkGlx.Context.glXDestroyContext (intptr,System.Runtime.InteropServices.HandleRef) <0xffffffff>
  at GdkGlx.Context.Destroy () <0x0005d>
  at FSpot.Widgets.PhotoImageView.OnUnrealized () <0x00034>
  at Gtk.Widget.unrealized_cb (intptr) <0x0004e>
  at (wrapper native-to-managed) Gtk.Widget.unrealized_cb (intptr) <0xffffffff>
  at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr) <0x00004>
  at (wrapper managed-to-native) Gtk.Object.gtk_object_destroy (intptr) <0xffffffff>
  at Gtk.Object.Destroy () <0x00038>
  at Gtk.Widget.Destroy () <0x00010>

Please see "Crash Log - Folder Importing"

Revision history for this message
z0man (z0manifest) wrote :
Changed in f-spot (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Chris Halse Rogers (raof) wrote :

Ok. The GDK-Pixbuf warning is a harmless red-herring.

The crash here is in destroying some of the F-Spot widgets, which use GLX. I suspect that this is actually a bug in your graphics drivers.

Could you please try running this command in a terminal:
"""
LIBGL_DRIVERS_PATH=/nowhere f-spot
"""
and then try to reproduce the crash? That will disable 3D acceleration while running f-spot. I think that should prevent the crash. If that works, I'll move this bug to the appropriate place.

Changed in f-spot (Ubuntu):
status: New → Incomplete
assignee: nobody → Chris Halse Rogers (raof)
Revision history for this message
z0man (z0manifest) wrote :

Ok I did run that command you requested and attempted to try and retrace my steps to see if I can replicate the bug.

Soon I clicked "Import" it reset the Xserver so I had to re-login.

The Import worked!

I ran your command with the added Log recording

***
LIBGL_DRIVERS_PATH=/nowhere f-spot > fspot-newlog
****
Please see attached log if that helps try and understand why the "Import" resets the Xserver.

Revision history for this message
Chris Halse Rogers (raof) wrote :

Oooh, boy. Ok. This isn't an f-spot bug; anytime the X server crashes it's a bug in the X server :)

Could you follow the steps outlined here: https://wiki.ubuntu.com/X/Backtracing to get a backtrace of your X server crash? Thanks!

affects: f-spot (Ubuntu) → mesa (Ubuntu)
Changed in mesa (Ubuntu):
assignee: Chris Halse Rogers (raof) → nobody
Bryce Harrington (bryce)
tags: added: xubuntu
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automatic notification.]

Hi z0man,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 517295

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 517295 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/517295

Changed in mesa (Ubuntu):
status: Incomplete → New
status: New → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in mesa (Ubuntu):
status: Incomplete → Expired
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.