GNOME Bugzilla – Bug 446227
crash in Window Selector: Right clicked on thunder...
Last modified: 2008-01-08 21:43:15 UTC
Version: 2.18.2 What were you doing when the application crashed? Right clicked on thunderbird bar in window bar in the bottom panel Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 282923008 vsize: 282923008 resident: 23240704 share: 17539072 rss: 23240704 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181537853 rtime: 384 utime: 331 stime: 53 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912679030400 (LWP 3521)] (no debugging symbols found) 0x00002aaaafc9e865 in waitpid () from /lib64/libpthread.so.0
+ Trace 139942
Thread 1 (Thread 46912679030400 (LWP 3521))
----------- .xsession-errors (1159 sec old) --------------------- localuser:edsall being added to access control list SESSION_MANAGER=local/smog:/tmp/.ICE-unix/3361 libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files error getting update info: Cannot open/read repomd.xml file for repository: fedora (gnome-panel:3479): Gtk-CRITICAL **: gtk_icon_theme_lookup_icon: assertion `GTK_IS_ICON_THEME (icon_theme)' failed connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
Just swithced to compiz, hadn't logged out and back in again. After doing that no further problems
This sounds like a bug in a fedora patch: http://cvs.fedora.redhat.com/viewcvs/devel/libwnck/libwnck-2.18.0-viewport.patch?root=core&rev=1.1&view=auto I'll modify libwnck to be more tolerant to some calls with bad arguments.
*** Bug 450196 has been marked as a duplicate of this bug. ***
*** Bug 457898 has been marked as a duplicate of this bug. ***
*** Bug 460737 has been marked as a duplicate of this bug. ***
*** Bug 473794 has been marked as a duplicate of this bug. ***
*** Bug 484392 has been marked as a duplicate of this bug. ***
*** Bug 487009 has been marked as a duplicate of this bug. ***
*** Bug 487609 has been marked as a duplicate of this bug. ***
*** Bug 487833 has been marked as a duplicate of this bug. ***
*** Bug 487835 has been marked as a duplicate of this bug. ***
*** Bug 487836 has been marked as a duplicate of this bug. ***
*** Bug 487838 has been marked as a duplicate of this bug. ***
*** Bug 493032 has been marked as a duplicate of this bug. ***
*** Bug 496022 has been marked as a duplicate of this bug. ***
*** Bug 498202 has been marked as a duplicate of this bug. ***
*** Bug 498201 has been marked as a duplicate of this bug. ***
Reporter, there is now bug https://bugzilla.redhat.com/show_bug.cgi?id=245022 open for you on the Red Hat bugzilla. Could I ask you to attach THERE your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below, please? Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. Don't forget to add yourself to the CC list of that bug. Thank you very much.
You don't need to do that, it has nothing to do with the X configuration, only with the compiz configuration, which might, or might not use viewports.
*** Bug 499843 has been marked as a duplicate of this bug. ***
*** Bug 506978 has been marked as a duplicate of this bug. ***