gnome panel unresponsive after gimp

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.

Sebastien,

I can reproduce the unresponsive panels at will - however, when I
activate the trace, it will not hang!

I have found that if I keep the System Monitor active on the desktop,
when the panels become unresponsive, I can kill the gnome-panel
process and all is well... Also, I notice that CPU2 is running at 100%
when the panels are not responding (CPU1 is running at 1% or 2%).

Do you have any suggestions?

Thanks,
Carter

On 3/15/07, Sebastien Bacher <email address hidden> 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.
>
> ** Changed in: gnome-panel (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>
> --
> gnome panel unresponsive after gimp
> https://launchpad.net/bugs/92293
>

--
Carter Adams
www.LeagueOperator.org

Marking unconfirmed, without a way to trigger the bug or a backtrace not a lot we can work on and the desktop team is already way overloaded with bugs and can't track every corner case like that one at the moment

Could you try if that's happening on feisty?

Sebastien,

This problem "seems" to have been fixed about 2 or 3 weeks ago. I had
discovered a work-around. I could run the System Monitor and have it
visible on the desktop. When the panels quit working, I could look at
the monitor and see that CPU2 was running at 100%, with the process:
gnome-panel showing 49%. Then I could kill the gnome-panel process -
it would immediately restart and all would be fine for a few minutes,
and then I would have to repeat the procedure. The last time I had to
do this was about 2 or 3 week ago! I think there must have been some
software update that fixed this for me.

I had done this same work using GIMP (and Image Viewer and Document
Viewer) on an older machine and had no problems. I then upgraded to a
dual-core, dual-processor machine and, I think, this problem showed up
immediately. I figured it must have had something to do with the dual
processors.

The problem was never consistent. I could edit/view images sometimes
4, 5, 6 times or more without the hang (Image Viewer and Document
Viewer would also cause the hanging of the panel) - and, sometimes the
very first edit/view would cause the hang. It was very frustrating!

The System Monitor work-around kept me from having to re-boot, but is
was still a PITA. Then, a couple of weeks ago the hangs stopped
happening ...

If the hang shows up again, I will dig out an old system and install
feisty - but I believe that it will work, as all of my older machines
are single-core/single-processor machines. I am very hesitant to
upgrade my new machine to feisty!

Thank you,
Carter

On 4/19/07, Sebastien Bacher <email address hidden> wrote:
> Could you try if that's happening on feisty?
>
> ** Changed in: gnome-panel (Ubuntu)
> Importance: Medium => Low
> Status: Unconfirmed => Needs Info
>
> --
> gnome panel unresponsive after gimp
> https://bugs.launchpad.net/bugs/92293
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Carter Adams
www.LeagueOperator.org

Sebastien,

I updated to Feisty yesterday - so far, so good. I haven't vigorously
tested, but all seems fine. When I upgraded, I went to the 64-bit
version, whereas on Edgy I was using the 32-bit one. However, it has
been a month or so since I last had the panel "hang" problem - I think
some normal update must have fixed it for me.

Thank YOU!
~Carter

On 4/19/07, Carter Adams <email address hidden> wrote:
> Sebastien,
>
> This problem "seems" to have been fixed about 2 or 3 weeks ago. I had
> discovered a work-around. I could run the System Monitor and have it
> visible on the desktop. When the panels quit working, I could look at
> the monitor and see that CPU2 was running at 100%, with the process:
> gnome-panel showing 49%. Then I could kill the gnome-panel process -
> it would immediately restart and all would be fine for a few minutes,
> and then I would have to repeat the procedure. The last time I had to
> do this was about 2 or 3 week ago! I think there must have been some
> software update that fixed this for me.
>
> I had done this same work using GIMP (and Image Viewer and Document
> Viewer) on an older machine and had no problems. I then upgraded to a
> dual-core, dual-processor machine and, I think, this problem showed up
> immediately. I figured it must have had something to do with the dual
> processors.
>
> The problem was never consistent. I could edit/view images sometimes
> 4, 5, 6 times or more without the hang (Image Viewer and Document
> Viewer would also cause the hanging of the panel) - and, sometimes the
> very first edit/view would cause the hang. It was very frustrating!
>
> The System Monitor work-around kept me from having to re-boot, but is
> was still a PITA. Then, a couple of weeks ago the hangs stopped
> happening ...
>
> If the hang shows up again, I will dig out an old system and install
> feisty - but I believe that it will work, as all of my older machines
> are single-core/single-processor machines. I am very hesitant to
> upgrade my new machine to feisty!
>
> Thank you,
> Carter
>
> On 4/19/07, Sebastien Bacher <email address hidden> wrote:
> > Could you try if that's happening on feisty?
> >
> > ** Changed in: gnome-panel (Ubuntu)
> > Importance: Medium => Low
> > Status: Unconfirmed => Needs Info
> >
> > --
> > gnome panel unresponsive after gimp
> > https://bugs.launchpad.net/bugs/92293
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
> --
> Carter Adams
> www.LeagueOperator.org
>

--
Carter Adams
www.LeagueOperator.org

thank you for the update, marking it fixed then. Feel free to reopen if you get the bug again