Metacity Dialogs appear and lock up the system.

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. Also, may you test it with a freshly new user?

As it is a dialog from metacity, it only opens a dialog when it needs
feedback about something. I've tried running
"/usr/lib/metacity/metacity-dialog [OPTIONS]" and there are no options
that I can give it to make it run, it just says I give it bad
arguments. So have a debugger can't really help.

Aaron-

Pedro Villavicencio wrote:
> Thanks for your bug report. Please try to obtain a backtrace
> http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
> bug report. This will greatly help us in tracking down your problem.
> Also, may you test it with a freshly new user?
>
> ** Changed in: metacity (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: New => Incomplete
>
>

what videocard and driver do you use?

Video Card: "Savage 4" which is made by "S3 Inc."
Driver: "savage4_smbus"

Aaron-

Sebastien Bacher wrote:
> what videocard and driver do you use?
>
>

do you get the issue if you use the vesa driver?

Yep.

Sebastien Bacher wrote:
> do you get the issue if you use the vesa driver?
>
>

unconfirming, looks like you are the only one getting the bug which is weird. Does it happen with an another user on the same box?

do you have easy steps to trigger the bug?

yeah, I made a new user and it still happens when I'm logged in as that
new user.

Sebastien Bacher wrote:
> unconfirming, looks like you are the only one getting the bug which is
> weird. Does it happen with an another user on the same box?
>
> ** Changed in: metacity (Ubuntu)
> Status: Incomplete => New
>
>

No, I've been trying to track down when metacity-dialog gets called, but
I guess I don't really understand metacity dialogs. I understand when
thunderbird or firefox would open a dialog box, but I don't really
understand why metacity would open a dialog. Some of the arguments give
an indication of why the metacity dialog gets called
"--kill-window-question [SOME PROGRAM]" With that said, I'm not sure why
that would be called. Is it because the underlying program not
responding? Sometimes it has to do with gthumb, sometimes firefox,
sometimes nautilus, etc. So I guess that's a long answer to a short
question, no I don't have any steps that could trigger the bug, I've
been trying to find a pattern, but as of yet, I haven't found one.

Sebastien Bacher wrote:
> do you have easy steps to trigger the bug?
>
>

After I wrote my last email about not being able to have easy steps to
trigger the bug, it left me thinking. I thought more about what I had
rambled about previously and why a metacity dialog would be triggered.
My guess had been that it was caused by a "Not Responding" dialog. Well
it turns out, that's exactly what is going on.

<TRIGGER>
If you open up the terminal and start any program (ex:
gnome-calculator), suspend it (Ctl+Z) and then try to close the window
as you would normally (via the metacity widget).
</TRIGGER>

It should bring up a dialog that says "This application isn't
responding, do you want to kill the application." Turns out, my system
never gets that far. I've never seen that dialog since I upgraded to
Gutsy. Instead of showing the dialog, it just hangs until I ssh in and
kill the process (ex: /usr/lib/metacity/metacity-dialog --screen 0
--timestamp 3288704419 --kill-window-question Calculator 0x2c00003).

Aaron-

Sebastien Bacher wrote:
> do you have easy steps to trigger the bug?
>
>

Could you try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report.

I've attached the backtrace in gdb-metacity.txt and my
.xsession-errors. Looking at the xsession-errors it gives gtk-warning
about not finding an icon file. This have something to do with it?

Sebastien Bacher wrote:
> Could you try to obtain a backtrace
> http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
> bug report.
>
>

GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
(gdb) handle siSIG33 pass notsstop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) attach 9095
Attaching to process 9095
Reading symbols from /usr/lib/metacity/metacity-dialog...(no debugging symbols found)...done.
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0
Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0
Reading symbols from /usr/lib/libgobject-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgobject-2.0.so.0
Reading symbols from /usr/lib/libglib-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libglib-2.0.so.0
Reading symbols from /usr/lib/libX11.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libX11.so.6
Reading symbols from /lib/tls/i686/cmov/libpthread.so.0...(no debugging symbols found)...done.
[Thread debugging using libthread_db enabled]
[New Thread -1219409648 (LWP 9095)]
Loaded symbols for /lib/tls/i686/cmov/libpthread.so.0
Reading symbols from /lib/tls/i686/cmov/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/tls/i686/cmov/libc.so.6
Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0
Reading symbols from /usr/lib/libpangocairo-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpangocairo-1.0.so.0
Reading symbols from /usr/lib/libpango-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpango-1.0.so.0
Reading symbols from /usr/lib/libXcomposite.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXcomposite.so.1
Reading symbols from /usr/lib/libXdamage.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXdamage.so.1
Reading symbols from /usr/lib/libXfixes.so.3...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXfixes.so.3
Reading symbols from /usr/lib/libatk-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libatk-1.0.so.0
Reading symbols from /usr/lib/libgmodule-2.0.so.0...(no debugging symbols found)...done.
Loaded s...

Could you run "ls -l /usr/share/icons/hicolor" and copy that to a comment?

gerberad@IBM:~$ ls -l /usr/share/icons/hicolor
total 3276
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 128x128
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 16x16
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 192x192
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 22x22
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 24x24
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 32x32
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 36x36
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 48x48
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 64x64
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 72x72
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 96x96
-rw-r--r-- 1 root root 4377 2007-04-30 22:12 autopackage-installer.png
-rw-r--r-- 1 root root 3266740 2007-05-24 07:57 icon-theme.cache
-rw-r--r-- 1 root root 22251 2006-12-06 17:54 index.theme
drwxr-xr-x 15 root root 4096 2007-04-15 06:50 scalable

Sebastien Bacher wrote:
> Could you run "ls -l /usr/share/icons/hicolor" and copy that to a
> comment?
>
>

Does running those commands make it work correctly?

sudo rm /usr/share/icons/hicolor/autopackage-installer.png
sudo touch /usr/share/icons/hicolor
sudo gtk-update-icon-cache /usr/share/icons/hicolor

The issue might be due to some autopackage you used, you should not install software not coming from Ubuntu

The following fixed some of the errors in .xsession-errors:
========================================
sudo rm /usr/share/icons/hicolor/autopackage-installer.png
sudo touch /usr/share/icons/hicolor
sudo gtk-update-icon-cache /usr/share/icons/hicolor

But below is what actually fixed the metacity-dialog issue:
========================================
sudo rm /usr/share/pixmaps/hicolor/autopackage-installer.png
sudo touch /usr/share/pixmaps/hicolor
sudo gtk-update-icon-cache /usr/share/pixmaps/hicolor

+++++++++++++++++++++++++++++++++++++++++
Thanks for the help! You were always quick and helpful in your replies.
I'm stoked to have it fixed. In response to "You should not install
software not comping from Ubuntu" - Point taken.

Sebastien Bacher wrote:
> Does running those commands make it work correctly?
>
> sudo rm /usr/share/icons/hicolor/autopackage-installer.png
> sudo touch /usr/share/icons/hicolor
> sudo gtk-update-icon-cache /usr/share/icons/hicolor
>
> The issue might be due to some autopackage you used, you should not
> install software not coming from Ubuntu
>
>

closing then, that's a broken user installation and solved now, and not a bug