~mistrynitesh/kubuntu-docs/fixes-two-bugs : revision 156

7

%kde-menus-C;

8

<!ENTITY language "en">

9

]>

10

10

11

12

<title>Bug Reports</title>

13

&legalnotice;

14

15

<para>

16

This document will provide you with step-by-step procedures in filing bug

17

reports for the &kubuntu; project.

16

This document provides step-by-step procedures for filing &kubuntu; bug reports.

18

17

</para>

19

18

</abstract>

20

19

</articleinfo>

22

21

23

22

<title>Types of Bug Reports</title>

24

23

<para>

25

There are typically three types of bug reports which are

26

<emphasis>crash</emphasis>, <emphasis>non-crash</emphasis>, and

27

<emphasis>feature request</emphasis>.

24

Generally, there are three types of bug reports: <emphasis>crash</emphasis>,

25

<emphasis>non-crash</emphasis>, and <emphasis>feature request</emphasis>.

28

26

</para>

29

27

<variablelist><title>Overview of bug types</title>

30

28

<varlistentry><term>Crash</term>

31

29

32

30

<para>

33

Pertains to an application or a system crash or failure. In this case, most of

34

the time, a crash dialog will be presented in which you can turn into a bug

35

report.

31

An application or system crash or failure. Most of the time, a crash dialog will

32

be presented that can be turned into a bug report.

36

33

</para>

37

34

</listitem>

38

35

</varlistentry>

39

36

<varlistentry><term>Non-crash</term>

40

37

41

38

<para>

42

Pertains to a bug or a regression that doesn't cause the application to crash,

43

but causes the application to not function as it should.

39

A bug or regression that doesn't cause the application to crash, but does cause

40

the application to stop functioning properly.

44

41

</para>

45

42

</listitem>

46

43

</varlistentry>

47

44

<varlistentry><term>Feature request</term>

48

45

49

46

<para>

50

Also known as a wish list item, this type of report is filed when you would like

51

to see a function added to an application or something changed in the

52

application that isn't a regression or a crash.

47

Also known as a wish list item, this type of report is filed to add a function

48

to an application, or to change something in the application that isn't due to a

49

regression or a crash.

53

50

</para>

54

51

</listitem>

55

52

</varlistentry>

63

60

64

61

<para>

65

62

KDE uses Bugzilla, a "Defect Tracking System". Bugzilla is one of the

66

most popular tools used in the open source development community and is used by

67

many projects.

63

most popular tools used in the open source development community.

68

64

</para>

69

65

<note><title>Register first</title>

70

66

<para>

71

Prior to reporting a bug, you must first register an account on KDE's Bugzilla

67

To report a bug, a person must be registered for an account on KDE's Bugzilla

72

68

at <ulink url="https://bugs.kde.org/createaccount.cgi"/>. A valid email address

73

69

is required for registration.

74

70

</para>

75

71

</note>

76

72

77

73

<para>

78

Only bugs related to KDE get filed here. If an application you are using is not

79

part of KDE, then you will need to file the report in Launchpad instead. Please

80

see the next section concerning Launchpad if you need to file a report there.

74

This system is only for bugs related to KDE. If the application is not part of

75

KDE, then the report should be filed in Launchpad instead. Please see the next

76

section, which covers filing reports concerning Launchpad.

81

77

</para>

82

78

</note>

83

79

</sect2>

87

83

<para>

88

84

Launchpad is an open source suite of tools that help people and teams to work

89

85

together on software projects. Launchpad is used by the Ubuntu and &kubuntu;

90

Project was well as various other open source projects.

86

Projects, as well as various other open source projects.

91

87

</para>

92

88

<note><title>Register first</title>

93

89

<para>

94

Prior to reporting a bug, you must first register an account on Launchpad at

90

To report a bug, a person must be registered for an account on Launchpad at

95

91

<ulink url="https://launchpad.net/+login"/>. A valid email address is required

96

92

for registration.

97

93

</para>

98

94

</note>

99

<note><title>File any bug in &kubuntu; here</title>

95

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

100

96

<para>

101

97

Launchpad can be used to file a bug report for any application available in the

102

Ubuntu application repositories. If the application you are filing a report

103

against is a KDE application, it is preferred that you use the KDE system for

104

filing.

98

Ubuntu or &kubuntu; repositories. If the report is for a KDE application, the

99

KDE Bug Tracking system (above) is preferred.

105

100

</para>

106

101

</note>

107

102

</sect2>

111

106

<title>Filing a Crash Report</title>

112

107

<para>

113

108

When an application crashes in &kubuntu;, the appropriate crash dialog will

114

appear usually allowing you to easily file a bug report from the dialog. If the

115

application is a KDE application, then the KDE crash dialog will appear allowing

116

you to report the bug, if it is not a KDE application, then the Ubuntu crash

117

dialog will appear, which will direct you to filing a bug on Launchpad.

109

appear. It is usually easy to file a bug report from the dialog. With a KDE

110

application, the KDE crash dialog will appear along with instructions

111

for reporting the bug. Otherwise, the Ubuntu crash dialog will appear with

112

instructions for filing a bug on Launchpad.

118

113

</para>

119

114

120

115

121

116

<para>

122

When an application crashes in KDE, you will be presented with a crash dialog

123

similar to the following images. Note that the first image is showing the

124

<guilabel>General</guilabel> tab which provides a brief overview of the crash to

125

the user. The second image is showing the <guilabel>Developer

126

Information</guilabel> tab which provides a trace of the crash that is useful to

127

developers.

117

When an application crashes in KDE, a crash dialog will be presented that is

118

similar to the following images. The first image shows the

119

<guilabel>General</guilabel> tab which provides an overview of the crash. The

120

second image shows the <guilabel>Developer Information</guilabel> tab which

121

provides trace information that is useful to developers.

128

122

</para>

129

123

<para>

130

124

147

141

</example>

148

142

</para>

149

143

<para>

150

From the crash dialog, if the trace is deemed valuable, filing a bug report is

151

easy. If the trace is not deemed valuable, then filing a bug report via the

152

wizard will not be possible, and would have to be done manually at <ulink

153

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

144

If the trace information is deemed valuable, filing a bug report is

145

easy with the crash dialog wizard. If the trace is not deemed valuable, then it

146

is not possible to file a bug report with the wizard. The bug report can still

147

be filed manually at <ulink url="https://bugs.kde.org/"/>.

154

148

</para>

155

149

<para>

156

150

To complete the bug reporting process, follow the procedure below.

159

153

<step>

160

154

<para>

161

155

<mousebutton>Click</mousebutton> the <guibutton>Report Bug</guibutton> button.

162

You will be presented with the following dialog.

156

The following dialog will appear.

163

157

</para>

164

158

<para>

165

159

174

168

</step>

175

169

<step>

176

170

<para>

177

<mousebutton>Click</mousebutton> the <guibutton>Next</guibutton> button. You

178

will be presented with the following dialog.

171

<mousebutton>Click</mousebutton> the <guibutton>Next</guibutton> button. The

172

following dialog will appear.

179

173

</para>

180

174

<para>

181

175

190

184

</step>

191

185

<step>

192

186

<para>

193

Select the options that are applicable to your case. The drop-down box under the

194

question, "<guilabel>Does the application crash again if you repeat the

195

same situation?</guilabel>" has the following options.

187

Select the applicable options. The drop-down box under the question,

188

"<guilabel>Does the application crash again if you repeat the

189

same situation?</guilabel>" has several options.

196

190

</para>

197

191

<para>

198

192

213

207

</step>

214

208

<step>

215

209

<para>

216

Depending on the information available in your crash report, you will be

217

presented with either one of the two following dialogs. The first is a dialog

218

letting you know there is not enough information to file a good report, and the

219

second is a dialog letting you know the information is good and you can continue

220

with the report filing.

210

Depending on the information available in the crash report, either of two

211

dialogs will appear. One is a dialog that indicates that there is not enough

212

information to file a good report. The other is a dialog indicating that the

213

information is useful, and that it would be helpful to continue with filing the

214

report.

221

215

</para>

222

216

<para>

223

217

241

235

</para>

242

236

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

243

237

<para>

244

You may need to install the proper debug packages in order to get a good trace.

245

Such packages include <filename>kdebase-dbg</filename>,

238

It may be necessary to install the proper debug packages in order to get a good

239

trace. Such packages include <filename>kdebase-dbg</filename>,

246

240

<filename>kdebase-workspace-dbg</filename>,

247

241

<filename>kdebase-runtime-dbg</filename>.

248

242

</para>

250

244

</step>

251

245

<step>

252

246

<para>

253

If there was enough information provided to continue filing a bug report using

254

the assistant, you will be presented with a dialog that allows you to login to

255

KDE's Bugzilla.

247

If enough information was provided to continue filing a bug report using

248

the assistant, a dialog will appear to allow logging in to KDE's Bugzilla.

256

249

</para>

257

250

<para>

258

251

266

259

</para>

267

260

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

268

261

<para>

269

You need to use the e-mail address in which you used to register with KDE's

270

Bugzilla.

262

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

271

263

</para>

272

264

</note>

273

265

</step>

274

266

<step>

275

267

<para>

276

After entering your username (e-mail address) and password to login,

268

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

277

269

<mousebutton>click</mousebutton> the <guibutton>Login</guibutton> button. The

278

assistant will now check for duplicates and then you will be presented with the

279

following dialog.

270

assistant will check for duplicates and display the following dialog.

280

271

</para>

281

272

<para>

282

273

291

282

</step>

292

283

<step>

293

284

<para>

294

If you recognize a possible duplicate report, you can

295

<mousebutton>click</mousebutton> the report in the list and then

296

<mousebutton>click</mousebutton> the <guibutton>Open selected report</guibutton>

297

button. You will be presented with either of the following dialogs.

285

If there is a possible duplicate report, <mousebutton>click</mousebutton> the

286

report in the list and then <mousebutton>click</mousebutton> the <guibutton>Open

287

selected report</guibutton> button. Either of the following dialogs will be

288

presented.

298

289

</para>

299

290

<para>

300

291

319

310

</step>

320

311

<step>

321

312

<para>

322

If your bug is in fact a duplicate, you can <mousebutton>click</mousebutton> the

323

<guibutton>Add as a possible duplicate</guibutton> button. This will go through

324

and file the report letting the developers know it is in fact a possible

325

duplicate. You could also <mousebutton>click</mousebutton> the <guibutton>Attach

326

to this report (Advanced)</guibutton> which will attach your crash information

327

to the report. It is recommended, unless you know what you are doing here, to

328

select <guibutton>Add as a possible duplicate</guibutton>.

313

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

314

<guibutton>Add as a possible duplicate</guibutton> button. This will file the

315

bug report and inform the developers that it may be a duplicate. This is

316

recommended, except in cases with experienced users where it is clearly not a

317

duplicate. <mousebutton>Clicking</mousebutton> the <guibutton>Attach to this

318

report (Advanced)</guibutton> will attach the crash information to the report.

329

319

</para>

330

320

<para>

331

If your bug is not a duplicate, you can simply <mousebutton>click</mousebutton>

321

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

332

322

the <guibutton>Next</guibutton> in the dialog showing the possible duplicates.

333

You will be presented with a dialog asking to <guibutton>Let me check more

334

reports</guibutton> or to prevent checking for more reports and continuing on to

335

file your report, you can <mousebutton>click</mousebutton> the <guibutton>There

336

are no real duplicates</guibutton> button. You will be presented with the

337

following dialog in which you can fill out the information concerning your

338

report.

323

A dialog will appear with <guibutton>Let me check more reports</guibutton>. To

324

prevent checking for more reports and continue to file the report,

325

<mousebutton>click</mousebutton> the <guibutton>There

326

are no real duplicates</guibutton> button. A dialog will appear to enter

327

additional information concerning the report.

339

328

</para>

340

329

<para>

341

330

350

339

</step>

351

340

<step>

352

341

<para>

353

Once you have completed filling in the details of the bug report,

354

<mousebutton>click</mousebutton> the <guibutton>Next</guibutton> button. You

355

will be presented with the following dialog.

342

Once the details of the bug report are complete,

343

<mousebutton>click</mousebutton> the <guibutton>Next</guibutton> button. The

344

following dialog will be presented.

356

345

</para>

357

346

<para>

358

347

368

357

<step>

369

358

<para>

370

359

If the information looks correct, <mousebutton>click</mousebutton> the

371

<guibutton>Next</guibutton> button. You will be presented with the following

372

dialog.

360

<guibutton>Next</guibutton> button. The following dialog will be presented.

373

361

</para>

374

362

<para>

375

363

384

372

</step>

385

373

</procedure>

386

374

<para>

387

<emphasis role="bold">Congratulations!</emphasis> You just completed a

388

successful crash report. Thank you for helping to make &kubuntu; and KDE better.

389

You will be notified via e-mail of any updates to the bug report. This allows

390

you to follow along with the progress as well as answer any further questions

391

the developers may have for you.

375

<emphasis role="bold">Congratulations on a successful bug report!</emphasis>

376

Identifying and reporting bugs are essential to improving &kubuntu; and KDE.

377

Some emails may be sent to the registered address to update progress or to

378

allow developers to get additional information about the bug.

392

379

</para>

393

380

</sect2>

394

381

395

382

<title>Launchpad</title>

396

383

<para>

397

When an application crashes in &kubuntu; that is not a KDE application, you will

398

be presented with a pop-up notification from <application>Apport</application>

399

similar to the following image.

384

When an application that is not KDE crashes in &kubuntu;, a pop-up notification

385

will appear from <application>Apport</application> that is similar to the

386

following image.

400

387

</para>

401

388

<para>

402

389

<example><title>Apport Crash Pop-pup Notification</title>

409

396

</para>

410

397

<note><title>Crash information may be different</title>

411

398

<para>

412

In order to create screen shots of the crash instance, I made the application

413

<application>VLC</application> crash purposely. Your dialogs that you are

414

presented may be different, and in the cases provided below, when you see the

415

application name, <application>VLC</application>, note that it will be the name

416

of the actual application that crashed for you.

399

The following screen shots were created by crashing the application

400

<application>VLC</application> deliberately. Crash dialogs associated with other

401

applications will be different. In an actual bug situation, the application

402

name, <application>VLC</application>, will be replaced by the name of the

403

application that actually crashed.

417

404

</para>

418

405

</note>

419

406

<para>

423

410

<step>

424

411

<para>

425

412

<mousebutton>Click</mousebutton> the <guibutton>Details</guibutton> buttons on

426

the <application>System Notification Helper</application>. You will be presented

427

with the following dialog.

413

the <application>System Notification Helper</application>. The following dialog

414

will be presented.

428

415

</para>

429

416

<para>

430

417

440

427

<step>

441

428

<para>

442

429

<mousebutton>Click</mousebutton> the <guibutton>Report Problem...</guibutton>

443

button. You will be presented with the following <guilabel>Collecting Problem

444

Information</guilabel> progress dialog.

430

button. The <guilabel>Collecting Problem Information</guilabel> progress dialog

431

will be presented.

445

432

</para>

446

433

<para>

447

434

<example><title>Collecting Problem Information</title>

456

443

</step>

457

444

<step>

458

445

<para>

459

After all of the information concerning the crash is collected, you will be

460

presented with a dialog that allows you to view the details of the report as

461

well as send the report to the developers. <mousebutton>Click</mousebutton> the

462

<guibutton>Details...</guibutton> button to view details of the report. You will

463

be presented with the following dialog.

446

After all of the information concerning the crash is collected, a dialog will

447

be presented that displays the details of the report, and the report is sent to

448

the developers. <mousebutton>Click</mousebutton> the

449

<guibutton>Details...</guibutton> button to view details of the report. The

450

following dialog will be presented.

464

451

</para>

465

452

<para>

466

453

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

474

461

</step>

475

462

<step>

476

463

<para>

477

<mousebutton>Click</mousebutton> the <guibutton>Send</guibutton> button to go

478

ahead and send the report to the developers, in this case it will send the

479

report to Launchpad. You will be presented with the following progress dialog.

464

<mousebutton>Click</mousebutton> the <guibutton>Send</guibutton> button to send

465

the report to the developers. In this case, it will send the report to

466

Launchpad. The following progress dialog will be presented.

480

467

</para>

481

468

<para>

482

469

<example><title>Uploading problem information</title>

490

477

</step>

491

478

<step>

492

479

<para>

493

After the progress dialog completes, your default web browser will open to

494

Launchpad either presenting you with the login page, or the beginning stage of

495

the online version of the bug reporting process. After logging in, if necessary,

496

you will be presented with the following page.

480

After the progress dialog completes, the default web browser will open to

481

Launchpad presenting either the login page or the beginning of the online

482

version of the bug reporting process. After logging in (if necessary) the

483

following page will be presented.

497

484

</para>

498

485

<para>

499

486

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

507

494

</step>

508

495

<step>

509

496

<para>

510

When Launchpad is finished processing the bug data, you will be presented with

511

the following page.

497

When Launchpad is finished processing the bug data, the following page will be

498

presented.

512

499

</para>

513

500

<para>

514

501

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

522

509

</step>

523

510

<step>

524

511

<para>

525

<mousebutton>Click</mousebutton> the <guibutton>Next</guibutton> button. You

526

will be presented with the following page.

512

<mousebutton>Click</mousebutton> the <guibutton>Next</guibutton> button. The

513

following page will be presented.

527

514

</para>

528

515

<para>

529

516

<example><title>Further information</title>

537

524

</step>

538

525

<step>

539

526

<para>

540

Fill in any extra information you can concerning the bug report such as what you

541

were doing when it crashed or the online file locations that may have caused the

542

crash. The following is just a very brief description filed with the report in

527

Any extra information can be filled in about the bug report such as what was

528

being done when it crashed or the online file locations that may have caused the

529

crash. The following is a brief description filed with the report in

543

530

this procedure.

544

531

</para>

545

532

<para>

555

542

<step>

556

543

<para>

557

544

<mousebutton>Click</mousebutton> the <guibutton>Submit Bug Report</guibutton>

558

button on the bottom of the page. You will be presented with the following page.

545

button on the bottom of the page. The following page will be presented.

559

546

</para>

560

547

<para>

561

548

<example><title>Thank you for your bug report</title>

569

556

</step>

570

557

</procedure>

571

558

<para>

572

<emphasis role="bold">Congratulations!</emphasis> You just completed a

573

successful crash report. Thank you for helping to make &kubuntu; better. You

574

will

575

be notified via e-mail of any updates to the bug report. This allows you to

576

follow along with the progress as well as answer any further questions the

577

developers may have for you.

559

<emphasis role="bold">Congratulations on making a successful crash

560

report!</emphasis>Identifying and reporting bugs are essential to improving

561

&kubuntu;. Some emails may be sent to the registered address to update progress

562

or to allow developers to get additional information about the bug.

578

563

</para>

579

564

</sect2>

580

565

</sect1>

582

567

583

568

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

584

569

<para>

585

When you feel an application has regressed in its functionality, you should

586

consider filing a bug report on that application. A regress occurs when a

587

previous release had a function that worked, but in the latest release it is not

588

working. In many cases this type of report will be filed by those who have more

589

experience and may be testing beta quality software, however there are cases

590

where a user needs to report an issue with an application that isn't crashing,

591

and the following procedures will help.

570

If an application has regressed in its functionality, a bug report should be

571

filed on that application. A regress occurs when a function worked in a previous

572

release but in the latest release, it is not working. In most cases, this type

573

of report will be filed by those who have more experience and may be testing

574

beta quality software. However there are situations where a user needs to report

575

an issue with an application that isn't working right, but isn't crashing. The

576

following procedures will help.

592

577

</para>

593

578

594

579

595

580

<para>

596

Filing non-crash related bug reports for KDE applications are done via your web

581

Filing non-crash related bug reports for KDE applications are done with a web

597

582

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

598

583

</para>

599

584

<note><title>Register first</title>

600

585

<para>

601

Prior to filing any sort of bug report with KDE, you should register an account

602

on the bug tracker if you haven't yet. KDE's bug tracker is located at <ulink

603

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

586

To report a bug, a person must be registered for an account on the bug tracker.

587

KDE's bug tracker is located at <ulink url="https://bugs.kde.org/"/>.

604

588

</para>

605

589

</note>

606

590

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

607

591

<step>

608

592

<para>

609

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

610

create a new account or login if you haven't already. Once logged in, you will

611

be presented with the following page.

593

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

594

create a new account or login. Once logged in, the following page will be

595

presented.

612

596

</para>

613

597

<para>

614

598

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

624

608

<para>

625

609

<mousebutton>Click</mousebutton> the <guilabel>Report New Wish or Bug</guilabel>

626

610

link in the top-right-hand corner of the page to start the process of filing the

627

bug report. You will be presented with the following page.

611

bug report. The following page will be presented.

628

612

</para>

629

613

<para>

630

614

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

638

622

</step>

639

623

<step>

640

624

<para>

641

<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. You

642

will be presented with the following page.

625

<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. The

626

following page will be presented.

643

627

</para>

644

628

<para>

645

629

<example><title>Software Configuration</title>

655

639

<para>

656

640

Select the proper <guilabel>KDE Version</guilabel> (required) and the

657

641

<guilabel>Distribution Method</guilabel> (Should be <guilabel>Ubuntu

658

Packages</guilabel>) from the drop down menus. <mousebutton>Click</mousebutton>

642

Packages</guilabel>) from the drop-down menus. <mousebutton>Click</mousebutton>

659

643

the <guibutton>Continue</guibutton> button when finished with the selections.

660

You will be presented with the following page.

644

The following page will be presented.

661

645

</para>

662

646

<para>

663

647

<example><title>Application Selection</title>

671

655

</step>

672

656

<step>

673

657

<para>

674

If the application you are filing the report on is in the

675

<guilabel>Application</guilabel> list, select it and press the

676

<guibutton>Continue</guibutton> button. If the application is not in the list,

677

skip to the next step.

658

If the application being reported is in the <guilabel>Application</guilabel>

659

list, select it and press the <guibutton>Continue</guibutton> button. If the

660

application is not in the list, skip to the next step.

678

661

</para>

679

662

</step>

680

663

<step>

681

664

<para>

682

665

Under the <guilabel>Find</guilabel> section under the

683

666

<guilabel>Application</guilabel> list, fill in the <guilabel>Keyword

684

Search</guilabel> text box with the application you would like to file the

685

report on. It should look similar to the following image.

667

Search</guilabel> text box with the application being reported. It should look

668

similar to the following image.

686

669

</para>

687

670

<para>

688

671

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

694

677

</example>

695

678

</para>

696

679

<para>

697

If the application is located, you will be returned to a page similar to the

698

previous with the application highlighted.

680

If the application is located, a page will be displayed similar to the previous

681

one with the application highlighted.

699

682

</para>

700

683

</step>

701

684

<step>

702

685

<para>

703

<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. You

704

will be presented with the following page.

686

<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. The

687

following page will be presented.

705

688

</para>

706

689

<para>

707

690

<example><title>General Information</title>

715

698

</step>

716

699

<step>

717

700

<para>

718

In the <guilabel>Summary</guilabel> text box, enter the summary in an

719

informational manner. An example is provided under the text box. Select

720

<guilabel>Linux</guilabel> in the <guilabel>Operating System</guilabel> drop

721

down menu. When completed, <mousebutton>Click</mousebutton> the

722

<guibutton>Continue</guibutton> button. You will be presented with the following

723

page.

701

In the <guilabel>Summary</guilabel> text box, enter the summary with

702

information similar to the example under the text box. Select

703

<guilabel>Linux</guilabel> in the <guilabel>Operating System</guilabel>

704

drop-down menu. When completed, <mousebutton>Click</mousebutton> the

705

<guibutton>Continue</guibutton> button. The following page will be presented.

724

706

</para>

725

707

<para>

726

708

<example><title>Check for Duplicate Bug Reports</title>

735

717

<step>

736

718

<para>

737

719

If a duplicate report is found, click on that report ID to view the report. If

738

it is a duplicate, then simply enter text in the large text box confirming it if

739

more information is needed. If it isn't needed, you do not need to enter

740

anything. If there are no duplicate reports found,

741

<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. You

742

will be presented with the following page.

720

it is a duplicate and more information is needed, then simply enter text in the

721

large text box confirming it. If more information is not needed, nothing need

722

be entered. If no duplicate reports are found, <mousebutton>Click</mousebutton>

723

the <guibutton>Continue</guibutton> button. The following page will be

724

presented.

743

725

</para>

744

726

<para>

745

727

<example><title>Bug Entry Form</title>

753

735

</step>

754

736

<step>

755

737

<para>

756

The <guilabel>Severity</guilabel> (required) drop down menu should display the

738

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

757

739

<guilabel>Bug - Bug report (no crashes)</guilabel> option. In the <guilabel>Long

758

Description in English</guilabel> (required) text box, enter in all information

740

Description in English</guilabel> (required) text box, enter all information

759

741

pertaining to the bug report. When completed, <mousebutton>Click</mousebutton>

760

the <guibutton>Continue</guibutton> button. You will be presented with the

761

following page.

742

the <guibutton>Continue</guibutton> button. The following page will be

743

presented.

762

744

</para>

763

745

<para>

764

746

<example><title>Bug Submitted</title>

772

754

</step>

773

755

</procedure>

774

756

<para>

775

<emphasis role="bold">Congratulations!</emphasis> You just completed a

776

successful non-crash related bug report. Thank you for helping to make &kubuntu;

777

and KDE better. You will be notified via e-mail of any updates to the bug

778

report. This allows you to follow along with the progress as well as answer any

779

further questions the developers may have for you.

757

<emphasis role="bold">Congratulations on making a successful non-crash related

758

bug report!</emphasis> Identifying and reporting bugs are essential to improving

759

&kubuntu; and KDE. Some emails may be sent to the registered address to update

760

progress or to allow developers to get additional information about the bug.

780

761

</para>

781

762

</sect2>

782

763

783

764

<title>Launchpad</title>

784

765

<para>

785

766

Filing non-crash related bug reports in non-KDE applications can be done either

786

by going to <ulink url="https://bugs.launchpad.net/ubuntu/+filebug"/> in your

787

web browser or by using the <application>Apport</application> bug reporting

788

application. The following procedure will display the use of

767

by going to <ulink url="https://bugs.launchpad.net/ubuntu/+filebug"/> in a web

768

browser or by using the <application>Apport</application> bug reporting

769

application. The following procedure will demonstrate the use of

789

770

<application>Apport</application> as this is the recommended way of filing

790

771

Ubuntu or non-KDE related bug reports.

791

772

</para>

809

790

<para>

810

791

In the <application>KRunner</application> dialog, enter <userinput>apport-bug -p

811

792

PROGRAM_NAME</userinput>. Replace <emphasis>PROGRAM_NAME</emphasis> with the

812

name of the program you are filing the bug report for. Press

813

<keycap>Enter</keycap> when complete. You will be presented with the following

814

dialog.

793

name of the program the bug report is for. Press <keycap>Enter</keycap> when

794

complete. The following dialog will be presented.

815

795

</para>

816

796

<para>

817

797

<example><title>Collecting Problem Information</title>

825

805

</step>

826

806

<step>

827

807

<para>

828

When the collection of information has been completed, you will be presented

829

with the following dialog.

808

When the collection of information has been completed, the following dialog

809

will be presented.

830

810

</para>

831

811

<para>

832

812

<example><title>Send problem report to the developers?</title>

841

821

<step>

842

822

<para>

843

823

<mousebutton>Click</mousebutton> the <guibutton>Details...</guibutton> button to

844

see details of the report to be followed. You will be presented with the

845

following dialog.

824

see details of the report to be followed. The following dialog will be

825

presented.

846

826

</para>

847

827

<para>

848

828

<example><title>Report Details</title>

857

837

<step>

858

838

<para>

859

839

<mousebutton>Click</mousebutton> the <guibutton>Send</guibutton> button to send

860

the report to the developers. You will be presented with the following progress

861

dialog.

840

the report to the developers. The following progress dialog will be presented.

862

841

</para>

863

842

<para>

864

843

<example><title>Uploading Problem Information</title>

872

851

</step>

873

852

<step>

874

853

<para>

875

After the information has been uploaded, your web browser will open and display

854

After the information has been uploaded, the web browser will open and display

876

855

a page similar to the following.

877

856

</para>

878

857

<para>

885

864

</example>

886

865

</para>

887

866

<para>

888

After the bug data is processed, you will be presented with the following page.

867

After the bug data is processed, the following page will be presented.

889

868

</para>

890

869

<para>

891

870

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

901

880

<para>

902

881

Enter text in the <guilabel>Summary</guilabel> text box that describes the bug

903

882

with a few words. When finished, <mousebutton>Click</mousebutton> the

904

<guibutton>Next</guibutton> button. You will be presented with the following

905

page.

883

<guibutton>Next</guibutton> button. The following page will be presented.

906

884

</para>

907

885

<para>

908

886

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

918

896

<para>

919

897

Enter text in the <guilabel>Further information</guilabel> text box describing

920

898

the bug in detail. When complete, <mousebutton>Click</mousebutton> the

921

<guibutton>Submit Bug Report</guibutton> button. You will be presented with the

922

following page.

899

<guibutton>Submit Bug Report</guibutton> button. The following page will be

900

presented.

923

901

</para>

924

902

<para>

925

903

<example><title>Thank you for your bug report</title>

933

911

</step>

934

912

</procedure>

935

913

<para>

936

<emphasis role="bold">Congratulations!</emphasis> You just completed a

937

successful non-crash related bug report. Thank you for helping to make &kubuntu;

938

better. You will be notified via e-mail of any updates to the bug report. This

939

allows you to follow along with the progress as well as answer any further

940

questions the developers may have for you.

914

<emphasis role="bold">Congratulations on making a successful non-crash related

915

bug report!</emphasis> Identifying and reporting bugs are essential to improving

916

&kubuntu;. Some emails may be sent to the registered address to update progress

917

or to allow developers to get additional information about the bug.

941

918

</para>

942

919

</sect2>

943

920

</sect1>