Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
task_small.png
CLOSED  Task #161  -  Crash Reporter: Crop the screenshot to the window size under linux or remove it.
Posted Feb 20, 2012 - updated Mar 06, 2012   Shortlink: http://arx.vg/161
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Not a bug" and resolution "WON'T FIX".
Issue details
  • Type of issue
    Task
  • Status
     
    		 Not a bug
  • Assigned to
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    Daniel Scharrer
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Time spent
    369369 hours
  • Category
    Not determined
  • Resolution
    WON'T FIX
  • Priority
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
Nothing entered.

#4
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Mar 05, 15:51
Another option would be to not include it by default under linux (how useful is the screenshot anyway for a crash report?) but keep it in the files list so a user can include it if they want. The main concern is that the crash reporter should not send any personal information unless explicitly included by the user.
#5
icon_reply.pngReply
Comment posted by
SebastienLussier
Mar 06, 00:58
Well, in fact the screenshot code is currently broken in fullscreen on Windows... looks like I would need to disable compositing for it to work... I guess this is not a priority, we should probably remove that feature for now.

I'll do this right now smileys/2.png
#6
icon_reply.pngReply
Comment posted by
SebastienLussier
Mar 06, 01:10
Done, i'll close this issue.
#7
icon_reply.pngReply
Comment posted by
SebastienLussier
Mar 06, 01:10
Removed feature

The issue was updated with the following change(s):
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to WON'T FIX.
  • This issue's progression has been updated to 100 percent completed.