continuous create of title bars in window list - after reboot after installing vmware user agent

Bug #655703 reported by dave_365
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gnome-panel

after installing vmware user agent and rebooting, it looks like new title bars are being created continuously in the window list. wnck-applet taking most of cpu. window title bars dont appear by <alt-tab>

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-panel 1:2.30.2-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
Date: Wed Oct 6 07:40:08 2010
ExecutablePath: /usr/lib/gnome-panel/wnck-applet
GConfNonDefault:
 /apps/panel/general/applet_id_list=[fast_user_switch_screen0,trashapplet_screen0,workspace_switcher_screen0,window_list_screen0,show_desktop_button_screen0,indicator_applet_screen0,notification_area_screen0,clock_screen0]
 /apps/panel/general/object_id_list=[browser_launcher_screen0,menu_bar_screen0]
 /apps/panel/general/toplevel_id_list=[bottom_panel_screen0,top_panel_screen0]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1292): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (bluetooth-applet:1296): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed

Revision history for this message
dave_365 (dave-365) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in gnome-panel (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gnome-panel (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.