GNOME Bugzilla – Bug 152303
gnome-cd-properties crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: magicdev Severity: normal Version: GNOME2.6.1 1.1.6 Gnome-Distributor: Debian Synopsis: gnome-cd-properties crash Bugzilla-Product: magicdev Bugzilla-Component: general Bugzilla-Version: 1.1.6 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: Running this app by an xterm I receive this message (gnome-cd-properties:14972): GdkPixbuf-CRITICAL **: file gdk-pixbuf-io.c: line 769 (gdk_pixbuf_new_from_file): assertion `filename != NULL' failed Steps to reproduce the crash: 1. Launch the application 2. 3. Expected Results: How often does this happen? every time I run it Additional Information: I didn't obtain the same error first of configure my desktop preferences This is a list of gnome-applications I'm running: esd gconfd gnome-keyring-daemon bonobo-activation-server gnome-settings-daemon xscreensaver gnome-smproxy metacity gnome-panel magicdev nautilus wnck-applet notification-area-applet clock-applet quick-lounge-applet gnome-vfs-daemon stickynotes_applet gtodo-applet hardware-monitor gnome-cpufreq-applet battstat-applet-2 mixer_applet2 gabber gnome-terminal When I insert a cd magicdev mounts it normally Debugging Information: Backtrace was generated from '/usr/bin/gnome-cd-properties' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1087553216 (LWP 14857)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x4071640e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 50031
Thread 1 (Thread 1087553216 (LWP 14857))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-10 05:51 ------- Unknown version 1.1.6 in product magicdev. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "magicdev". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** This bug has been marked as a duplicate of 146450 ***