Bug 16661 - Xsane crashed with bug report (attached)
Summary: Xsane crashed with bug report (attached)
Status: RESOLVED NOTOURBUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Security (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: X.Org Security
QA Contact: X.Org Security
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-10 02:36 UTC by Richard Prangnell
Modified: 2008-07-15 09:26 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
automatically generated report including stack trace (550.12 KB, text/plain)
2008-07-10 02:36 UTC, Richard Prangnell
no flags Details

Description Richard Prangnell 2008-07-10 02:36:30 UTC
Created attachment 17615 [details]
automatically generated report including stack trace

Bug report automatically generated first time Xsane ran. No further occurrences since and seems now to be working ok.
Comment 1 Adam Jackson 2008-07-11 07:53:50 UTC
This appears to be a crash in Xsane, not in the X server.  It's not clear why you filed this here at all, let alone as a security bug...
Comment 2 Richard Prangnell 2008-07-15 03:09:58 UTC
Hi

Sorry if the bug report went to the wrong place. I am unfamiliar with
the bug reporting page and must have missed out making a selection from
a pick list somewhere. It's a pity the bug report generator doesn't
provide the correct email address...

I suppose I'll just have to ignore the bug reports in future as I found
the reporting page just too complicated.

Thanks anyway.

On Fri, 2008-07-11 at 07:54 -0700, bugzilla-daemon@freedesktop.org
wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=16661
> 
> 
> 
> 
> 
> --- Comment #1 from ajax at nwnk dot net <ajax@nwnk.net>  2008-07-11 07:53:50 PST ---
> This appears to be a crash in Xsane, not in the X server.  It's not clear why
> you filed this here at all, let alone as a security bug...
> 
> 
Comment 3 Adam Jackson 2008-07-15 08:57:34 UTC
(In reply to comment #2)
> Hi
> 
> Sorry if the bug report went to the wrong place. I am unfamiliar with
> the bug reporting page and must have missed out making a selection from
> a pick list somewhere. It's a pity the bug report generator doesn't
> provide the correct email address...
> 
> I suppose I'll just have to ignore the bug reports in future as I found
> the reporting page just too complicated.

Bugs in Xsane should be filed with the Xsane project.  It's a fine project and all, this just isn't their bug system.

http://www.xsane.org/xsane-contact.html
Comment 4 Richard Prangnell 2008-07-15 09:26:18 UTC
Thanks for the clarification. I'm sure you are right about Xsane being a
fine project. its a bit frustrating though, when you just try to help by
submitting a bug report but can't find anywhere for it to go.
Never, mind; I'll know next time. Sorry you were troubled.

Best wishes

RP

On Tue, 2008-07-15 at 08:57 -0700, bugzilla-daemon@freedesktop.org
wrote:
> http://bugs.freedesktop.org/show_bug.cgi?id=16661
> 
> 
> ajax at nwnk dot net <ajax@nwnk.net> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>          Resolution|                            |NOTOURBUG
> 
> 
> 
> 
> --- Comment #3 from ajax at nwnk dot net <ajax@nwnk.net>  2008-07-15 08:57:34 PST ---
> (In reply to comment #2)
> > Hi
> > 
> > Sorry if the bug report went to the wrong place. I am unfamiliar with
> > the bug reporting page and must have missed out making a selection from
> > a pick list somewhere. It's a pity the bug report generator doesn't
> > provide the correct email address...
> > 
> > I suppose I'll just have to ignore the bug reports in future as I found
> > the reporting page just too complicated.
> 
> Bugs in Xsane should be filed with the Xsane project.  It's a fine project and
> all, this just isn't their bug system.
> 
> http://www.xsane.org/xsane-contact.html
> 
> 


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.