Bug triage/2008-03-26

From Second Life Wiki
Jump to navigation Jump to search

Next meeting: 2008-03-26 at 3pm PST at Bridie Linden's house.


(Bugs reported in 1.19.1 RC2 — consider for import?, sorted by votes)

  • VWR-5785 - Votes: 4 - Large sculpts don't load correctly until selected. - Aminom Marvin
    • Imported - Assigned to Qarl Linden
  • VWR-5520 - Votes: 2 - Strange and sudden video corruption in viewer RC - Spank Lovell
    • Waiting for info from Spank
  • VWR-5653 - Votes: 2 - Copy and paste don't work - Haravikk Mistral
    • Resolved
  • VWR-5601 - Votes: 2 - curl_multi_perform () freezes viewer - Michelle2 Zenovka
    • Resolved
  • VWR-5463 - Votes: 2 - Windlight causes graphics card degredation and eventually disables graphics card. - Goldie Katsu
    • Suggestions posted to poster
  • VWR-5812 - Votes: 2 - RC: A media size matching a bit position (64,128,256,512) will be placed on the wrong size texture when played by the viewer - anthony reisman
    • Imported - Assigned to Samuel Linden
  • VWR-5778 - Votes: 2 - Raffle item giver, items given when camping timeout after unknown time, even when clicking accept item never arrives. - Xavier Lemieux
    • Imported - Assigned to Aric Linden
  • VWR-5555 - Votes: 1 - Windlight largely incompatible with system - Arawn Spitteler
    • Won't Fix
  • VWR-5711 - Votes: 1 - Star and moon/sun water reflection renderings greatly distorted when viewed from high altitudes (and other sky render glitches) - Brandon Shinobu
    • Imported - Assigned to Pastrami & Zen Linden
  • VWR-5623 - Votes: 1 - Application Not Responding on Quit, Forced to Quit - Simil Miles
    • Needs More Info
  • VWR-5621 - Votes: 1 - Very poor keystroke response time in IM or Chat sessions. Also poor avatar resonsiveness to the movement keys (arrows). - aaron23 decuir
    • Imported - Assigned to Kona Linden
  • VWR-5367 - Votes: 1 - New video features (V19.1) are not fully supported in LSL - Garmin Kawaguichi
    • Not a bug - Requested screen shots
  • VWR-5718 - Votes: 1 - Kicked off voice after exactly 30 seconds when using Linux - equibrad voom
    • Imported - Assigned to Tofu Linden
  • VWR-5673 - Votes: 1 - llTargetOmega() (rotating objects) wont stop when child prim - Drako Nagorski
    • Andrew Linden asked for update
  • VWR-5616 - Votes: 1 - 1.19.1 crash (Linux) double free or corruption - Vex Streeter
    • Imported - Assigned to Tofu Linden
  • VWR-5769 - Votes: 1 - Mousewheel works inconsistent/not always - Jam Meili
  • VWR-5808 - Votes: 1 - Viewer always creates "url_history.xml" file in "C:\" directory. - Angus Boyd
    • Imported - Assigned to Aric Linden
  • VWR-5816 - Votes: 1 - llMessageLinked() appears to travel a maximum of 19.3 meters, not reaching linked objects beyond that point. - Kenn Nilsson
    • Can't Reproduce
  • VWR-5821 - Votes: 1 - Bandwidth and packet loss meters tool tip missing - Drew Dwi
    • Not a bug

Fast Track Import

(Move bugs here that have solid repros, or valid patches that you have reviewed)

Hot by Vote

High Voted Bugs



Misc Pool

Misc Pool

Pre-meeting activity

Some issues will be resolved in the course of building this agenda. Rather than deleting them from the proposed agenda, move the issue and associated discussion into the appropriate section below.




Transcript is/will be at Bug triage/2008-03-26/Transcript

Creating An Agenda

Community members generally collaborate on the agenda for bug triage meetings. Here's how you can quickly fill in an otherwise blank agenda:

Setting up

  • Go to Bug_Triage/YYYY-MM-DD where YYYY is the four digit year code, MM is the two digit month code, and DD is the day code
  • Write and save {{subst:Triage Template}} as the only content of your new page. This will copy the complete markup from Template:Triage Template as a starting point for your agenda.
  • Fill in the relevant time, date, and location info for the upcoming meeting. The easiest way to do this is to copy the entire block of information from an earlier meeting of the same type (RC, regular, etc...) and modify the date and time as needed.

Populating the issue listings section(s)


  1. !/usr/bin/env perl

use XML::Simple;

my $bugs = XMLin($ARGV[0]);

foreach my $item (@{$bugs->{channel}->{item}}) {

 $title = $item->{title};
 $title =~ s/^\^\*\] //;
 $key = $item->{key}->{content};
 $votes = $item->{votes};
 $reporter = $item->{reporter}->{username};
 print "* $key - Votes: $votes - $title - $reporter\n";



  • Pick a reasonable cutoff point, and copy the output into the appropriate section of your newly created page.