Public bug reported:
Binary package hint: metacity
Since I upgraded to gutsy the following occurs: everytime a metacity
dialog is started, it locks up gnome. I can't CTL-ALT-DELETE to restart
X, I can't do anything graphically. To get my system back, I have to
ssh in and kill the process. Below
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 hel
Video Card: "Savage 4" which is made by "S3 Inc."
Driver: "savage4_smbus"
Aaron-
Sebastien Bacher wrote:
> what videocard and driver do you use?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a mem
Yep.
Sebastien Bacher wrote:
> do you get the issue if you use the vesa driver?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-
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: In
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 indicati
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
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/DebuggingProgra
[EMAIL PROTECTED]:~$ ls -l /usr/share/icons/hicolor
total 3276
drwxr-xr-x 15 root root4096 2007-04-15 06:50 128x128
drwxr-xr-x 15 root root4096 2007-04-15 06:50 16x16
drwxr-xr-x 15 root root4096 2007-04-15 06:50 192x192
drwxr-xr-x 15 root root4096 2007-04-15 06:50 22x22
drwxr-xr-x 1
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-dia
Public bug reported:
Binary package hint: metacity
Since I upgraded to gutsy the following occurs: everytime a metacity
dialog is started, it locks up gnome. I can't CTL-ALT-DELETE to restart
X, I can't do anything graphically. To get my system back, I have to
ssh in and kill the process. Below
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 hel
Video Card: "Savage 4" which is made by "S3 Inc."
Driver: "savage4_smbus"
Aaron-
Sebastien Bacher wrote:
> what videocard and driver do you use?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a mem
Yep.
Sebastien Bacher wrote:
> do you get the issue if you use the vesa driver?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-
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: In
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 indicati
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
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/DebuggingProgra
[EMAIL PROTECTED]:~$ ls -l /usr/share/icons/hicolor
total 3276
drwxr-xr-x 15 root root4096 2007-04-15 06:50 128x128
drwxr-xr-x 15 root root4096 2007-04-15 06:50 16x16
drwxr-xr-x 15 root root4096 2007-04-15 06:50 192x192
drwxr-xr-x 15 root root4096 2007-04-15 06:50 22x22
drwxr-xr-x 1
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-dia
Public bug reported:
Binary package hint: metacity
Since I upgraded to gutsy the following occurs: everytime a metacity
dialog is started, it locks up gnome. I can't CTL-ALT-DELETE to restart
X, I can't do anything graphically. To get my system back, I have to
ssh in and kill the process. Below
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 hel
Video Card: "Savage 4" which is made by "S3 Inc."
Driver: "savage4_smbus"
Aaron-
Sebastien Bacher wrote:
> what videocard and driver do you use?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a mem
Yep.
Sebastien Bacher wrote:
> do you get the issue if you use the vesa driver?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-
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: In
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 indicati
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
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/DebuggingProgra
[EMAIL PROTECTED]:~$ ls -l /usr/share/icons/hicolor
total 3276
drwxr-xr-x 15 root root4096 2007-04-15 06:50 128x128
drwxr-xr-x 15 root root4096 2007-04-15 06:50 16x16
drwxr-xr-x 15 root root4096 2007-04-15 06:50 192x192
drwxr-xr-x 15 root root4096 2007-04-15 06:50 22x22
drwxr-xr-x 1
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-dia
Public bug reported:
Binary package hint: metacity
Since I upgraded to gutsy the following occurs: everytime a metacity
dialog is started, it locks up gnome. I can't CTL-ALT-DELETE to restart
X, I can't do anything graphically. To get my system back, I have to
ssh in and kill the process. Below
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 hel
Video Card: "Savage 4" which is made by "S3 Inc."
Driver: "savage4_smbus"
Aaron-
Sebastien Bacher wrote:
> what videocard and driver do you use?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a mem
Yep.
Sebastien Bacher wrote:
> do you get the issue if you use the vesa driver?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-
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: In
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 indicati
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
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/DebuggingProgra
[EMAIL PROTECTED]:~$ ls -l /usr/share/icons/hicolor
total 3276
drwxr-xr-x 15 root root4096 2007-04-15 06:50 128x128
drwxr-xr-x 15 root root4096 2007-04-15 06:50 16x16
drwxr-xr-x 15 root root4096 2007-04-15 06:50 192x192
drwxr-xr-x 15 root root4096 2007-04-15 06:50 22x22
drwxr-xr-x 1
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-dia
Public bug reported:
Binary package hint: metacity
Since I upgraded to gutsy the following occurs: everytime a metacity
dialog is started, it locks up gnome. I can't CTL-ALT-DELETE to restart
X, I can't do anything graphically. To get my system back, I have to
ssh in and kill the process. Below
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 hel
Video Card: "Savage 4" which is made by "S3 Inc."
Driver: "savage4_smbus"
Aaron-
Sebastien Bacher wrote:
> what videocard and driver do you use?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a mem
Yep.
Sebastien Bacher wrote:
> do you get the issue if you use the vesa driver?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-
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: In
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 indicati
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
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/DebuggingProgra
[EMAIL PROTECTED]:~$ ls -l /usr/share/icons/hicolor
total 3276
drwxr-xr-x 15 root root4096 2007-04-15 06:50 128x128
drwxr-xr-x 15 root root4096 2007-04-15 06:50 16x16
drwxr-xr-x 15 root root4096 2007-04-15 06:50 192x192
drwxr-xr-x 15 root root4096 2007-04-15 06:50 22x22
drwxr-xr-x 1
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-dia
Public bug reported:
Binary package hint: metacity
Since I upgraded to gutsy the following occurs: everytime a metacity
dialog is started, it locks up gnome. I can't CTL-ALT-DELETE to restart
X, I can't do anything graphically. To get my system back, I have to
ssh in and kill the process. Below
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 hel
Video Card: "Savage 4" which is made by "S3 Inc."
Driver: "savage4_smbus"
Aaron-
Sebastien Bacher wrote:
> what videocard and driver do you use?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a mem
Yep.
Sebastien Bacher wrote:
> do you get the issue if you use the vesa driver?
>
>
--
Metacity Dialogs appear and lock up the system.
https://bugs.launchpad.net/bugs/134745
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-
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: In
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 indicati
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
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/DebuggingProgra
[EMAIL PROTECTED]:~$ ls -l /usr/share/icons/hicolor
total 3276
drwxr-xr-x 15 root root4096 2007-04-15 06:50 128x128
drwxr-xr-x 15 root root4096 2007-04-15 06:50 16x16
drwxr-xr-x 15 root root4096 2007-04-15 06:50 192x192
drwxr-xr-x 15 root root4096 2007-04-15 06:50 22x22
drwxr-xr-x 1
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-dia
Yep, the fix from #16 worked for me. I wasn't expecting that change to
apply to MPlayer and VLC, but it did. I'm ready to rock! And by rock, I
mean watch "Slayer - War at Warfield"...
--
Video is tinted blue after update to karmic
https://bugs.launchpad.net/bugs/409640
You received this bug notif
61 matches
Mail list logo
