gnome-panel-screenshot crashes when saving PNG

Thanks for your bug report. Which version of Ubuntu and gnome-utils do you use? What happens if you run gnome-screenshot from the terminal - can you get a backtrace from it? (http://wiki.ubuntu.com/Backtrace).

I experience the same crashes (the backtrace I get is exactly the same as posted above), but cannot reproduce them in order to help more about the issue. Nevertheless, I post here a confirmation of this bug.

Using an up-to-date Ubuntu 6.06 LTS system, gnome-utils 2.14.0-0ubuntu5.

On 9/13/06, istoyanov <email address hidden> wrote:
> Using an up-to-date Ubuntu 6.06 LTS system, gnome-utils 2.14.0-0ubuntu5.

I'm using Edgy with gnome-utils 2.16.0-0ubuntu1.

I can't seem to reproduce the bug every time; running it within gdb works just fine. I'll post back if I can get it to crash again.

I don't do screenshots very often, but according to my vague remembrance the utility tends to crash when a previous screenshot *.png file is already present on the desktop.

When I have more observations, I'll share them here accordingly.

On 9/13/06, istoyanov <email address hidden> wrote:
> I don't do screenshots very often, but according to my vague remembrance
> the utility tends to crash when a previous screenshot *.png file is
> already present on the desktop.

Nope; I actually ended up with 10 or so screenshots on my Desktop trying to get it to crash. :P Screenshot.png is the first, then Screenshot-1.png, etc.

That's why I said "according to my vague remembrance":) Today I tried to induce the crash again by starting gnome-screenshot >10 times from the CLI, but to no avail...

I can confirm. Attached bug report, which doesn't say a lot.

Encountered bug, can't reproduce.

ENV: Edgy BETA / 2.16.0-0ubuntu

First use of screenshot since upgrade to Edgy. Used Prt Scr to trigger it, and I had changed the name the file name.

Similar uninteresting backtrace.

Happens to me, too, and this is generated:

Memory status: size: 1667072 vsize: 0 resident: 1667072 share: 0 rss: 548864 rss_rlim: 0
CPU usage: start_time: 1161131168 rtime: 0 utime: 95 stime: 0 cutime:0 cstime: 0 timeout: 95 it_real_value: 0 frequency: 6124

Backtrace was generated from '/usr/bin/gnome-panel-screenshot'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

Unfortunately I'm not able to reproduce the crash. It's weird the backtraces are all not saying anything.

the bug is not useful without a debug backtrace, closing. Feel free to reopen if there is a backtrace available for it