Hello,

Thanks for packaging gnome-screenshot.

Most of the times I take a screenshot, I need to do some postprocessing
afterwards: so every time I save the file, then I open gimp and go to
look for the file that I saved.

It would be very useful to me if gnome-screenshot allowed to open the
image in an editor (such as gimp) instead of saving it.


Ciao,

Enrico

severity 465452 minor
severity 465453 minor
severity 465455 minor
severity 465460 minor
tags + 465452 upstream
tags + 465453 upstream
tags + 465455 upstream
tags + 465458 upstream
tags + 465460 upstream
tags + 465468 upstream
tags + 465478 upstream
thanks

Hi,
I'm not sure what you expect from this flood of bug reports.

These are all against the version of asterisk present in the stable
suite of Debian which means that no minor fixes are accepted -- only
security fixes and severe bugs, such as data corruption.

Moreover, these are all are upstream issues and I'm not sure what we can
do about them. Forwarding them to Digium is not an option for many
reasons: a) upstream needs a license disclaimer on all patches b) these
are against asterisk 1.2 which is frozen for only security fixes.

I'd suggest to:
- Verify which of these apply to asterisk 1.4 (present in
   unstable/testing).
- Report back which of them apply so we can close the rest.
- Open up a bug report against bugs.digium.com suggesting your fixes to
   upstream (be careful not to report any bristuff issues!)
- Then report back the URLs of the bugs on Digium's BTS.

I may be requiring too much from you but your bugs are *code* bugs and
you should approach upsteam with those.

I am keeping the bugs open for the moment even though I'm not too sure
about it.

Thanks,
Faidon

 EBUGID?

This would be nice, but you should note that gimp already has a
screenshooter, which is much better than gnome-screenshot anyway, so
this looks superfluous.

Cheers,

Hello Faidon,

sorry that I found so many bugs in your package ;-)
I had to fix them because I needed a stable version. Later I reported them and
shared my patches "in the hope that they would be useful".

Actucally I had thought that asterisk taking up all CPU time (#465460),
accessing freed memory (#465453), memory leaks (#465455) and a broken build
system (#465452, #465458) wouldn't be considered minor bugs that are not
worth fixing...

Hmmm... I had just read the bug reporting guidelines
http://www.debian.org/Bugs/Reporting where it says:
| Don't file bugs upstream
|
| If you file a bug in Debian, don't send a copy to the upstream software
| maintainers yourself, as it is possible that the bug exists only in Debian.
| If necessary, the maintainer of the package will forward the bug upstream.

In fact, I believe that some of the reported bugs only exist in your package
(which is based on 1.2.13) and have long been fixed in upstream 1.2.26.
Thus reporting them to you seemed reasonable to me.

I'm afraid you are, I wish I had more time though. If I were to test/debug
Digium's current version to see whether the bugs still exist there, I could
have used their version in the first place.
(In fact, what *is* the advantage of Debian asterisk_1.2.13~dfsg-2etch2 over
Digium asterisk-1.2.26 ?)
Anyway, at least some of them do apply to asterisk 1.4, too, e.g. #465460.

Why, they are just *bug* reports. The fact that I happened to find and share
some possible fixes shouldn't make a difference. The patches are meant as a
suggestion, just an example of how the bugs could be fixed. Just ignore the
patches if they bother you. ;-)

Not for me!

Best regards,
Philipp
bristuff: xagi-test
putenv (was fixed upstream somewhere between 1.2.13 and 1.2.26)
bristuff: memleak
local_queue_frame_livelock (applies to 1.4 too)
SOLINK
tune_ast_softhangup_nolock
Not mine (and not an asterisk bug)

Hello!

I am investigating gnome-utils bugs and found your report here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465478

You can drag the image from gnome-screenshot and drop it into GIMP,
which will open it for editing. Does that work for you, or you need
something else?

See you,

Thanks, I didn't know it.

That would solve half of the problem, in that if gimp isn't open one
also has to go through the steps of starting gimp AND creating an empty
image.  Note that if I have to start gimp manually, I can just as well
use its own acquire from screen function.

It would certainly make things easier than saving to a file and then
loading the file in gimp, which would mean going twice through those
insulting abominations that are gnome file dialogues.

I still wouldn't mind an "edit" button.  If someone decides that it
would clutter the interface too much, however, I might disagree, but
that would be fair enough with me.


Ciao,

Enrico

Hey Enrico,

I actually agree with you on this. I'll forward your bug to an upstream
bug report that is discussing a new UI for the screenshot app.

Thanks!