~ubuntu-branches/ubuntu/precise/kubuntu-docs/precise-updates

>Also known as a wish list item, this type of report is filed to add a function to an application, or to change something in the application that isn't due to a regression or a crash. </para>

</listitem>

</varlistentry>

</variablelist>

</sect1>

<title

>Bug Trackers Used By &kubuntu;</title>

<title

>KDE's Bug Tracking System</title>

<para

><ulink url="https://bugs.kde.org/"

></ulink

></para>

<para

>KDE uses Bugzilla, a "Defect Tracking System". Bugzilla is one of the most popular tools used in the open source development community. </para>

<note

><title

>Register first</title>

<para

>To report a bug, one must register for an account on KDE's Bugzilla at <ulink url="https://bugs.kde.org/createaccount.cgi"

></ulink

>. A valid email address is required for registration. </para>

</note>

<note

><title

>Samo za KDE greške</title>

<para

>Bugzilla is only for KDE bugs. If the application is not part of KDE, for instance Firefox, LibreOffice, or VLC, then the report should be filed in Launchpad instead. Please see the next section, which covers filing reports concerning Launchpad. </para>

</note>

</sect2>

<title

>Launchpad</title>

<para

><ulink url="https://launchpad.net/"

></ulink

></para>

<para

>Launchpad is an open source suite of tools that help people and teams to work together on software projects. Launchpad is used by the Ubuntu and &kubuntu; Projects, as well as various other open source projects. </para>

<note

><title

100

>Register first</title>

101

<para

102

>To report a bug, one must register for a Launchpad account at <ulink url="https://launchpad.net/+login"

103

></ulink

104

>. A valid email address is required for registration. </para>

105

</note>

106

<note

107

><title

108

>For any bug in &kubuntu;</title>

109

<para

110

>Launchpad can be used to file a bug report for any application available in the Ubuntu or &kubuntu; repositories. For KDE applications, the KDE Bug Tracking system (above) is preferred. </para>

111

</note>

112

</sect2>

113

</sect1>

114

115

116

<title

117

>Filing a Crash Report</title>

118

<para

119

>When an application crashes in &kubuntu;, the appropriate crash dialog will appear. It is usually easy to file a bug report from the dialog. With a KDE application, the KDE crash dialog will appear along with instructions for reporting the bug. Otherwise, the Ubuntu crash dialog will appear with instructions for filing a bug on Launchpad. </para>

120

121

<title

122

>KDE</title>

123

<para

124

>When an application crashes in KDE, a crash dialog will be presented that is similar to the following images. The first image shows the <guilabel

125

>General</guilabel

126

> tab which provides an overview of the crash. The second image shows the <guilabel

127

>Developer Information</guilabel

128

> tab which provides trace information that is useful to developers. </para>

129

<para>

130

131

<title

132

>KDE Crash Dialog (General tab)</title>

133

134

135

136

</imageobject>

137

</mediaobject>

138

</example>

139

</para>

140

<para>

141

142

<title

143

>KDE Crash Dialog (Developer Information tab)</title>

144

145

146

147

</imageobject>

148

</mediaobject>

149

</example>

150

</para>

151

<para

152

>If the trace information is deemed valuable, filing a bug report is easy with the crash dialog wizard. If the trace is not deemed valuable, then it is not possible to file a bug report with the wizard. The bug report can still be filed manually at <ulink url="https://bugs.kde.org/"

153

></ulink

154

>. </para>

155

<para

156

>To complete the bug reporting process, follow the procedure below. </para>

157

<procedure

158

><title

159

>Filing the bug report after a crash</title>

160

<step>

161

<para

162

><mousebutton

163

>Click</mousebutton

164

> the <guibutton

165

>Report Bug</guibutton

166

> button. The following dialog will appear. </para>

167

<para>

168

169

<title

170

>Dobro došli u pomoćnik za prijavljivanje</title>

171

172

173

174

</imageobject>

175

</mediaobject>

176

</example>

177

</para>

178

</step>

179

<step>

180

<para

181

><mousebutton

182

>Click</mousebutton

183

> the <guibutton

184

>Next</guibutton

185

> button. The following dialog will appear. </para>

186

<para>

187

188

<title

189

>Šta znate o padu?</title>

190

191

192

193

</imageobject>

194

</mediaobject>

195

</example>

196

</para>

197

</step>

198

<step>

199

<para

200

>Select the applicable options. The drop-down box under the question, "<guilabel

201

>Does the application crash again if you repeat the same situation?</guilabel

202

>" has several options. </para>

203

<para>

204

205

<title

206

>Does the application crash again if you repeat the same situation?</title>

207

208

209

210

</imageobject>

211

</mediaobject>

212

</example>

213

</para>

214

</step>

215

<step>

216

<para

217

>After selecting the applicable items from the dialog in the previous step, <mousebutton

218

>click</mousebutton

219

> the <guibutton

220

>Next</guibutton

221

> button. </para>

222

</step>

223

<step>

224

<para

225

>Depending on the information available in the crash report, either of two dialogs will appear. One is a dialog that indicates that there is not enough information to file a good report. The other is a dialog indicating that the information is useful, and that it would be helpful to continue with filing the report. </para>

226

<para>

227

228

<title

229

>Not enough information for developers to continue the reporting process</title>

230

231

232

233

</imageobject>

234

</mediaobject>

235

</example>

236

</para>

237

<para>

238

239

<title

240

>This crash information is useful</title>

241

242

243

244

</imageobject>

245

</mediaobject>

246

</example>

247

</para>

248

<note

249

><title

250

>If there was not enough information...</title>

251

<para

252

>It may be necessary to install the proper debug packages in order to get a good trace. Such packages include <filename

253

>kdebase-dbg</filename

254

>, <filename

255

>kdebase-workspace-dbg</filename

256

>, <filename

257

>kdebase-runtime-dbg</filename

258

>. </para>

259

</note>

260

</step>

261

<step>

262

<para

263

>If enough information was provided to continue filing a bug report using the assistant, a dialog will appear to allow logging in to KDE's Bugzilla. </para>

264

<para>

265

266

<title

267

>KDE Bug Tracking System Login</title>

268

269

270

271

</imageobject>

272

</mediaobject>

273

</example>

274

</para>

275

<note

276

><title

277

>Use e-mail address as username</title>

278

<para

279

>Use the e-mail address that was used to register with KDE's Bugzilla. </para>

280

</note>

281

</step>

282

<step>

283

<para

284

>After logging in with username (e-mail address) and password, <mousebutton

285

>click</mousebutton

286

> the <guibutton

287

>Login</guibutton

288

> button. The assistant will check for duplicates and display the following dialog. </para>

289

<para>

290

291

<title

292

>Bug Report Possible Duplicates List</title>

293

294

295

296

</imageobject>

297

</mediaobject>

298

</example>

299

</para>

300

</step>

301

<step>

302

<para

303

>If there is a possible duplicate report, <mousebutton

304

>click</mousebutton

305

> the report in the list and then <mousebutton

306

>click</mousebutton

307

> the <guibutton

308

>Open selected report</guibutton

309

> button. Either of the following dialogs will be presented. </para>

310

<para>

311

312

<title

313

>The report you selected is already marked as a duplicate of bug...</title>

314

315

316

317

</imageobject>

318

</mediaobject>

319

</example>

320

</para>

321

<para>

322

323

<title

324

>Showing the duplicate bug report you selected</title>

325

326

327

328

</imageobject>

329

</mediaobject>

330

</example>

331

</para>

332

</step>

333

<step>

334

<para

335

>If the bug appears to be a duplicate, <mousebutton

336

>click</mousebutton

337

> the <guibutton

338

>Add as a possible duplicate</guibutton

339

> button. This will file the bug report and inform the developers that it may be a duplicate. This is recommended, except in cases with experienced users where it is clearly not a duplicate. <mousebutton

340

>Clicking</mousebutton

341

> the <guibutton

342

>Attach to this report (Advanced)</guibutton

343

> will attach the crash information to the report. </para>

344

<para

345

>If the bug is not a duplicate, simply <mousebutton

346

>click</mousebutton

347

> the <guibutton

348

>Next</guibutton

349

> in the dialog showing the possible duplicates. A dialog will appear with <guibutton

350

>Let me check more reports</guibutton

351

>. To prevent checking for more reports and continue to file the report, <mousebutton

352

>click</mousebutton

353

> the <guibutton

354

>There are no real duplicates</guibutton

355

> button. A dialog will appear to enter additional information concerning the report. </para>

356

<para>

357

358

<title

359

>Details of the Bug Report</title>

360

361

362

363

</imageobject>

364

</mediaobject>

365

</example>

366

</para>

367

</step>

368

<step>

369

<para

370

>Once the details of the bug report are complete, <mousebutton

371

>click</mousebutton

372

> the <guibutton

373

>Next</guibutton

374

> button. The following dialog will be presented. </para>

375

<para>

376

377

<title

378

>Preview Report</title>

379

380

381

382

</imageobject>

383

</mediaobject>

384

</example>

385

</para>

386

</step>

387

<step>

388

<para

389

>If the information looks correct, <mousebutton

390

>click</mousebutton

391

> the <guibutton

392

>Next</guibutton

393

> button. The following dialog will be presented. </para>

394

<para>

395

396

<title

397

>Send Crash Report</title>

398

399

400

401

</imageobject>

402

</mediaobject>

403

</example>

404

</para>

405

</step>

406

</procedure>

407

<para

408

><emphasis role="bold"

409

>Congratulations on a successful bug report!</emphasis

410

> Identifying and reporting bugs are essential to improving &kubuntu; and KDE. Some emails may be sent to the registered address to update progress or to allow developers to get additional information about the bug. </para>

411

</sect2>

412

413

<title

414

>Launchpad</title>

415

<para

416

>When an application that is not KDE crashes in &kubuntu;, a pop-up notification will appear from <application

417

>Apport</application

418

> that is similar to the following image. </para>

419

<para>

420

<example

421

><title

422

>Apport Crash Pop-pup Notification</title>

423

424

425

426

</imageobject>

427

</mediaobject>

428

</example>

429

</para>

430

<note

431

><title

432

>Crash information may be different</title>

433

<para

434

>The following screen shots were created by crashing the application <application

435

>VLC</application

436

> deliberately. Crash dialogs associated with other applications will be different. In an actual bug situation, the application name, <application

437

>VLC</application

438

>, will be replaced by the name of the application that actually crashed. </para>

439

</note>

440

<para

441

>To complete the bug reporting process, follow the procedure below. </para>

442

<procedure

443

><title

444

>Filing the bug report after a crash</title>

445

<step>

446

<para

447

><mousebutton

448

>Click</mousebutton

449

> the <guibutton

450

>Details</guibutton

451

> buttons on the <application

452

>System Notification Helper</application

453

>. The following dialog will be presented. </para>

454

<para>

455

456

<title

457

>Sorry, the program "vlc" closed unexpectedly.</title>

458

459

460

461

</imageobject>

462

</mediaobject>

463

</example>

464

</para>

465

</step>

466

<step>

467

<para

468

><mousebutton

469

>Click</mousebutton

470

> the <guibutton

471

>Report Problem...</guibutton

472

> button. The <guilabel

473

>Collecting Problem Information</guilabel

474

> progress dialog will be presented. </para>

475

<para>

476

<example

477

><title

478

>Prikupljanje Informacija o Problemu</title>

479

480

481

<imagedata fileref="help:/images/C/apport-dialog-collecting-info.png"

482

format="PNG"/>

483

</imageobject>

484

</mediaobject>

485

</example>

486

</para>

487

</step>

488

<step>

489

<para

490

>After all of the information concerning the crash is collected, a dialog will be presented that displays the details of the report, and the report is sent to the developers. <mousebutton

491

>Click</mousebutton

492

> the <guibutton

493

>Details...</guibutton

494

> button to view details of the report. The following dialog will be presented. </para>

495

<para>

496

<example

497

><title

498

>Send problem report to the developers? (Details)</title>

499

500

501

502

</imageobject>

503

</mediaobject>

504

</example>

505

</para>

506

</step>

507

<step>

508

<para

509

><mousebutton

510

>Click</mousebutton

511

> the <guibutton

512

>Send</guibutton

513

> button to send the report to the developers. In this case, it will send the report to Launchpad. The following progress dialog will be presented. </para>

514

<para>

515

<example

516

><title

517

>Šaljem informaciju o problemu</title>

518

519

520

521

</imageobject>

522

</mediaobject>

523

</example>

524

</para>

525

</step>

526

<step>

527

<para

528

>After the progress dialog completes, the default web browser will open to Launchpad presenting either the login page or the beginning of the online version of the bug reporting process. After logging in (if necessary) the following page will be presented. </para>

529

<para>

530

<example

531

><title

532

>Please wait while bug data is processed...</title>

533

534

535

536

</imageobject>

537

</mediaobject>

538

</example>

539

</para>

540

</step>

541

<step>

542

<para

543

>When Launchpad is finished processing the bug data, the following page will be presented. </para>

544

<para>

545

<example

546

><title

547

>Extra debug information will be added...</title>

548

549

550

551

</imageobject>

552

</mediaobject>

553

</example>

554

</para>

555

</step>

556

<step>

557

<para

558

><mousebutton

559

>Click</mousebutton

560

> the <guibutton

561

>Next</guibutton

562

> button. The following page will be presented. </para>

563

<para>

564

<example

565

><title

566

>Više informacija</title>

567

568

569

570

</imageobject>

571

</mediaobject>

572

</example>

573

</para>

574

</step>

575

<step>

576

<para

577

>Any extra information can be filled in about the bug report such as what was being done when it crashed or the online file locations that may have caused the crash. The following is a brief description filed with the report in this procedure. </para>

578

<para>

579

<example

580

><title

581

>Daljnje informacije (Dovršeno)</title>

582

583

584

585

</imageobject>

586

</mediaobject>

587

</example>

588

</para>

589

</step>

590

<step>

591

<para

592

><mousebutton

593

>Click</mousebutton

594

> the <guibutton

595

>Submit Bug Report</guibutton

596

> button on the bottom of the page. The following page will be presented. </para>

597

<para>

598

<example

599

><title

600

>Hvala na izvještaju o grešci</title>

601

602

603

604

</imageobject>

605

</mediaobject>

606

</example>

607

</para>

608

</step>

609

</procedure>

610

<para

611

><emphasis role="bold"

612

>Congratulations on making a successful crash report!</emphasis

613

>Identifying and reporting bugs are essential to improving &kubuntu;. Some emails may be sent to the registered address to update progress or to allow developers to get additional information about the bug. </para>

614

</sect2>

615

</sect1>

616

617

618

<title

619

>Filing a Non-Crash or Regression Report</title>

620

<para

621

>If an application has regressed in functionality, a bug report should be filed on that application. A regress occurs when a function worked in a previous release but in the latest release, it is not working. In most cases, this type of report will be filed by those who have more experience and may be testing beta quality software. However there are situations where a user needs to report an issue with an application that isn't working right, but isn't crashing. The following procedures will help. </para>

622

623

<title

624

>KDE</title>

625

<para

626

>Filing non-crash related bug reports for KDE applications are done with a web browser using <ulink url="https://bugs.kde.org/"

627

></ulink

628

>. </para>

629

<note

630

><title

631

>Register first</title>

632

<para

633

>To report a bug, one must register for an account on the bug tracker. KDE's bug tracker is located at <ulink url="https://bugs.kde.org/"

634

></ulink

635

>. </para>

636

</note>

637

<procedure

638

><title

639

>Filing a bug report without a crash</title>

640

<step>

641

<para

642

>In a web browser, go to <ulink url="https://bugs.kde.org/"

643

></ulink

644

> and either create a new account or login. Once logged in, the following page will be presented. </para>

645

<para>

646

<example

647

><title

648

>Welcome to the KDE Bug Tracking System</title>

649

650

651

652

</imageobject>

653

</mediaobject>

654

</example>

655

</para>

656

</step>

657

<step>

658

<para

659

><mousebutton

660

>Click</mousebutton

661

> the <guilabel

662

>Report New Wish or Bug</guilabel

663

> link in the top-right-hand corner of the page to start the process of filing the bug report. The following page will be presented. </para>

664

<para>

665

<example

666

><title

667

>Welcome to the KDE Bug Report Wizard!</title>

668

669

670

671

</imageobject>

672

</mediaobject>

673

</example>

674

</para>

675

</step>

676

<step>

677

<para

678

><mousebutton

679

>Click</mousebutton

680

> the <guibutton

681

>Continue</guibutton

682

> button. The following page will be presented. </para>

683

<para>

684

<example

685

><title

686

>Software Configuration</title>

687

688

689

690

</imageobject>

691

</mediaobject>

692

</example>

693

</para>

694

</step>

695

<step>

696

<para

697

>Select the proper <guilabel

698

>KDE Version</guilabel

699

> (required) and the <guilabel

700

>Distribution Method</guilabel

701

> (Should be <guilabel

702

>Ubuntu Packages</guilabel

703

>) from the drop-down menus. <mousebutton

704

>Click</mousebutton

705

> the <guibutton

706

>Continue</guibutton

707

> button when finished with the selections. The following page will be presented. </para>

708

<para>

709

<example

710

><title

711

>Izbor programa</title>

712

713

714

715

</imageobject>

716

</mediaobject>

717

</example>

718

</para>

719

</step>

720

<step>

721

<para

722

>If the application being reported is in the <guilabel

723

>Application</guilabel

724

> list, select it and press the <guibutton

725

>Continue</guibutton

726

> button. If the application is not in the list, skip to the next step. </para>

727

</step>

728

<step>

729

<para

730

>Under the <guilabel

731

>Find</guilabel

732

> section under the <guilabel

733

>Application</guilabel

734

> list, fill in the <guilabel

735

>Keyword Search</guilabel

736

> text box with the application being reported. It should look similar to the following image. </para>

737

<para>

738

<example

739

><title

740

>Application Selection (Search for application)</title>

741

742

743

744

</imageobject>

745

</mediaobject>

746

</example>

747

</para>

748

<para

749

>If the application is located, a page will be displayed similar to the previous one with the application highlighted. </para>

750

</step>

751

<step>

752

<para

753

><mousebutton

754

>Click</mousebutton

755

> the <guibutton

756

>Continue</guibutton

757

> button. The following page will be presented. </para>

758

<para>

759

<example

760

><title

761

>Opšte informacije</title>

762

763

764

765

</imageobject>

766

</mediaobject>

767

</example>

768

</para>

769

</step>

770

<step>

771

<para

772

>In the <guilabel

773

>Summary</guilabel

774

> text box, enter the summary with information similar to the example under the text box. Select <guilabel

775

>Linux</guilabel

776

> in the <guilabel

777

>Operating System</guilabel

778

> drop-down menu. When completed, <mousebutton

779

>Click</mousebutton

780

> the <guibutton

781

>Continue</guibutton

782

> button. The following page will be presented. </para>

783

<para>

784

<example

785

><title

786

>Check for Duplicate Bug Reports</title>

787

788

789

790

</imageobject>

791

</mediaobject>

792

</example>

793

</para>

794

</step>

795

<step>

796

<para

797

>If a duplicate report is found, click on that report ID to view the report. If it is a duplicate and more information is needed, then simply enter text in the large text box confirming it. If more information is not needed, nothing need be entered. If no duplicate reports are found, <mousebutton

798

>Click</mousebutton

799

> the <guibutton

800

>Continue</guibutton

801

> button. The following page will be presented. </para>

802

<para>

803

<example

804

><title

805

>Bug Entry Form</title>

806

807

808

809

</imageobject>

810

</mediaobject>

811

</example>

812

</para>

813

</step>

814

<step>

815

<para

816

>The <guilabel

817

>Severity</guilabel

818

> (required) drop-down menu should display the <guilabel

819

>Bug - Bug report (no crashes)</guilabel

820

> option. In the <guilabel

821

>Long Description in English</guilabel

822

> (required) text box, enter all information pertaining to the bug report. When completed, <mousebutton

823

>Click</mousebutton

824

> the <guibutton

825

>Continue</guibutton

826

> button. The following page will be presented. </para>

827

<para>

828

<example

829

><title

830

>Greška prijavljena</title>

831

832

833

834

</imageobject>

835

</mediaobject>

836

</example>

837

</para>

838

</step>

839

</procedure>

840

<para

841

><emphasis role="bold"

842

>Congratulations on making a successful non-crash related bug report!</emphasis

843

844

</sect2>

845

846

<title

847

>Launchpad</title>

848

<para

849

>Filing non-crash related bug reports in non-KDE applications can be done either by going to <ulink url="https://bugs.launchpad.net/ubuntu/+filebug"

850

></ulink

851

> in a web browser or by using the <application

852

>Apport</application

853

> bug reporting application. The following procedure will demonstrate the use of <application

854

>Apport</application

855

> as this is the recommended way of filing Ubuntu or non-KDE related bug reports. </para>

856

<procedure

857

><title

858

>Filing a bug report without a crash</title>

859

<step>

860

<para

861

>Open <application

862

>KRunner</application

863

>, the KDE run command interface, by pressing <keycombo

864

><keycap

865

>Alt</keycap

866

><keycap

867

>F2</keycap

868

></keycombo

869

>. </para>

870

<para>

871

<example

872

><title

873

>KRunner</title>

874

875

876

877

</imageobject>

878

</mediaobject>

879

</example>

880

</para>

881

</step>

882

<step>

883

<para

884

>In the <application

885

>KRunner</application

886

> dialog, enter <userinput

887

>apport-bug -p PROGRAM_NAME</userinput

888

>. Replace <emphasis

889

>PROGRAM_NAME</emphasis

890

> with the name of the program the bug report is for. Press <keycap

891

>Enter</keycap

892

> when complete. The following dialog will be presented. </para>

893

<para>

894

<example

895

><title

896

>Prikupljanje Informacija o Problemu</title>

897

898

899

900

</imageobject>

901

</mediaobject>

902

</example>

903

</para>

904

</step>

905

<step>

906

<para

907

>When the collection of information has been completed, the following dialog will be presented. </para>

908

<para>

909

<example

910

><title

911

>Želite li da pošaljete izvještaj autorima?</title>

912

913

914

915

</imageobject>

916

</mediaobject>

917

</example>

918

</para>

919

</step>

920

<step>

921

<para

922

><mousebutton

923

>Click</mousebutton

924

> the <guibutton

925

>Details...</guibutton

926

> button to see details of the report to be followed. The following dialog will be presented. </para>

927

<para>

928

<example

929

><title

930

>Detalji izvještaja</title>

931

932

933

934

</imageobject>

935

</mediaobject>

936

</example>

937

</para>

938

</step>

939

<step>

940

<para

941

><mousebutton

942

>Click</mousebutton

943

> the <guibutton

944

>Send</guibutton

945

> button to send the report to the developers. The following progress dialog will be presented. </para>

946

<para>

947

<example

948

><title

949

>Šaljem Informaciju o Problemu</title>

950

951

952

953

</imageobject>

954

</mediaobject>

955

</example>

956

</para>

957

</step>

958

<step>

959

<para

960

>After the information has been uploaded, the web browser will open and display a page similar to the following. </para>

961

<para>

962

<example

963

><title

964

>Please wait while bug data is processed.</title>

965

966

967

968

</imageobject>

969

</mediaobject>

970

</example>

971

</para>

972

<para

973

>After the bug data is processed, the following page will be presented. </para>

974

<para>

975

<example

976

><title

977

>Report a bug... (Summary)</title>

978

979

980

981

</imageobject>

982

</mediaobject>

983

</example>

984

</para>

985

</step>

986

<step>

987

<para

988

>Enter text in the <guilabel

989

>Summary</guilabel

990

> text box that describes the bug with a few words. When finished, <mousebutton

991

>Click</mousebutton

992

> the <guibutton

993

>Next</guibutton

994

> button. The following page will be presented. </para>

995

<para>

996

<example

997

><title

998

>Report a bug... (Further information)</title>

999

1000

1001

1002

</imageobject>

1003

</mediaobject>

1004

</example>

1005

</para>

1006

</step>

1007

<step>

1008

<para

1009

>Enter text in the <guilabel

1010

>Further information</guilabel

1011

> text box describing the bug in detail. When complete, <mousebutton

1012

>Click</mousebutton

1013

> the <guibutton

1014

>Submit Bug Report</guibutton

1015

> button. The following page will be presented. </para>

1016

<para>

1017

<example

1018

><title

1019

>Hvala na izvještaju o grešci</title>

1020

1021

1022

1023

</imageobject>

1024

</mediaobject>

1025

</example>

1026

</para>

1027

</step>

1028

</procedure>

1029

<para

1030

><emphasis role="bold"

1031

>Congratulations on making a successful non-crash related bug report!</emphasis

1032

> Identifying and reporting bugs are essential to improving &kubuntu;. Some emails may be sent to the registered address to update progress or to allow developers to get additional information about the bug. </para>

1033

</sect2>

1034

</sect1>

1035

1036

1037

<title

1038

>Popunjavanje zahtjeva za opcijom ili liste želja</title>

1039

<para

1040

>The easiest way to request a new feature in either an application or the operating system is to file a bug, otherwise known as a wishlist report. </para>

1041

1042

<title

1043

>KDE</title>

1044

<para

1045

>Filing a feature request report in KDE is exactly the same as filing a <link linkend="filing-non-crash-kde"

1046

>non-crash KDE bug report</link

1047

>. </para>

1048

</sect2>

1049

1050

<title

1051

>Launchpad</title>

1052

<para

1053

>Filing a wishlist report for &kubuntu; is exactly the same as filing a <link linkend="filing-non-crash-lp"

1054

>non-crash Launchpad bug report</link

1055

>. </para>

1056

</sect2>

1057

</sect1>

1058

1059

</article>

1060

<!--

1061

Local Variables:

1062

mode: xml

1063

sgml-minimize-attributes:nil

1064

sgml-general-insert-case:lower

1065

sgml-indent-step:0

1066

sgml-indent-data:nil

1067

End:

1068

1069

vim: tabstop=2:shiftwidth=2:expandtab:indentexpr=:tw=80:

1070

kate: space-indent on; indent-width 2; tab-width 2; indent-mode none;

1071

-->

Older »