GNOME Bugzilla – Bug 503100
crash in Volume Control: добавил переключатель ре...
Last modified: 2007-12-17 22:10:37 UTC
Version: 2.18.0 What were you doing when the application crashed? добавил переключатель режима каналов Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 42483712 vsize: 42483712 resident: 13869056 share: 10383360 rss: 13869056 rss_rlim: 4294967295 CPU usage: start_time: 1197400815 rtime: 350 utime: 329 stime: 21 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208334096 (LWP 4772)] (no debugging symbols found) 0x00d51402 in __kernel_vsyscall ()
+ Trace 181572
Thread 1 (Thread -1208334096 (LWP 4772))
----------- .xsession-errors --------------------- (gtk-window-decorator:4190): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed DCOP aborting call from 'anonymous-4684' to 'knotify' KCrash: Application 'knotify' crashing... ScimInputContextPlugin() ~ScimInputContextPlugin() ScimInputContextPlugin() X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 Minor opcode: 0 Resource id: 0x3e00037 ~ScimInputContextPlugin() QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * ) (gnome-volume-control:4772): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 471133 ***